How to reconcile Shopify and ShipBob inventory by hand
Export current inventory from both systems, match SKUs and locations, and use a second snapshot to confirm each gap.
When the warehouse and store disagree, start with current inventory exports from both sides. The aim is to find the items that differ after you’ve matched the same units, locations and stock rules. You can do this in a spreadsheet. Keep the exports as evidence and make any eventual inventory correction through your usual process.
1. Define the stock pool first
Pick one Shopify store and the ShipBob locations that supply it. Write down the Shopify location names and the ShipBob stock pool that feeds each one. If several sites feed one Shopify location, confirm which sites the connector includes before combining them. Leave out retail stock and other warehouses if they’re outside the comparison. If a warehouse pool is shared with other channels, confirm whether the whole pool or only a share is offered through the store.
Start with plain stocked variants. Put virtual bundles and prebuilt kits in a separate review group so they don’t show up as missing items or false gaps. Record the buffer or exclusions the connector is meant to apply, if any.
2. Export Shopify inventory
In Shopify admin, open Products → Inventory → Export. Choose the relevant location or export all locations and filter in the sheet. Select All states and choose the variants you want to check. Keep Location, Available and the SKU where one is present. Save Committed, Unavailable, Incoming and On hand (current) too so you can explain rows later. Shopify’s export guide shows the two CSV formats and what the columns mean. Shopify inventory CSV guide
Import the SKU column as text to preserve leading zeroes. Record when you requested the export and when it arrived. Leave a blank or nonnumeric count unresolved until you can confirm the quantity.
3. Export the ShipBob Inventory Status data
Open Inventory Status in the ShipBob dashboard. Use the page’s filters and export the relevant rows. Keep the SKU, inventory ID and quantity fields available to you. If the export doesn’t show the warehouse split you need, check the scope in the dashboard or ask whoever manages the integration for a location-level inventory extract. ShipBob documents an inventory API response grouped by fulfillment center. ShipBob Inventory Status export release notes and ShipBob location-level inventory documentation
Take this snapshot as close to the Shopify one as you can. For a regular SKU, ShipBob’s Shopify connector starts with Fulfillable minus Exception and deducts any buffer you configured. Use those quantities for the stock pool the connector syncs. The ShipBob API’s separate Sellable field uses a different calculation that includes Awaiting stock. ShipBob connector overview · ShipBob inventory buffer · ShipBob API field definitions
4. Match the rows and subtract
Make a clean sheet with one row per SKU and comparable location group. Retain the original rows in separate tabs. Match the two sides by SKU and location group, using an explicit mapping where the identifiers differ. Check for duplicates before using a lookup. A lookup that returns the first result can mask a duplicate. Mark missing matches for review, including warehouse items that are absent from the Shopify export.
For each matched row, subtract the quantity you expect the connector to send from Shopify Available. Apply any configured buffer once. In a fictional row with nine units on Shopify and an expected connector quantity of six after any buffer, the gap is plus three. A positive gap means the store offers more than the comparison count. A negative gap means the store offers fewer. Keep both signs visible and sort positive gaps by urgency.
Keep a disposition column for exceptions such as “mapping missing,” “bundle review,” or “location unclear.” That lets the person rechecking the sheet focus on real comparisons. If a zero is confirmed, record a numeric zero. If a number is unavailable, keep it blank and say why so it can’t be mistaken for a shortage.
5. Pull both readings again
Wait through the normal sync window for your store and repeat both exports. If you haven’t measured that window, use the steps in how to tell sync lag from real drift. Keep the first and second readings side by side. A mismatch that closed needs a different response from one that persisted. Note when a new order or receipt happened between reads so a fresh change doesn’t look like the same stuck one.
Check unusual rows against the variant page and warehouse item record. First check scope and mapping, then look for an inventory change that explains the remaining gap. If you need to ask for help, send the affected SKU, both location names, both sets of counts and the relevant event timestamp. Avoid handing off an entire catalog when one row shows the issue.
Keep the sheet for the next check
Save the mapping, the timestamps and what you learned about buffers. Update the mapping when the catalog or fulfillment setup changes. A clean report means the two compared records agreed at the time you read them. If both agree on a count that’s wrong on the shelf, ask the warehouse to count the item.
If you’d like to test scheduled rechecks for this workflow, you can register interest in the planned pilot.