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.
Overview
This page provides a consolidated view of all the capabilities, APIs, and documentation required to implement a Just Walk Out store using app-based entry. In this model, the retailer manages shopper identity verification through a mobile app, delegates charge calculation to their own POS system, and handles payment orchestration independently.
Store Profile
Attribute
Value
Entry Method
Mobile app QR code scan
Identity Verification
Retailer-managed via Verify Identity Keys API
Charge Calculation
Order Delegation (retailer POS)
Payment Orchestration
Retailer-managed
Catalog Management
Catalog API
APIs in Scope
API
Endpoint
Purpose
Upload Catalog
POST /v1/catalog/upload
Upload product catalog to Amazon systems
Get Catalog Upload Status
POST /v1/catalog/getCatalogUploadStatus
Check catalog upload processing status
Verify Identity Keys
POST /v1/identity/identity-keys
Authorize shoppers at the JWO gate
Create Purchases
POST /v1/order/purchases
Receive the shopping cart and create a purchase record
Required Configurations
The following configurations must be completed in the Merchant Portal and AWS before the store can operate:
Configuration
Owner
Description
AWS Account Allowlisting (Catalog API)
Amazon / Retailer
Retailer's AWS account must be allowlisted to invoke the Catalog API
Merchant Portal — Catalog API
Amazon
Catalog API configured for the merchant in the Merchant Portal
SNS Subscription (Catalog Notifications)
Retailer
SQS queue subscribed to Amazon's SNS topic for catalog upload results
Identity Connector — ARN Allowlisting
Retailer
Identity Gateway ARNs allowlisted in the retailer's Identity Connector
Merchant Portal — Identity Connector
Amazon
Identity Connector configured and associated with store(s)
Identity Connector — Connectivity Test
Retailer
Connectivity test completed via Merchant Portal
Ordering Connector — ARN Allowlisting
Retailer
Ordering Gateway ARNs allowlisted in the retailer's Ordering Connector
Merchant Portal — Ordering Connector
Amazon
Ordering Connector configured and associated with store(s)
Ordering Connector — Connectivity Test
Retailer
Connectivity test completed via Merchant Portal
Mobile App — QR Code Generation
Retailer
Mobile app generates Scan Key Codes per JWO specifications
Available Partners
The following partners have pre-built integrations that support the APIs required for this store model (Catalog, Identity Connector, and Ordering Connector):
Partner
Catalog
Identity Connector
Ordering Connector
Compass Digital
Yes
Yes
Yes
Grubhub
Yes
Yes
Yes
Sodexo Everyday
Yes
Yes
Yes
Tapin2
Yes
Yes
Yes
Transact Campus
Yes
Yes
Yes
SkyTab Venue
Yes
Yes
Yes
The following partners support individual integrations and can be combined to cover all required APIs:
Partner
Available Integrations
CBORD
Identity Connector, Ordering Connector
Transact Quickcharge
Identity Connector, Ordering Connector
Volante Systems
Identity Connector, Ordering Connector
Cognizant Technology Solutions
Catalog, Ordering Connector
MyVenue
Catalog, Ordering Connector
Everi
Identity Connector
Lava.ai
Identity Connector
YinzCam, Inc.
Identity Connector
RapidRMS
Catalog
1. Catalog Management
Before your store can operate, you must upload a product catalog to Amazon's systems. The catalog maps SKUs to barcodes, product names, and store IDs so that items picked up by shoppers can be identified.
Set up your AWS account and IAM role with Invoke API permissions
Deploy the CloudFormation templates for SQS and connectivity testing
Onboard your AWS account and SQS ARN via the Merchant Portal
Confirm the SNS subscription for upload result notifications
Upload your catalog (max 10,000 items per request, 10 requests/second)
Track upload status via the Get Catalog Upload Status API or SNS/SQS notifications
Download and process the upload result report from the S3 presigned URL (valid for 60 minutes)
2. Shopper Entry — App-Based Authorization
Shoppers enter the store by scanning a QR code generated by your mobile app. Amazon calls your Verify Identity Keys API to authorize the shopper. You verify the identity key and return a gate decision.
Build a mobile app that generates QR code Scan Key Codes per JWO specifications
Implement the Verify Identity Keys API (POST /v1/identity/identity-keys) as your Identity Connector
Decode the Base64-encoded identityKey and validate the shopper
Return visitor details with type SHOPPER, ASSOCIATE, or CASH_SHOPPER
Handle all requests idempotently using the authEvent.id
Ensure responses return within 2 seconds
Gate Behavior
Response Code
Gate Action
200
Gate opens
400
Gate remains closed
401
Gate remains closed
429
Gate remains closed
500
Gate follows store default decision
3. Charge Calculation — Order Delegation
After the shopper exits, Amazon calls your Create Purchases API with the virtual shopping cart. You calculate pricing, apply promotions and taxes, and return a purchaseId.
