TODO · 待填 — service #1 name
TODO · 待填
Describe service #1: what it does for the seller, and which Amazon data it needs to do it.
Fill in before submitting for review — see docs/registration-checklist.md
Built on the Amazon Selling Partner API
TODO · 待填
Positioning paragraph (2–3 sentences): who the company is, what problem it solves, and which Amazon sellers it serves.
Fill in before submitting for review — see docs/registration-checklist.md
About us
TODO · 待填
Company overview: legal entity, year founded, where the team is based, size, and the market it operates in.
Fill in before submitting for review — see docs/registration-checklist.md
TODO · 待填
A short statement of what the company does day to day for its customers, and how it makes money (e.g. SaaS subscription, service retainer, per-order fee).
Fill in before submitting for review — see docs/registration-checklist.md
For Amazon sellers
This is the section Amazon's reviewers look at most closely: it has to state plainly what your application does on a seller's behalf once they authorize it.
TODO · 待填
Describe service #1: what it does for the seller, and which Amazon data it needs to do it.
Fill in before submitting for review — see docs/registration-checklist.md
TODO · 待填
Describe service #2: what it does for the seller, and which Amazon data it needs to do it.
Fill in before submitting for review — see docs/registration-checklist.md
TODO · 待填
Describe service #3: what it does for the seller, and which Amazon data it needs to do it.
Fill in before submitting for review — see docs/registration-checklist.md
Full detail, including the SP-API data each service uses, is on the Services page.
How it works
We access your Amazon selling account only through Amazon's official authorization flow. You stay in control and can revoke access from Seller Central at any time.
You begin the connection from your account on this site.
Amazon asks you to review the access being requested and confirm consent.
Amazon redirects back to our registered callback with a one-time authorization code.
We exchange that code for a long-lived credential, stored encrypted, and used only for the services you signed up for.
TODO · 待填
State exactly which SP-API roles / data types your application requests, and the business reason for each one.
Fill in before submitting for review — see docs/registration-checklist.md
Security & compliance
Amazon's Data Protection Policy sets binding requirements for anyone handling Selling Partner data. This section states how we meet them.
The entire site, including both OAuth endpoints, is served over HTTPS.
Authorization credentials issued by Amazon are encrypted before they are written to our database.
TODO · 待填
Remaining security controls: access control and least privilege, logging and monitoring, incident response and breach notification timeline, data retention and deletion schedule, subprocessors, and any certifications held.
Fill in before submitting for review — see docs/registration-checklist.md
Questions about our services, our use of Amazon Selling Partner data, or a partnership? We're happy to talk.
Contact us