Advance exchange: the return leg nobody is watching

What an advance exchange actually is

An advance exchange is a replacement shipped to the customer before the faulty item comes back, usually under a warranty or a service contract, with a prepaid label and a deadline for returning the original. Every page that explains this explains the outbound leg, which is what a support plan sells, and it's the easy half. The moment the replacement ships you hold two open orders traveling in opposite directions, and the one coming back carries your money. The half going out has a dashboard. The half coming back has a spreadsheet. Microsoft gives a Surface customer 10 calendar days to post the original back and bills the retail price of the device plus shipping and handling if it doesn't arrive, and the only thing between those two outcomes is a parcel nobody is watching.

Three things go by this name.

• Warranty and service cross-shipment: the manufacturer or its service provider ships a working unit first and the customer returns the faulty one inside a stated window. This page uses that sense.
• A service contract with an exchange fee: in industrial and field-service agreements the same words mean a component swap against a fee, not a warranty benefit. Different commercial object, different accounting entry.
• A returns-portal catalog rule: in some DTC returns software it means swapping for a different product rather than a different variant. Nothing ships early, and the mechanic you want is an instant exchange.

How an advance exchange runs, step by step

1. The fault is reported and verified, often by a diagnostic or a triage rule rather than a person.
2. A return authorization is raised against the original order, and the replacement is approved before anything is inspected.
3. The replacement order is created and released to fulfillment immediately, with a prepaid return label going out alongside it.
4. The customer ships the original back, on some plans in the replacement's own packaging, inside a window the merchant set.
5. The unit arrives, is inspected, and is repaired, refurbished, restocked or scrapped. If it never arrives, the customer is billed.

Four of those five steps are things you can watch happen. Step four is a promise. The work waiting at the far end of it is a reverse fulfillment order, the record of what it takes to process a return, and it doesn't open until somebody posts the parcel.

The return duty nobody reads

Two published advance exchange programs state their terms, and they don't agree. Microsoft asks for the original Surface back within 10 calendar days of the replacement arriving, and bills "Microsoft's retail price of the device plus a shipping & handling fee" if it does not. Visioneer allows 10 business days from the replacement's delivery date, bills "the replacement device and the currently advertised list price", and requires the faulty unit to travel back in the box the replacement came in.

Same promise, two different windows, one counted in calendar days and one in business days, plus a packaging condition on one and not the other. A stated timeframe is the easy part to copy. The operations that enforce it are not, which is how a merchant ends up with a window and no way to hold it.

The non-return charge is the loudest line in the document and the quietest topic in the field. It's a merchant charge against a customer who believes they returned the item, so it's a billing dispute, not a returns policy, on deadlines somebody else wrote: a cardholder has 60 days to assert a billing error, and the creditor has 30 days to acknowledge and two billing cycles, never later than 90 days, to resolve it.

Two orders now, and nobody watching either

An advance exchange doesn't close anything, it opens a second order. One broken promise has become two, and the second was raised automatically before anyone looked at the first.

• The replacement isn't actually there: the stock number said yes and the shelf said no. The warehouse finds out days later, the customer when a tracking number never moves.
• The faulty unit is posted and never scanned: the label was used, the parcel is somewhere, and your only view is an absence. Postage on scan-based return labels is charged at first use, so the billing job can't separate a customer who kept the item from a slow consolidator.
• The faulty unit lands and nothing closes it: it sits on a receiving dock uninspected, no disposition is made, and the unit is invisible to the next customer who wants one and to finance.
• Both legs break at once: the exchange was triggered by a fulfillment problem, so the replacement is picked from the same location, by the same process, with the same result.

Almost every brand does nothing about all four until the customer emails. Then a stalled exchange becomes a ticket for a helpdesk, a system for replying about problems rather than resolving them. Answering the customer and moving either order are different jobs, and the order management system holds both records while calling neither broken. Missing is the layer that watches both legs against the promise and acts on the one that stops: proactive e-commerce operations, a category rather than a better inbox.

What warranty law says about the duty you just imposed

