Fulfillment Delays: Put Shipping Evidence And Refund Costs In The Contract

When an ecommerce business outsources warehousing and dispatch, the operational work moves, but the seller's shipping promises to customers do not. That is the core issue a fulfillment agreement needs to solve. Under the Federal Trade Commission's Mail, Internet, or Telephone Order Merchandise Rule, the seller remains responsible for the shipping representation it made, whether it had a reasonable basis for that representation, whether it offered the customer a delay or cancellation choice when required, and whether refunds were handled promptly if the customer did not consent to delay.

That means a fulfillment contract should do more than price storage, pick, and pack. It should define when an order is truly ready for warehouse action, what counts as shipment, what evidence proves a carrier actually took possession, when exceptions must be escalated, and how internal reimbursement works if delays trigger refunds, reshipments, or credits. This article focuses on that upstream agreement and joined shipping-evidence task for ordinary physical merchandise. It is general information only and is not legal advice.

The Seller's Promise And The Warehouse Record

The main legal and commercial risk is a mismatch between customer-facing promises and warehouse-facing evidence.

A seller may advertise that an item ships within 2 business days while the fulfillment provider measures success by creating a label, placing the order in a queue, or marking it ready to ship. Under the FTC rule, shipment means the merchandise is physically placed in the possession of the carrier. That is narrower than many warehouse status labels, and it matters.

A simple hypothetical helps test the draft. Assume your store accepts an order on Monday at 10:00 a.m., payment clears immediately, and the order contains ordinary physical merchandise already shown as in stock. Your storefront says ships within 2 business days. The provider imports the order at 10:15 a.m., prints a label on Tuesday, and the carrier picks up on Thursday afternoon. If that pickup misses the promised shipping window, the contract should make it easy to identify the problem, document what happened, and allocate provider-side financial consequences without confusing them with what the customer is owed.

When Does The Seller's Shipping Clock Start?

The FTC rule does not tie the clock to when the warehouse imports an order. The key concept is receipt of a properly completed order.

For covered sales, that generally means the seller has received both payment, or the relevant authorization, and an order containing the information needed to process and ship it. If payment is later dishonored, the timing analysis can change. The practical point is that the legal clock is tied to the seller's receipt of a properly completed order, not to a later provider timestamp.

That is why a contract should not define provider deadlines only by saying within X hours after receipt. It should also explain what data the seller must transmit, when an order is deemed transmitted, and when the provider must acknowledge whether the order is actionable or blocked by an exception.

For example, the agreement may state that:

• an order transmission is complete only when required fields, SKU mapping, ship-to address, service level, and payment-release status have passed through successfully;
• the provider must send an acknowledgment or exception notice within a negotiated period such as 30 or 60 minutes during operating hours;
• orders missing information, failing fraud-hold release, or tied to unavailable inventory are not treated as warehouse-ready until the seller is notified of the exception; and
• the provider must identify whether the hold is a data issue, inventory issue, packaging issue, or carrier-capacity issue.

Those are negotiated examples, not statutory cutoffs. Their purpose is to stop the later argument that the warehouse never really had the order, or had it too late, when the seller is reconstructing whether a delay notice should have gone out.

If your storefront does not clearly state a shipping time, the FTC rule generally expects shipment within 30 days after receipt of a properly completed order. There is also a 50-day baseline in the specific situation where the buyer applies to the seller for credit to pay in whole or in part. Most ecommerce merchants will still want much tighter internal timelines because customer expectations and marketplace standards are usually stricter than the federal default.

Label Creation Is Not Shipment

Many fulfillment disputes turn on sloppy status language.

A warehouse may report that an order is processed, manifested, ready to ship, or awaiting carrier scan. Those events can all be useful operationally, but they are not the same thing. Under the FTC rule, shipment occurs when the merchandise is physically placed in the possession of the carrier.

So a printed label is not enough by itself. A carton sitting on a dock is not enough by itself. A tracking number is not always enough either if the carrier has not actually taken possession.

Your agreement should distinguish at least three events:

• Warehouse-ready: the order has been picked, packed, and staged with documents complete.
• Label-created: a carrier label or manifest exists in the system.
• Carrier-handover: the carrier has actually taken physical possession of the parcel.

