1. Which APIs we call
The workbench connects to the official Selling Partner API (SP-API), the successor to MWS. Listings management uses three API groups:
| API | Purpose |
|---|---|
| Listings Items API | Create, update, pause, delete and query a single SKU |
| Feeds API | Bulk jobs for many SKUs at once, asynchronous with a processing report |
| Product Type Definitions API | Read valid attributes and options per product type |
2. How authorisation works
- Once public self-service authorisation is available, the connection page will direct you to Amazon's official consent screen. Current beta onboarding uses an assisted process;
- After you approve, Amazon returns a one-time code to our callback page;
- The trusted authorisation flow exchanges the one-time code for tokens and validates the connection. Token lifetime and authentication follow Amazon's current API requirements;
- Revoke platform access in Seller Central and separately delete the store in the app to clear local credentials. Removing a local store is not itself platform-side revocation.
Public self-service authorisation is not yet available. Current onboarding is assisted, with the customer present. Any future change to token storage will be reflected in this page and the privacy policy before release.
3. Roles requested — and not requested
| Role | Purpose |
|---|---|
| Product Listing | Create and update listings, publish and delist, read product type definitions |
| Pricing | Read and update prices |
| Inventory | Read and update available quantity |
| Orders / buyer PII | Not requested. Buyer names, phone numbers and addresses are out of scope |
| Advertising | Not requested. Ad plans are produced locally |
4. What data, used how, stored where
| Data | Purpose | Storage | Retention |
|---|---|---|---|
| Seller ID, tokens | Call the API, refresh tokens | Encrypted config on your machine | Deleting the store clears local credentials; revoke platform access separately in Seller Central. |
| SKU, ASIN, listing attributes | Build listings, reconcile | Local task data folder | Deleted with the task or history clear |
| Job results and error reports | Show outcome, retry failures | Local task data folder | Same as above |
| Access logs | Troubleshooting and audit | Local | Retained according to the installed version's log settings; user-clearable. |
Data is stored locally by default and is not used for our own model training, resale or advertising. Necessary data is sent to Amazon to execute an operation; content submitted to a model goes to the provider you configured. See the privacy policy for details.
5. Revoking access and deleting data
- In the app: Amazon integration → select store → delete; tokens and cached data are removed.
- In Seller Central: Apps and services → Manage your apps → remove authorisation.
- Deletion requests for contact and support records can be submitted when public contact channels are available. Requests are handled under applicable law after verification; local data must be cleared separately.
6. Security measures
- HTTPS/TLS is used for platform traffic, with authentication following current Amazon SP-API requirements. Credentials are not written to logs in plaintext.
- Local credentials are protected using encryption and operating-system access controls, as specified for the delivered version.
- Least-privilege roles, per-store token isolation, rate limiting and backoff on API calls.
- Store writes require explicit user initiation and confirmation. During beta, the available interface or assisted process depends on enabled capabilities; execution results are recorded.
7. Current availability
The listings capability is implemented and internally tested. It is currently in beta, onboarding a limited number of customers with our assistance. We will update this page when it opens generally.