Support Channel-Based Order Management
Identify which DoorDash channel each order came from — required across every tier of the DoorDash Integrations Program
Overview
Channel-based order management (also referred to as order experience tags, or channel-based order tags) lets a merchant clearly identify which DoorDash channel each order came from. Merchants need this visibility both at the individual order level and in aggregated reporting. The most critical use case is accurate financial reporting: merchants need orders broken out by channel for reconciliation.
DoorDash passes the applicable channel on every order payload in the experience field. This doc covers the subset of experience values relevant to DoorDash Integrations Program requirements, which partner tiers require support for which values, and what partners must do to fulfill the requirement.
Before You Begin
This doc assumes you're already receiving orders from DoorDash — see Order Integration for how the experience field (and other notable fields) arrive on the order payload. The full list of possible experience values is documented in the Marketplace Order Model; this doc covers only the subset relevant to Integrations Program requirements.
The experience Field on Orders
| Value | Channel |
|---|---|
doordash | DoorDash Marketplace |
storefront | First-party DoorDash Online Ordering |
caviar | Caviar |
marketplace_catering | Catering orders placed through the DoorDash Marketplace catering experience |
meal_manager | Catering orders placed through DoorDash Meal Manager |
online_ordering_catering | Catering orders placed through DoorDash first-party Online Ordering (Storefront) catering |
This table covers only the experience values relevant to Integrations Program tier requirements. See the Marketplace Order Model for the complete field reference.
Partner Tier Requirements
| Requirement | experience values required |
|---|---|
| Certified (net new partners) | doordash, caviar, storefront |
| Marketplace Preferred | doordash, marketplace_catering, meal_manager |
| Omnichannel Preferred | online_ordering_catering, storefront |
| Platinum | doordash, marketplace_catering, meal_manager, online_ordering_catering, storefront |
For related catering order handling context, see Support Catering Orders.
Fulfilling the Requirement
To satisfy channel-based order management requirements, partners must:
- Ingest the order experience field. DoorDash transmits an
experiencefield (the order experience tag) on the order payload indicating which DoorDash channel the order came from. Partners must ingest this field. - Surface it everywhere the order appears. The experience must be visible in order views and included in all reporting, including financial reconciliation reporting.
Financial reconciliation is the most critical use case here — merchants rely on the experience field to break out orders by channel for reconciliation. Reporting that omits it doesn't meet the requirement.
FAQ
Q: What is the experience field, and why does it matter?
A: It's a field DoorDash includes on every order payload indicating which DoorDash channel (Marketplace, Storefront, Caviar, catering, etc.) the order came from. Merchants rely on it to break out orders by channel, most critically for financial reconciliation reporting.
Q: Is the full list of experience values larger than what's in this doc?
A: Yes. This doc lists only the subset relevant to DoorDash Integrations Program tier requirements. See the Marketplace Order Model for the complete field reference.
Q: Is it enough to just store the experience value, or does it need to be shown to merchants?
A: Storing it alone isn't sufficient. It must be surfaced in order views and included in all reporting, including financial reconciliation reporting.
Next Steps
- Review Order Integration for how the
experiencefield arrives on the order payload - Review the Marketplace Order Model for the complete list of
experiencevalues - Review Support Catering Orders for related catering order handling