Vendor Central vs Seller Central for Hybrid Brands

Vendor Central vs Seller Central comes down to who buys the product. In Vendor Central you sell to Amazon by purchase order, at a cost price Amazon approves. In Seller Central you sell directly to customers, at a price you set. One brand can run both, even on the same ASIN, but a listing never transfers between the two accounts.

A typical version of the question comes from a brand already selling to Amazon: "We sell through Vendor Central, and marketing wants Seller Central for the SKUs Amazon won't order. Can we run both on the same catalog, and what actually changes on each side?" The table answers the first half. The second half depends on each ASIN (Amazon Standard Identification Number) in the catalog.

The table is the same for every brand; the split is not. The Vendor Central MCP reads which ASINs are on open purchase orders, and the Selling Partner MCP reads which ones the brand holds stock and seller listings for, in one AI client. Each ASIN lands in first-party (1P), third-party (3P) or both on this month's orders, with Amazon Agent Atlas holding each account's rules while it sorts.

Vendor Central sells to Amazon and Seller Central sells to customers, and the two MCPs read what that changes

Vendor Central and Seller Central differ first in who the buyer is. Amazon's Brand Registry glossary puts it in one line each: a seller "has a Seller Central account and sells products directly to customers via the Amazon website," and a vendor "has a Vendor Central account and sells products to Amazon as a third party."

Amazon's own labels disagree there: its Vendor Central FAQ calls Vendor Central first-party (1P) and Seller Central third-party (3P), and this guide follows the FAQ. Everything else in the comparison follows from who buys.

Price

A vendor controls the cost price, which Amazon's Update costs page defines as "the price you would like us to pay you for your product." Amazon reviews a cost proposal within seven days, and an approved cost applies only to purchase orders issued on or after its start date. That page does not apply to Advantage vendors.

The retail price is Amazon's. Its Business discounts page says "We set retail prices independently." A vendor can supply a list price, such as a manufacturer's suggested retail price (MSRP), that reflects a price at which substantial sales are made by retailers; Amazon may not display one it cannot verify. A seller sets the price the customer pays, in Manage Inventory or through Automate Pricing rules.

Orders

A vendor receives purchase orders (POs) and "must confirm or reject all POs using the appropriate acknowledgement code within 24 hours of the order being placed." A low confirmation rate may lead Amazon to order fewer products, and delivering outside the shipping window can bring a cancelled PO and chargebacks. A seller receives customer orders and fulfills them itself or through Fulfillment by Amazon (FBA).

Service

On a Vendor Central sale, Amazon Customer Service handles the customer. On a Seller Central sale it depends on fulfillment. Amazon handles customer inquiries, refunds and returns on FBA orders. On orders the seller ships, customers contact the seller, unless the seller opts into Customer Service by Amazon for post-order contacts or ships Prime items through Seller Fulfilled Prime.

Money and reporting

A vendor is paid on payment terms "mutually agreed during the initial contract setup," and depending on those terms can take a cost discount for earlier payment through Quick Pay Discount. A seller pays Amazon a referral fee, a percentage of the total sales price, on every sale, plus a selling plan fee and, when Amazon fulfills, a per-unit FBA fee based on size and weight.

Vendors read sales and inventory in Amazon Retail Analytics (ARA) and customer search and buying behavior in Brand Analytics, both in Vendor Central. Sellers read Business Reports, and Brand Analytics once the brand's administrator grants access.

Those rows are also what the agent reads for each account. On the vendor side the Vendor Central MCP returns open POs and their acknowledgement status; on the seller side the Selling Partner MCP returns orders, FBA inventory and listing state. The table above is the static version; the agent fills it in per ASIN.

A brand can run Vendor Central and Seller Central on the same ASIN, and Atlas holds the rules that keep them separate

A hybrid brand runs both accounts at the same time, and Amazon allows it in so many words. Its Vendor Central FAQ says "a supplier can maintain both accounts simultaneously, as these are separate services that serve different business models," and that "sellers and vendors can sell identical products on the same ASIN at the same time."

The same answer sets the three rules a hybrid brand operates under:

1. No transfers. "Direct listing transfers are not possible, and each requires independent listing creation." A product listed in Vendor Central has to be created again in Seller Central.
2. The Featured Offer decides who serves the customer. "The responsibility for customer assistance is determined by Featured Offer ownership at the time of purchase." Amazon's Featured offer page for vendors notes that Amazon, vendors and third-party sellers can offer the same product, and each eligible offer may become the featured one, "based on price, delivery speed, and other factors."
3. Brand Registry spans both. A brand Administrator assigns selling roles, Brand Representative or Reseller, to Seller Central accounts and Vendor Central accounts alike, and an account ID starting "amzn1.pa.o" identifies a vendor or seller company across Amazon's marketplaces.

