Published November 2, 2026 · 3 min read

Size Exchanges at a 3PL: When Should Replacements Ship?

An exchange needs two linked movements. Decide the replacement release event, stock reservation and exception ownership before promising the new size.

247 Fulfillment TeamFulfillment centers in Canada and the U.S.

Evaluate size-exchange fulfillment as two linked movements: the original item coming back and the replacement variant going out. Before choosing a 3PL, decide which event releases the replacement, when its stock is reserved, and who handles a price difference or a return that never arrives. A warehouse that processes returns accurately still needs a separate instruction for the outbound exchange.

For an apparel or footwear brand, the failure is often visible to the customer before it appears in a report. Support promises the larger size, another order consumes the last unit, and the returned smaller size sits in inspection. Buying the complete exchange workflow means testing the promise, reservation and shipment together.

Choose the release event deliberately

There are three common policies. Each trades customer waiting time against inventory and non-return exposure. Your brand should own the policy and eligibility decision; the 3PL should execute the authorized release and report exceptions.

Policy Release condition What the buyer must resolve
Inspection first The correct returned item passes the approved check Inspection capacity and the customer's longer wait
Carrier acceptance first A defined return-carrier event is received An event is not proof of parcel contents or condition
Advance exchange The brand authorizes outbound before receipt Non-returns, security arrangements and customer follow-up

Specify the event precisely. A return label being created is different from a carrier accepting the parcel. “Return received” can mean delivered to the building or checked in against the actual item. The release condition must match the system event the integration can supply.

247's returns-processing service describes check-in, inspection, grading and inventory disposition. Use that scope as the inbound half of the discussion, then separately agree the outbound exchange authorization and timing.

Separate the promise from the stock reservation

A selected replacement size does not necessarily mean a unit is reserved. Shopify's current return and exchange guidance states that exchange inventory is not reserved until the return is processed. A returns app, order-management system or custom workflow may add a different reservation mechanism. Demonstrate the actual arrangement your store will use rather than assuming all systems behave alike.

Ask how long a reservation lasts, which system owns it, and what happens when a customer changes the requested size. Protect the exact eligible variant. A balance for the product family does not prove that the required colour and size are available. Expired or cancelled reservations should release once, with an audit record.

Use a case record that closes both movements

Connect the original order, return reference, expected inbound variant, approved replacement variant, release policy, reservation, any financial approval, outbound authorization and both tracking references. Keep customer correspondence in the support platform while providing the warehouse the fields it needs.

A customer changing from medium to large should update the authorized replacement, not leave two valid outbound instructions. A retry after a timeout must not create a second shipment. Where a replacement is genuinely lost and another is authorized, retain a distinct shipment reference under the same case.

Financial completion and physical completion also differ. An even exchange may have no product-price difference but still incur return transport and outbound handling. A more expensive replacement may need payment approval before release. The merchant owns refund, payment and customer-policy decisions unless another scope is expressly agreed.

Reconcile a small exchange cohort

Hypothetical example, using units rather than a performance benchmark. A brand approves 100 same-value size exchanges. Ten customers cancel before dispatch. Of the remaining 90 cases, 70 returned items pass inspection, 12 are delivered but await inspection, and eight have not arrived.

Under an inspection-first policy, the expected state is 70 replacements shipped and 20 open cases, assuming every approved replacement is available. The returned products have a separate reconciliation: 82 physically received, of which 70 passed and 12 await review. Counting 82 received parcels as 82 completed exchanges would overstate completion.

Assume each of the 70 completed cases incurs CAD $9 return transport, CAD $3 inspection, CAD $3.50 outbound handling and packaging, and CAD $10 outbound transport. These are hypothetical inputs, not 247 prices. Cost is 70 × $25.50 = CAD $1,785, excluding original delivery, tax, product losses and support. “Even exchange” does not mean cost-free fulfillment.

Test the awkward cases before signing

Ask finalists to demonstrate a sold-out replacement, wrong item returned, rejected condition, unpaid price difference, duplicate instruction, changed size, cancelled exchange and return-carrier event arriving late. Include a case with multiple items where only one line is exchanged. Confirm that an approved returned unit becomes sellable only after the relevant inspection and putaway steps.

The returns workflow guide covers recovery of the inbound item. Your exchange acceptance sheet should add reservation expiry, authorized outbound release and case-level reconciliation. Measure time from the chosen release event to dispatch as well as total customer waiting time; otherwise an efficient outbound station can conceal a slow inspection queue.

Ask for a quote covering the full cycle and exception ownership. If the desired advance-exchange integration is unavailable, compare inspection-first service with a clearly communicated customer promise. Bring 247 your exchange policy, sample case records and variant demand to define what can be supported before offering it at checkout.

Keep reading

All articles