Inventory Synchronization Errors
Troubleshooting guide to resolve inventory synchronization errors
Inventory synchronization issues can occur at multiple stages, leading to discrepancies in stock levels across platforms. Accurate inventory synchronization is crucial to prevent underselling or overselling for retailers. This document aims to provide detailed steps to diagnose and resolve issues related to inventory synchronization between ERP systems, HotWax Commerce, and Shopify.
Scenario 1: An inventory file did not finish importing into OMS
Inbound file processing and outbound Shopify publication are separate. Locate the configured import and establish its outcome before retrying anything.
Confirm the expected inventory source, import configuration, file name, and timestamp.
Review its Data Manager file history, processing state, record counts, and errors.
Verify which records changed inventory in OMS. A failed or lost response does not prove no records were applied.
Correct the cause and use a supported, scoped recovery. Do not re-upload an entire file merely because a folder or status says failed.
After verifying the OMS quantities, investigate the matching channel or physical-location event path for Shopify delivery.
Follow Troubleshoot file imports and inventory import methods. These are inbound inventory procedures, not Shopify event publishers.
Scenario 2: The inventory file is in the wrong SFTP location
Confirm the source system's approved path and file-name pattern with the integration owner. Compare them with the configured OMS retrieval job and import configuration. Keep the investigation read-only until the expected file and any prior processing are established.
For NetSuite SFTP setup, see Set up SFTP. A file's presence on SFTP does not establish successful import or Shopify delivery.
Scenario 3: Shopify rejects or delays an inventory update
An outbound inventory batch can fail when Shopify rejects the request, throttles the connection, or the target is unavailable.
Diagnose and resolve the failure
Open the Company App.
Select
Shopify, open the affected connection, then selectInventory sync.Review
Channel inventory eventsorPhysical inventory eventsfor the affected target, then open its waiting-batch row orEvent history.Open the affected batch.
Record its System Message identifier, Shopify target, status, and delivery errors.
Confirm the connection's Shopify write access and the target location.
Check Shopify status information when the error indicates an outage or throttle.
Correct the cause, then use the approved recovery process before selecting
Resend.
Resend uses the batch's original payload and idempotency key; it does not recalculate current inventory. Do not keep retrying without correcting the recorded error. Verify the resulting batch state and Shopify quantity.
Scenario 4: Shopify inventory events are not reaching the target
The physical-location and channel paths have separate event queues and publishers. A completed inbound inventory import does not prove either outbound path ran.
Open Company >
Shopify> the connection >Inventory sync.Confirm the affected target's physical mapping or aggregate channel.
Check the appropriate event-source and capture controls. Changes made while capture is off are not available for later replay.
For a physical location, inspect
Physical inventory eventsandPublish physical batches (all shops). For a channel, inspectChannel inventory eventsand itsSend channel batchespublisher.Review waiting events, batches, publisher state, schedule, parameters, and latest run.
For batches that remain in flight, have the integration owner verify sender coverage for the affected message type and inspect its result.
Correct the cause. Use
Reset physical ATP (this shop)or the channel'sReset channel ATPwhen available-inventory reconciliation is required;Reset physical on-handis a separate quantity reconciliation.Review the approved recovery's scope and outcome, then verify Shopify at the mapped location.
Supported missing jobs created with Set up start paused. Do not activate an arbitrary schedule or duplicate publisher. Keep manual discard jobs paused and unscheduled.

See Monitor Shopify inventory sync for the complete event, job, sender, and reconciliation workflow.
Scenario 5: Shopify write access is missing
Outbound inventory fails when the selected Shopify connection cannot write inventory.
Diagnose and resolve access
Open the Company App.
Select
Shopifyand open the affected connection.Select
Access scopes.Under
Connection access, confirmSHOP_RW_ACCESS. Do not selectSHOP_READ_WRITE_ACCESS; it has the same description but does not satisfy the current inventory service gate.Under
Granted OAuth scopes, refresh the Shopify scopes and confirmwrite_inventoryfor the approved connection profile.Resolve a missing connection-access value in HotWax Commerce or a missing OAuth scope through the approved Shopify connection flow.
Return to
Inventory syncand retry only the affected batch or reset.
Do not place access tokens or credentials in screenshots, tickets, or documentation.
Last updated
Was this helpful?