Make a customer return something on your schedule or be billed and you have imposed a duty. On a full warranty, a federal statute has an opinion about that. Under the Magnuson-Moss federal minimum standards the warrantor must remedy within a reasonable time and without charge, and "shall not impose any duty other than notification upon any consumer as a condition of securing remedy", unless the warrantor can demonstrate that the duty is reasonable. The FTC's worked example is closer still: "A requirement that the consumer return a warranty registration card or a similar notice as a condition of performance under a full warranty is an unreasonable duty."

Disclosure binds too. A written warranty has to carry a step-by-step explanation of the procedure the consumer follows to obtain performance, and a return window that appears only in a confirmation email isn't that. If the exchange is paid for, the replacement is a sale and the FTC's Mail, Internet, or Telephone Order Merchandise Rule applies: ship inside the stated time or within 30 days, or give the buyer a choice between a definite revised date and a prompt refund. A no-charge warranty replacement isn't obviously a sale, so don't assume the rule reaches it. This is what the text says, not legal advice.

When cross-shipping is the wrong answer

Cross-shipping optimizes for speed toward the replacement, which skips the question underneath it: is a replacement right for this fault. Three times it's not. A batch defect, where the replacement carries the same fault. A mis-pick or a stock-sync failure, where the cross-ship comes from the location that already got it wrong. A delivery exception or damage in transit, where nothing was wrong with the product and a second shipment pays twice for one outcome. The fault reason is the cheapest signal in the flow and almost nobody routes on it. The return duty is a fair fraud control, and NRF and Happy Returns put fraudulent returns at 9 percent of all returns, but a fraud control isn't a fulfillment control.

Running an advance exchange without adding a failure mode

We built Keeyu on detect, decide, act. Detect from events the systems already emit: the replacement's allocation and pick, the outbound scan, the return label's first scan, the return still sitting unprocessed. Every failure mode above is the absence of an expected event inside an expected window, which is a detectable condition rather than a feeling. Decide against the promise rather than a queue position: is the replacement allocatable, is there stock elsewhere, is a cross-ship right at all or is it a repair or a refund. Then act: reallocate, expedite, chase the inbound leg before the charge job runs, or tell the customer where the replacement is. That's post-purchase operations doing the work.

Keeyu doesn't run a warranty program, doesn't repair or refurbish anything, and isn't a returns portal, a 3PL or a carrier. We don't write your warranty terms, and we replace none of those systems. We watch the two orders an advance exchange creates and act when one stops moving. Whether to offer advance exchange at all is a margin decision we don't make for you.

Every order is a promise, and an advance exchange is a brand making a second promise before it has kept the first. The replacement goes out ahead of a resolution while the faulty unit travels back unwatched and a billing job counts down. We detect the leg that stalls, decide what it needs, and act before anyone writes in. To see that on your own orders, book a Keeyu demo.

• National Retail Federation and Happy Returns. 2025 Retail Returns Landscape. NRF returns research.
• Microsoft Learn. Advanced Exchange replacement for Surface devices, updated 2026-07-14. Surface advanced exchange terms.
• Visioneer. Advance Exchange warranty plan terms. Visioneer advance exchange plan.
• Shopify developer documentation. Returns apps and reverse fulfillment orders. Shopify returns apps.
• United States Postal Service. Customer Returns label services. USPS return services.
• 15 U.S.C. 2304, Magnuson-Moss federal minimum standards for warranty, via Cornell Legal Information Institute. 15 U.S.C. 2304.
• 16 CFR 700.7, FTC interpretation of warranty registration cards, via Cornell Legal Information Institute. 16 CFR 700.7.
• 16 CFR 701.3, disclosure of written warranty terms, via Cornell Legal Information Institute. 16 CFR 701.3.
• 16 CFR 435.1, FTC Mail, Internet, or Telephone Order Merchandise Rule definitions, via Cornell Legal Information Institute. 16 CFR 435.1.
• 16 CFR 435.2, the same rule's shipping and cancellation duties, via Cornell Legal Information Institute. 16 CFR 435.2.
• 12 CFR 1026.13, Regulation Z billing error resolution, via Cornell Legal Information Institute. 12 CFR 1026.13.