Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazonアプリストア
Ring
AWS
ドキュメント
Support
Contact Us
My Cases
Docs
Resources
Ecommerce Plug-ins
Publish
Connect
アクセスいただきありがとうございます。こちらのページは現在英語のみのご用意となっております。順次日本語化を進めてまいりますので、ご理解のほどよろしくお願いいたします。

App Entry Store Validation Plan

Disclaimer: This document contains sample content for illustrative purposes only. Organizations should follow their own established best practices, security requirements, and compliance standards to ensure solutions are production-ready.

Summary

This validation plan is designed for existing partners who have pre-built integrations and do not need to build from scratch. It provides a focused subset of the full App Entry Store Test Plan to validate that the partner's integration is correctly configured and functioning for a specific store deployment.

Use this plan when:

  • A partner has already built the integration for app-based entry
  • The store is being onboarded using an existing partner solution
  • You need to confirm connectivity, configuration, and end-to-end flow correctness without re-testing the full build

APIs Under Validation

API Endpoint Validation Focus
Verify Identity Keys POST /v1/identity/identity-keys Connectivity, valid/invalid key handling
Create Purchases POST /v1/order/purchases Connectivity, pricing accuracy, empty cart handling

1. Connectivity Validation

1.1 Verify Identity Keys API Reachable

Test Case ID: VAL-CONN-001 Objective: Verify the partner can invoke the Verify Identity Keys API

Test Steps:

  1. Call POST /v1/identity/identity-keys with a valid test identity key
  2. Verify HTTP 200 response

Expected Result: API responds without authentication or network errors

1.2 Ordering Connector Reachable

Test Case ID: VAL-CONN-002 Objective: Verify Amazon can invoke the partner's Ordering Connector (Create Purchases API)

Test Steps:

  1. Trigger the Merchant Portal connectivity test for the Ordering Connector
  2. Verify successful response

Expected Result: Connectivity test passes; HTTP 200 returned


2. Identity Verification Validation

2.1 Valid Identity Key — Successful Entry

Test Case ID: VAL-ID-001 Objective: Verify a valid identity key is accepted and shopper is authorized

Test Steps:

  1. Call Verify Identity Keys with a valid base64-encoded identity key
  2. Verify response contains VALID status
  3. Verify gate opens

Expected Result: HTTP 200; identity verified; gate opens

2.2 Invalid Identity Key — Entry Denied

Test Case ID: VAL-ID-002 Objective: Verify an invalid identity key is rejected

Test Steps:

  1. Call Verify Identity Keys with an invalid or expired identity key
  2. Verify response indicates invalid key

Expected Result: Entry denied; appropriate error response

2.3 Correct Key Channel

Test Case ID: VAL-ID-003 Objective: Verify the correct keyChannel (OPTICAL) is used for QR code scanning

Test Steps:

  1. Call Verify Identity Keys with keyChannel: OPTICAL
  2. Verify successful response

Expected Result: HTTP 200; key channel accepted


3. Charge Calculation Validation (Create Purchases)

3.1 Single Item Cart — Correct Pricing

Test Case ID: VAL-OP-001 Objective: Verify the partner's Ordering Connector returns correct pricing for a single item

Test Steps:

  1. Send a Create Purchases request with one known-price item
  2. Verify purchaseId is returned
  3. Verify the calculated price matches the expected catalog price

Expected Result: HTTP 201; purchaseId returned; price correct

3.2 Multi-Item Cart with Promotions

Test Case ID: VAL-OP-002 Objective: Verify promotions are applied correctly

Test Steps:

  1. Send a Create Purchases request with items that have active promotions
  2. Verify discounts are applied correctly

Expected Result: HTTP 201; purchaseId returned; promotions applied

3.3 Empty Cart Handling

Test Case ID: VAL-OP-003 Objective: Verify empty cart returns empty purchaseId

Test Steps:

  1. Send a Create Purchases request with cartItems: []
  2. Verify empty purchaseId is returned

Expected Result: HTTP 201; purchaseId: ""

3.4 Tax Calculation

Test Case ID: VAL-OP-004 Objective: Verify tax is calculated correctly for the store's jurisdiction

Test Steps:

  1. Send a Create Purchases request with taxable items
  2. Verify tax amount matches expected rate for the store location

Expected Result: HTTP 201; tax calculated correctly

3.5 Idempotency

Test Case ID: VAL-OP-005 Objective: Verify duplicate requests return the same purchaseId

Test Steps:

  1. Send a Create Purchases request
  2. Send the same request again with the same idempotentShoppingTripId
  3. Verify both return the same purchaseId

Expected Result: Same purchaseId returned; no duplicate records


4. Error Handling Validation

4.1 Invalid Identity Key Format

Test Case ID: VAL-ERR-001 Objective: Verify 400 error handling for malformed identity key

Test Steps:

  1. Call Verify Identity Keys with a malformed identity key
  2. Verify appropriate error response

Expected Result: Error handled gracefully; no system crash

4.2 Rate Limit Handling

Test Case ID: VAL-ERR-002 Objective: Verify the partner handles 429 responses correctly

Test Steps:

  1. Trigger a 429 response (or simulate)
  2. Verify the system retries after the Retry-After period

Expected Result: System retries with backoff; no data loss


5. End-to-End Flow Validation

5.1 Complete Shopping Journey — App Entry

Test Case ID: VAL-E2E-001 Objective: Validate the full shopper journey from app entry to charge calculation

Test Steps:

  1. Shopper scans QR code at gate
  2. Verify Identity Keys returns VALID → gate opens
  3. Shopper picks up items and exits
  4. Amazon sends cart → Create Purchases returns purchaseId with correct pricing
  5. Amazon processes payment and generates receipt

Expected Result: Seamless end-to-end flow; identity verified, pricing calculated correctly

5.2 Empty Cart Journey

Test Case ID: VAL-E2E-002 Objective: Validate the empty cart flow

Test Steps:

  1. Shopper enters store via app and exits without items
  2. Amazon sends empty cart → Create Purchases returns empty purchaseId
  3. No charge on shopper's payment method

Expected Result: Empty purchaseId returned; no charge


6. Configuration Validation Checklist

Configuration Validated Notes
Verify Identity Keys API allowlisted ☐  
Ordering Connector ARN allowlisted ☐  
Ordering Connector configured in Merchant Portal ☐  
Ordering Connector connectivity test passed ☐  
Store ID correctly mapped ☐  
Catalog uploaded and active ☐  
QR code scanning configured ☐