Most WooCommerce shops choose their 3PL first and their integration second. The warehouse wins on price per pick, location and storage fees, and then someone asks “and how do the orders get there?”. At that point the answer is whatever the warehouse happens to offer, and you find out what it doesn’t do the first week of December.
So here is the checklist I would go through before signing anything. It is the same list I have been using to design Wareferry, so yes, I’m biased. I’ll try to be fair anyway.
The checklist
- Push or pull, and who holds which keys. Does the shop send orders to the warehouse, or does the warehouse read them from the shop with your API key?
- What data leaves the shop. Only the order being shipped, or anything the key can reach?
- Tracking back in WooCommerce. In the order, in the customer’s email and in My Account.
- HPOS and the block checkout. Declared compatibility, not “should work”.
- Stock sync. How often, in which direction, and what happens on conflict.
- Lots and expiry. If your products have a shelf life.
- Several warehouses and routing. One country or many, and who decides where each order goes.
- Logs. Can you see what was sent and what came back, without exposing personal data?
- Cancellations. What happens when an order is cancelled after it was sent.
- A free version that really works. Or a trial dressed as one.
- Support. Who answers, and do they know WooCommerce.
Now the reasons behind each point.
Push, pull and the keys
This is the first question because it decides most of the others. In a pull model, you create a WooCommerce REST API key and hand it to the operator. Their system reaches into your shop and takes the orders. In a push model, your shop sends each order outward, using your own account with the warehouse, and the operator never receives credentials to your store.
Pull is easier for the operator. Push is easier on your conscience (and on your breach risk). If the integration asks for a key with read/write access to orders and customers, or worse, for a Shop Manager login, write that down in red.
What data leaves
Directly related. A warehouse needs a name, a shipping address, a phone if the carrier asks for one, and the order lines. Ask the vendor what else goes out. If the honest answer is “whatever the API returns”, you have your answer.
Tracking where the customer looks
The customer doesn’t log into your 3PL’s portal. They look at the shipping email and, if they are the organised type, at My Account. The tracking number and carrier must end up in both, automatically. Every “where is my order?” email you receive is, in part, an integration that stopped halfway.
HPOS and blocks
WooCommerce moved orders to their own tables (HPOS) and the cart and checkout to blocks. A plugin that still reads orders from wp_posts or hooks into the old shortcode checkout is living on borrowed time. Check that compatibility is declared, not assumed.
Stock, lots and warehouses
The warehouse is the source of truth for physical stock, so it has to flow back to the shop regularly. Once a day is too little if you sell fast; every minute is usually overkill. Ask how often and what the plugin does when the numbers disagree.
If you sell anything that expires, ask about lots and expiry dates explicitly. And if you have, or plan to have, stock in more than one warehouse (one in the US and one in the EU, say), ask how the integration decides which one ships each order. “Manually” is a valid answer for ten orders a week. Not for three hundred a day.
Logs and cancellations
Something will fail. A SKU that doesn’t exist on the warehouse side, an address the carrier rejects, a timeout. You need a log that shows what was sent and what the operator answered. Ideally masked, so it doesn’t become a second copy of your customer database.
And cancellations: the customer cancels ten minutes after paying, the order was already sent. Does the plugin tell the warehouse? Does it tell you when it’s too late? Ask. Then ask again.
Free, trialware and support
A free version should be able to do the basic job on its own, indefinitely. If it stops after fifty orders, or nags you on every admin screen, it’s a demo. Fine, but call it a demo. And support: you want someone who understands both the operator’s API and WooCommerce, because most problems live exactly in between.
How Wareferry answers the list
Since I said I’m biased, I’ll be explicit. Wareferry is a family of WooCommerce plugins, one per operator: Amazon MCF, ShipBob, Hive and several more. It is push: the operator never gets your WooCommerce keys or admin access, and it uses your own account with the warehouse (details in how it works). It supports HPOS and the cart and checkout blocks, and the request log is masked. The free version works for real, with no limits and no trialware. Pro adds automatic sending, hourly stock, lots and expiry, several warehouses per country and routing (see Free vs Pro).
And the honest part: it is in development. Nothing is for sale, there are no prices, and I won’t pretend it has a long production track record. Apply the checklist to it as well. That’s what it’s for.
If you want to hear when it’s ready, the waitlist is open. No spam, just a note when the first plugins can be installed.
