Skip to main content
Vendor Central is the dedicated module inside 247CloudHub for sellers operating on the Amazon Vendor (1P) programme rather than (or alongside) the more common Seller Central (3P) marketplace. The two relationships look superficially similar to a buyer but are operationally very different, and Vendor Central handles the 1P-specific workflow. A 3P seller lists product on Amazon and Amazon takes a referral fee on each sale. A 1P vendor sells stock wholesale to Amazon, and Amazon retails it to the end customer. The order, the inventory, the invoicing, and the fulfilment models are different. CloudHub’s Vendor Central module is built for the 1P model, and 247CloudHub is one of the few multichannel platforms that handles both models from one console.

​
Vendor Setup

Path: Home, Vendor Central, Amazon Vendor Central Marketplace. The setup page mirrors the Marketplace Accounts page in the Configure module, but scoped to Vendor Central credentials specifically. The grid columns: Two view tabs at the top: View Existing Amazon Accounts and Add a Amazon Marketplace Account.

​
Adding a vendor account

  1. Click Add a Amazon Marketplace Account.
  2. Enter the vendor credentials supplied by Amazon (Vendor API key, vendor seller ID, target marketplace country).
  3. Authorise via the Amazon Vendor API authentication flow.
  4. Once authorised, the account appears in the grid. Toggle Status to Active.

​
Why Vendor Central credentials are different from Seller Central

The Vendor API and the Seller Partner API are different APIs with different authorisation flows, different rate limits, and different data shapes. A single physical Amazon account can be both a 3P seller and a 1P vendor, but each side requires its own connection. CloudHub keeps them separate so the right API is called for the right operation.

​
Organisation Settings inside Vendor Central

Path: Home, Vendor Central, Organisation Settings. This page is a Vendor-Central-scoped read of the same Company Details that show up under Configure Organisation Settings. Same fields: The page is the same data viewed in the Vendor Central context. Edits sync back to the master Configure record. The reason the page exists in Vendor Central: vendor users typically have access only to the Vendor Central module (not the wider Configure module), so the organisation details are surfaced where they need to read or edit them.

​
How Vendor Central differs from the rest of CloudHub

The other CloudHub modules are built around 3P (marketplace seller) workflows: orders flow in from Amazon Seller Central, eBay, the webstore, etc., are fulfilled by the merchant, and dispatch is direct to consumer. Repricing rules apply, Buy Box is the metric, Optimise pushes inventory levels per channel. Vendor Central is built around 1P (wholesale to Amazon) workflows:
  1. Orders are Purchase Orders. Amazon sends a PO to the vendor, not a buyer-to-vendor order. The vendor accepts, ships in bulk to an Amazon FC, and invoices Amazon.
  2. Inventory is wholesale. Vendor inventory exists in cases or pallets, not single units in bins. The “Add a Product” pattern is different.
  3. Two sub-models. Vendor Retail (RTV, ship cases to Amazon FCs) and Vendor Direct Fulfillment (DF, vendor ships individual units direct to consumer on Amazon’s behalf). Different paperwork, different SLA, different label schemes.
  4. No repricing. Amazon owns the retail price; the vendor agrees a wholesale price. Repricing rules do not apply.
  5. No Buy Box. Amazon retails the listing as-is; there are no other 3P sellers competing for Buy Box on a 1P listing.
This is why Vendor Central is its own module rather than a tab inside the standard 3P workflow.

​
How merchants use Vendor Central

Three patterns:
  1. Pure 1P seller. All trade is wholesale to Amazon Retail. CloudHub’s Vendor Central is the operational console; the rest of CloudHub is unused. Some sellers in this category use 247CloudHub for the Amazon-relationship reporting alone.
  2. Hybrid 1P and 3P seller. Some SKUs sold 1P (wholesale to Amazon), some SKUs sold 3P (Seller Central). CloudHub handles both from one workspace. The buyer differentiation between PO ingest (1P) and direct order ingest (3P) is automatic.
  3. Vendor moving to Vendor Direct Fulfillment. Sellers who started with Vendor Retail (ship cases to Amazon) moving to Vendor Direct Fulfillment (ship to consumer directly) use the Direct Fulfillment surface to gradually onboard SKUs to the new model.

​
Common questions

Can I run a single workspace for both 1P (Vendor) and 3P (Seller) on Amazon? Yes. Add the Vendor account in Vendor Central, the Seller account in Configure Marketplace Accounts. Both sync into the same workspace and the same Common Inventory. Does the Vendor Central inventory share stock with my Seller Central inventory? The Common Inventory is shared. A unit allocated to a Vendor PO decrements the Common Inventory; a unit sold via Seller Central decrements the same Common Inventory. The hybrid model only works if you carefully manage allocation between the two channels (typically with separate stock pools per warehouse or per virtual location). What happens when Amazon sends a PO that I cannot fulfil in full? Use Reject PO Items inside the Vendor Direct Fulfillment or Vendor Retail flow. CloudHub records the rejection, and Amazon’s PO management updates accordingly. Persistent rejection drops the vendor’s fulfillment-rate score, which is a chargeback risk. Is Vendor Central available for all Amazon marketplaces? Yes for all marketplaces where Amazon offers Vendor Central (UK, US, DE, FR, IT, ES, JP, others). Each marketplace is a separate vendor account under the same module.

​
Next steps