Splitting a fulfilment creates new work assignments, not new ordered units. Before connecting a warehouse workflow, require a map from original lines to fulfilled, remaining and replacement assignments. Summing every original and child record together can double the apparent order.
Primary evidence and claim boundaries
Shopify Flow’s fulfilment-order-split trigger provides original and resulting fulfilment orders, with an optional replacement. The trigger does not include the specific affected line items; the resulting orders must be read for them. Primary reference · Read 18 October 2026.
Filled acceptance example
Original synthetic teaching scenario, not a client case, provider integration test or business result. The example policy needs the actual owner’s approval; scroll the table on narrow screens.
| Input and state | Declared check | Expected output and decision |
|---|---|---|
| Order lineL1 quantity 4; already fulfilled1 | Unfulfilled scope is3 | Reconcile only the remaining3 against split assignments |
| RemainingF2:L1=1; replacementF3:L1=2 | 1+2=3 | Matches unfulfilled scope |
| Original unfulfilledF1=3 also counted with F2/F3 | 3+1+2=6 | Double-counted lineage; reject |
| Trigger received, child line items not read | No resulting quantities | Keep reconciliation unknown, not zero affected items |
Practical handover procedure
- Define order-line identity separately from fulfilment-order identity and record which original assignments are superseded. Keep already fulfilled quantities outside the unfulfilled split scope.
- Supply the four records to the integration team. Require an item-level conservation report with original-to-child lineage and missing-read errors.
- In an authorised isolated store, exercise a partial fulfilment followed by a split. Verify source reads, line IDs and warehouse acknowledgements; no notification alone proves shipment.
Interpret the outcome
The correct total is4 ordered units:1 already fulfilled and 3 still assigned. Six unfulfilled units in the third row are an accounting artefact, not new demand. A replacement may be absent; the implementation must use actual returned records instead of assuming a fixed number of children.
Acceptance decision
Every active assignment must trace to an original line and conserve the stated remaining quantity, with missing child reads reported as incomplete.
Limits and unverified work
Synthetic lineage and arithmetic, no Flow activation, API mutation, warehouse instruction, shipment or payment. Plan/app support remains an implementation check.
Download the filled bilingual acceptance record — Contains the inputs, steps, expectations and limits. This is a teaching record, not an executable production integration.
Related next decision: Carry the line-item identity into returns and 3PL handover.