Andrew Schmid is Chief Product Officer at Route. Package protection, tracking, notifications, claims, returns, exchanges, warranties – the whole tail end of the transaction that most brands treat as plumbing.
Here’s what everybody covering this space keeps missing: they write about post-purchase as a bundle of features to buy. Better tracking. Faster claims. Fewer support tickets. That’s the trade press version of the story, and it’s the wrong story.
The real story is that most brands don’t have a post-purchase strategy. They have a post-purchase org chart, and they’ve mistaken it for one.
The fine print
Walk into any retailer and ask who owns the customer after checkout, and you’ll get six honest answers. Marketing owns the promise. Ecommerce owns conversion. Operations owns fulfillment. Care owns the complaint. Finance owns the refund. Risk owns fraud.
Every one of those groups is doing its job correctly. That’s the fine print nobody wants to sit with: the fragmentation isn’t a failure of execution. It’s the org chart working exactly as designed. It just wasn’t designed around the customer – it was designed around internal accountability, and those are not the same target.
Notice what that org chart optimizes for at each handoff. Care wants the ticket closed. Finance wants the refund processed cleanly and within policy. Risk wants the fraud exposure contained. Ops wants the exception out of the queue. Every one of those is a locally rational objective, and none of them is “did this customer get what she came for.” String six locally rational objectives together and you don’t get a coherent customer outcome – you get a relay race where each runner hands off the baton the moment it’s no longer their problem.
The customer doesn’t experience six departments. She experiences one brand deciding, in real time, whether the thing it promised before checkout is the thing it’s willing to deliver after.
The mechanics
Trace what actually happens when a product shows up in the wrong size.
The company already spent to acquire that customer. The customer already converted, already paid, already put revenue inside the business. Then the product is wrong, and the standard machinery treats that as a transaction to unwind: generate a label, ship it back, inspect it, refund it, and – if you’re lucky – hope she starts over.
That’s not what she wanted reversed. She wanted the product. She still wants the product. What the system gave her instead was an invitation to leave.
Sit with the economics of that for a second, because they’re worse than they look. The acquisition cost is sunk – spent whether the transaction survives or not. The revenue is already inside the business. The customer has already proven demand by paying once. A refund doesn’t just erase the sale; it converts a fully paid-for, demand-confirmed customer back into a cold lead the business will have to pay to reacquire, assuming she comes back at all. The company is choosing to re-run the most expensive part of the funnel – the part it just finished paying for – because the exchange workflow was harder to build than the refund workflow.
Run that forward and the second-order effect is the one that matters more than the first: every unnecessary refund isn’t just a lost sale, it’s an admission that the business would rather destroy value it already captured than build the muscle to route her to an exchange. A frictionless swap keeps the revenue inside the business and probably produces a better experience than the refund does. That’s not a nice-to-have. That’s the entire argument that customer experience and margin are in tension falling apart under its own weight – because in this specific decision, the higher-effort customer outcome and the higher-margin business outcome are the same outcome.
The same logic runs through lost and damaged orders. A fast replacement can beat a refund on both sides of the ledger at once: better for the customer, who gets what she actually ordered, and better for the business, which keeps the transaction instead of unwinding it and eating the reacquisition cost later. A proactive notification, sent before the customer has to ask, can eliminate the contact entirely – no ticket, no hold time, no chance for the silence itself to become the story she tells about the brand. None of these are service upgrades. They’re the same commercial decision made three different ways, all pointing at preserving value the business already has instead of destroying it and hoping to win it back.
What it means for how you measure this
First, the standard post-purchase dashboard is measuring the wrong thing entirely. Ticket volume, average handling time, refund rate, contact deflection – these describe how efficiently the business processed an event. None of them describe whether the business preserved the customer or the value of the transaction. A chatbot can deflect a contact without solving anything. A returns operation can issue a fast, clean refund and still land on the worst commercial outcome available: the customer keeps her money and has no reason to come back. Every one of those metrics can hit target in the same quarter that customer lifetime value quietly erodes, because they were never built to see it.
Second, that gap is invisible by design, which is what makes it dangerous. Nobody exits a confusing return flow and files a report on their reduced lifetime value. They just don’t come back. The damage shows up months later as softer repurchase and heavier paid-acquisition dependence, fully disconnected from the moment that caused it – by which point it’s been absorbed into a dozen other explanations: market conditions, competitive pressure, a marketing team that isn’t performing. The actual cause, a returns flow that quietly taught customers not to bother, never makes it into the postmortem. If you’re only watching operational metrics, you will never see the mechanism doing the damage, and you’ll spend the resulting budget fixing the wrong department.
That’s the deeper problem with measuring post-purchase operationally: it doesn’t just miss the value being destroyed, it actively rewards the behavior destroying it. A team hitting its refund-processing-time target has no visibility into, and no incentive to care about, whether that refund was the right resolution in the first place.
The signal behind the signal
There’s a distinction buried in here that’s bigger than returns policy: the difference between an inconvenience and a relationship-level failure is almost always time. A lost package with a replacement already moving is a problem. A lost package the customer spends six days proving is a referendum on the brand.
Which means the real signal isn’t whether something goes wrong – it will. The signal is how long the brand lets the customer sit inside the problem before acting like it matters. Schmid’s framing on this is worth sitting with: a neutral post-purchase experience behaves more like a negative one than a positive one. “Nothing bad happened” isn’t a competitive advantage. It’s the floor. An order that arrives on time, as expected, doesn’t earn the brand anything in the customer’s mind – it simply confirms the deal she already thought she was getting. It’s the failures, handled fast and well, that actually move the relationship, because they’re the only moments where the brand has to prove the promise was real under conditions where it would have been easier not to.
Read that as a leading indicator and it says something uncomfortable about where AI investment in this category is headed. The lazy version of AI in post-purchase makes the customer work harder to reach a human – a bot that closes tickets and repeats policy, optimizing an internal efficiency number nobody outside the building cares about. It’s automation aimed at the metrics in the section above, which is exactly the problem: it makes the wrong measurement more efficient.
The version that actually matters automates the resolution itself: understand what happened, determine what the customer actually wants, apply the rules that matter, remove the approvals that don’t. That’s a materially harder build. It requires the brand to actually decide, ahead of time, what a good outcome looks like for a lost package versus a wrong size versus a damaged item – decisions most organizations have never forced themselves to make explicitly, because the fragmented org chart let each department make its own local version of that call. One approach makes the existing process cheaper. The other changes the economics of the process. Brands buying the first and calling it innovation are going to find that out the hard way, probably around the same time their retention numbers do.
Where this leaves the category
Checkout made sense as the finish line back when the hard problem was getting people comfortable enough to transact online at all. That problem is solved. The market is very good – arguably too good – at generating transactions. There is more acquisition technology, more targeting precision and more conversion tooling available today than at any point in ecommerce history, and virtually none of it has anything to say about what happens the moment after it succeeds.
The harder, more valuable problem now sits on the other side of the purchase, where the customer stops evaluating the product page and starts evaluating the company. She’s no longer watching the brand make a promise. She’s watching it decide whether to keep one, under conditions the brand didn’t choose and can’t fully control – a carrier lost the package, a size ran differently than expected, a warehouse made a mistake. What she’s actually evaluating isn’t whether something went wrong. It’s what the brand does next, and how much of her own time it costs her to find out.
Most brands have built the processes to survive that moment. Very few have built a strategy to win it. The ones treating post-purchase as an economic-architecture problem – organized around preserving the transaction and the relationship, not around routing tickets – are the ones who’ll compound, because every preserved transaction lowers their dependence on the next paid acquisition. Everyone else is going to keep optimizing the funnel and wondering why retention won’t move, without ever tracing the leak back to the six departments quietly working against each other on the other side of the buy button.
