Developer Console
Merci de votre visite. Cette page est disponible en anglais uniquement.

Dash Replenishment Service Certification

Amazon Dash Replenishment users expect a high quality and consistent experience across all products. To help you meet this bar and build the best possible DRS integration, this document explains the product testing process, and provides an overview of the typical Dash Replenishment Services (DRS) development lifecycle.

Product testing

Product testing is broken into two steps: pre-certification and product submission. During pre-certification, you will use a series of checklists provided by Amazon to ensure that your product meets functional and user experience (UX) requirements.

After you've completed the pre-certification checklists, they must be submitted to Amazon for evaluation prior to commercial distribution of your DRS-connected product. Please work with your Amazon point of contact to schedule product submission and testing. This process takes approximately 4 weeks.

This is a high-level overview of the process that begins once Amazon receives your product for evaluation:

Physical product shipped to Amazon
Pre-certification documents submitted
Acceptance testing and UX evaluation
Functional testing
Certification report and OK-to-ship

Step 1: Pre-certification

Please review the pre-certification list and run all checks to ensure that both your physical product and your digital portals (companion apps or website) work as defined in our guidelines. Your Amazon point of contact will provide all the necessary documentation to run these tests.

Step 2: Submit your product for certification

After you've completed the pre-certification checklists, please work with your Amazon point of contact to submit the results and schedule your certification slot. After review, authorization to ship products along with shipping instructions will be provided to you directly from the testing team. The Amazon DRS certification team requires physical access to most devices.

Step 3: Testing by Amazon

Physical testing of your product will begin and the Amazon DRS certification team will perform a UX assessment along with functional testing focusing on the same test areas as outlined in our pre-certification checklist.

Post certification

After your device is certified by the Amazon DRS certification team, some of the device settings like the device image and slot names will not be editable. Please ensure that any customer-facing information in your DRS Self-Service Portal is finalized prior to submitting.


After your device is certified, Amazon recommends that you run our pre-certification checks again, using production devices. If your product requires a companion app or website, you should also test that downloads from the app stores or the production website work, and test the DRS flow once more.

Firmware Updates

Any updates or changes to the firmware must be tested by the product owner before being deployed to products in the field (OTA update). If significant updates are made, the product must be re-submitted for testing prior to deployment. This ensures that the changes are compliant with DRS requirements.

Adding new device models

If you are planning to launch a new model, please contact your Amazon point of contact.

Expanding internationally

When you submit for certification we will validate your product against the marketplaces you selected in your DRS Self-Service Portal (ex., If you later decide to include additional marketplaces, your product will go through the Amazon DRS certification to ensure that the experience for the new country is localized.

Pre-certification checklist

Certification timelines and go-to-market will depend on the quality of the product at the time of the DRS certification. Our team will verify the functionality of your product and the DRS lifecycle including: joining the service from your website or companion app, pairing the device, managing the auto-replenishment settings, using the device and triggering re-ordering.

The following list includes a pre-certification checklist you must run before you submit your product for Amazon DRS certification.

1. Amazon DRS set-up

The companion app or website must present an Amazon Dash Replenishment teaser page soon after adding a device to the device maker account. If there is no device maker account step, the teaser page should appear soon after the OOBE or after using the device for the first time.

1.1 Amazon Teaser Page -­ Get Started

  • Teaser page shall have options to Skip, Learn More, Remind me Later (Optional), or Continue.
  • Teaser page should show up shortly after partner device and account setup.
  • It is acceptable for the teaser page to show up after X amount of time or X amount of usage.
  • The teaser page shall include either Amazon Dash logo.

1.2 Amazon Teaser Page -­ Visual Acceptance

Confirm that the teaser page was implemented as per the latest approved UX. Teaser page examples are available in the documentation.

1.3 Complete Setup - Device Maker Congratulations Page

Confirm that the confirmation page was implemented as per the latest approved UX. The confirmation page should have a button to re­direct user to main app page.

1.4 Complete Setup ­- "Manage reordering" button

A "Manage reordering" button must be implemented to allow customers to change their DRS settings. This button will use the "Device Management and Settings" page.

1.5 Amazon DRS Registration ­- Forward/Backward Navigation through WebView UI(iOS)

If you are using a WebView in your companion app, or a website you must ensure that the navigation is possible both backward and forward.

1.6 Amazon DRS Registration - Notification

An email should be received upon finalising the reordering selection.

1.7 SSO Login with LWA (iOS and Android apps only)

When testing a native companion app ensure the DRS registration is tested with:

  • Amazon Shopping app logged in - this will trigger a Single Sign-On experience without requiring username/password to be used
  • Amazon Shopping app is uninstalled or logged out - This will invoke a webview within the app or in a browser

2. User lifecycle

2.1 Email Notification ­- Amazon DRS Subscription Status Change

An email should be received upon changing the reordering selection.

2.2 Email Notification ­- Amazon Order Confirmation

Verify that a new order triggers a confirmation email stating that the customer has 24 hours to cancel it.

2.3 Email Notification ­- Amazon DRS Deregistration

Verify that upon deregistration, a confirmation email is received.

3. Inventory Management

3.1 ­Initial Stock

The app or website should capture the baseline inventory level after the customer completes the DRS registration. This is important if the customer has some product available already. Inventory for baseline shall be indicated in the units used for the ordering decisions. For example, "pounds", "ounces", "boxes".

3.2 Inventory -­ Normal Usage

Use the device and monitor the product inventory levels change. The inventory balance in the app or website must reflect that change.

4 Ordering

4.1 Ordering - Replenishing a slot

An order is placed for the configured product, SNS notification is received regarding the order status. Confirmation email is received by the customer.

4.2 Ordering -­ Multiple Replenishment

After receiving an "itemShipped" SNS notification, the notification will contain an estimatedDeliveryDate. On that date, the inventory should be updated and a logic implemented to delay the next reorder for the same slot.

4.3 Ordering -­ Multiple DRS Slots

If you have a device with multiple slots, simulate a "low inventory" signal for a specific slot and ensure the reordering only happens for that slot.

5. Server communication

5.1 Data Transmission ­- Security

All data transmitted between the DRS device and device maker’s cloud must be secure (https://). Amazon recommends SSL encryption for all data transfers.

Last updated: Aug 07, 2018