Diagnose and resolve common issues with orders, inventory sync, connections, and more.
When orders remain in Pending status and never advance to Ready, it usually means the rules engine could not find a matching routing rule. Here is what to check.
Go to Automation Rules and verify that at least one routing rule matches the order's conditions (source channel, SKU, client, etc.). If no rule matches, the order stays pending.
Open the Connections page and verify the destination connection is healthy (green indicator). If the connection is down, orders are held in pending until it recovers.
Open the order detail view. If the order shows is_held = true, it was placed on hold by a rule or manually. Release the hold to allow processing.
Rules are evaluated in priority order. A higher-priority rule with stop_on_match = true might be blocking a later routing rule from running.
The order's audit timeline shows exactly which rules were evaluated and what happened. Look for "No routing rule matched" in the timeline events.
Quick fix: If you need orders to flow immediately, create a catch-all routing rule with no conditions and the lowest priority. This ensures every order gets routed to a default destination.
Orders move to Failed status when WarpWare cannot transmit them to the destination system. The error message on the order tells you exactly what went wrong.
401 UnauthorizedCause: API token expired or was revoked
Fix: Re-authenticate the connection from Settings. Refresh the OAuth token or generate a new API key.
422 Validation ErrorCause: Required fields missing or invalid (e.g., missing shipping address, invalid SKU)
Fix: Check the error detail for the specific field. Fix the order data and retry.
429 Rate LimitedCause: Too many requests to the destination API
Fix: WarpWare retries automatically with backoff. No action needed unless it persists over 30 minutes.
Connection timeoutCause: Destination server did not respond
Fix: Check the destination system's status page. WarpWare will retry automatically.
Duplicate external_idCause: The destination already has an order with this ID
Fix: Verify if the order was actually received. Clear the duplicate flag if re-sending is needed.
If inventory levels are not updating on your sales channels or are not being pulled from your warehouse, check the following.
Go to the inventory source settings and confirm the sync direction is set to Pull, Push, or Bidirectional — not Disabled.
Shopify requires an inventory_item_id for each variant to sync inventory. If the product was created outside Shopify or the variant is missing this ID, sync will silently fail. Check the product variant in Shopify admin.
Shopify inventory writes require a location_id. Go to the connection settings and verify a location is selected. If the store has multiple locations, ensure the correct one is mapped.
Inventory sync only works for products that are linked to a master SKU. Go to the Products page and verify the platform variant is connected to a master product.
Each inventory source shows a "last synced" timestamp. If it is stale, the connection may be down or rate-limited. Check the connection health indicator.
If available quantity shows 0 but your warehouse has stock, your buffers may be set too high. Review product-level and source-level buffers.
Shopify note: Shopify rate-limits inventory updates. If you have thousands of SKUs, inventory pushes are batched and may take several minutes to fully propagate. Check the sync queue in the dashboard.
Connections can fail for a variety of reasons. The connection health indicator on the Connections page gives you a quick status — green, yellow, or red.
OAuth tokens (Shopify, Amazon, WooCommerce) can expire or be revoked from the platform side. WarpWare detects this when an API call returns 401.
Most platforms enforce API rate limits. WarpWare handles this automatically with backoff and retry, but sustained high volume can cause temporary delays.
WarpWare pings every connection at regular intervals to verify it is reachable and authenticated.
WarpWare has built-in duplicate detection to prevent the same order from being processed twice. Here is how it works and how to resolve duplicate issues.
If an order was correctly flagged as a duplicate but you need to re-import it (e.g., the original was deleted or the data has changed):
Caution: Clearing a duplicate flag and re-ingesting an order will create a new order in WarpWare. If the original was already sent to a warehouse, you may end up with two fulfillment requests. Always verify the original order's status before clearing duplicates.
If you have gone through these steps and the issue persists, reach out directly and we will help diagnose.