A wholesale channel needs seven layers of tooling, and an Amazon seller already owns none of them, because Seller Central covers the equivalent of all seven for the marketplace and hides the fact that they are separate jobs. The layers are: a source of candidate accounts, verification, a record of accounts, a way to send and follow up, a catalog the buyer can read, a way to take and fulfill an order, and a view of what is working.
Most brands start by buying the fourth layer, discover their list is the problem, then buy the first, and end up with two subscriptions and no record of who they talked to. Working through the layers in order is cheaper and faster.
Layer one: where candidate accounts come from
Everything downstream is determined here. A perfect email to the wrong company produces nothing, and the most common reason a first wholesale push fails is a list assembled from whatever came to mind.
There are three honest sources. Manual research, which means reading store sites, distributor catalogs and trade directories and writing down what you find. General business databases, which cover companies broadly but rarely know what a store stocks. And product-led research, where the starting point is your item and the output is the kinds of retailers and distributors that carry that kind of item.
For a brand with one product line, the third is the one that matches the question you are actually asking. Paste your listing into WholesalePilot and the preview shows which distributors and retailers would plausibly stock it, which gives layer one a real starting point instead of a blank spreadsheet.
Whatever the source, insist on four fields per row: company, type, what they stock, and how they buy. A row missing the last two is a name, not a lead.
Layer two: verification, before anything is sent
Verification checks that an address exists before you use it. It is a separate layer because it protects an asset that takes months to rebuild, which is the reputation of the domain you send from.
Mailbox providers treat a high bounce rate as evidence of scraped data and respond by filtering everything you send, silently. One careless campaign can put you in that state for a quarter.
The practice is short. Verify every address before the first send. Remove invalid ones. Treat catch-all domains, where the server accepts anything and confirms nothing, as a separate lower-volume group. Prefer a named contact over a shared inbox. Re-verify any list older than a season, because retail staff turnover is high.
This layer also does something unglamorous but valuable: it forces the list to be deduplicated. Retail groups own multiple store names, and sending the same pitch three times to one buying office is a bad first impression that costs nothing to avoid.
Layer three: a record that thinks in accounts, not orders
This is the layer Amazon sellers most underestimate, because the marketplace never required it. On Amazon, the unit of everything is an order, and the customer is anonymous. In wholesale, the unit is an account, and the order is an event inside it.
A record built for accounts holds the company, every person you have dealt with there, every message in both directions, the samples you sent, the prices you quoted, the terms you agreed, the purchase orders, and the dates that matter such as their category review. When the buyer changes jobs, the history stays with the company, and the new buyer inherits a relationship rather than a cold start.
A record built for orders holds none of that. It knows what shipped and to where. If you try to run wholesale out of your order history or your accounting software, what you lose is exactly the information that makes the second conversation better than the first.
It does not have to be expensive. A spreadsheet with one row per account and a linked sheet of interactions works for the first fifty accounts, and it is better than an unused product. What it cannot do is remind you, which is why it stops working somewhere past a hundred accounts.
Layer four: sending and following up
The mechanics of this layer, including domain choice, warm-up, cadence and the rule about stopping on reply, are covered in full in outreach automation for Amazon sellers. Two points belong here rather than there.
First, this layer has to write into layer three. A sending tool that keeps its own contact list separate from your account record guarantees a split brain within a month, where the sequence thinks a company is cold and you know you met them at a trade show.
Second, judge it by reply handling rather than by sending features. Every product in this category can send a sequence. The ones worth paying for make it easy to see who replied, what they said and what you owe them today.
Layer five: the catalog a buyer can actually read
A buyer needs a document, not a link to a marketplace listing. Three artifacts cover almost every request.
- A one-page sell sheet per item. Photograph, description, item number, unit barcode, case pack, case dimensions and weight, wholesale price, suggested retail, minimum order.
- A line sheet. The same fields for your whole range on one page, which is what a buyer forwards internally.
- An item setup file. A spreadsheet of every attribute a retailer's system demands. Build it once and reuse it, because every new account asks for the same fields in a different order.
Keep them in one place with the current version obvious. The most common failure here is three versions of the price list in circulation, one of which a buyer is quoting back at you six months later.
Layer six: taking and fulfilling the order
Purchase orders arrive by email, through a portal, or over a structured data exchange for larger retailers. Each one has to be acknowledged, picked, shipped to a routing guide and invoiced against the right terms.
An Amazon seller's instinct is to route this through the marketplace's fulfillment, which works for small direct orders and fails at pallet scale. The operational choices are laid out in wholesale fulfillment for Amazon sellers, and the systems that run this layer as you grow are covered in B2B software for Amazon sellers.
The one piece to get right immediately is the invoice, because it is where terms, tax status and deductions all meet. Get the format right on the first account and every later one is a copy.
Layer seven: seeing whether any of it works
The last layer answers one question: which activity produces accounts that reorder. Reply rate by account type, accounts opened per hundred contacted, revenue per account, days to first reorder, and the share of accounts that ordered twice.
None of that appears in Seller Central, and most of it is derivable from layers three and six if those are kept honestly. How to assemble the view is in analytics for the wholesale channel.
What the whole stack costs and where to start
| Layer | Start with | Upgrade when |
|---|---|---|
| Accounts and verification | A researched list, verified | Manual research caps your volume |
| Account record | A spreadsheet | You miss follow-ups |
| Sending | One warmed mailbox | Replies get lost |
| Catalog | A sell sheet and line sheet | Buyers ask for setup files |
| Orders and analytics | Templates and a tab | Orders outgrow email |
Start at the top and only move down when the layer above is actually constraining you. A brand with fifty verified, well-chosen accounts and a spreadsheet will out-sell a brand with a full software stack and a list of names, every time.
Questions Amazon sellers ask about a wholesale stack
Do I need a CRM on day one? You need a record. A spreadsheet is a record. Buy software when forgetting a follow-up is costing you accounts.
Can I run wholesale out of Seller Central? Only the Amazon business customer side of it, which is a different channel with its own mechanics, covered in Amazon seller B2B sales. Independent retailers and distributors live entirely outside it.
How many tools is too many? If you cannot name the decision each subscription informs, that is too many. Five is a normal ceiling for a small brand running two channels.
What is the most common gap? Verification. It is skipped because it seems administrative, and it is the layer that determines whether anything you send is read.
Should the catalog be a portal or a document? A document first. Portals earn their place once repeat buyers are reordering regularly, not while you are still winning the first accounts.