Vendor Central vs Seller Central: Where a 3PL Fits

By Bernardo Campelo, Forbes Business Council E-Commerce Leader, Amazon SPN Certified provider, Amazon SP-API authorized partner, and Founder of PrepVia.

A brand manager opens two tabs before the coffee finishes brewing. One is Vendor Central, where a purchase order landed overnight and Amazon is the buyer. The other is Seller Central, where the same brand lists a different set of SKUs and sells directly to the customer. Same company, same warehouse floor, two completely different sets of rules for what happens to a pallet next.

The confusion is rarely about the software. Both portals carry the Amazon name, and a buyer new to either account can be forgiven for assuming the difference is cosmetic. It is not. One account makes Amazon the retailer, and the brand sells wholesale into it. The other makes the brand the retailer, and Amazon is the marketplace and, for FBA, the warehouse. Every downstream decision, who writes the order, who sets the shelf price, how a mislabeled carton turns into money lost, follows from that one distinction.

The account decides who owns the inventory, who issues the order, and how a prep mistake turns into a deduction, and a prep center has to operate inside those rules rather than pick the ones it prefers.

Who Owns the Inventory in Each Account

Seller Central is a marketplace. A brand or reseller lists a product, keeps title to every unit until a customer buys it, and decides how many units to send into Amazon's fulfillment network and when. Whether Amazon picks, packs, and ships that unit through FBA, or the seller ships it directly through FBM, the inventory belongs to the seller the entire time it sits on a shelf, inside a prep center, or inside an Amazon warehouse.

Vendor Central works the other way. Amazon is the customer. A brand accepted into the program, most commonly by invitation rather than self-service signup, sells inventory to Amazon outright through a purchase order, the same way a supplier sells into any wholesale retail account. Once Amazon receives and accepts the shipment, Amazon owns the goods, sets the retail price, decides how much to reorder and when, and carries the inventory risk of a slow-moving SKU on its own balance sheet rather than the brand's.

That single fact, who owns the box once it clears receiving, explains most of the other differences between the two accounts. In Seller Central, the brand owns the inventory at every step up to the customer's doorstep. In Vendor Central, ownership transfers the moment Amazon accepts the purchase order shipment, and everything the prep center does before that moment has to satisfy a buyer's specification, not the brand's own preference.

This is why the two accounts attract different kinds of businesses. Our brand clients most often run FBA through Seller Central because they want direct control of price and the customer relationship. Our wholesale and distribution clients are the ones most likely to also hold a Vendor Central account, since selling wholesale into a large retail buyer is already how the rest of their business operates outside Amazon.

In Seller Central, the seller starts every replenishment cycle. The seller decides which ASIN needs more inventory, builds a shipment plan, and creates the inbound shipment inside Seller Central or through the Selling Partner API. Amazon does not ask for units. The seller offers them, and Amazon's own inventory performance signals, sell-through rate, days of cover, storage limits, tell the seller when to ship more.

In Vendor Central, Amazon starts the cycle. Amazon's own replenishment system forecasts demand and issues a purchase order to the vendor specifying the SKU, the quantity, the cost per unit, and a requested delivery date. The vendor's job is to accept or reject that purchase order within the window Amazon sets, not to decide independently how much inventory to send. A vendor can negotiate cost during onboarding, but once a PO is issued, the quantity on it is Amazon's number, not the vendor's.

Price follows the same split. A Seller Central seller sets the price a customer sees, subject to Amazon's own marketplace fair pricing policies. A Vendor Central vendor sets the cost Amazon pays for the unit. What Amazon charges the customer on the product page is Amazon's decision entirely, and a vendor can see its product marked up, discounted, or bundled into a promotion without a say in that specific choice.

The Purchase Order and the Delivery Window

A Vendor Central purchase order is a specific commercial document, not a general reorder request. It carries a PO number, a list of SKUs and quantities, an agreed cost per unit, a requested delivery date, and the distribution center the shipment is destined for. Accepting the PO, in whole or in part, is a commitment to deliver that quantity to that address by that date.

Amazon's vendor operations set a delivery window around the requested date, not a single day, and expect the shipment to arrive inside it. Arriving early can be as much of a problem as arriving late, since an unscheduled early delivery can be refused at a dock that planned its labor around the appointment it was given. Missing the window either way is one of the more common ways a clean purchase order turns into a chargeback.

Nothing about this delivery window exists in Seller Central the same way. An FBA seller creates a shipment plan and books a delivery slot through Amazon's own partnered carrier process, and a late shipment mostly costs the seller in check-in time and Amazon's own capacity limits, not a deduction tied to a specific purchase order number.

Chargebacks: How Bad Prep Becomes a Deduction on the Invoice

A Vendor Central chargeback is Amazon deducting money from what it owes the vendor, rather than sending a separate bill the vendor has to pay. The deduction shows up inside the payment remittance, often weeks after the shipment already left the dock, which means the vendor frequently learns about a labeling or case pack mistake long after anyone could have fixed it on the floor.