Amazon Agent Atlas carries these rules from Amazon's own help pages, so the agent quotes the FAQ rather than a forum post when it explains a split.

Vendor Central is invitation-only, so the choice is per ASIN, starting from the POs the Vendor Central MCP reads

Vendor Central is not an account a brand opens on its own. Amazon's FAQ states "Vendor Central is invitation-only," and About Vendor Central adds that it "requires that you have a trademark registered for the products you sell to Amazon." A reseller, or a brand without a registered trademark, is pointed to other ways to sell on Amazon.

That shapes the decision. A vendor already in Vendor Central is not choosing an account; it is choosing, per ASIN, between waiting for Amazon's purchase orders and listing the product itself. The Vendor Central MCP shows which ASINs have no open PO behind them, and Atlas carries the terms of Amazon's one route before a seller offer.

That route is Born to Run. If Amazon has not placed a PO and you own the brand, you may be able to request an order by submitting "a quantity you think will sell for 10 weeks," which Amazon reviews and, if approved, buys. Participation is "by invitation only, at Amazon's sole discretion," and units unsold after the 10-week sell-through period follow the disposition path you chose when you submitted the request.

Seller Central's two selling plans

• Individual: $0.99 per item sold, with no subscription fee.
• Professional: $39.99 a month when you have active listings, so more than 40 sales a month covers it. It includes the Selling Partner API (SP-API), bulk listings and automated pricing, which matters for the next section.

Managing Vendor Central day to day means confirming POs inside the 24-hour window, proposing costs, and keeping list prices current. Suppliers can also invite brokers or third-party managers, who "can then manage multiple brands through account page drop-downs."

The Selling Partner API reaches both accounts, so one AI client runs the Vendor Central MCP and the Selling Partner MCP side by side

Both accounts sit on the same API family. Amazon's Listings APIs page says they are "available to all selling partners including vendors and sellers." Vendors authorize an application per vendor group, which covers every vendor code in it, and Amazon's developer docs allow a maximum of 10 vendor groups per application through self-authorization. Sellers get SP-API access on the Professional plan.

That is what lets a hybrid brand run both accounts from one place. Kuudo connects the Vendor Central MCP, for purchase orders, shipments, invoices and Retail Analytics, and the Selling Partner MCP, for orders, inventory, pricing and listings, to the AI client the team already uses.

The question that opened this guide becomes one request: which ASINs has Amazon ordered on POs in the last month, and which do we hold FBA stock for with no PO behind them? The agent reads the purchase orders through the Vendor Central MCP and FBA inventory and seller listings through the Selling Partner MCP, then sorts each ASIN into three lists: covered by Amazon's orders, candidate for a seller offer, or already on both.

Around the two accounts

• Advertising: vendors and sellers advertise through the same Amazon Ads API, so the Amazon Ads MCP runs campaigns for both.
• History: Amazon Agent Flow lands Selling Partner and Ads data in a lake in your own cloud, so questions across months of orders and ad spend do not wait on live API calls.
• The rule: which ASINs stay first-party is the brand's call, written once as a Skill the agent runs the same way every time.
• Approval: creating a seller listing is a write, and write tools apply your workspace policy, which may require someone to approve each listing before it goes live.

What happens next: split the catalog by ASIN, then write the split as a Skill

Start from the catalog, not the account. For each ASIN, the agent answers three questions from live data: is Amazon ordering it on current POs, do we hold our own stock for it, and which offer holds the Featured Offer now. The answers sort it:

• Amazon orders it: it stays in Vendor Central.
• Amazon has stopped ordering it: a Born to Run request comes first if your business is invited, then a seller offer.
• It runs on both: watch which offer wins the Featured Offer, because that also decides who answers the customer.

Then connect the second account the Amazon way: assign the selling role in Brand Registry, create the listings in Seller Central (they will not transfer), and keep confirming POs inside 24 hours on the vendor side, because a low confirmation rate may cost orders.

The pattern is one catalog, two relationships with Amazon, and a rule per ASIN instead of a policy per channel.

Next: confirmed POs carry chargeback risk when a delivery misses its window, so Dispute Amazon PO On-Time Accuracy Chargebacks covers what to do when one lands.