Stock sync apps for Shopify: setup and fixes
When Shopify stock differs across locations or channels, map your stock-sync app to the right variants and repair conflicting inventory updates.
- Published
- Last updated
Set up a stock sync app for Shopify by choosing one stock source, matching each variant to its location and testing the resulting availability. If quantities already disagree, compare the same variant, location and inventory state before changing anything. A successful import can still leave customers buying against the wrong stock.
Choose the stock source and sync method
Choose which system decides the quantity for each variant and location before enabling an inventory app for Shopify. Two systems that both replace the same quantity can undo each other’s changes.
Shopify’s native inventory management covers quantities, transfers and purchase orders, with separate stock records for locations. You can manage these in the admin without a stock-sync app. An external connection is useful when the quantity originates elsewhere, such as a supplier file or warehouse system. Shopify’s inventory and locations guidance describes the native controls.
Match the app pattern to the stock source
| Pattern | Authoritative source | Update direction | Timing | Who resolves conflicts? |
|---|---|---|---|---|
| Native Shopify inventory | Shopify records and physical counts | Store operations update Shopify | Sales and recorded stock movements | Your inventory operator |
| Supplier-feed connector | Supplier’s quantity file | Supplier to mapped Shopify locations | Scheduled import or manual run | Feed owner corrects the source and mapping |
| Warehouse connection | Warehouse stock and reservations | Orders go out, inventory updates return | Connector-specific events or batches | Warehouse integration owner reconciles both records |
| Shared multichannel inventory | Central inventory system | Channel orders return to the centre, availability goes out | Connector-specific | Central inventory owner prevents repeated deductions |
For example, syncX: Stock Sync documents supplier-feed updates and separate settings for replacing quantities or adding and deducting them. A file containing the current balance needs replacement behaviour. Reapplying a file containing a stock movement needs protection against applying that movement twice.
Before setup, secure access to inventory settings and the connector’s logs. Activate Track quantity for the variants whose stock Shopify must track. Keep a current inventory export and a copy of the feed configuration. Use a disposable product and locations for the first run. The operator responsible for stock must also own the decision to resume a paused feed.
Map variants and locations before importing
Map each source variant to exactly the Shopify variant and location that hold its stock. A product title alone cannot distinguish a small blue shirt from a large blue shirt.
- Choose a stable identifier shared by both systems. A stock keeping unit (SKU) or barcode works when its value consistently identifies one variant. Preserve leading zeros and check spaces in source values.
- Find missing identifiers separately from duplicates. A blank SKU gives the connector nothing to match. The same SKU on two different variants creates an ambiguous match that needs correction before bulk updates.
- Map each source warehouse to its intended Shopify location. Confirm that the variant is stocked there. Similar location names are insufficient evidence that the mapping is right.
- Preview one product with at least two variants across two locations. Use different quantities, such as small: 6 and 2, large: 9 and 4. Each previewed result must reach only its intended variant-location pair.
- Apply the limited update and reopen those records. Confirm that all four quantities match the preview and that an unrelated product is unchanged before expanding the import.
A missing identifier causes an unmatched row. Duplicate records can make one row affect several products or leave some products unchanged, depending on the connector’s duplicate setting. Enabling a duplicate-update option does not establish that those products share one physical stock pool.
Stock Sync’s duplicate-SKU guidance recommends consistent unique identifiers and a preview before applying updates. Its feed documentation also separates location selection from quantity mapping. Keep these checks separate when diagnosing a match that appears correct but changes the wrong stock.
Set availability and update rules
Map the source quantity to the inventory state it actually describes. Physical stock and stock available to sell can differ even when both systems are correct.
Shopify’s inventory states distinguish the following quantities.
- On hand is the total physically recorded at the location.
- Committed stock is set aside for orders or other commitments.
- Unavailable stock is held back, including damaged goods or safety stock.
- Available stock can be sold. Incoming stock becomes available only after receipt into the appropriate state.
As a hypothetical example, 12 on hand minus 3 committed minus 1 unavailable leaves 8 available. If the source already reports 8 sellable units, subtracting those reservations again would publish too little stock. If it reports 12 physical units, publishing all 12 as available would release reserved stock.
Apply a buffer once, in the system responsible for availability. Record whether it is already deducted from the exported figure. When stock reaches zero, Shopify’s initial inventory setup explains the Continue selling when out of stock setting. Disable it for variants that must stop selling at zero. Shopify POS has separate selling behaviour, so test that channel separately if you use it.
A scheduled feed leaves Shopify using the last imported balance until the next run. An event-driven connector responds to changes, but a delayed or failed event still creates a stale quantity. Compare the source event time with the last successful update for the affected item. The label “real-time” alone does not prove that existing stock was reconciled when the connection started.
Decide what an omitted row means before enabling zero-stock rules. A complete supplier file might omit unavailable products. A partial file might omit unchanged products. Treating the second file as a complete stock list can incorrectly set unrelated stock to zero.
Verify sales, cancellations and returns
Verify the stock movement in both systems and the customer’s ability to buy. The connector’s completed status proves only that its process finished.
Use this hypothetical walkthrough for a connector that returns Shopify orders to a central source. Assume one sellable variant at one location, a zero buffer and an otherwise idle store. The source publishes available stock after accounting for reservations.
Expected quantities through an order
| Event | Source available | Shopify available | Shopify committed | Shopify on hand |
|---|---|---|---|---|
| Reconciled starting balance | 5 | 5 | 0 | 5 |
| Sell 2, then process the order at the source | 3 | 3 | 2 | 5 |
| Cancel the unfulfilled order and restock once | 5 | 5 | 0 | 5 |
| Place a fresh order for 2 and fulfil it | 3 | 3 | 0 | 3 |
| Receive and restock 1 sellable returned unit | 4 | 4 | 0 | 4 |
Inspect each event before starting the next. The source must receive the sale before sending back its next available balance. Otherwise, an old balance of 5 could overwrite Shopify’s reduced availability of 3.
Shopify’s cancellation instructions include a restock choice. Its refund instructions also separate refunding money from restocking items. Return stock to sellable availability only after the unit is received and judged sellable under your process. Record the receiving location so another warehouse does not gain the unit.
After each movement, open the correct storefront variant and proceed towards checkout with the intended delivery address. Confirm that an available quantity can be purchased. Then test zero availability with continued selling disabled, accounting for other locations that can fulfil the order. Shopify’s location fulfilment guidance explains why a positive total elsewhere can affect the outcome.
For a supplier-feed-only setup, use the same quantity comparison after each import. Orders will not reach the supplier merely because an inventory file imports successfully. Keep a separate order handoff if the supplier must reserve units for your sales.
Find and repair stock mismatches
Pause the affected feed if it makes unexpected changes, then inspect one variant-location pair before attempting a bulk correction. Keep the original source file and the before-and-after quantities.
Work through these checks in order, starting with errors you can confirm without writing stock.
- Compare the source row with the matched variant identifier. Search Shopify for duplicate SKUs and inspect missing values. Correct the mapping or identifier, then preview the affected rows again.
- Compare the connector’s destination with the Shopify location record. Stock at a non-fulfilling location can differ from online availability. Correct the destination and preview one variant before running it.
- Read the failed item’s error and check inventory-write permission. Restore the specific missing authorisation if the log reports an access failure. A location error needs a location correction, not repeated authorisation.
- Inspect adjustment history for another app, manual update or overlapping feed. If the correct value later changes back, identify that second writer. Pause its overlapping updates and assign one owner to the quantity.
- Compare the quantity mode with the file’s meaning. A balance of 7 imported twice must remain 7. A movement of minus 2 applied twice changes stock by minus 4 and needs duplicate-event protection.
For a timed-out update, read the current quantity and adjustment history before retrying. An uncertain response does not prove that the first write failed. Correct the current balance from the authoritative source after accounting for intervening sales, then retry only through a process that recognises the original event.
For a custom connector, Shopify’s absolute quantity API documents expected-current-quantity checks and idempotency protection against duplicate requests. Keep those protections enabled during recovery. A packaged connector’s support team must resolve uncertain retry behaviour before an operator manually replays stock movements.
Resume the limited feed and repeat the same sale-and-restock check. Recovery means that source and Shopify quantities agree after each event, an unchanged second run leaves stock unchanged and checkout respects the resulting availability. If they still differ, send support the affected identifier and location, source row, expected quantity and adjustment history. Include the connector’s event or run identifier without credentials.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.