Shopify Connector / Fulfillment BC Posted Sales Shipment → Shopify fulfillmentCreate (GraphQL) Microsoft BCApps issue #13812 (open, approved); Microsoft Learn: Troubleshooting shipment synchronizations

Shipment Sync Fails After a Fulfillment Order Was Moved and Merged in Shopify

Raw System Error String
Fulfillment order line item does not exist.

What It Means

You posted a sales shipment in Business Central, but 'Sync Shipments to Shopify' does not mark the Shopify order fulfilled. The Shopify Log Entry shows the userError 'Fulfillment order line item does not exist.' Shopify rejects the whole fulfillment, so even the correct lines on that shipment are not fulfilled. The posted shipment gets Shpfy Fulfillment Id = -1.

Root Cause

Someone changed the location of a fulfillment order in Shopify (the 'Change location' action or fulfillmentOrderMove) to a location that already had an open fulfillment order for the same order. Shopify merges the two: the line items move into the open fulfillment order and keep their FulfillmentOrderLineItem id, and the emptied fulfillment order becomes CLOSED. On the next order sync the connector keeps a stale row for the closed fulfillment order: its line 'Fulfillment Status' stays OPEN (status is only set on insert) and lines Shopify no longer returns are never cleaned up. When shipping, the connector reads rows in primary-key order, so if the closed fulfillment order has the lower id the stale row takes the shipped quantity, and the fulfillmentCreate mutation sends the closed fulfillment order id with the moved line item. Shopify answers 'Fulfillment order line item does not exist.' Reported on BC 27 with Shopify API 2026-01; the code was unchanged on main when the issue was filed.

Step-by-Step Fix

  1. Search for 'Shopify Log Entries', choose the 'With errors' view, and open the fulfillmentCreate request. Confirm the response contains 'Fulfillment order line item does not exist.' and note the fulfillment order id it sent.
  2. Open the Shopify Order in Business Central and choose 'Sync order from Shopify' to pull the latest fulfillment orders.
  3. Open the order's 'Fulfillment Orders' page. Look for a fulfillment order whose header status is CLOSED but which still has a line with Remaining Quantity > 0, while the same line item also exists under an open fulfillment order. That stale row is the cause.
  4. Because a re-sync does not clear the stale row (the bug in #13812), the quickest workaround is to fulfill this order manually in Shopify Admin (with the carrier and tracking number from the posted shipment), so the customer gets the notice.
  5. If you want the connector to retry instead, after the stale data is corrected (for example by your partner, or after the fix ships), open the posted sales shipment, choose 'Update Document', and change the Shopify Fulfillment Id from -1 to 0. Then run 'Sync Shipments to Shopify' again.
  6. Prevention: avoid changing a fulfillment order's location in Shopify after the order is synced to Business Central, especially to a location that already has an open fulfillment order for the same order. Watch BCApps #13812 for the connector fix (refresh line status on update, close lines Shopify no longer returns).

Verification Steps

How to verify: The Shopify order shows as Fulfilled with the tracking number, the order's Completed Fulfillments page in Business Central lists the fulfillment, and the posted shipment's Shopify Fulfillment Id is no longer -1.

Sources & References

Early Access · 30-Day Sandbox Pilot

Stop Order Sync Failures Before Customers Notice

The Order Flow Doctor monitors Microsoft Dynamics 365 Business Central order flows across Shopify, EDI (TrueCommerce, SPS), 3PLs, and carriers. Get automated root-cause diagnosis and one-click fixes.

We respect your privacy. No spam. You will only be contacted when pilot slots open for your stack.