GUIDES
Multichannel inventory sync: Amazon, Walmart and Shopify without overselling
Multichannel inventory sync means keeping one available-to-sell number for each SKU and pushing it to every channel you sell on, fast enough that two channels never sell the same last unit. Getting it right takes the right stock model, a buffer on each channel, SKU mapping that includes bundles and a weekly reconciliation. This guide covers all of them, with the channel rules that make overselling expensive in 2026.
Key takeaways
- Decide which stock is shared and which is ring-fenced before you choose a tool. FBA and WFS stock sit in separate pools from your own warehouse stock.
- A buffer per channel, sized to the sync interval and sales speed, prevents most overselling. A worked formula is below.
- Overselling costs more than the lost sale. Walmart expects cancellations at 2% or below (Walmart, Jul 28, 2026); Amazon's target for pre-fulfillment cancellations is under 2.5%.
- Amazon Multi-Channel Fulfillment can fill Walmart and Shopify orders from FBA stock, but Walmart requires neutral packaging and Amazon Logistics blocked, and MCF fees rose in 2026.
- Reconcile weekly: channel quantities, 3PL available stock and your system of record should agree for every top SKU.
What is multichannel inventory sync?
Multichannel inventory sync is the process that keeps the quantity listed on Amazon, Walmart, Shopify and any other channel equal to the stock you can actually ship. One system holds the true number for each SKU, the "system of record", and every sale on any channel reduces it and updates the others.
The system of record can be your 3PL's warehouse system, an inventory app, an ERP or Shopify itself for smaller stores. What matters is that there is exactly one, and that everyone, including your 3PL, agrees which one it is.
Sync covers two directions. Stock flows out to channels as a listed quantity. Orders flow back in and reduce stock. Most overselling happens when the second direction is slow.
Why stores oversell
Stores oversell for five reasons, and a store that oversells regularly usually has more than one of them.
- 01Sync lag.
The system updates channels every 15 or 30 minutes, or hourly. During a busy hour, two channels can each sell the last few units before either update lands.
- 02Marketplace orders arriving late.
Sellers commonly describe marketplace orders reaching Shopify or the inventory app minutes after the sale, so Shopify keeps selling stock that has already gone.
- 03Separate pools treated as one.
FBA stock is in Amazon's network and WFS stock is in Walmart's. If your Shopify quantity includes units sitting in an Amazon fulfillment center, Shopify will sell units you cannot ship from your warehouse.
- 04Received is not the same as available.
Your 3PL may count stock as received days before it is put away and sellable. Push the received number and you list stock nobody can pick.
- 05Bundles and kits.
A three-pack sold on Amazon uses three single units. If the bundle is not mapped to its components, the singles stay listed on Walmart and Shopify at the old quantity.
1:19
Read the transcript Captions are on screen Characters are fictional. Voices are AI-generated.
Three stock models, and when each fits
How you split stock decides how hard sync is. There are three common models, and many brands run a mix of them by SKU.
| Model | How it works | Sync difficulty | Fits when |
|---|---|---|---|
| Shared pool, merchant-fulfilled | All channels sell from one warehouse (yours or a 3PL). One number, pushed everywhere | Highest: every sale on every channel must update every other channel quickly | Most orders are merchant-fulfilled and you want maximum availability per unit |
| Split pools: FBA, WFS and a merchant pool | Amazon sells from FBA, Walmart from WFS, Shopify from your 3PL. Each pool is its own number | Lower: each channel reads only its own pool; the work moves to replenishment planning | You use FBA and WFS and can afford stock in three places |
| FBA as the hub with Multi-Channel Fulfillment | Amazon FBA holds stock; Walmart and Shopify orders are sent to Amazon MCF to ship | Medium: one pool, but every non-Amazon order must reach MCF reliably | Small catalogs, Amazon-first brands, and stock you would rather not split |
The FBA-as-hub model got more expensive and more rule-bound in 2026:
- Amazon's MCF fees rose by an average of $0.30 a unit from Jan 15, 2026, mainly on 1 to 2 unit orders (Carbon6, vendor estimate).
- A 3.5% fuel and logistics surcharge applies to MCF fulfillment fees from May 2, 2026 (Amazon).
- Walmart allows Amazon MCF only with neutral packaging and unbranded delivery vehicles, and you must block Amazon Logistics as a carrier (Walmart packaging policy, updated Dec 10, 2025).
Split pools cost more in stock and less in sync. If you are deciding between WFS and FBA for a channel, our WFS vs FBA guide compares the fees.
Buffers and reserved stock, with a formula
A buffer is stock you hold back from a channel's listed quantity so that sales during the sync gap do not oversell. It is the cheapest fix for most overselling, and it should be set per channel, not as one number for the store.
The formula we use:
Channel buffer = sync interval (hours) × units sold per hour on that channel at peak × safety factor
The safety factor covers bursts: a deal, an ad spike, a mention. We start at 2 and adjust after a month of data.
Illustrative · sample figures:
| Channel | Sync interval | Peak units per hour | Safety factor | Buffer |
|---|---|---|---|---|
| Shopify | 15 minutes (0.25 h) | 4 | 2 | 0.25 × 4 × 2 = 2 units |
| Walmart (merchant-fulfilled) | 60 minutes (1 h) | 1.5 | 2 | 1 × 1.5 × 2 = 3 units |
| Amazon (merchant-fulfilled) | 30 minutes (0.5 h) | 3 | 2 | 0.5 × 3 × 2 = 3 units |
With 40 units on hand in a shared pool, Shopify would list 38, Walmart 37 and Amazon 37. Each channel stops selling a little before stock truly runs out, and the last units go to whichever channel sells them first.
Reserved stock is different from a buffer. It is stock held for a purpose: a wholesale order, a promotion, a replacement for a damaged inbound. Reserve it in the system of record so it never appears on any channel.
Buffers cost you some sales on the last units. That is the trade: a few late sales lost against cancellations that count against your account. For slow movers, a buffer of one is usually enough. For your top sellers, use the formula.
Event-driven vs scheduled sync
Event-driven sync updates every channel when something happens: a sale, a return, a receipt. Scheduled sync updates on a timer. Event-driven is faster; scheduled is simpler and more forgiving of channel API limits.
| Event-driven | Scheduled | |
|---|---|---|
| How it updates | On each order, return or receipt | Every N minutes |
| Main risk | A missed or failed event leaves one channel wrong until the next full refresh | Sales during the interval can oversell |
| What to check | A daily full refresh as a safety net, and an alert on failed updates | Interval length on your busiest channel; buffers sized to it |
Most tools combine both: events for orders, a scheduled full refresh to correct drift. Ask any tool or provider what happens when a channel's API is down for an hour, and where you will see it.
Mapping SKUs, bundles and kits across channels
Each channel has its own identifiers: ASIN and seller SKU on Amazon, item ID and SKU on Walmart, variant SKU on Shopify. Sync only works if every one maps to the same internal SKU.
Rules that prevent most mapping errors:
- One internal SKU per sellable unit.
The internal SKU is the key; channel identifiers point to it.
- Bundles as components.
A three-pack is mapped as three of the single SKU, so every bundle sale reduces the single's stock everywhere.
- Kits with a bill of materials.
A gift set with a jar, a brush and a box reduces each component.
- No shared SKUs between conditions.
New and refurbished, or retail and resale, need separate SKUs.
- Retire mappings when a listing dies.
An old listing still mapped can come back to life with stock attached.
Walmart standards apply to resale separately: Walmart's return rate standard is 6% or below, or 9% or below for resold items (Walmart, Jul 28, 2026). Keep resale on its own SKUs so you can measure it.
Channel rules that make overselling expensive
Overselling turns into cancellations, and cancellations are measured. Each channel publishes targets, and an oversold weekend can push a small seller past them.
| Channel | Rule | Threshold | Source |
|---|---|---|---|
| Walmart | Cancellation rate | 2% or below | Walmart Marketplace Learn, updated Jul 28, 2026 |
| Walmart | On-time delivery rate | 90% or above | Same |
| Walmart | Late shipment rate | 5% or below | Same |
| Amazon | Pre-fulfillment cancellation rate | Under 2.5% | Amazon Seller Forums, staff account health guide |
| Amazon | Late shipment rate | Under 4% | Same |
| Amazon | Low-inventory-level fee | Applies when both 30-day and 90-day historical days of supply are below 28 days | Amazon |
The list for Walmart above is three of its eight standards; our Walmart seller performance standards guide has all eight. Walmart says missing them "may result in suppression, suspension or termination".
The Amazon low-inventory-level fee pulls the other way: hold too little FBA stock and you pay a fee, hold too much elsewhere and you oversell. Planning both sides is part of the same job. Our low-inventory fee guide explains the rule, and the reorder point calculator helps set the stock levels underneath your buffers.
What to look for in a sync tool
-
Event-driven order updates
with a scheduled full refresh behind them.
-
Walmart support
for both merchant-fulfilled and WFS items, not only Amazon and Shopify.
-
FBA and WFS awareness,
so marketplace-fulfilled stock is kept apart from your warehouse pool.
-
Buffers per channel and per SKU,
not one global setting.
-
Bundles and kits
mapped to components.
-
A connection to your 3PL
that reads available stock, not received stock.
-
An audit log
showing every quantity change, its source and its time.
-
Failure alerts
when a channel update fails, sent to a person.
We do not recommend a specific tool here; the right one depends on your channels, your 3PL and your catalog. These are the criteria we check before any client chooses one.
If you would rather have this built and run for you, our Stock Flow module (RELAY-03) sets up one inventory number across Amazon FBA, Walmart WFS, Shopify and your 3PL, with reorder points and stockout alerts, inside your own accounts. It is part of our inventory and 3PL management service, at a fixed fee shown on our pricing page.
1:36
Read the transcript Captions are on screen Characters are fictional. Voices are AI-generated.
Returns and restocks: the other half of sync
Returns put stock back, and that is where many sync setups quietly go wrong. A returned unit should reach your available number only after someone has inspected it and confirmed it can be sold as new.
- Merchant-fulfilled returns.
Add the unit back to the system of record when the 3PL marks it inspected and sellable, not when the return label is scanned. A unit added at the scan is a unit you may sell before you know it is damaged.
- FBA customer returns
go back into Amazon's network, not your warehouse, and only into FBA sellable stock if Amazon grades them sellable. They never belong in your Shopify or Walmart pool.
- WFS returns
work the same way inside Walmart's network, with their own return processing fee.
- Damaged or opened units
belong on a separate SKU or in a non-sellable location, so they never sync to a channel by accident.
The same applies to inbound stock. Add a purchase order to available stock when the 3PL shows it put away and sellable, not when the truck is booked or the ASN is sent. Selling stock that is still on the water is the fastest way to a cancellation.
Someone has to own all of this. In a small store it is the founder; as channels are added it becomes a weekly job. Whoever owns it should have the authority to change buffers and the time to read the failure log.
A weekly reconciliation checklist
Sync tools drift. A weekly 30-minute check on your top SKUs catches the drift before it becomes cancellations.
- Export available quantity per SKU from your system of record.
- Export listed quantity per SKU from Amazon (merchant-fulfilled), Walmart and Shopify.
- Check that each channel equals system of record minus that channel's buffer.
- Export FBA and WFS inventory and check inbound shipments against what you sent.
- Export the 3PL's received and available numbers and investigate any gap. Our 3PL invoice audit guide covers the received versus available check.
- Check bundle and kit availability against component stock.
- Review last week's cancellations by reason. Any "out of stock" cancellation is a sync or buffer problem.
- Review the tool's failure log and confirm every failed update was retried.
- Adjust buffers for any SKU that oversold or sat unsold behind its buffer.
If this list keeps finding the same problems, the overselling across channels page explains how we fix the cause rather than the symptom. For the fee and performance rules on each channel, start from our ecommerce operations guides.
What is multichannel inventory sync?
It keeps one available-to-sell quantity per SKU, held in a single system of record, and updates Amazon, Walmart, Shopify and any other channel whenever stock changes. Sales on any channel reduce the shared number and update the others. Done well, two channels never sell the same last unit.
How do I sync inventory across Amazon, Walmart and Shopify?
Pick one system of record, choose a stock model (shared pool, split pools or FBA with Multi-Channel Fulfillment), map every channel SKU to one internal SKU including bundles, set a buffer per channel and connect a tool that updates on each order with a scheduled full refresh. Then reconcile weekly.
Why am I still overselling with a sync app?
Usually because of sync lag without buffers, marketplace orders reaching the app late, bundles not mapped to components, or the 3PL feeding received stock instead of available stock. Check each in turn. A buffer sized to your sync interval and peak sales fixes most cases on its own.
Should I use FBA stock for Walmart and Shopify orders?
You can, through Amazon Multi-Channel Fulfillment, and it keeps stock in one pool. Walmart requires neutral packaging, unbranded vehicles and Amazon Logistics blocked. MCF fees rose in 2026, including a 3.5% surcharge from May 2, 2026, so price it per order against your 3PL or WFS before you commit.
How big should my inventory buffer be?
Multiply the channel's sync interval in hours by its peak units sold per hour and a safety factor, starting at 2. A channel syncing every 30 minutes and selling 3 units an hour at peak needs a buffer of 3. Slow movers usually need a buffer of one. Review buffers monthly against actual oversells.
What happens if I oversell on Walmart?
You cancel the order, and Walmart counts it. Walmart's cancellation standard is 2% or below, and missing performance standards may result in suppression, suspension or termination (Walmart, Jul 28, 2026). Oversold orders can also hurt on-time delivery if you try to fill them late.
How do bundles affect inventory sync?
A bundle uses component stock. If a three-pack is listed as its own item with its own quantity, selling it does not reduce the single units listed elsewhere, and you oversell the singles. Map every bundle and kit to its components so each sale reduces each component on every channel.
How often should I reconcile inventory across channels?
Weekly for your top SKUs by revenue, and after any big event: a promotion, a 3PL move, a new channel or a large inbound. The weekly check takes about 30 minutes with exports from each channel, the 3PL and your system of record, using the nine steps on this page.
Next step
Ask a real expert. Free.
A real person replies within one business hour, 9am to 6pm US Central, Monday to Friday.