They are two different businesses to support. Vendor Central is wholesale: Amazon buys from you, sets the retail price, and the work runs through purchase orders and chargebacks. Seller Central is retail: you keep price, inventory, and the customer. Ask any agency which one it operates daily, not which one it has seen.
The short version
- The account type decides the job. Support on 1P is supply chain and deductions. Support on 3P is merchandising and advertising.
- Price control is the real difference. On Vendor Central you recommend a price. On Seller Central you set it.
- Hybrid accounts fail on ownership, not on strategy. Two systems, one catalog, and usually nobody responsible for both.
- Most agency experience is 3P. That is fine, as long as it is stated rather than implied.
- Ask for named account access and a named operator in whichever system you actually run.
What I learned buying this from the other side
Before Flapen, I ran data and technology at BRANDED and at Moonshot Brands, two large Amazon aggregators. Part of that job was sitting on the buying side of agency relationships and looking at the accounts underneath them. The pattern that repeated had nothing to do with strategy decks. It was that support quality tracked exactly one thing: whether the team had run that specific account type, day after day, with their own hands on the console.
People who had only worked in Seller Central described Vendor Central problems in Seller Central language. They talked about buy box and inventory age when the actual issue was a purchase order that was never confirmed and a shortage claim nobody disputed inside the window. The reverse happened too. It is not incompetence. Two systems, two vocabularies, two failure surfaces.
So the question to ask a candidate is narrow and unglamorous: which of the two do you log into every morning, and for how many brands.
How the two account types differ where support actually happens
| Area | Vendor Central (1P) | Seller Central (3P) |
|---|---|---|
| Who owns the customer | Amazon buys the stock and resells it | You sell directly and hold the relationship |
| Retail price | Amazon sets it, you can only recommend | You set it |
| Demand signal | Purchase orders from Amazon | Your own inventory and forecast |
| Money leaks | Chargebacks, shortage claims, co-op terms | Fees, returns, storage, wasted ad spend |
| Catalog authority | Contested, often slow to correct | Yours, subject to brand registry |
| Speed of change | Slower, mediated through Amazon | Same day, in your own hands |
| Access model | Vendor accounts and permissions | Granted user permissions you can revoke any time |
Neither is strictly better. 1P removes operational burden and removes control with it. 3P keeps both. What matters for hiring is that a support scope written for one is close to useless for the other.
Failure modes, ranked by what they cost
1. Deductions nobody disputes. On 1P, chargebacks and shortage claims accumulate quietly and are only recoverable inside a window. This is the single most expensive gap, because the money is already gone by the time anyone reads the report. Ask who owns the deductions process by name.
2. Losing pricing control without planning for it. When Amazon sets retail, promotional pricing elsewhere can drag your Amazon price down and your wholesale margin with it. Brands discover this after the fact more often than before.
3. Hybrid catalogs with no single owner. Running both account types on the same ASINs creates contention over content, price, and stock. The strategy can be sound and still lose money because two teams are editing the same detail page.
4. Support cases opened in the wrong system. Cases routed through the wrong path can sit for weeks. An operator who has done it before knows which path resolves which category of issue.
5. An agency learning your account type on your account. Sometimes acceptable, if disclosed and priced accordingly. Never acceptable when it is discovered in month three.
6. Forecast gaps that end in a stockout. Rank does not wait. On either account type, an out of stock period costs more than the units missed, because the position has to be rebought afterwards.
What to ask before you sign, whichever side you are on
Ask which account type they run daily and for how many brands. Ask for the name of the person who would hold your account and how many other brands that person carries. Ask what access they need and confirm it is granted through your own account permissions, revocable by you at any time. Ask what happens to the work if you leave: at Flapen you keep the Seller Central account, campaigns, creative, and a written handover, on 30 days notice.
Then ask for a written audit before any commitment. Ours comes back within 48 hours with prioritized fixes and no charge attached, and it is the cheapest way to find out whether a team understands the system you actually operate.
What most agencies will not tell you
Very few agencies specialize in Vendor Central, because the work is less visible and harder to attribute. Advertising, listings, and creative all photograph well in a case study. Recovering deductions does not. So a brand on 1P asking for help will often be sold a 3P scope with a new label on it, and the parts that would have moved the number are absent.
The second thing: a proposal that never mentions your account type is a template. Read the first page again. If it could have been sent to any brand on either system, it was.
Related answers
- Who to hire to run my Amazon FBA
- Red flags when choosing an Amazon partner
- Contract terms to negotiate with Amazon agencies
- Amazon agency vs in-house team pros and cons
- Amazon agency pricing and economics: the complete guide
Tell us which console you log into every morning and we will scope from there, at Flapen.
