Who Should Send The Shipment Confirmation — Merchant, Warehouse, Or Carrier?

Shipment Confirmation A message or system update confirming that an order or shipment has been dispatched. That confirmation can be produced by different parties — merchant, warehouse (3PL), or carrier — depending on commercial terms, system integrations, and customer expectations.

Ownership of the shipment confirmation is both contractual and practical. The party that controls the physical release of goods is usually best placed to confirm dispatch, but commercial realities — marketplaces, drop-ship models, and multi-party fulfillment — introduce nuance. The choice affects timing, data completeness, and responsibility for errors.

Merchant Responsibilities

Merchants are typically the party responsible for customer-facing confirmations. When a merchant arranges shipping or owns the customer relationship, they should send a confirmation to the buyer that includes tracking and expected delivery. Merchants must also ensure internal systems (order management, invoicing) reflect the dispatched status for accounting and returns.

• When Arranged By Merchant: Merchant triggers confirmation after the pack-and-ship event — this may come from an internal WMS or a 3PL callback.
• Customer Notifications: Merchant handles notification cadence (email, SMS) and is responsible for refund/return policies tied to ship date.

Warehouse / 3PL Responsibilities

Warehouses physically release goods and therefore are often the authoritative source for proving dispatch. In 3PL relationships, the warehouse typically sends a system-to-system confirmation (API or EDI) to the merchant and sometimes the carrier. This confirmation contains the granular data merchants need for inventory reconciliation and marketplaces need for order status.

• When Warehouse Should Send: If the warehouse performs picking, packing, and tendering to the carrier, it should emit the confirmation to all upstream systems immediately after pickup or handoff.
• Service Level Agreements: SLAs should define the maximum time between pickup and confirmation transmission — typically measured in minutes for e-comm fulfillment.

Carrier Responsibilities

Carriers provide tracking and status updates once freight is in their control. Their confirmations (tracking events, scans, pickup confirmations) are authoritative for transit status and final delivery evidence. Carriers do not always supply item-level SKU detail, so carrier messages usually complement, rather than replace, merchant or warehouse confirmations.

• Carrier Events: Pickup confirmation, in-transit scans, and delivery scans are used to update customer-facing tracking and confirm actual transit milestones.
• Limitations: Carriers typically lack vendor SKU-level itemization — if that detail is required, it must come from the warehouse or merchant.

Recommended Pattern For Most Fulfillment Flows

Implement a two-tier confirmation pattern: the warehouse (or shipping location) emits the initial shipment confirmation with full item and package detail to the merchant/OMS and marketplace; the carrier emits tracking and pickup confirmations to both shipper and recipient. Systems reconcile these two messages to detect discrepancies.

Agreements should specify which confirmation is the source of truth for billing, inventory decrement, and chargeback disputes.

Practical Clauses For Contracts And SLAs

To avoid disputes, contracts between merchants and warehouses should state:

• Timing SLA: Maximum time between pickup and confirmation transmission.
• Data Schema: Required fields and accepted formats (EDI, API schema versions).
• Exception Handling: How to surface and resolve mismatches between warehouse and carrier confirmations.

In short, the Shipment Confirmation is most reliable when the party that performs the physical release (warehouse/3PL) supplies the initial, detailed confirmation and the carrier supplies the transit and delivery events. Merchants remain responsible for customer-facing notices and for reconciling confirmations from both warehouses and carriers under clearly defined SLAs.