Skip to content

Amazon MCF for WooCommerce, done right

If you already hold stock in FBA, Amazon MCF can fulfil your WooCommerce orders from that same inventory, and Wareferry pushes each order out without ever sharing your store credentials.

A merchant at a laptop sends parcels from a fulfilment warehouse straight to customers' doors

If you sell on Amazon and you also run a WooCommerce store, you already own a warehouse you are paying for twice. Your stock sits in FBA. Amazon picks it, packs it, ships it, handles returns. And then your WooCommerce orders come in through a completely different door, and you are back to printing labels at the kitchen table (or paying a second fulfilment provider to hold inventory you already have in Amazon’s building).

Amazon has a service for exactly this. It is called Multi-Channel Fulfillment (MCF), and it lets you fulfil orders from any sales channel using your FBA inventory. Place a WooCommerce order, push it to MCF through the SP-API, and Amazon ships it from the same stock pool. No second warehouse. No double inventory. That is the promise, anyway.

The plumbing: Fulfillment Outbound over the SP-API

The technical bit is not exotic. Amazon exposes a Fulfillment Outbound section in its Selling Partner API (SP-API). You create a fulfilment order, you give it the shipping address and the SKUs, you poll for status, and you get back a tracking number when the parcel moves. A WooCommerce plugin can sit in the middle: new paid order comes in, it builds the MCF request, sends it, and writes the tracking back onto the order.

So why isn’t everyone doing it already? They are, sort of. The connectors exist. They are just not great. Never Settle’s plugin runs around 90 € a year and sits at roughly 3.1 stars. M2E’s offering is closer to 279 $ a year. I am not here to throw rocks (keeping a live SP-API integration working is genuinely hard, and Amazon changes the rules often), but the market is thin, pricey, and nobody seems delighted. That is usually a sign there is room to do it properly.

Where Wareferry fits

Wareferry (say it “WAIR-ferry”) is a family of WooCommerce plugins, one per fulfilment operator, built around a single idea: push. Your store is the source of truth. When an order is ready, Wareferry pushes it out to the operator and nothing flows the other way into your admin.

That matters more than it sounds. The usual integration model asks you to hand a third party an API key into your store, or worse, an admin account, so they can reach in and read your orders. I never liked that. With the push model, the operator (and Amazon) never receives your WooCommerce keys and never touches your admin. The plugin lives inside your WordPress, uses your Amazon account and your SP-API credentials, and talks outward only. You can read the longer version on how it works.

For the Amazon case specifically, that means: your FBA stock, your MCF contract, your SP-API app. Wareferry just does the boring, repetitive job of turning each WooCommerce order into a clean Fulfillment Outbound request and shipping it off.

What MCF can and can’t do

Be clear-eyed about the service before you build a business on it. MCF is good at the thing it does and silent about the things FBA never exposed:

  • It fulfils from your pooled FBA inventory, so you are not holding two piles of the same product.
  • It returns tracking, and it handles the carrier side for you.
  • It does not give you stock broken down by batch or lot, and it does not expose expiry dates. That is an FBA limitation, not a Wareferry one, and if you sell anything perishable or batch-tracked you need to know it going in.

None of that is a dealbreaker for most sellers. It is just the kind of detail that nobody mentions until an order goes wrong.

The honest status

Here is the part the marketing people would cut. The Amazon MCF plugin is early. What exists today is a scaffold and a written SP-API spec: the shape of the request, the status polling, the mapping from WooCommerce order to fulfilment order. What does not exist yet is a version I would let near your production store.

Two things are holding it there on purpose. First, credentials: deciding exactly how the plugin should store and rotate your SP-API tokens is a security decision, and I would rather get it right than ship it fast. Second, the name. Amazon has strict brand rules about what you may call a product that touches their platform, and I am not going to paint myself into a legal corner over a clever title. On top of that, SP-API registration (getting Amazon to approve the application at all) takes its own sweet time. So I am not going to promise you a verified, battle-tested production integration today, because I don’t have one.

What I can promise is the shape of the thing. When Wareferry for Amazon MCF ships, it ships as a genuinely free version: no seat limits, no trialware, no thirty-day countdown that turns your fulfilment off on day thirty-one. You can read where it is headed on the Wareferry for Amazon MCF page.

If you already have stock in FBA and a WooCommerce store, you are the exact person I am building this for. Nothing is on sale yet (there are no prices, and there won’t be a paywall on the core job), but I would like to tell you the day it is ready. Join the waitlist and I will. No warehouse required. You already have one.

Amazon, FBA and Multi-Channel Fulfillment are trademarks of Amazon.com, Inc. or its affiliates. Wareferry is not affiliated with, endorsed by, or sponsored by Amazon.