Skip to main content

Asynchronous / Batch Workflows

Asynchronous workflows allow shippers to generate tracking codes and labels in-house and send shipment data to DashLink later in scheduled batches.

This model is often used by high-volume fulfillment centers or operations with automated sorting and label-printing systems.

How it works​

  1. Generate tracking code
  2. Print and apply the label
  3. Ship the parcel
  4. Send batched create-delivery requests to DashLink
    • Typically once a day or every few hours

Benefits​

  • Eliminates real-time API dependency during fulfillment
  • Suitable for large batch or automated operations
  • Allows custom or specialized label generation

Risks​

This can produce exception statuses such as:

  • parcel_awaiting
  • parcel_delayed

Create-delivery calls may fail​

Examples:

  • Invalid or unserviceable address
  • Missing required fields
  • Incorrect facility configuration

If the label is already on the package, these errors cannot be corrected easily.

Tracking code collisions​

You must ensure tracking codes are globally unique.

Best practices​

  • Validate addresses upstream (cart/checkout) before label generation
  • Ensure tracking codes follow DashLink formatting rules
  • Run reconciliation to detect parcels that reached facilities before being created
  • Keep webhook ingestion running continuously
  • Coordinate arrival delay settings with DashLink during onboarding