StoreFulfil™ Library

Operating journey / step 50

Run the floor

Troubleshooting

Use this guide when work has reached this point. If the visible state does not match, stop and follow the named hand-off.

Troubleshooting: Stale Inventory

Resolving mismatches between Shopify and StoreFulfil.

Updated Aug 2026
Owner: Inventory Manager
Area: Inventory

Before you begin

Diagnose a stale inventory view by checking location, timestamp, connection, and sync result before anyone makes a stock decision.

Prerequisites

  • The client and mapped Shopify location are known.
  • The Admin can view the inventory timestamp and run Sync now.
  • A mismatch is recorded with a SKU or product reference.

Stop and check

Do not call local inventory real-time or sync a destructive correction without checking the mapped location.

If stock levels appear out of sync, manual synchronisation can be triggered.

Resolution

  1. Navigate to the Inventory section.
  2. Use the 'Sync now' action to reconcile the current stock level with the mapped Shopify location.

What this is and when to use it

Use this Admin guide when the inventory screen does not agree with a recent count or Shopify change.

Refresh safely

  1. Confirm the client and mapped Shopify location.
  2. Note the displayed quantity and timestamp.
  3. Check connection health, then use the supported Sync now action once.
  4. Compare the returned rows and errors with the physical or Shopify evidence.

Questions and hand-off

If The location is wrong

Do not adjust stock. Correct the mapping before using the result.

If The mismatch remains after sync

Pause the stock decision and give before/after values, timestamps, and SKU to the Inventory Manager.

What happens next

A fresh mapped-location result supports the next stock decision; a remaining mismatch stays an investigation, not an automatic correction.

Expected Outcome

StoreFulfil refreshes the inventory reported for the mapped Shopify location.

Runbook evidence

Use these signals to decide whether the work is ready to continue, complete, or needs an owner.

State checkpoints

Possibly stale

The local timestamp is older than the operational decision allows or a source change is expected.

Next: Check the mapped location and connection health before syncing.

Sync completed

StoreFulfil returned a refresh result for the mapped location.

Next: Compare the affected rows and record failures or unrecognised items.

Mismatch remains

The refresh did not explain the difference or the location/source data is wrong.

Next: Pause the stock decision and escalate with the comparison evidence.

Completion evidence

  • The location, fresh timestamp, affected quantity, and sync result have been reviewed.

Escalation evidence

  • Record the client, location, SKU, before/after values, timestamps, and displayed result.

Work safely

Who may take this action

Warehouse Admin

What you should see

The local timestamp is older than the operational decision allows or a source change is expected.

Safe next step

Check the mapped location and connection health before syncing.

What not to do

Do not call local inventory real-time or sync a destructive correction without checking the mapped location.

How to tell it is complete

The location, fresh timestamp, affected quantity, and sync result have been reviewed.

© 2026 STOREFULFIL PTY LTD (ACN 701 718 649 · ABN 98 701 718 649), Queensland, Australia · StoreFulfil™ Operations Library.

Content Index