Only the last event aligns with the rule's shipment definition. The first two are still useful because they act as early-warning points. If many orders are stuck between label creation and carrier handover, the seller may need to change customer-facing messaging, send delay options, add pickups, or suspend an aggressive shipping claim.

The contract should also address proof of carrier possession. Depending on the provider's model, that may include pickup manifests, carrier scan files, trailer close-out records, carton-level acceptance events, or other operational records that can be reconciled across systems. The point is not to require one national format. The point is to avoid a situation where the provider can show only that it intended to ship.

This distinction also helps separate a shipping representation from a delivery guarantee. A promise about shipping is about when the seller expects to place the merchandise in the carrier's possession. It is not necessarily a promise about the date the package will arrive to the buyer. Your storefront copy and your fulfillment agreement should keep that line clear.

Contract Terms For Early Warning

The best fulfillment agreements do not just assign blame after the fact. They create an exception-and-escalation system early enough for the seller to make the customer decision the law requires.

At a minimum, negotiate around these questions:

• Order transmission and acknowledgment: When is an order treated as received by the provider, and how quickly must exceptions be reported?
• Daily cutoff times: What are the real same-day or next-day processing cutoffs for each service level, weekend schedule, and holiday period?
• Inventory exception alerts: How quickly must the provider flag stock shortfalls, damaged inventory, SKU mismatches, or quarantine holds?
• Carrier pickup evidence: What records show physical carrier possession, and when must those records be available to the seller?
• Joined record access: Can the seller export order, inventory, label, manifest, pickup, exception, and cancellation data in a usable format?
• Capacity changes: How much notice must the provider give if labor shortages, system outages, weather events, or peak surcharges reduce throughput or pickup windows?
• Customer-action escalation: When must the provider escalate an issue so the seller can decide whether to revise a shipping representation, send a delay notice, pause sales of a SKU, or stop advertising expedited dispatch?

These provisions matter because the FTC rule focuses on reasonable basis and prompt delay handling. If your provider learns at noon that a carrier has canceled pickup, but the contract lets it wait until a later review cycle to mention that fact, the seller loses time it may need for customer communications.

You can also require monitoring tools. The FTC merchandise-order business compliance guide discusses reasonable preventive efforts such as contract terms requiring compliance-related cooperation, seeding orders to monitor performance, and watching for unusual surges in customer complaints. In practice, that can mean test orders, exception-rate thresholds, and regular reporting on the gap between label-created and actual-handover times.

None of those steps makes the seller immune. They are risk controls, not a transfer of liability.

Delay Notices Need Useful Warehouse Alerts

If the seller cannot ship within the promised time, or within the rule's default timing when no time was clearly stated, the seller generally must offer the buyer a clear choice: consent to a delay or cancel for a prompt refund. That offer has to be made within a reasonable time after the seller first becomes aware it cannot ship on time, and no later than the applicable shipping deadline.

The seller may also need to give a definite revised shipping date if it has a reasonable basis for one. If it does not have a reasonable basis for a definite date, the notice must say so and explain the reason for the delay. The rule then applies different consent mechanics depending on whether the revised delay is definite or indefinite, and on how long the revised delay is.

This is where joined evidence matters. The provider's exception feed should tell the seller enough, and early enough, to decide which path applies. A vague status such as carrier issue is rarely enough. The seller needs to know whether the order can still make the promised shipping date, whether a definite new handover date is supportable, or whether no reliable date can be given yet.

Require the provider to flag at-risk orders promptly, explain the operational cause, identify whether a definite handover date is supported, and update the seller when facts change. Order-level records should preserve that sequence.

Keep the legal roles separate. The seller's delay notice to the customer is one issue. The provider's obligation to reimburse the seller for part of the resulting loss is another. A well-drafted service agreement helps the seller do the first without waiting for the second.

Who Pays When Delays Cause Refunds, Reshipments, Or Credits?

Under the FTC rule, if a customer does not consent to a delay, the seller's refund obligation is not replaced by a service credit from the warehouse. The seller cannot treat an internal credit memo as though it satisfies the customer-facing refund duty.

That means the agreement should separate at least three buckets of money:

• Customer refunds: amounts the seller must return to the buyer when cancellation or refund rights arise under the rule.
• Customer remediation costs: reshipments, upgraded freight, replacement inventory, support labor, and similar commercial costs the seller may choose or need to incur.
• Provider-side adjustments: service credits, fee reversals, reimbursements, or other internal remedies between seller and provider.

