All inventory guides

Why Shopify inventory goes out of sync with a 3PL

Trace a difference between your store and your warehouse by checking timing, stock pools, SKU mappings and inventory history.

Shopify shows six units in stock. Your third-party logistics provider (3PL) says it can ship two. Before you edit the number that customers see, find out which four units account for the difference. A count that stayed stale needs a different fix from a count that includes the stockroom at your retail store.

Pick one SKU you can trace. First check the timing and what each number counts. If the gap started right after a catalog or warehouse move, jump to the change you made. The order is a troubleshooting guide, and the causes can show up together.

1. The two reads caught different points in the sync

An order, receipt, return or adjustment can change the count in one system before the other has updated. A connector might pass changes along in batches or use another update schedule. Check how yours is set up and which direction the relevant update should go. You can see the same difference if one export was taken before a sale and the other was taken after it, even when both systems are currently in agreement.

Write down when each number was read and when the last relevant stock event happened. Use the same time zone for all three. Take new readings close together after the time your connector normally needs to catch up. If the gap closes, keep those timestamps so you know what ordinary lag looks like. If it stays open, check what the numbers include before treating it as a failed sync.

2. The two numbers describe different stock

Shopify’s Available quantity excludes stock that is committed, unavailable or incoming. On hand covers the units at a location, including those already committed or set aside. Comparing Available with a warehouse on-hand total can therefore manufacture a gap. Shopify inventory states

Check the location scope too. If a variant draws on a 3PL and your own stockroom, look at the Shopify location or locations that correspond to the 3PL supply. Shopify’s inventory CSV can show separate rows by location and include all inventory states. On the warehouse side, establish whether a column is a single site, a group of sites or an account-wide total. Write down any buffer or exclusions your connector is supposed to apply. For ShipBob’s Shopify connector, compare Shopify Available with the expected quantity after exceptions and any configured buffer. Shopify inventory CSV guide · ShipBob connector overview · ShipBob inventory buffer

3. One SKU is pointing at a different item

Check mappings if a handful of variants stay wrong while their neighbours move as expected. Start with a SKU that was recently renamed, replaced or split into multiple variants. Confirm the storefront variant and warehouse item refer to the same size, colour and unit of measure. A carton of six and a single unit can share a similar name and produce a very predictable difference.

Use each system’s item identifier alongside the SKU. Look for blanks, duplicate codes or an old item that still receives updates. When the mismatch involves a kit, put its component list next to the storefront offer and check how many of each component ship with an order. The guide to bundles and reserved units walks through the calculation.

4. Another update replaced the expected count

If a count looks right after one update and wrong again later, find out who else can write to it. Check for stock imports, hand edits and other software your team uses to manage the same inventory. Ask which tool is supposed to own the quantity at the affected location. Several people can be following their own procedures correctly and still undo one another’s changes.

Start with the variant’s inventory adjustment history in Shopify. Record the change, the time and any source Shopify displays. Compare those with the warehouse event and any run details your connector provides. Look for the order of events before deciding which writer needs to change. Shopify inventory adjustment history

5. A stock change never made it through

Once the timestamps, stock pools and mapping line up, follow one event. Did the receiving or order change appear where it started? Is there a connector run that saw it? Does the destination show it? If the connector records errors, capture the exact message and time. Check whether one SKU failed while the rest of the run went through. Share a small example with whoever owns the connector, including the SKU, location, two readings and the event you expected to move the count.

Consider the physical units if neither system’s number makes sense. A recount can uncover units shelved under the wrong item or a receipt entered twice. If both systems agree on a wrong physical count, comparing their records can’t reveal it.

Turn one example into a repeatable check

Keep a short log of confirmed mismatches and their causes. Once you can explain one SKU from start to finish, run the same check on a few more to see whether the cause is shared. The manual Shopify and ShipBob reconciliation shows how to turn those checks into a sheet your team can reuse.

If tracing the same gaps has become a routine job, you can request early access to the planned pilot.