Seller Central vs Vendor Central: Which Amazon Path Fits Your Brand

Seller Central and Vendor Central are not two skins on the same account. On Seller Central you are the third-party retailer: you list, you price, you own the inventory until a shopper buys, and you pay Amazon's published selling fees. On Vendor Central you are a wholesale supplier: Amazon issues purchase orders, Amazon owns the retail price on the detail page, and your "fee" is the gap between wholesale and retail plus the deductions on the remittance. For a $100K–$10M brand, the right path is whichever model protects contribution margin and catalog control on the ASINs that matter — and for many operators that answer is hybrid, not a pure choice.

This is the decision frame we use on Amazon marketplace ops before anyone rebuilds listings or ads: which portal owns each hero ASIN, who can edit the content Rufus reads, and whether the fee math still works after FBA or Vendor deductions. Pair it with listing work built for Rufus and backend attributes so the channel decision does not outrun the catalog.

What each portal actually is

Seller Central is Amazon's third-party (3P) marketplace console. Any eligible business can register, create listings (or join existing ASINs as a secondary offer), set a retail price, and fulfill with merchant fulfillment (FBM) or Fulfillment by Amazon (FBA). You remain the seller of record on the order. Shoppers see your offer competing for the Featured Offer (Buy Box) against other 3P sellers and, sometimes, against Amazon Retail.

Vendor Central is Amazon's first-party (1P) wholesale console. Access is invitation-based. Amazon Retail buys inventory from you on purchase orders (or related 1P programs such as direct fulfillment / drop-ship variants where those apply to your agreement). Amazon is the seller of record on the customer order. You negotiate cost, ship against POs (or fulfill under the agreed 1P model), and get paid on Vendor terms — not on the 3P payout cadence sellers watch in Seller Central.

1P vs 3P on Amazon

1P (Vendor Central) means Amazon Retail buys from you and resells to the shopper. 3P (Seller Central) means you sell directly to the shopper on Amazon's marketplace and pay Amazon fees for the privilege.

The vocabulary mismatch is why teams talk past each other. A "Vendor Manager" is a 1P relationship. A "Seller Support case" is a 3P workflow. Brand Registry enrollment can attach to either selling relationship, but content editing rights, advertising products, and chargeback rules still follow the portal that owns the commercial relationship for that ASIN.

Price, inventory, and who edits the page

The practical differences show up in three places operators feel every week: price, inventory risk, and page control.

Price

On Seller Central you set the offer price. You still compete under Buy Box rules — competitive pricing, stock, fulfillment speed, and account health all matter — but the dial is yours. That matters for MAP policy, promo calendars, and testing elasticity on a hero SKU.

On Vendor Central, Amazon Retail typically sets the customer-facing retail price. Your lever is the cost you negotiate and the terms around allowances. If Amazon decides to run a price cut to win the category, your wholesale cost does not automatically move with it. Brands that need tight MAP discipline often keep the sensitive ASINs on Seller Central for that reason alone.

Inventory

Seller Central with FBA: you ship inventory into Amazon's network, Amazon picks and packs, and you pay fulfillment and storage fees until the unit sells. Aged inventory and storage surcharges are your problem. Seller Central with FBM: you own fulfillment end to end.

Vendor Central on a classic PO model: Amazon buys (or commits to buy under the PO), takes title per the agreement, and the inventory risk profile shifts toward Amazon Retail — subject to returns, shortage claims, and chargebacks that still land on the remittance. Direct fulfillment / vendor flex-style setups change who holds physical stock; read your specific agreement instead of assuming "1P always means Amazon warehouses the units."

Content and catalog

Both paths still need complete backend attributes, honest bullets, and A+ that machines can extract. Rufus and off-site assistants do not award points for which portal uploaded the field. What changes is who can edit what, how fast.

On Seller Central, Brand Registry–enrolled brands usually have a clearer path to own and update listing content for their brand. On Vendor Central, content changes often route through Vendor workflows and Amazon Retail priorities — fine when the partnership is healthy, slow when a seasonal attribute fix is sitting in a queue. If AI shopping is already shaping discovery in your category, treat edit latency as a commercial risk, not a paperwork annoyance. The same Rufus-era listing discipline applies; the bottleneck is often access, not knowledge.

The fee math sellers actually feel

Seller Central publishes its selling fees. That transparency is the point of the model.

On top of the Professional plan, every sale carries a referral fee: a category percentage of the total item price, or a minimum (commonly $0.30), whichever is greater. Many everyday categories land in the 8–15% band — for example Consumer Electronics is often cited at 8%, while Home & Kitchen and several Beauty/Health bands sit at 15% above low price thresholds. Clothing uses tiered rates by price band. Media adds a closing fee on top of referral. Optional FBA adds per-unit fulfillment by size tier and weight, monthly storage by cubic foot, and aged-inventory surcharges when units sit too long.

None of that is mysterious. Pull Amazon's Revenue Calculator in Seller Central for a real ASIN, plug your price, and you get a net proceeds estimate before ads. Ads are separate — and how you judge them should follow TACOS, not ACoS alone.

Vendor Central looks "cheaper" because there is no referral fee line. The cost lives elsewhere:

• Wholesale cost below the retail price Amazon will sell at — your margin is negotiated, not residual after a published percentage.
• Co-op / marketing allowances and other program deductions that reduce what remits.
• Shortage, damage, and chargeback codes that show up after the PO ships.
• Payment terms (often Net 30 / 60 / 90 style cycles depending on agreement) that change cash conversion versus Seller Central disbursements.

