Wholesale and industrial distributors use Salesforce to coordinate selling across branches and sales roles. The ERP keeps running orders, inventory and price contracts. The CRM works best as the place where reps see the whole customer: its ship-to locations, open orders, buying history and falling volume. Most distributors leave pricing and fulfillment in the ERP and surface that data in Salesforce. Self-service reordering and supplier rebate tracking usually come after the core rollout.
Why do distributors need a different Salesforce setup than manufacturers?
A distributor sells thousands of other companies' products to thousands of customers, mostly through repeat orders. The selling job is protecting and growing an existing book, not chasing a few large deals.
That shifts where the value sits. Opportunities still matter for new accounts, project bids and line reviews. Yet most revenue arrives as everyday orders that never touch an opportunity record. A useful distribution org is built around accounts, order activity and rep coverage. Pipeline is one view among several, not the center of the design.
Distributors also carry supplier relationships that manufacturers usually do not. Vendor programs, rebates and co-op funds affect margin as much as customer pricing does. The CRM has to reflect both sides of the business.
How should a distributor model bill-to accounts, ship-to locations and branches?
Mirror the customer structure your ERP already uses, and keep the ERP customer number on every Salesforce account. Most distributors use a parent account for the bill-to and child accounts for ship-to locations.
Get this decision right before anything else, because reporting, territories and integration all depend on it. Points to settle early:
- Which level reps own: the corporate parent, the bill-to, or each ship-to job site or plant.
- How branches appear: as a field on the account, as a territory, or as a separate branch record used for reporting.
- Whether national or key accounts sit above regional bill-tos in a hierarchy with their own owner.
- How to handle one-time ship-to addresses, which can flood Salesforce with near-empty accounts if synced blindly.
- Which system creates new customers, and how a credit application becomes an active ERP account.
A common rule is that the ERP creates customers and Salesforce receives them. Prospects live in Salesforce until credit approves them. After that, the ERP number links the two records.
How do inside and outside sales teams share accounts in Salesforce?
Give each account a primary owner and record the second rep in an account team role. Then build activity views that show both reps' work on the same timeline.
Outside reps typically own the relationship and visit key buyers. Inside reps handle quotes, order follow-up and smaller accounts by phone and email. Conflict starts when both believe they own the same customer, or when commissions split unclearly.
Territory design follows the same logic. Some distributors assign by branch, some by geography, and some by vertical such as contractors or plant maintenance. Salesforce territory features can model overlapping coverage, but availability depends on edition. Ask your Salesforce account team which territory tools your licenses cover before you design coverage rules.
Keep the first version simple. A single owner plus a team role usually beats a complex territory model nobody maintains.
Should contract pricing stay in the ERP or be copied into Salesforce?
For most distributors, contract and matrix pricing should stay in the ERP, with Salesforce calling it or showing a summary. Copying every price into Salesforce only makes sense when reps quote heavily inside the CRM.
Distribution pricing is rarely a single price book. It layers customer contracts, branch price levels, cost-plus rules, quantity breaks and supplier special-pricing agreements. Rebuilding all of that in Salesforce creates a second pricing engine that must match the first exactly.
| Approach | Works well when | Trade-offs |
|---|---|---|
| ERP prices, Salesforce looks them up live | Reps need an accurate price for a known item while talking with a customer | Depends on ERP availability and a reliable API; quoting stays light inside Salesforce |
| ERP builds the quote, Salesforce records the outcome | Quotes are long, high-volume line lists created by inside sales | Reps switch screens; Salesforce sees totals and status, not every line |
| Selected prices mirrored into Salesforce | A defined set of contract items is quoted often in the CRM | Sync jobs must keep prices current; stale prices cause disputes |
| Full pricing rebuilt in a Salesforce quoting tool | Configured or project quotes need approvals and margin rules | Highest effort; two pricing engines must stay identical |
Catalog size matters too. Syncing hundreds of thousands of items into Salesforce products is rarely worth it. Many distributors sync only active or stocked items, or search the ERP catalog from the quote screen.
Can reps see order history and open orders without leaving Salesforce?
Yes, through integration or data virtualization. The choice depends on how fresh the data must be and how much you want stored in Salesforce.
Syncing order headers, and sometimes lines, gives fast reports and lets automation react to orders. Virtualization, such as Salesforce Connect with external objects, shows ERP records live without copying them. Virtualized data has reporting and automation limits, and Salesforce Connect is licensed separately. Check current terms and limits with your Salesforce account team.
A practical split is common. Sync summarized history for reporting and signals. Show open orders, backorders and invoice status live from the ERP on the account page. Our ERP integration guide goes deeper on which system owns each record and how often to sync.
How can Salesforce flag reorder gaps and customers drifting away?
Compare each account's recent purchasing with its own normal pattern, then alert the owning rep when buying drops or stops. These signals depend entirely on ERP order data reaching Salesforce.
Useful signals for a distribution book include:
- No order in longer than the account's usual reorder interval.
- A product category the customer bought regularly that has gone quiet.
- Rolling quarter sales well below the same period last year.
- Rising returns or credit memos on one account.
- A ship-to location that stopped ordering while its bill-to keeps buying.
Start with two or three signals and route them as tasks, not just dashboard tiles. Reps act on a call list; they rarely browse a chart looking for trouble.
How do supplier programs and rebates fit into the CRM?
Treat suppliers as accounts with their own contacts, programs and targets. Leave rebate calculation in the ERP or a dedicated rebate tool unless volumes are modest.
Salesforce can track which manufacturer programs a distributor joined, growth targets per line, and joint promotions or co-op activity. It can also log supplier-sponsored opportunities and special-pricing requests. Calculating earned rebates from invoice lines is heavy work best done where the invoices live. Salesforce does offer rebate functionality in some industry products; confirm the fit and licensing with your account team.
What about customer portals and B2B ordering?
A customer portal lets buyers reorder, check order status and download invoices without calling a rep. Distributors usually build it on Experience Cloud or B2B Commerce, depending on how much online ordering they need.
Experience Cloud fits account self-service: order status, documents, cases and a simple reorder request. B2B Commerce is built for real online buying with catalogs, carts and contract pricing. Both need live or near-live ERP pricing and inventory, so the integration work grows quickly. Packaging and licensing for these products change, so confirm current options with your Salesforce account team. Launch the portal after internal reps trust the order data, not before.
How should returns and RMAs be handled in Salesforce?
Run return requests as cases in Service Cloud, and let the ERP issue the RMA number and credit. The case holds the conversation; the ERP holds the money.
A typical flow captures the invoice, item, quantity and reason on the case. Someone approves it, the ERP creates the RMA, and the case closes when credit posts. Reason codes matter here. They show which suppliers, branches or items cause the most returns, which feeds supplier conversations later.
Which reports matter most to distribution leaders?
Share of wallet and margin by account matter most, and both depend on ERP data. Salesforce reports them well once invoice and cost data arrive reliably.
- Sales and gross margin by account, branch, rep and product category, sourced from ERP invoices.
- Share of wallet: actual purchases against an estimate of the customer's total spend in your categories.
- Accounts below their prior-year pace, ranked by revenue at risk.
- Coverage: key accounts without an outside visit or call in a set period.
- Quote volume and win rate for inside sales, where quotes are tracked in Salesforce.
- Return volume and reason by supplier line.
Agree on margin definitions with finance first. Distributors often argue over whether margin includes rebates, freight or branch allocations. Salesforce should display the ERP's answer, not invent its own.
What mistakes do distributors make when they roll out Salesforce?
Most failures come from loading too much ERP data or building processes reps never asked for. These are the patterns we watch for:
- Syncing every ship-to, item and order line before anyone knows which records reps will use.
- Rebuilding contract pricing in Salesforce and then fighting price mismatches with the ERP.
- Forcing every repeat order through an opportunity, which buries real pipeline in noise.
- Leaving inside sales out of design, so the people who touch accounts daily see little value.
- Launching a customer portal before order and pricing data in Salesforce is trusted.
How did one manufacturer and distributor connect NetSuite and Salesforce?
One manufacturer we worked with, in manufacturing and distribution, had a Salesforce org that multiple inexperienced admins had made hard to use. Reps were not using it, email was not captured, and NetSuite data sat apart from the CRM.
We consolidated record types and removed redundant fields and automations. We added Outlook integration to capture customer communications and integrated NetSuite through Boomi. We also automated lead assignment and built dashboards for lead flow and conversion. Afterward, all 99 of its reps were working in Salesforce, where nobody had used it before, and NetSuite and Salesforce data were unified. That was a Sales Cloud cleanup and integration project, not an industry-cloud rollout. Our NetSuite integration guide covers similar connections.
What belongs in a distributor's first Salesforce phase?
Phase one should give reps a trustworthy account view and a reason to open Salesforce every day. Pricing engines, portals and rebates can wait.
- Bill-to and ship-to hierarchy matched to ERP customer numbers.
- Account ownership for outside reps and team roles for inside reps.
- Order history summarized from the ERP, plus open orders shown on the account.
- Two or three reorder or decline alerts routed to reps as tasks.
- Email and calendar capture so activity is logged without extra typing.
- Sales and margin dashboards by branch and rep, sourced from ERP data.
Pilot with one branch or region and both sales roles. Expand once those reps open Salesforce daily without being reminded.