The most common causes trace directly back to prep and packaging. A carton labeled with the wrong UPC, a pallet built at the wrong height or case count, a case pack quantity that does not match the purchase order, a shipment that misses the delivery window, each of these can trigger a deduction sized as a percentage of the purchase order's value or a flat fee per unit or carton. None of it requires Amazon to prove intent. A mismatch between the paperwork and the pallet is enough.

This is a meaningfully different risk than what a Seller Central seller faces on an FBA shipment. There, a missing Amazon barcode gets applied by Amazon and logged as a defect on the Inbound Performance dashboard, other prep problems can get units refused, and a unit that arrives without proper prep loses its reimbursement if it is later damaged or lost. The FBA inbound defect fee is a separate charge for shipments that are misrouted, deleted, abandoned, or incomplete against the plan, which we cover in our breakdown of the FBA inbound defect fee. An FBA seller finds out about a labeling problem at check-in and can often correct the next shipment within days. A vendor finds out inside a remittance statement, after the fact, with no simple return path for units already accepted into Amazon's own inventory.

For a vendor running any real purchase order volume, this is the argument for treating physical prep, case pack count, pallet configuration, barcode placement, exactly to the routing guide's specification, as a financial control rather than a packaging preference. There is no dock associate available to wave through a shipment that is close enough.

Where EDI Actually Enters the Picture

Electronic Data Interchange, EDI, is the plumbing that most Vendor Central relationships eventually run through once volume passes what a person can key into a web portal by hand. A vendor can technically manage a small number of purchase orders directly inside the Vendor Central portal, reading each PO and confirming it manually. That does not scale past more than a handful of purchase orders a week.

At real volume, the purchase order itself arrives as an EDI 850 document. The vendor commonly confirms it with an EDI 855 acknowledgment. Before or at the time the shipment leaves for the distribution center, the vendor transmits an EDI 856 advance ship notice, the electronic document describing exactly what is on the truck, down to the carton and pallet level. After delivery, the vendor invoices Amazon through an EDI 810. A vendor with the scale to justify it usually hires an EDI provider or works through a value-added network to automate that exchange rather than keying documents by hand.

None of this exists in Seller Central. A seller can run FBA and FBM entirely through the Seller Central web interface or the Selling Partner API, with no EDI trading partner relationship required at any volume. That is one of the clearest practical differences between the two accounts, and it catches sellers off guard when they move from one to the other and expect the same tools to apply.

It is worth being precise about what a prep center actually does in this chain, since the phrase EDI gets used loosely. PrepVia does not transmit EDI documents on a vendor's behalf. What a prep center controls is the physical shipment, the carton count, the pallet build, the labels, and that physical shipment has to match the electronic advance ship notice unit for unit. An accurate 856 sitting on top of a pallet that does not match it is worse than no EDI at all, since it tells Amazon's system to expect something the dock will not find.

Routing and the Appointment at the Distribution Center

Once a purchase order is accepted, a Vendor Central shipment still has to get to the right building on the right day, and Amazon controls that process more tightly than it does for an FBA shipment. The vendor submits a routing request, specifying carton count, pallet count, and weight for the accepted PO. Amazon's transportation team returns routing instructions: which carrier to use, whether the freight moves collect or prepaid, and a scheduled delivery appointment at the specific distribution center named on the PO.

Arriving without that appointment, or outside the window it specifies, risks a refusal at the dock or another chargeback layered on top of any labeling issue. A shipment can be built perfectly and still get turned away for showing up on the wrong day. This part of Vendor Central resembles freight scheduling more than retail shipping, and it is worth reading alongside our broader guide to mastering Amazon inbound shipping, since the underlying freight mechanics overlap even though the paperwork does not.

Seller Central's version of this is lighter by comparison. An FBA seller creates a shipment plan, and Amazon's partnered carrier program books the pickup and the delivery appointment automatically once the plan is confirmed. The seller still has to show up on time, but the seller is not negotiating a routing guide or waiting on a separate transportation team's instructions before freight can even be booked.

What a Prep Center Can and Cannot Do in Each Model

What a Prep Center Handles

For a Seller Central FBA shipment, a prep center receives raw inventory, applies FNSKU or manufacturer barcode labels depending on the brand's registry status, a distinction covered in our guide to manufacturer barcode eligibility, poly bags or bundles items where required, boxes them to Amazon's FBA packaging specification, and either builds the inbound shipment plan directly or hands off a finished, labeled shipment ready to book.

For a Vendor Central purchase order, a prep center receives raw inventory, builds the case pack and pallet exactly to the configuration the routing guide specifies for that PO, applies the UPC or GS1-128 pallet labels Amazon requires, and stages the freight for whichever carrier the routing instructions named. The packing list and bill of lading it produces has to match the advance ship notice already transmitted, since a mismatch at the dock is exactly the kind of error that becomes a chargeback weeks later.

