Bevz Pick a Delivery Service for Onboarding API
This document outlines the integration flow for onboarding new DoorDash and Grubhub stores through the [Delivery Services Onboarding API](#tag/Pick-a-Delivery-Service-for-Onboarding-API/operation/onboard). ## DoorDash Onboarding ### Overview Onboarding a store to DoorDash is an asynchronous process initiated by Bevz via a webhook. Once the POS sends a request to the [Delivery Services Onboarding API](#tag/Pick-a-Delivery-Service-for-Onboarding-API/operation/onboard), DoorDash processes the information, performs necessary checks, and notifies Bevz of the outcome through a webhook. ### Process Flow 1. **Initiate Onboarding Request** - The POS sends a request to the Delivery Services Onboarding API with all required store and sensitive information. - Refer to the [Delivery Services Onboarding API](#tag/Pick-a-Delivery-Service-for-Onboarding-API/operation/onboard) for required fields. 2. **DoorDash Processing** - DoorDash attempts to map the store using the provided details, requests approval from the merchant, and performs internal checks such as menu QA and business admin verification. 3. **Receive Webhook Notification** - Once DoorDash completes processing, they send a webhook notification to Bevz indicating the onboarding status (e.g., approved, pending, rejected) and any relevant details or next steps. 4. **Finalize Onboarding** - The integration is activated once all requirements and approvals are met. If issues arise (e.g., missing hours, menu errors, compliance problems), DoorDash notifies the merchant and Bevz for resolution. ## Grubhub Onboarding ### Overview The onboarding process enables POS systems to initiate a Grubhub store onboarding request via the [Delivery Services Onboarding API](#tag/Pick-a-Delivery-Service-for-Onboarding-API/operation/onboard). Bevz provides an auto-populated onboarding form, which the POS can present to the store. After submission, a Grubhub representative contacts the store to complete setup. ### Process Flow 1. **Initiate Onboarding Request** - The POS sends a request to the Delivery Services Onboarding API. - This request contains the required store information (e.g., store details, sensitive data). 2. **Generate Onboarding Link** - Bevz responds with a unique onboarding link. - This link points to a form that is pre-filled with store data provided in step 1. 3. **Customer Completes Form** - The POS system embeds or redirects the store to the generated onboarding link. - The store reviews and completes the form. 4. **Grubhub Representative Follows Up** - Once the store submits the form, the information is sent to Grubhub. - A Grubhub representative contacts the store to finalize onboarding and assist with setup.