Keep two orders distinct while they share one parcel

Confirm the two orders are genuinely separate sales

Before recording anything about the parcel, establish that the two orders are distinct commercial commitments: separate order records, separate payment records, and if applicable separate buyers. Consolidating a shipment is a physical efficiency. It does not merge the obligations, and nothing about the shared parcel should cause support to treat the pair as one sale.

If the two orders belong to different buyers, flag the privacy dimension immediately. Each buyer's delivery evidence, messages and any later dispute concern only their own order. The reconciliation happens inside authorized internal records; it is not something either buyer needs to see.

Map every packed line to its order and the parcel

Build the packing map from the genuine records: for each order, the items and quantities it requires; for the parcel, the items and quantities actually packed. Every packed unit must be attributable to exactly one of the two orders. A unit that cannot be attributed is an unresolved packing finding, not a spare.

Compare both orders' required quantities against the packed totals. If the parcel covers everything both orders owe, both can reference the same tracking record as their delivery evidence. If anything for either order was left out, record that remainder against the correct order as outstanding work with an owner, rather than letting the shared parcel imply both orders are complete.

Record the combination in the system you actually use

ShipStation's documentation for combining shipments confirms that multiple order records can be represented in one shipment, which is the capability this workflow relies on. The same documentation advises attention to combined packing information and to marketplace notifications, because channel compatibility affects what the sales channel and the buyers are told. Verify how your channel receives the combined result before treating its order pages as accurate.

ShipStation's legacy mode differs from the newer layout, and other platforms handle combined shipments differently or not at all. Confirm the actual tool, layout and integration in use. If your system cannot record two orders on one shipment, keep the linkage in your internal fulfillment records rather than forcing the orders into a structure that misstates them.

Keep notifications, remedies and privacy order-specific

Each buyer's shipment message should describe only their own items and the shared tracking reference, with no hint of the other order's contents or recipient. Where the tool sends combined packing information to a marketplace or channel, check what that channel actually displays so one buyer is not shown the other's goods.

Payment and remedy records stay per order. A refund, a shortage claim or a delivery dispute on one order is resolved against that order's own payment and packing allocation, even though the parcel was shared. The shared tracking record is evidence about the parcel's journey; it is not a merged account of what either buyer is owed.

Handle exceptions without disturbing the other order

If the parcel is delayed, damaged or lost, both orders are affected physically but each needs its own resolution: its own buyer update, its own approved remedy and its own closure. Assign the carrier issue a single operational owner to avoid contradictory actions, while keeping the two commercial resolutions separate.

Record the final state per order: what it contained, the shared tracking evidence, and how any exception was resolved. If shared-parcel combinations keep producing channel or notification mismatches, describe the pattern and your platform through a Prism consultation and confirm scope, responsibilities, fees and terms before any work begins.

Shared parcel order map

Complete one map per combined parcel using genuine internal references. Every packed unit must belong to exactly one order. The sheet records the linkage; it does not merge the orders, move money or authorize remedies.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.