Shopify Orders: Endless Owns Fulfillment Planning After Import

Shopify supplies the initial fulfillment plan when an order is created in Endless. Later planning — splitting, moving between buildings, changing quantities, or cancelling — happens in Endless. Reload Order and later Shopify webhooks bring current sales quantities across, but they do not add, move, split, or remove operational fulfillments to match Shopify’s structure.

Removed lines stay on the order at their original quantity, so you can see what was purchased alongside the current quantity Shopify reports. Fulfillment work is reconciled to the current quantities: reservations are released for reductions, fulfillments emptied by a reduction are cancelled, and ready, in-progress, and completed work is preserved. A shipment that already went out is kept even when Shopify later reduces the sales line, and an Excess demand signal is raised so you can see why a fulfilled quantity now exceeds the order.

Seeing And Applying What Shopify Reports

The saved source fulfillment plan and its change history are visible on the order regardless of whether it differs from Endless. Open the source plan viewer from the order to see the last complete plan Shopify reported and the meaningful changes since — location, grouping, active state, and quantity. Display-only differences and retried polls do not create timeline entries.

When Shopify’s fulfillment orders differ from Endless in warehouse, quantity, or grouping, an amber “Fulfillment orders differ” badge shows in the order source bar and a Fulfillment orders differ signal is raised on the order. Warehouse comparison falls back to your Shopify location mappings when the identity registry has no entry, so a fulfillment created at the same warehouse on both sides does not read as a difference.

Update Fulfillments is available from the order Actions menu and from a right-aligned button on the drift alert. Draft and allocated differences are replaced and their reservations released; ready, in-progress, and completed work must already match, or the operation is refused. New fulfillments land in draft without running fulfillment-created automations, so the arrangement can be reviewed before it moves.