What an Ecommerce Fulfillment Partner Should Be Able to Produce on Demand

Trust in an ecommerce fulfillment arrangement is not a feeling. It is a set of documents that exist whether or not anyone asks, and the test worth running is speed: how long does it take a provider to produce a specific record for a specific order from three weeks ago? A partner who cannot pull one is a partner whose reporting you will have to reconstruct from invoices. Order fulfillment evidence is the same stack of paperwork whichever building holds it; the only real variable is who can put a given number on screen inside ten minutes.

The proof-of-pick record

For a disputed line you want the item as it was on the bench, not as it was listed in a catalog. That means a scan or a photograph tied to the order number, with the SKU value the store actually sold and the quantity actually boxed. Where a labeling step sits between the two, the record should show both identities, because a claim of a wrong item is usually a claim about which identity the customer saw.

The count sheet, not the dashboard figure

A live stock number tells you what a system believes. A dated count sheet tells you what a person found in a bin, with the discrepancies beside it. Ask for the last cycle count on your three fastest SKUs and look at how many lines came back clean. An inventory position reported at 99.5% accuracy is a statement about a method; the count sheet is the evidence for it, and you are entitled to see the difference.

The carrier handover manifest

The document that proves a parcel physically left the building is the handover, and it is dated and timed against the lane's cut-off, not against your promise date. Our note on what a tracking number can prove goes through why a label event and a carrier scan are two different facts. Ask which of the two a provider's reporting is built on; if the answer is the first, your dashboard will disagree with every marketplace scorecard.

The exception log with names in it

Every warehouse has exceptions. The useful document is not the one that proves cleanliness but the one that proves handling: what happened, who on the shift owned it, when it was answered, and what the customer was told. Ask for a week of it. An exception log with empty owner fields is a filing cabinet, and one with named owners and reply times is an operation.

The reconciliation you can run yourself

Take one dispatch day, list the orders your store paid, and compare line by line with what the provider reports as dispatched. Anything unexplained is either a hold, a short pick, or a duplicate; all three are recoverable, and none of them is acceptable as a surprise. Our discrepancy and claims article sets out the evidence chain we keep for the disputed ones, including the limits of what a warehouse can prove after a carton has left.

What these records are for

Not for policing a partner on a good day. They are the reason a bad day costs money instead of a customer: a claim with a scan behind it settles, and a claim with a screenshot of a dashboard does not. If a provider treats the request as unusual, that is the finding, and it arrives before your volume does.

Two limits we would rather say out loud

We cannot produce a carrier scan a carrier never performed, and we cannot hand you a customs document that your broker holds; those records belong to other parties and we route you to them. Declared values are yours to set, and compensation on any claim is based on the declared value, which is why the figure on the entry is a question for your broker rather than a dial we turn.

Questions this desk gets asked

How far back should these records be retrievable?

Far enough to cover a customer dispute and a carrier claim. Ask a provider for a specific order from several weeks ago and time the answer; that measurement tells you more than a policy document.

Is a photograph of every parcel worth paying for?

Only on the lines where disputes cluster. Blanket photo capture raises handling cost on every order to insure a small number, and a scan tied to the order does most of the same work.

What if the provider says the data is internal?

Then the reporting you receive is a summary with no audit path. Agree what you can request before volume moves, because that conversation is much cheaper in the empty chair.

By Tony Zhang, FulfillDock by SBT. Compiled by the desk that answers these requests, from the record set it keeps for its own weekday dispatches. Published 23 October 2026, last checked 23 October 2026