What Stays With the Brand

A prep center is not a party to either commercial relationship with Amazon, and there are real limits to what it can decide. Accepting or rejecting a purchase order, negotiating vendor cost, transmitting the EDI documents, and disputing a chargeback all sit with the brand or vendor, not with the warehouse packing the pallet. A good prep center will flag a problem it sees, a case pack that looks wrong against the PO, a delivery window that looks tight, but it cannot make the business decision on the brand's behalf.

Brands and wholesalers running both accounts at once tend to give their prep partner the clearest, most specific instructions per purchase order rather than a single standing spec, since a Vendor Central case pack and pallet configuration can change PO to PO in a way a static FBA prep instruction sheet per ASIN does not.

Vendor Central vs Seller Central, Side by Side

Put next to each other, the two accounts answer the same five questions in opposite ways.

The prep center's job looks similar on paper in both rows, get the physical product right, but the consequence of getting it wrong lands on a completely different financial mechanism depending on which account the shipment belongs to.

Frequently Asked Questions

What is the main difference between Vendor Central and Seller Central?

Vendor Central makes Amazon the buyer of a brand's inventory through a purchase order, and Amazon owns and resells the product at a price it sets. Seller Central makes the brand the retailer, keeping ownership of the inventory and setting its own price, whether Amazon fulfills the order through FBA or the brand ships it directly through FBM.

Who owns the inventory in Vendor Central versus Seller Central?

In Vendor Central, ownership transfers to Amazon once it receives and accepts a purchase order shipment at the distribution center. In Seller Central, the seller keeps ownership of every unit until a customer purchases it, regardless of whether the unit is sitting in a prep center, inside an Amazon fulfillment center, or in the seller's own warehouse.

What triggers a chargeback on a Vendor Central purchase order?

Chargebacks most commonly trace back to a mismatch between the physical shipment and the purchase order or the advance ship notice: wrong labeling, an incorrect case pack quantity, a pallet configuration that does not match the routing guide, or a delivery outside the requested window. Amazon deducts the chargeback from the payment it owes the vendor rather than issuing a separate invoice.

Do I need EDI to sell on Vendor Central?

Not at very low volume, since a vendor can technically manage a handful of purchase orders directly inside the Vendor Central portal. At any meaningful volume, EDI becomes close to a practical requirement, since purchase orders, acknowledgments, advance ship notices, and invoices all move faster and more accurately as EDI 850, 855, 856, and 810 documents than as manually keyed entries.

Can a brand sell on both Vendor Central and Seller Central at the same time?

Yes, and it is common among wholesalers and distributors that already sell to multiple retail accounts outside Amazon. Running both means managing two separate inventory pools, two pricing logics, and two sets of prep instructions, often for overlapping SKUs, which is why brands doing this successfully give their prep partner PO-specific instructions rather than one standing spec.

What can a prep center do for a Vendor Central purchase order?

A prep center can receive the inventory, build the case pack and pallet to the routing guide's specification for that PO, apply the required UPC or GS1-128 labels, stage the freight for the named carrier, and produce a packing list and bill of lading that match the advance ship notice. It cannot accept the purchase order, negotiate cost, transmit the EDI documents, or dispute a chargeback on the vendor's behalf.

Who is responsible when a prep mistake causes a Vendor Central chargeback?

Contractually, the vendor is responsible to Amazon for the chargeback, since the vendor is the party named on the purchase order. Whether the vendor can then recover that cost from its prep center depends entirely on the service agreement between the two, which is one more reason to confirm labeling and case pack accuracy in writing before volume moves through a new prep partner.

Final Take

Vendor Central and Seller Central are not two flavors of the same Amazon account. One is a wholesale relationship where Amazon buys the inventory and controls what happens next. The other is a marketplace relationship where the brand keeps that control and Amazon, through FBA, mostly provides storage and shipping. A brand running both is really running two different businesses through the same login credentials.

A prep center sits inside both relationships without being a party to either. It can build the physical shipment correctly, and correctly means something different in each account, an FNSKU label and a poly bag in one, a case pack built exactly to a routing guide in the other. What it cannot do is accept a purchase order, set a price, transmit an EDI document, or argue a chargeback with Amazon's vendor support team, since none of that touches the box on the pallet.

The mistake we see most often is treating the two accounts as the same operational problem with two different logins. A brand evaluating a 3PL for Vendor Central work should ask directly whether the facility has built pallets to a routing guide before, not just whether it can label an FBA carton, since the two skills overlap less than the shared word warehouse suggests.

Get the account right, get the prep instructions specific to the purchase order, and the rest of the relationship with Amazon, on either side of the login screen, becomes a normal vendor or seller operation rather than a recurring source of deductions nobody can fully explain.