A worked comparison shape (illustrative)

Take a mid-market home goods ASIN at a $40 retail price on Seller Central Professional:

• Referral at 15% → $6.00
• Plan fee amortized is small at volume (ignore for a single-unit view, or allocate ~$40/month across units)
• FBA fulfillment might run roughly several dollars depending on size tier — use the live calculator, not a blog guess
• Net before ads and COGS is retail minus referral minus FBA/storage minus returns reserve

On Vendor at a negotiated $22 cost into a $40 retail:

• Gross wholesale looks like $22
• Then subtract expected co-op percentage, historical chargeback rate, and the cash cost of Net-60 versus weekly Seller disbursements
• Amazon owns retail price moves; your contribution does not automatically follow a holiday markdown

The "winner" is whichever net contribution and cash cycle your brand can live with — not which portal sounds more prestigious.

When Seller Central is the better default

Choose or keep Seller Central as the primary path when most of these are true:

• You need price control for MAP, DTC parity, or aggressive testing.
• Your catalog changes weekly — new variants, attribute corrections, seasonal copy — and you cannot wait on Vendor content queues.
• You are still proving product-market fit on Amazon and need fast listing iteration.
• Advertising and organic measurement need to sit next to offer-level control (Sponsored Products structure, SPAG discipline where you use it, Brand Analytics tied to your 3P account).
• Amazon has not offered Vendor terms that beat your 3P contribution after honest deductions.

Seller Central is also the usual entry for brands that are not yet invited into Vendor. Chasing a Vendor invite before the 3P economics and catalog are healthy often trades control for a logo on a portal login.

When Vendor Central earns its seat

Vendor can be the right commercial home when:

• Amazon Retail demand for your ASINs is real and the cost + terms clear a better net than 3P after fees and ads.
• You want Amazon to carry more of the retail pricing and retail inventory burden under a classic PO model that fits your supply chain.
• Your team is thin on marketplace ops and a clean PO rhythm is easier than Buy Box, FBA aging, and 3P account health — accepting less page agility in exchange.
• Specific ASINs are replenishment staples where Amazon already wins the Buy Box as Retail and fighting 3P is wasteful.

Vendor is a poor fit when your brand story depends on frequent creative refreshes, tight MAP, or Rufus-facing attribute fixes that need same-week publication. It is also a poor fit when the invite exists mainly so Amazon can source cheaper — always model the remittance.

Hybrid is the grown-up answer for many brands

Most of the mid-market accounts we see that scale past early traction do not live in one portal forever. They assign portals by ASIN role:

1. 1

   Score each hero ASIN on control vs. contribution

   For the top 20 revenue ASINs, write two numbers: expected 3P contribution after fees/FBA/ads, and expected 1P contribution after cost/deductions/terms. Add a binary: "Must control retail price or listing weekly? Y/N."

2. 2

   Keep control ASINs on Seller Central

   Anything with Y on price or weekly content stays 3P unless Vendor terms are so strong the brand deliberately accepts the trade.

3. 3

   Move or open Vendor only where Amazon Retail clears the bar

   PO-friendly replenishment heroes with stable specs and acceptable net can sit on Vendor without starving the brand of agility elsewhere.

4. 4

   Keep one catalog source of truth

   Attributes, titles, and claim language should live in a master sheet that feeds both portals — the same discipline as multi-channel enrichment. Do not let Vendor and Seller drift into two conflicting product truths.

Hybrid fails when nobody owns the matrix. If marketing assumes Seller content rights while ops ships only Vendor POs on the same ASIN family, you get conflicting offers, confused Buy Box dynamics, and attribute edits that never land where Rufus reads them.

How this choice shows up in AI shopping

Portal choice is a commercial decision. Discovery is increasingly a data decision. Rufus and off-site assistants compare products on structured facts, review corroboration, and clear claims — not on whether the offer behind the ASIN is 1P or 3P.

What portal choice changes for AI-era ops:

• Edit speed: Seller Central usually lets a Brand Registry brand fix a wrong dimension or missing material field faster. Wrong fields create confident wrong answers; blank fields create non-answers. Both cost conversion.
• Evidence ownership: Reviews and Q&A still sit on the ASIN. Overclaiming on either portal manufactures negative evidence the same way.
• Ad vs. organic mix: On 3P you feel TACOS directly against your P&L. On 1P, Amazon Retail's retail media and pricing behavior can shift demand in ways your Vendor login only partially explains — measurement discipline still matters, but the levers differ.

So do not pick Vendor hoping it "fixes Rufus," and do not pick Seller Central hoping fees alone buy discovery. Pick the portal for margin and control, then run the catalog playbook on whichever login owns the page.

A one-afternoon decision checklist

If you need a shippable answer this week:

1. 1Export top 20 ASINs by trailing 90-day revenue.
2. 2For each, estimate 3P net (referral + FBA/storage from the Revenue Calculator + a realistic ad load via TACOS).
3. 3If you have Vendor history or an invite, estimate 1P net from actual remittances — not the pitch deck cost.
4. 4Flag ASINs that need weekly content or strict MAP → default Seller.
5. 5Flag stable replenishment ASINs where 1P net wins → Vendor candidates.
6. 6Write the hybrid matrix in one sheet and assign an owner.

When the matrix is messy — wrong browse nodes, thin attributes, A+ that is image-only — fix the listing substrate before you migrate volume between portals. Moving a broken ASIN from Seller to Vendor does not enrich it.