Amazon SP API Vendor Authorization
The purpose of this document is to give good understanding how Hemi will incorporate the Vendor APIs within our current Amazon integration
Summary of Changes: (The purpose of this table is to keep traceability and Product team to highlight the things that were changed into the scope, based on comments or discussions)
| Version | Date | Created / Updated | Notes |
|---|---|---|---|
| v1.0 | 09.02.2024 | Bogomil Pavlov | First publish |
Everything in terms of authorization is the same as for our current SP-API authorization with the only difference the code which we are obtaining from Amazon when the user authorize us is from a different link. At the moment we are using only https://sellercentral.amazon.com however we need to add additional option which will be a radio button field in Account Amazon table where we will decide if the account is Seller or Vendor and based on the selection we will have two separate links for authorization: Seller - https://sellercentral.amazon.com/apps/authorize/consent?application_id=amzn1.sp.solution.e2986443-af83-4c60-8f05-84deb0c00af8&state={UNIQUE_PARAMETER_VALUE}&version=beta
From there on everything is the same and should work the same way as https://www.notion.so/threecolts/Amazon-SP-API-Authorization-and-Database-structure-53c67c6aff684d3ea64d6df48762423c?pvs=11
Once we are authorised we will have two separate vendor types Direct Fulfillment and Retail. A Vendor account can run one or both types at the same time, but the management of those, as opposed to Sellercentral is managed through different APIs. We should be ready to have both or only one running and to do so we should simply have the different crons with their respective flows and mapping. To manage the availability we should follow the current Amazon standard (to become standard for all functionality) and have Control Flags for each Amazon flow under Account Amazon table
Please note an Account can be either a Vendor or Seller but never both so based on the authorization we will store the correct access token in the cache and only the respective crons will be available.