A delivery exception rarely ruins a customer relationship by itself. The difficult part is the hour after the first exception event appears: nobody on the seller's side can say who may contact the carrier, who may contact the customer, and who can approve a replacement. Those answers are much easier to settle while the parcel is still moving normally.
For sellers holding stock in China and releasing orders individually through cross-border parcel channels, the operating agreement should settle three things before the first outbound release: who monitors tracking, which evidence is retained, and who approves a commercial remedy. FulfillNexa by SBT can scope tracking follow-up and agreed exception handling within ecommerce and FBM fulfillment work, and the exception owner should be confirmed before launch. The sections below explain why each decision matters and what both sides should record.
Why exception responsibility should be agreed before dispatch
An exception is the moment a shipment's normal path is interrupted. It may be a missed scan, a held parcel, a failed delivery, an address query or a return to origin. The event itself does not tell you who will pay for the next step.
China fulfillment operations can follow carrier milestones and investigate exceptions using the order reference, tracking events and available packing or delivery evidence. That is operational follow-up. It is not the same as deciding that the seller will refund a buyer, that a marketplace claim will be approved, or that a replacement must be sent at a particular cost. Unless separately agreed in writing, those remain the seller's commercial decisions.
Separating the two roles is practical. When the same person both investigates and approves a remedy without written limits, small issues may be resolved quickly but without a consistent record, while larger issues wait for someone further up to be found. Recording the split in writing avoids both outcomes.
Agree who monitors tracking and what triggers action
Tracking review should have one named owner on each side. On the seller's side this may be an operations lead or customer service manager. On the provider's side it should be a defined function rather than a personal mailbox, so the arrangement survives staff changes.
Then agree what triggers action. A parcel with no new event for several days is not the same as one showing a customs hold, and neither is the same as one recording a delivery attempt. Both sides should agree which events are monitored only, which must be reported to the seller, and which should prompt the provider to raise an investigation with the carrier. Writing down that list is the first step and should be checked against the channels actually used, because a tracking number alone is not evidence that the carrier has physically accepted the parcel. The acceptance scan and subsequent events show that the goods are moving.
Consider the monitoring window as well. If the seller's customer service team answers buyers in a different time zone from the warehouse, agree which side speaks first and whether the seller must be notified before the buyer is contacted. Without that agreement, the common result is either two messages to the same customer or none at all.
Agree what evidence is retained and for how long
The quality of an exception investigation depends on the records behind it. Before launch, both sides should confirm what is kept for each order and where it is stored.
Useful records generally include the order number, the picked SKUs and quantities, the packed weight and dimensions recorded at packing, the selected carrier and lane, timestamped tracking events, and any packing photographs captured under the agreed workflow. If the seller provides special packaging or inserts, an approved packing example should be filed so it can later be compared with what was actually agreed if a dispute arises.
Two cautions apply here. Weight and dimension records describe the parcel as it left packing; they do not by themselves prove what was inside. Tracking events describe what the carrier reported, not the physical condition of the goods. Both sides should record the materials that exist and agree what weight each type of record carries when an exception is assessed, rather than treating any single item as decisive.
Also agree the retention period and who can access the records, including whether the seller can obtain materials directly for marketplace claims. Sellers usually need those materials quickly, and an access request that takes days may miss the deadline a customer or platform has set.
Set approval limits for replacements, refunds and returns
This is the item most often left vague. Unless separately agreed, customer refunds, warranties and marketplace decisions remain with the seller. The starting point is therefore clear: the provider investigates and reports, and the seller decides.
What still needs to be agreed is how the seller's decision reaches the warehouse, and what the provider may do without further instructions. Both sides can set a clear approval path: who inside the seller's business may approve a replacement, up to what order value or product category that person may act alone, and who approves above it. Any limited authority granted to the provider should be written, capped and reviewed periodically, not assumed from past practice.
Returns need a separate agreement. Return handling and logistics investigations vary by destination. If returned parcels are routed back to the China warehouses, receiving and inspection take place there; delivery points in the destination market do not receive customer returns or hold goods sent in for inspection. Both sides should confirm the return address, authorization process, inspection scope and what happens to the stock afterwards: restocking, quarantine or disposal. A further question is whether an uninspected return goes straight back into sellable stock. Holding returned shipments explicitly aside until someone with authority decides is the safer default.
Put the exception plan into the operating scope
The exception plan does not need to be long, but it should sit in the operating agreement rather than scattered across email threads. It should name the monitoring owner on each side, list the trigger events, describe the evidence files and retention method, and set out the approval path for replacements and refunds. It should also record which decisions the provider will not make on the seller's behalf.
Because product acceptance, charges and delivery arrangements are confirmed for each actual shipment, the plan should be reviewed again when a lane, carrier or product range changes. A process built around one parcel channel may not fit another, and the exception owner named at launch may no longer be the right person a season later.
None of this stops a parcel from going missing. What it does is make sure that when one does, the team knows who is watching, what is in the file, and who may make the call.
Common questions
What does the exception scheme cost?
The cost of the commercial remedies agreed in the plan must be settled in the agreement. Freight and goods value for a replacement, inspection costs for returned items and any restocking handling should each be confirmed against the quotation rather than assumed to be the provider's responsibility. Product acceptance, charges and delivery arrangements require shipment-specific confirmation, so set the amount limits together with the approval authority and route anything above them through the seller's internal approval.
What should the seller provide before launch?
At minimum, three things: a list of internal people who can approve replacements and refunds with their amount limits, a contact who can receive exception notifications, and the seller's return address and authorization process. If the seller has special packaging requirements, also provide a packing example and confirm how it will be filed. Without these, the process stalls waiting for confirmation when an exception occurs.
What if the provider misses an exception?
This is a responsibility question to settle in the plan beforehand: who monitors, how often tracking is reviewed and what happens after a missed report. In practice, the seller is better off keeping a sampling check on tracking rather than relying entirely on one side's monitoring. Agree at launch how often each side checks and how quickly a found exception must be shared.
Can the provider replace goods on my verbal instruction?
Do not assume so. A verbal instruction is difficult to trace and cannot be checked against an amount limit. Any replacement authorization should be written and stay within the agreed people and limits. If an urgent temporary authorization is genuinely needed, put a written record in place afterwards; otherwise neither side will be able to explain the cost at the next reconciliation.