Amazon MCF Shopify Integration: Setup, Order Routing, and the 2026 Traps

What the Amazon MCF Shopify integration actually moves

MCF is not a sales channel and it is not a Shopify app that lists your products on Amazon. It is a fulfillment backend. The integration wires up exactly four data flows:

1. The app creates a Shopify location called Amazon Fulfillment (or Amazon Fulfillment – UK for the UK marketplace).
2. Amazon pushes fulfillable inventory for every mapped SKU into that location.
3. A buyer checks out, and Shopify order routing decides which location owns each line item.
4. Line items sitting at the Amazon Fulfillment location become an MCF fulfillment request at the ship speed you mapped, and Amazon writes the tracking number back into the Shopify order.

Everything outside those four flows stays yours, and that is where most of the operational surprises live.

There are also hard ceilings worth knowing before you model this for a high-AOV or kitted catalog: a single MCF order accepts up to 250 units and 100 unique SKUs. Larger orders have to be split and resubmitted. Partial fulfillment is supported, which sounds helpful and is the cause of the most common support ticket in this setup — see the routing note below.

Official app, third-party connector, or the MCF API

There are three ways to connect Shopify to MCF, and the deciding factor is almost never features. It is country coverage, catalog size, and whether Shopify or something else is your system of record.

The API path is underrated for anyone running more than one storefront. Once you have two Shopify stores, a marketplace or two, and a warehouse of your own, the question stops being how do I connect Shopify to MCF and becomes what decides where each order ships from. That decision does not belong inside a fulfillment app. If that is the shape of your problem, it is the same work as any other Amazon SP-API and multichannel order integration: one service that owns routing, and connectors that only execute.

A useful rule: start on the official app, because it costs nothing and proves the inventory and ship-speed assumptions. Move to the API when routing logic, not fulfillment, becomes the bottleneck.

The old Amazon MCF: US Fulfillment app is gone — what to do now

Amazon consolidated MCF and Buy with Prime into one Shopify app and deactivated the legacy Amazon MCF: US Fulfillment app on September 30, 2026. If you were on it, migration is no longer optional, and the sequence matters because both apps can create their own Shopify location.

1. Install and onboard the new app first. Do not uninstall the old one yet.
2. Move the catalog in bulk instead of remapping by hand: in the legacy app, open Manage product catalog, choose Update using CSV, and download the CSV with both Mapped and Unmapped selected. Upload that file on the same screen in the new app.
3. Fix order routing before you test. In Settings → Shipping and delivery → Order routing, use the ranked-locations rule and rank Amazon Fulfillment above Amazon MCF. Skip this and orders silently keep routing to the dead location.
4. Place test orders and confirm four things: SKU mapping, routing, ship-speed mapping, and that a fulfillment request shows as Accepted in Shopify with a matching order in Seller Central.
5. Only then uninstall the legacy app.

Amazon's MCF and Buy with Prime app user guide for Shopify carries the current version of these steps, including the per-country connect and disconnect flow if you run more than one marketplace.

One pre-check before you schedule the cutover: the new app ships Buy with Prime alongside MCF, and Buy with Prime carries payment requirements of its own. Confirm your gateway setup is eligible rather than discovering it mid-migration.

SKU mapping and ship-speed mapping, the two steps that decide everything

Make auto-mapping do the work

The app auto-maps a product when the Shopify SKU string matches the Amazon seller SKU exactly. Anything that does not match has to be mapped one at a time, and there is no bulk mapping tool in normal operation — the CSV import exists on the migration path, not as a general feature.

So the single highest-leverage thing you can do on a catalog of any size is normalize your Shopify SKUs to your Amazon seller SKUs before you install the app. An hour of find-and-replace in a product CSV beats a week of clicking through a mapping table. Watch the usual culprits: trailing whitespace, case differences, and the variant suffixes Shopify adds that Seller Central never had.

Bundles have two valid shapes. Either build the bundle in Shopify with any bundling app and map each component SKU, or create the bundle in Seller Central so it gets a single Amazon SKU and mirror that SKU in Shopify. The second is cleaner; the first is the only one that lets MCF fulfill part of a bundle.

Shipping rates are yours, ship speeds are the mapping

The app does not calculate shipping rates and does not add options at checkout. Customers only ever see rates you configured yourself. The setup is:

• Create a Shopify shipping profile for the Amazon Fulfillment location and set the rates you want to sell.
• In the app, set a default MCF speed, then map each of those Shopify rates to an Amazon ship speed.
• Amazon lists two domestic speeds: Standard at 3 business days and Expedited at 2 business days.

Be deliberate here, because this mapping is a margin decision disguised as a configuration screen. Every rate you point at Expedited raises the per-unit fulfillment fee on every order that picks it, including the free-shipping tier if you mapped it carelessly. Guides that still describe a three-tier Standard, Expedited and Priority lineup with a 3-to-5 day Standard are quoting a rate card Amazon has moved on from; check the current speeds rather than the blog that ranks for them.

How to make Shopify submit orders to MCF automatically

Installing the app does not make orders flow. Fulfillment requests still have to be triggered, and you have three options:

The Flow workflow is small: trigger on Order ready to fulfill, condition Location name equals Amazon Fulfillment, action Submit fulfillment request.

Build it in Flow rather than using blanket auto-fulfill, for one reason: MCF is fast and effectively unrecallable. Once the request is accepted, a fraudulent order, a pre-order that should not have shipped yet, or a wholesale order that needed an invoice first is already in a tote. Adding two or three extra conditions to that Flow — hold flagged-risk orders, hold a specific tag, hold pre-orders — costs ten minutes and is the difference between automation and an unmonitored outbound pipe.

The same caution applies to order routing. Because MCF supports partial fulfillment, an order containing one Amazon-stocked item and one item at your own warehouse will split: two parcels, two tracking numbers, one confused customer. Decide on purpose whether you want that split or whether routing should keep mixed orders whole at a single location.

The 2026 fee layers that decide whether MCF beats a 3PL

MCF pricing is not one number. It is a stack, and modelling only the base fulfillment fee is how merchants end up surprised in Q4.

Amazon's Multichannel Fulfillment service page is the source to check these against, because the surcharge and peak windows move more often than the rate card itself.

Two things in that table carry most of the decision. The first is units per order: MCF's per-unit cost falls sharply on multi-unit orders and is at its worst on single light units, which is exactly the profile a regional 3PL prices best. If your Shopify AOV is one small item, run the comparison before you commit; if your customers buy three at a time, MCF is hard to beat without signing a volume contract somewhere.

The second is reporting. MCF fees never appear in Shopify. They show up in Seller Central under Reports → Payments → All statements, where the per-order FBA/MCF fee sits in column O of the downloaded file. Until you pull that report into whatever you use for margin, every profit number in your Shopify dashboard is overstated by the cost of shipping. Building that reconciliation once, on day one, is worth more than any configuration tweak in this article.

When MCF orders stop flowing, check these in order

Most broken MCF setups fail at one of two joints: the SKU mapping, or the routing rule that decides which location owns a line item. Both are cheap to get right at setup and expensive to untangle once orders are flowing. If the shape of your problem is less which button and more which system should own fulfillment decisions across our stores and marketplaces, that is an architecture question — tell us what your stack looks like and we will tell you honestly whether an app covers it or not.