When Seller Delivery Works as a Backup Channel
The courier rate is not the cost of a successfully delivered order.
A customer is expecting an order today. It is packed, but the primary route has stopped: a delivery slot is unavailable, a pickup location is overloaded, or the item cannot travel through the usual flow. A seller could respond by launching its own delivery operation across the catalogue. That decision can create a costly second operation around one local failure.
A better starting point is a narrower question: which segment can support a backup route financially and operationally? Seller-managed delivery does not require a fleet. The seller can work with a contractor, while retaining responsibility for coordinating the order from fulfilment through delivery and returns.
The potential reach is substantial. The US Census Bureau estimated US retail e-commerce sales at $292.9 billion in the second quarter of 2025 before seasonal adjustment. This is a measure of retail sales, not parcel volume or delivery profitability. It provides market context; it cannot tell an individual seller whether a backup route will pay for itself.
Measure the cost of a successful order
A single trip rate leaves out failed handoffs, returns, repeated customer contact and the time spent resolving exceptions. Calculate the complete cost for the period and segment being tested:
Full cost per successful backup delivery = (picking + packing + dispatching + route or contractor + support + failed attempts + returns + allocated fixed costs) ÷ number of delivered orders.
Use the same product, delivery area and promised window to compare this figure with the primary channel. Then estimate the impact of a failed delivery using the business’s own records: cancelled orders, lost contribution margin, compensation and, where measurable, lost repeat purchases. Keep those potential losses separate from delivery costs to avoid counting the same loss twice.
The comparison needs a decision threshold. A backup route can cost more per delivered order and still make sense if the avoidable loss during an outage exceeds that additional cost. That depends on the frequency and duration of disruption, the orders affected and the capacity available. The model does not establish a universal break-even point.
Seller fulfilment adds responsibilities
On Amazon, Fulfilled by Merchant allows sellers to manage fulfilment themselves and use it alongside Fulfillment by Amazon. Amazon describes settings for handling time, transit time and capacity. Its US seller-fulfilled process also includes a prepaid returns programme. These are Amazon-specific arrangements; they do not mean that every marketplace offers the same settings or return process.
This example makes the operating question visible. A seller must know which orders it can fulfil, how they move to a carrier, what customers are told and how returns enter the process. Before treating seller fulfilment as a backup, confirm the marketplace rules, inventory availability, delivery commitments and whether the intended switch is supported for that particular offer. The existence of two fulfilment options does not establish that an order can be switched between them after it is placed.
Get QTIM’s stories in your inbox
Join Medium for free to get updates from this writer.
Choose a scenario with a defined purpose and test it separately:
A zone near the warehouse tests density and travel time. A product that needs special handling tests packaging and the handoff. A disruption scenario tests how quickly the team can activate the alternative and return to the primary flow. None of these tests proves that the whole catalogue is ready to move.
Map the work between warehouse and support
The courier tariff may omit work already absorbed by the team: picking outside the regular wave, checking stock, assigning a carrier, contacting a customer again, returning an item to available stock and resolving compensation. Those actions belong in the pilot calculation even when no separate invoice identifies them.
Map the events for each order: accepted, picked, handed to the carrier, delivered, failed attempt, return and compensation. For each event, identify an owner, a source of truth and the action required when the expected update does not arrive. A status in the marketplace, warehouse system and support tool should describe the same order; reconciliation is needed when they disagree.
Delivery also affects the customer’s decision before an order is placed. In its 2025 survey, DHL reports responses from 24,000 online shoppers in 24 markets and identifies delivery and returns as factors in cart abandonment. This is survey evidence about shoppers’ stated behaviour, not proof that a backup route improves conversion or meets a particular service level. For the pilot, measure the experience directly: did customers receive the promised window, accurate updates and a workable return path?
The Qtim team designs e-commerce systems and integrations between warehouse management, delivery services and marketplace APIs. A shared event map helps the team establish which system supplies each status and where an exception needs attention.
Set boundaries before the first pilot order
Choose one delivery area or a group of products with similar handling requirements. Define the delivery window, appoint an operations owner and list orders excluded from the test. For example, keep products with an untested return process in the primary flow until that process is ready.
Record the baseline before launch: cost per successful delivery, share delivered within the promised window, cancellations, returns, support contacts and contribution margin. Compare the backup with the primary route for the same segment and time window. Record the frequency of activation and the time needed to switch, because an option that cannot be activated during a disruption will not protect the promise.
There is also a valid alternative: repair the primary route. A backup is worth testing when the main flow cannot cover a critical scenario or recovery takes longer than the business can wait. Otherwise, the extra operating burden may outweigh its value.
Scale after two checks
First, does the full cost of successful delivery fit the economics of the tested segment, including the cost of keeping backup capacity available?
Second, can the team consistently meet the promise on timing, order status and returns?
Positive results on both support expanding the specific scenario tested. If either fails, adjust the route, keep it limited or close it. The decision is tied to the segment and its observed performance, not a universal order-volume threshold.
When the primary flow repeatedly misses orders or delivery windows, the Qtim team can help map the pilot’s events and integrations. The starting point is a defined scenario, a calculation and a list of systems that need consistent order statuses.
