Catalog Frequently Asked Questions
Summary
The following is a list of common questions asked regarding the Just Walk Out catalog service
Frequently Asked Questions
Q: I am receiving a 403 un-authorized error when I invoke the catalog API
A: The 403 error when calling the Amazon API can be triggered due to a few common issues. If you are unable to resolve the issue please reach out to your Amazon contact.
-
Missing permission: The AWS IAM role you are assuming is missing the necessary permissions to invoke the API. The IAM role needs to have the
execute-apipermission. If you do not have a policy that provides that permission you will get a 403 error. -
Onboarding to Amazon is not complete: You will need to complete the onboarding for your AWS account to the Amazon systems using the steps here to authorize your account to call the Amazon API.
Q: I setup the SQS URL but I do not see the subscription message
A: Check your SQS policy to ensure the correct permissions are setup especially the SNS ARN in the source to ensure that the Amazon SNS is able to publish to your SQS.
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AllowSNSToSendMessage",
"Effect": "Allow",
"Principal": "*",
"Action": "sqs:SendMessage",
"Resource": "YOUR_SQS_ARN",
"Condition": {
"ArnEquals": {
"aws:SourceArn": "AMAZON_SNS_TOPIC_ARN"
}
}
}
]
}
Q: Can I delete an item in the Just Walk Out catalog?
A: You can now archive items from the Just Walk Out catalog using two self-service methods:
- Excel Template: Set the operation field to "Archive" in the catalog template. See Archive SKU Manual.
- Catalog Management UI: Use the web interface to archive SKUs directly through the portal. See Archive SKU UI.
Q: Can I update an item SKU in the Just Walk Out catalog?
A: You can update an item SKU in the Just WalkOut service by working with the Amazon support team.
Q: Is there a limit on the number of items for the Catalog API?
A: Yes , there is a limit of 10 requests per second and 10,000 items per upload Further details can be seen here
Q: What are the invocation URLs for the catalog API?
A: The catalog API endpoints vary by region
Note: The region needs to be aligned with the store
| Region | Invocation URL |
|---|---|
| NA | https://us-east-1.catalog.amazonphysicalstores.com/v1/catalog/upload |
| EU | https://eu-west-1.catalog.amazonphysicalstores.com/v1/catalog/upload |
| FE | https://us-west-2.catalog.amazonphysicalstores.com/v1/catalog/upload |
Q: What are the SNS topic ARNs the catalog API?
A: The SNS topic ARNs vary by region
| Region | Invocation URL |
|---|---|
| NA | arn:aws:sns:us-east-1:040655018570:CatalogProcessingReportNotification |
| EU | arn:aws:sns:eu-west-1:315499632379:CatalogProcessingReportNotification |
| FE | arn:aws:sns:us-west-2:156895682664:CatalogProcessingReportNotification |
Q: What are the invoke URL for the get upload status?
A: The URL will vary by region
| Region | Invocation URL |
|---|---|
| NA | https://us-east-1.catalog.amazonphysicalstores.com/v1/catalog/getCatalogUploadStatus |
| EU | https://eu-west-1.catalog.amazonphysicalstores.com/v1/catalog/getCatalogUploadStatus |
Q: What if have items that don't have scannable barcodes, like hot foods/sandwiches?
A: You can use a PLU (Product Lookup) type of code. If you are using the catalog api, you will have to specify the external_product_id_type in the payload
Q: What happens if I upload an item with an existing SKU? A: If the upload contains a SKU that already exists, Amazon will treat it as an update and don't remove the SKU.
Q: What is the logic for the barcode? A: At the barcode level, the process behaves differently. The set of barcodes mapped to a SKU is replaced with exactly what's in the upload, not merged with what's already there.
When Amazon ingests a SKU, the process will write the full barcode list as a single operation, so any previously-mapped barcodes that are not included in that upload get dropped.
So sending just a new barcode to a SKU that already has scannable barcodes will wipe the historical barcodes that weren't in that file.
Q: So do I need to upload the entire SKU's barcodes every time?"
A: Yes. Each upload for a SKU must contain the complete set of barcodes for that SKU. The system aggregates all the lines that share a SKU within a single file into one catalog record — it does not pull in barcodes from previous uploads. So all barcodes for a SKU need to be present, as separate lines, in the same upload.