A realistic clause may say that if a delay is caused by the provider's failure to meet stated fulfillment service levels, the provider will issue specified fee credits and reimburse certain documented out-of-pocket costs up to negotiated caps, subject to exclusions such as seller inventory inaccuracies, bad address data, force majeure wording, or carrier-wide network disruptions.

But whether a broader indemnity, limitation-of-liability carveout, or refund-cost pass-through is enforceable depends on the contract language, the governing law, and the facts. Businesses should not assume there is a universal rule that the warehouse must absorb all refunds, or that any indemnity clause will always be enforced as written. Fault allocation, exclusions, indemnities, and recoverable cost categories in a supplier agreement should be reviewed under the actual contract and applicable state law by independent qualified US counsel.

In negotiation, ask practical questions such as:

• Are seller-paid customer refunds recoverable only when the provider was the sole cause, or also when it was a contributing cause?
• Are freight charges, packaging charges, and payment processing losses included or excluded?
• Do service credits reduce invoices only, or can the seller receive cash reimbursement for direct losses?
• Is there a claim window, documentation standard, or monthly cap?
• Are peak periods handled differently?
• Does the limitation of liability carve out repeated SLA failures, major data issues, or serious operational breakdowns?

Shipping Records That Can Be Joined

The FTC does not impose a standalone recordkeeping mandate with one fixed retention period for every seller, but its guidance makes clear that documentation matters. In an enforcement action, a seller that cannot document systems and procedures may face a rebuttable-presumption problem on reasonable basis.

For fulfillment relationships, the goal is not to hoard every log forever. The goal is to preserve enough joined evidence to answer the core timing questions for each order.

Useful order-level records often include:

• the date and time the seller received the properly completed order;
• the customer-facing shipping representation in effect at the time of sale;
• the date and time the order was transmitted to the provider;
• the provider's acknowledgment or first exception notice;
• inventory status at the relevant time;
• pick-pack completion time;
• label creation time;
• actual carrier-handover evidence;
• any customer delay notice sent and the contents or template used;
• any customer consent, cancellation, or non-response outcome recorded under the applicable notice path; and
• the date and method of any refund.

FTC guidance also notes that businesses often ask how long to keep records and points to federal and state limitation periods as practical considerations. That is not the same as a universal retention mandate. Your business should choose a retention approach that fits its risk profile, platform evidence needs, and the states where it operates.

Frequently Asked Questions

Does Outsourcing Fulfillment Shift FTC Responsibility To The Warehouse?

No. FTC guidance states that the seller is the party responsible under the rule, even when a fulfillment house or drop shipper is involved. Contract terms and monitoring can reduce risk, but they do not transfer the seller's compliance duty.

Can We Define Shipment As Label Creation In The Contract?

Internal milestones can distinguish processing stages, but using label creation as the legal substitute for shipment creates risk. The FTC rule defines shipment as physical placement in the carrier's possession.

Do We Have To Give A Refund Within Seven Calendar Days?

No universal seven-calendar-day rule applies. The FTC rule uses prompt-refund standards tied to payment method, including seven working days in many situations and a billing-cycle standard for certain credit-sale refunds. The answer depends on how the customer paid and which refund branch applies.

Can A Service Credit Replace The Customer's Refund?

No. A service credit is an internal provider remedy. It does not replace the seller's customer-facing refund obligation when the rule requires a refund.

Key Takeaways

• The seller remains responsible for FTC merchandise-order rule compliance even when a fulfillment house handles storage and dispatch.
• The legal shipping clock is tied to receipt of a properly completed order, not when a warehouse later imports the order.
• Shipment means physical carrier possession, so label creation and ready-to-ship statuses should be treated as separate operational milestones.
• Your fulfillment agreement should require clear order acknowledgments, exception alerts, carrier-handover evidence, joined record access, capacity-change notice, and customer-action escalation.
• Customer refunds and delay consent are separate from provider service credits or reimbursement, and broader fault allocation terms need contract- and state-law review.
• Good joined records help support shipping representations, delay handling, and internal recovery discussions when something goes wrong.

To explore fulfillment agreements, ecommerce terms and shipping-evidence clauses through the Sprintlaw platform's business-document services, contact (888) 449-8437 or team@sprintlaw.com.