Amazon BSA readiness

1 · Current status

The public HOLONA prototype uses illustrative seller scenarios and does not read or write a seller account. No Seller Central credentials, SP-API tokens, Ads API tokens, customer marketplace data, or Amazon buyer information are processed by this website.

2 · Readiness gates before a pilot

1. Confirm the operating entity and the Amazon agreements that apply to the proposed integration.
2. Complete the required developer registration, security profile, use-case review, and data-access approvals.
3. Implement least-privilege OAuth scopes, attributable requests, secret rotation, revocation, and deletion behavior.
4. Validate tenant isolation, data classification, retention, audit logs, incident response, and subprocessor controls.
5. Run a read-only shadow pilot before requesting or enabling any write scope.
6. Document evidence for every public compliance claim and remove claims that cannot be verified.

3 · Intended integration boundary

The intended design uses official Amazon APIs only. It does not rely on scraping, shared Seller Central passwords, session replay, or browser automation to access seller accounts. High-impact actions are intended to remain advisory or require explicit operator approval, subject to validation during the pilot.

4 · Relationship to Amazon

HOLONA is an independent product-research project. Amazon, Seller Central, SP-API, and related names are trademarks or services of Amazon and are referenced only to describe the intended integration domain. Nothing on this page implies an Amazon partnership or endorsement.

5 · Contact

Questions about the readiness plan can be sent to contact@holona.io.