Overview
DashLink Parcels is a parcel-optimized delivery solution built on top of the DoorDash Drive API.
While it shares infrastructure with the core Drive product, its payloads, behaviors, and operational flows are significantly different. This documentation covers everything needed to build a complete DashLink parcel integration.
When to use this documentation
Use this documentation exclusively when integrating shipments that use:
order_fulfillment_method = "parcel"- DashLink-specific operational settings (cutoff times, days of operation, arrival delays)
- DashLink-generated or shipper-generated parcel tracking codes
- Parcel-specific webhook events (e.g.,
parcel_labeled,parcel_scanned,parcel_received_to_redeliver)
Key differences from standard Drive
DashLink differs from DoorDash Drive “restaurant/same-day” deliveries in several ways:
- Longer networks — Parcel shipments move through mid-mile and regional sortation facilities, not just a courier pickup and dropoff.
- Multiple scans — Each shipment may produce multiple events as it moves through facilities.
- Custom tracking codes — Shippers may provide their own tracking codes (15–35 chars), or DashLink can generate them.
- Label-based workflow — Labels may be printed before the shipment enters DashLink’s system (asynchronous) or after a successful create call (synchronous).
- Special account configurations — Cutoff times, days of operation, and arrival delays profoundly affect delivery date calculations.
What you will learn
- How parcel shipments flow from label creation → facility arrival → mid-mile → last-mile → delivery
- How to perform synchronous or asynchronous parcel creation
- How address validation, phone numbers, and SMS settings affect the customer experience
- How to read and map parcel webhooks for live tracking
- How to generate, decode, or print labels
- How to structure multi-shipper and aggregator integrations