Skip to content

Does your fulfilment company need your WooCommerce API keys?

Most fulfilment connectors want a WooCommerce API key that reads your entire store, and here is why that is a privacy, security and GDPR problem you can avoid.

A worried shopkeeper hugs a ring of keys while a delivery company asks for them

Last month I set up a fulfilment connector for a small WooCommerce shop. The first screen asked for a REST API key with read and write access to the whole store. The second asked, as a fallback, for a Shop Manager login. I stopped there. The warehouse wanted to pack boxes, and in exchange I was about to hand them a master key to every order, every customer, every email and postal address the shop had ever stored.

That is the normal way these things work, and almost nobody blinks. I blinked.

What a WooCommerce API key actually gives away

A WooCommerce REST API key is not scoped to “the next order from Tuesday”. It is scoped to resources: orders, customers, products, coupons, reports. A read/write key with access to orders can list every order you have ever taken, with full billing and shipping details, line items, totals, notes, and the customer records behind them. A Shop Manager account is worse, because it can also log into wp-admin and poke around the rest of the site.

So when a fulfilment company asks for “just an API key”, what they are really asking for is a standing, long-lived credential that can pull your entire order history whenever it likes. Not the five orders they need to ship today. All of them. Forever, until you remember to revoke the key.

Why I think that is a problem

Privacy

Your customers gave you their data to buy a thing. They did not sign up to have a third-party logistics provider hold a live tap into the whole database. Most of them have no idea the warehouse can even see their name.

Attack surface

Every credential you hand out is one more place your customer list can leak from. The fulfilment company’s laptop, their staging server, the CSV someone exported “just to check something”, the integration middleware they use for forty other shops. You have now multiplied the number of systems that, if breached, breach you. And you control none of them.

Data minimisation

I am not a lawyer, but I can read. Article 5.1.c of the GDPR says personal data must be “adequate, relevant and limited to what is necessary” for the purpose. The purpose here is: put items in a box and ship them to an address. That needs the shipping address, the line items, maybe a phone number for the courier. It does not need read access to orders from three years ago, and it certainly does not need a Shop Manager account.

Handing over a full-store API key to do a job that needs five fields is, almost by definition, not “limited to what is necessary”. You can argue about the edges. You cannot really argue that the whole order history is minimal.

Push, not pull

This is the itch I started scratching with Wareferry (yes, “WAIR-ferry”, like a ferry that carries your parcels). It is a family of WooCommerce plugins, one per operator or warehouse, built around one stubborn idea: the warehouse never gets a key to your shop.

The usual model is pull. The warehouse holds your credentials and reaches into your store to fetch orders. Wareferry flips it. The model is push: your shop decides what to send, and sends only that, outward, to the warehouse. The operator never receives your WooCommerce API keys. No admin access. No Shop Manager seat. Nothing to revoke later because there was never a key in the first place.

Concretely:

  • Each order is pushed individually, when it is ready to ship, carrying the minimum fields the warehouse needs to pack and dispatch it.
  • The connection uses the shop’s own account with the warehouse. The warehouse authenticates you to them, not the other way round.
  • There is no credential sitting in the fulfilment company’s systems that can enumerate your customers. They see the orders you pushed, and that is the end of the list.
  • Your historical orders, your unrelated products, your draft and cancelled orders, your other customers: none of it ever leaves.

If you want the mechanics, I wrote them up in how it works. The short version is that data minimisation stops being a policy you promise and becomes something the architecture enforces, because the warehouse literally cannot ask for more than you pushed.

The honest caveats

Wareferry is in development. Nothing is for sale yet, there are no prices to quote, and I am not going to pretend it has been battle-tested across a thousand production stores, because it has not. When the free version lands it will be a real free version, the plugin does the job with no limits and no trialware nagging, not a crippled demo designed to push you onto a paywall.

And to be fair to the pull model: it is simpler to build, and if your warehouse already supports it, it works. I just don’t think “it works” is the same as “your customer list should live on someone else’s server”.

So, back to the question in the title. Does your fulfilment company need your WooCommerce API keys? To ship a box, no. They need an address and a list of items. Everything beyond that is convenience for them and risk for you. If that trade has ever made you uneasy, put your email on the waitlist and I’ll tell you when the first plugins are ready.