What is different in wholesale sales
A wholesaler's revenue looks stable from a distance and leaks constantly up close. The top hundred accounts reorder weekly through the ERP or the B2B webshop, no salesperson involved. Meanwhile some of them are quietly trialling a competitor, a few are shrinking with their own markets, and the growth has to come from accounts nobody has opened yet. Sales in wholesale is what happens at the edges of the order stream.
Three motions matter. Hunting: opening new accounts, from first contact to first order, which runs weeks to months and is won on assortment, terms and delivery reliability. Growing: putting more of your range into accounts that only buy one category. Defending: spotting order decay early and visiting before the competitor's rep becomes the incumbent. Each motion has a different rhythm, and only the first looks like a classic pipeline.
Buyers are pragmatic professionals. A purchasing manager or owner-operator who cares about margin, availability and whether you deliver on Tuesday like you said. Loyalty is real but conditional, and switching is easy in the age of B2B webshops.
An example wholesale pipeline
The new account pipeline we deploy for distributors and importers. It ends at proven reordering, not at the first invoice.
| Stage | Exit criterion |
|---|---|
| Qualified account | Assortment fit and yearly potential estimated, buyer identified. |
| Visit or demo held | Meeting done, current supplier and terms documented. |
| Terms proposed | Prices, minimums and delivery terms on the table. |
| First order placed | Opening order received and delivered. |
| Reordering | Second and third order placed. The account is habit now. |
That final stage is deliberate. A first order in wholesale is a trial, not a customer. Accounts that never reorder are the industry's silent kill zone, and keeping the deal open until the habit forms makes the leak measurable. Range extension and win-back deals run in a second pipeline. The split follows the process rule from pipeline design, and the deals in it are created by triggers, not by memory.
The fields and automations that matter
Fields: customer segment as a fixed list, region or territory, expected annual purchasing, current supplier, price tier, and product categories bought as a multi option. The categories field powers the range gap report, which shows every account buying category A but not category B. That one view generates a season of warm visits. Hold every other field against the standard in custom fields that earn their place.
The automations lean on ERP data. Order gap alerts open a defend deal when last order date exceeds the account's normal rhythm. A first order trigger creates the onboarding sequence: a thank you call task, a second order check at three weeks, a range conversation at two months. And territory routing assigns new leads by region field the moment they arrive. Wire the monthly ERP sync per account, revenue and last order date, through the API or middleware, and the Insights dashboards start showing account health instead of anecdotes.
Trade fairs deserve their own workflow, because they remain the biggest new account source in most wholesale categories. Scan or import fair contacts into the Leads inbox the same week, tagged with the fair name as source, and open deals only for the ones a rep qualifies. Teams that let fair leads sit in a spreadsheet until October lose the season, and teams that dump every scanned badge into the pipeline as a deal drown it. The middle path is exactly what the lead inbox exists for.
Common mistakes
The cardinal mistake is syncing every order into the pipeline. Ten thousand small deals make every report meaningless and train the team to ignore the CRM. Orders are data on the account. Deals are things a human wins.
The second is closing the new account deal at first invoice. Measure to reorder, or the team optimises for openings that evaporate.
The third is running defence on gut feel. Without the order gap alert, reps visit the friendly accounts, not the leaking ones. The data exists in the ERP. The alert is one integration away.
The fourth is importing the full ERP customer file as open deals, which buries the twenty real opportunities under two thousand sleeping accounts. Import organisations with their history, open deals only where a motion is live, and keep the file clean with the routine from data hygiene.
Questions
Do repeat orders belong in Pipedrive?
Routine reorders, no. They live in the ERP or webshop and would flood the pipeline. What belongs in Pipedrive is the exception: a reactivation after silence, a range extension, an annual agreement. The rule is simple. If a salesperson has to win it, it is a deal.
How do we manage price lists and customer-specific discounts?
The ERP owns pricing. In Pipedrive, store the customer's price tier as a field and use products with the standard list for quoting new business. Rebuilding a discount matrix in CRM fields creates two versions of the truth, and finance will trust neither.
Can Pipedrive handle rep territories?
Yes. Ownership rules plus visibility groups map cleanly onto geographic or account-based territories. Automatic assignment by postcode or country field works through workflow automation. What Pipedrive will not do is optimise territory boundaries for you.
What does a field rep actually log after a customer visit?
One activity with three lines: what changed at the customer, what was promised, next visit date. The mobile app makes this a two minute car park habit. Setups that ask for more per visit get nothing per visit.
How do we spot accounts we are losing to a competitor?
Order gap detection. Push last order date from the ERP into Pipedrive and alert when a customer exceeds their usual ordering rhythm. Wholesale customers rarely announce a switch. They just order less, then stop.