Skip to main content

Key Concepts

This page defines the foundational concepts used throughout all DashLink parcel integrations.

Order Fulfillment Method​

All DashLink parcel requests must include:

"order_fulfillment_method": "parcel"

This distinguishes parcel deliveries from standard Drive use cases.

Tracking Code / External Delivery ID​

A parcel’s tracking code appears in several fields:

  • external_delivery_id — Shipper-provided or empty string if DashLink will generate
  • pickup_reference_tag — Internal tracking identifier, always stable

Both serve as unique tracking identifiers in different parts of the system.

Tracking code rules​

  • Must be 15–35 characters
  • Must be unique
  • Recommended: prefix with a 3-letter shipper code (e.g., DLK123...)
  • Avoid leading zeros

Facility Concepts​

DashLink operations depend on precise facility modeling:

Origin Facility​

Where the shipment originates (warehouse or store). Identified by origin_facility_id.

Mid-Mile Facility​

Regional facilities where inbound parcels are scanned, sorted, and dispatched further. Example webhook events:

  • parcel_mid_mile_arrived
  • parcel_mid_mile_departed

Destination / Last-Mile​

Where Dashers pick up parcels for final delivery.

Address Components​

DashLink requires structured address components:

dropoff_address_components.street_address
dropoff_address_components.sub_premise
dropoff_address_components.city
dropoff_address_components.state
dropoff_address_components.zip_code

DashLink may also return updated address components after validation.
(See Address Validation Best Practices.)

Package Metadata​

Each parcel is modeled as exactly one item:

  • Name
  • Height, Width, Length
  • Weight
  • Volume (auto-computed or provided)
  • Description
  • External order ID

Only one item is currently allowed per parcel request.

Label Types​

DashLink supports:

  • ZPL 203 dpi
  • ZPL 300 dpi
  • PDF (4x6")

Labels may be:

  1. DashLink-generated, returned as base64
  2. Shipper-generated, using the tracking code and barcode requirements

Proof of Delivery (POD)​

Upon a successful delivery, DashLink will return:

  • A dropoff verification image
    • URL of the POD image will be valid for 7 days
    • Recommended to download and store the image on your servers
    • A refreshed POD URL (valid for another 7 days) will be returned by calling our delivery status endpoint
  • A signature image if signature was required

Delivery Notifications​

SMS settings dramatically impact delivery outcomes:

  • “Dasher confirmed” SMS is recommended to prompt recipients to update delivery instructions
  • "Delivery created" SMS must remain off for parcels, because retries would retrigger it