Reference Data: DoorDash Baseline Account Fields [Guide]

Modified on Wed, 16 Sep at 12:12 PM

Article 1: DoorDash Onboarding Requirements and Configuration Guides [Information]Article 2: Reference Data: DoorDash Baseline Account Fields [Guide]Article 3: Reference Data: DoorDash Client (Billing) Account Fields [Guide]Article 4: Reference Data: Order-Level DoorDash Fields [Guide]
Onboarding and ConfigurationBaseline Account(Billing) AccountOrder-Level Fields
   You are hereYou are here   

   

This reference lists the carrier-specific DoorDash Baseline Account fields used in techSHIP configuration.


Use it together with the linked Baseline Account setup steps: the setup guide covers the shared configuration flow, while this article defines the confirmed field values, field behavior, and carrier-specific configuration details.

    

   
Note   

  

For a complete overview of supported carriers and related setup guides, refer to techSHIP supported Carriers - Master List [Guides List].

   

   

   


Warning

Review DoorDash Onboarding Requirements and Configuration Guides [Information] before configuring the Baseline Account so required credentials and account settings are confirmed.

 
   


TABLE OF CONTENTS


Adding a Baseline Account


Follow the UI Navigation steps in How to Add a Carrier Baseline Account [Step-by-Step guide], using the carrier-specific values provided in this guide.

   

Go to Go to    
Article: Essential ConfigurationArticle: Carrier-Specific
Essential Configuration
 
Carrier-Specific
This article 

   

Carrier-Specific Instructions

   Return to Go to 
Article: Essential ConfigurationArticle: Carrier-Specific
Essential ConfigurationCarrier-Specific

   

Carrier Tab


The Carrier tab contains the Baseline Account fields used to identify the carrier connection and define confirmed carrier-specific behavior. Highlighted fields indicate mandatory and optional configuration groups.




A

Developer ID: Identifies the DoorDash developer credential used with Key ID and Signing secret to authenticate the Baseline Account.

     

B

Key ID: Identifies the DoorDash signing key used with Developer ID and Signing secret.

     

C

Signing secret: Provides the secret used with Developer ID and Key ID to authenticate the DoorDash connection.

     

D

DashLink-approved custom prefix: Defines the DoorDash-approved prefix used when custom external delivery IDs are configured.

Use only a prefix approved by DoorDash. Configure this field together with Custom total length.

     

E

Custom total length: Defines the total length of the custom external delivery ID used with the approved custom prefix.

Custom external delivery IDs must be unique, 15–35 characters, and cannot start with zero. Configure this field together with DashLink-approved custom prefix.

     

F

Pickup external business ID: Identifies the DashLink Parcel business/account used by DoorDash for this Baseline connection.

     

G

Origin facility ID: Identifies the DoorDash origin facility used for pickup processing. The configured facility determines the pickup location used by DoorDash.

     

H

Pickup business name: Provides the pickup business name for the Baseline Account when a value is configured.

     

Labels Tab


Set Mode to the confirmed label format supported for this carrier. 

   


Warning

Select Save before continuing so the configured settings are applied.

  
   

    

Finalizing the Setup


Once the Baseline Account has been created, validated, and saved, continue with Reference Data: DoorDash Client (Billing) Account Fields [Guide].


   

      Go to Go to    
Article 1: DoorDash Onboarding Requirements and Configuration Guides [Information]Article 2: Reference Data: DoorDash Baseline Account Fields [Guide]Article 3: Reference Data: DoorDash Client (Billing) Account Fields [Guide]Article 4: Reference Data: Order-Level DoorDash Fields [Guide]
Onboarding and ConfigurationBaseline Account(Billing) AccountOrder-Level Fields

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article