How to Split and Merge Shopify Fulfillments

A Shopify order can contain one or more fulfillments that group line items and quantities for operational handling. Shopify notes that orders may be split when no single location has enough inventory or when products cannot ship together because of delivery methods, profiles, preorders, subscriptions, or pickup. Before changing the grouping, list each line item, quantity, assigned location, delivery method, fulfillment service, due date, package requirement, and current status.

Distinguish an order from its fulfillment work. Payment, customer identity, discounts, and order totals can remain unchanged while fulfillment orders are split, merged, moved, held, requested, or completed. Do not use split or merge to hide an inventory shortage or rewrite a customer promise. If the underlying issue is location assignment, an order edit, a fulfillment hold, or a third-party service request, use that workflow and preserve the reason.

Split when selected items or quantities need a different package, ship date, service, location workflow, or exception owner. Confirm that the destination fulfillment can be processed without breaking inventory reservations or an active service request. Record the original fulfillment order, items moved, quantities, reason, owner, and expected next state. Shopify's Flow documentation explains that a split can produce original, remaining, and in some cases replacement fulfillment-order objects, so integrations must not assume one identifier survives unchanged.

Perform the change from the supported Shopify admin or web path and immediately inspect both resulting groups. Shopify states that split and merge are not available in the mobile app, although the web version can be used on a mobile device. Confirm no item is missing or duplicated, locations are correct, holds remain intentional, and each group has a valid fulfillment path. If a third-party app initiated the split, capture its event or request ID and compare the same quantities in the warehouse system.

Merge when separate unfulfilled groups from the same location can be picked, packed, and shipped together without changing the promised service. Shopify says multiple fulfillments from the same location can be merged based on line items and quantities, and notes that merging can simplify fulfillment and reduce shipping costs. That possibility is not proof that every same-location group belongs in one parcel. Check shipping profiles, hazardous or fragile handling, temperature, preorder timing, subscription rules, pickup, carrier service, package capacity, and customer instructions.

Before merging, verify neither group has a purchased label, open fulfillment-service request, tracking event, manifest assignment, or warehouse task that will become orphaned. Preserve the original identifiers in the operational log. After the merge, confirm the new combined fulfillment contains every intended unit once, has the correct location, and remains eligible for the chosen label and package. If the merge changes shipping cost or delivery timing, resolve the customer promise before releasing the combined shipment.

Do not split or merge around an active carrier label without a label decision. Map each label to its package, quantities, tracking number, and fulfillment order. Void an unused label through the approved carrier or Shopify path before replacing it, and never attach one tracking number to two physical parcels. For a combined shipment, recalculate weight, dimensions, declared value, service, and package count from the actual packed goods rather than reusing one group's estimate.

Review Flow workflows, webhooks, warehouse subscriptions, and fulfillment-service integrations that react to split or merge events. Shopify exposes dedicated fulfillment-order split and merged triggers, and the split trigger can include several resulting objects. Ensure automations are idempotent, use current identifiers, and do not release holds, duplicate tasks, or send premature notifications. Test with a safe order before enabling a new automation, then compare Shopify, the app, and the warehouse after the event.

Run a quantity-level reconciliation after every split or merge. Sum fulfilled, unfulfilled, held, and canceled quantities for each variant and compare them with the original order. Verify location assignments, inventory commitments, warehouse tasks, labels, tracking numbers, packages, customer notifications, and the Shopify timeline. A visually tidy order is not sufficient if one unit disappeared from a pick list or a stale service request can still ship it.

Track reasons for splits and merges, manual corrections, label voids, delayed releases, duplicate tasks, and delivery exceptions. Repeated manual regrouping may reveal routing, inventory, product-profile, package, or integration defects. Fix the upstream owner rather than teaching operators to normalize every order by hand. Close the case only when Shopify and every downstream system agree on which units will leave which location in which parcel, under one verified customer promise.

Keep a recovery checklist for orphaned labels, stale warehouse tasks, duplicate fulfillment-service requests, missing tracking messages, and quantities assigned to no active group. Stop release work while the checklist is open. Compare against the original order rather than assuming the newest fulfillment object is complete.

Restore one authoritative grouping in Shopify and every downstream system before purchasing another label. Document which identifiers were retired and which survived. If an integration cannot consume the corrected state, isolate the order for manual handling and open the upstream defect instead of continuing with parallel truths.