Vendor Code
A vendor code is the short identifier Amazon assigns inside a Vendor Central vendor group to one specific relationship, such as a product category, a brand, or a business agreement, which is why a single company's Vendor Central login can carry several of them.
A vendor code is the short identifier Amazon assigns inside a Vendor Central vendor group to one specific relationship, such as a product category, a brand, or a business agreement, which is why a single company’s Vendor Central login can carry several of them.
What it is
Operators tend to say “the account” for two different things. The vendor group is the Vendor Central account you sign into, and the vendor codes sit inside it. Amazon’s Selling Partner API documentation describes codes as the way one vendor group lists products in specific categories, carries different business agreements, and manages different brands. Each code stands for one relationship with Amazon, so a company with two brands or two agreements can end up holding several codes under the same login.
The code itself is short and alphanumeric. One third-party Vendor Central glossary describes it as a five-character code that uniquely identifies a vendor account within a region, with an example in the form ABC1D. Because that format comes from a third-party glossary and not from Amazon, check your own codes before you build a spreadsheet, script, or integration that assumes a fixed length.
Vendor codes come by invitation, and there’s no self-service sign-up that produces one.
Where it lives in Vendor Central
Third-party integration documentation from Openbridge places the list under Settings > Contacts, where you can view the codes two ways, By Vendor Code and By People. Amazon’s own Vendor Central help sits behind the login and couldn’t be checked directly, so confirm the labels your account actually shows.
Why it matters to a vendor
The code you pick determines whose data you’re looking at. Authorizing a third-party application through the Selling Partner API grants it access to every vendor code in the vendor group, so before you approve an app, know which codes the group contains and which business each one represents. When a tool, integration, or report asks for a single code and you choose the wrong one, you get data for a different brand, category, or agreement than the one you meant.
Keep a short internal list that maps each vendor code to the brand, category, or agreement it covers and notes who on your team has access to it, so whoever connects the next integration can pick the right code without guessing.
Related terms
- Vendor API: the vendor-scoped part of Amazon’s Selling Partner API, where app authorization happens at the vendor group level.
- Amazon Vendor Central API: How to Get Your Sales, Inventory, and Traffic Data Out: what registering an application involves and what the API returns.
- Glossary index: the rest of the Vendor Central terms and InsightLeap metrics.