What an Amazon Vendor Manager Actually Does

An Amazon Vendor Manager (VM) is the retail-side owner of a product category. Within Amazon's rules and category guidance, the VM decides which vendors get purchase orders, on what terms, and how hard Amazon pushes for margin, marketing investment, and supply chain programs in the annual negotiation. If you sell 1P, the VM is your counterpart, your negotiation opponent, and occasionally your advocate. How much they do for your brand depends on how much you help them hit the goals their leadership set.

I held this seat. Most of what vendors believe about it is either too cynical or too hopeful, so here is what the job actually looks like from the inside, and what that means for how you work with yours.

I spent three years on Amazon's retail teams owning categories as a Senior Vendor Manager. First in the B2B business unit on commercial food service, then on the Furniture team, where I took on Children's and Dining Room Furniture. The category P&L was mine to run end to end, against goals set by my manager, the business unit leadership team, and retail executive leadership.

The score was contribution margin against plan, in basis points, on that P&L. Under it sat a metric tree: every workstream mapped to the input or output metric it was expected to move, reported against plan weekly in the category WBR, one owner per line, every variance explained or escalated. I was also expected to automate myself out of the job, hands off the wheel in Amazon parlance.

My first manager explained the job in week one: 10 to 20 high-visibility action items would land every week, and I would pick the 5 with the most impact on my P&L and category goals. Next week brought a new set plus last week's backlog.

When your VM goes quiet, a bigger fire is usually burning somewhere else. They may also go quiet if they read you as a poor partner. They're not the person to pester about a content upload issue on a detail page.

What is your Amazon Vendor Manager judged on?

Sales growth and profitability of their category. In the seat I held, the internal profitability metrics stayed on Amazon's side of the table, deliberately as I read it. Amazon does not want a vendor to know when it is highly profitable on an ASIN in that vendor's catalog. The closest a vendor gets is Net PPM (net pure product margin): what Amazon earns reselling your products after subtracting its costs and adding back your contra-COGS funding. A vendor whose Net PPM flatters the category gets attention and POs. One whose economics drag it triggers cost-decrease requests, term increases, or CRaP status, where Amazon quietly stops reordering.

The VM is weighing you against their own scorecard. In my experience, every ask I made at negotiation traced back to a line on my metric tree; expect the same of the VM across from you.

The two lists a VM reviews every week

When I was at Amazon, CRaP list reviews were part of our Weekly Business Review (WBR) cadence. There were two lists we reviewed every week. The first was a list of ASINs that we lost the most dollars on that week. The second was a list ranking the ASINs where we were losing the most dollars per transaction.

When talking with Vendor Partners I regularly warned them that these were the two things that would bring their SKUs onto both my and my category leadership's radar. It could be caused by losing a little bit of money on every transaction on a high velocity ASIN, from deep losses on very few transactions or a combination of the two.

Both lists are driven by price, because Amazon matches the lowest price it can find, so a product selling cheaper through another channel drags its own Net PPM down. That is why Amazon experts keep coming back to channel management and control over distribution: the price Amazon matches elsewhere is the price that decides its margin on you.

What does your VM actually control on a 1P account?

A VM controls the terms Amazon proposes to you, the ordering posture behind them, the exceptions that get written down, and the escalations that get unstuck. From the seat, those four were the levers I could pull for a vendor.

• Terms proposals. The VM drives the Annual Vendor Negotiation (AVN), proposing the next 12 months of co-op, freight, damage, and payment terms. In the 2025 cycle, 64 percent of surveyed vendors received cost-price-decrease requests, averaging 6.25 percent, per Consulterce's 2025 vendor survey.
• Assortment and ordering posture. Which ASINs Amazon leans into, and whether marginal SKUs stay ordered at all. Your commercial agreements do not obligate Amazon to issue you purchase orders, nor do they require you to accept them.
• Negotiated exceptions. Waivers and amendments to standard terms; the emails documenting them are your evidence when automated billing later charges a term your VM waived.
• Escalation paths. A VM can unstick operational problems that support tickets cannot.

What a VM does not control: retail pricing (algorithmic), most compliance chargebacks (systematic), and the finance systems that process deductions. Vendors regularly burn goodwill asking VMs to fix things the VM cannot touch.

When does a 1P vendor hear from its VM?

The relationship has a calendar. Amazon sends preliminary performance reviews and trade-term proposals in late Q4; the negotiation cycle runs one to three months and most agreements finalize by the end of February. Mid-year check-ins run as Quarterly Business Reviews, which are your chance to course-correct before the next cycle rather than re-litigate the last one. The practical consequence: preparation starts in Q3, because a vendor who first opens their Net PPM data in December is negotiating against a counterpart who has been staring at it all year.

How should a 1P brand work with its VM?

Bring your own numbers, trade rather than give, and write down every exception. Those three practices separated the vendors who came out of my negotiations intact from those who absorbed whatever I proposed.

1. Bring your own data. The VM will present Amazon's version of your performance. You need an independent one: your Net PPM by ASIN, your chargeback and fill-rate trends, your co-op spend against what it bought you. A number I could carry into my own WBR moved the conversation, because I could report it against plan.
2. Never give without asking. Treat a request for another point of co-op as the opening of a trade. The vendors who fared best countered with cost increases, freight reductions, or faster payment terms.
3. Document everything the VM agrees to. The gap between what a VM negotiates and what Amazon's billing systems execute is a recurring source of recoverable deductions. In the seat I held, the waiver email ended arguments; my read is that it stays the highest-yield document in co-op recovery.

Access is also tiered, and unpaid at every tier. At Amazon I ran two kinds of vendor: the ones I managed, and the long tail a playbook and an offshore team managed for me. In my experience the managed tier went to the strategic vendors the category's goals depended on. That tier decides whether a person or a playbook answers you. Amazon also sells paid attention (Amazon Vendor Services, from roughly $1,600 per month); the same Consulterce survey found it pushed in about 30 percent of 2025 negotiations. Whether AVS is worth it is a separate question. It is a different product from the VM relationship you already have.

Why does this matter for your margin?

Because the VM relationship is where your cost structure gets set, and the billing systems downstream of it are where that structure leaks. The terms agreed at AVN become the co-op and allowance deductions on every remittance; the exceptions your VM grants are only worth what you can prove when the system charges you anyway. We wrote about where those leaks show up in Amazon deductions explained, and the 1P-vs-3P economics that frame the whole relationship in Vendor Central vs Seller Central.

If your last AVN moved terms against you and nobody has since audited what the new terms actually bill versus what was signed, that reconciliation is the fastest recoverable-margin conversation available. The Margin Recovery Audit runs it; it starts with a free scan.