The Wholesale distribution landscape
In distribution, the ERP is the business. Orders, inventory, contract pricing, vendor costs and rebates all run through it, and the people who run it are cautious for good reason. A pricing error on thousands of SKUs is expensive. So your first job is to show that Salesforce will not compete with the ERP. It shows reps and customers what the ERP knows, adds the activity and account planning the ERP was never built for, and sends back only what the ERP needs.
- 01
Buying decisions usually sit with the owner, president or COO in privately held distributors, with the VP Sales as the champion and the IT or ERP manager as the gatekeeper.
Larger distributors may have a dedicated sales operations or e-commerce leader. Family ownership and long tenure are common, which means relationships and trust move deals more than slide decks. Expect a careful buyer who wants references from businesses that look like theirs.
- 02
The sales model is different from manufacturing.
Distributors usually have outside reps who visit accounts, inside reps who take orders and quote by phone, and counter or branch staff. Coverage overlaps. Compensation is often on gross margin, not revenue, so margin data matters to reps more than almost anything else you can show them. Territory and account ownership questions will come up in the first meeting.
- 03
Digital ordering is the other pressure point.
Ask whether customers are asking to reorder, check stock or see their negotiated pricing online, and whether a competitor already offers it. Salesforce B2B Commerce supports reorders with pre-negotiated pricing, buyer-specific entitlements and ordering on behalf of other locations, according to Salesforce's product page. That conversation usually belongs in phase two, after accounts and order history are visible in Salesforce.
Who buys, and how to open with them (5)
Owner, President or COO
Cares about: Growing share of wallet with existing customers, protecting margin and not betting the company on a system change.
“Of your top 200 accounts, how many are buying less from you than they did two years ago, and do you know why?”
- Where do you think you are losing share inside accounts you already serve?
- What would you need to see in the first six months to call this a success?
- Who else has to be comfortable with this decision before you sign?
VP Sales
Cares about: Rep coverage, account growth, margin by rep and keeping top performers productive without adding admin work.
“When an outside rep walks into an account, what do they know about that customer's last 90 days of orders, and where did they get it?”
- How do outside and inside reps split accounts, and where does that cause friction?
- How do you spot an account that is slowly buying less, before it is gone?
- How are reps paid, and what data do they argue about at commission time?
Inside Sales or Customer Service Manager
Cares about: Call volume, quote speed and how much of the day goes to order status questions that a customer could answer for themselves.
“What share of the calls your team takes are someone asking where their order is?”
- How do quotes get built today, and how many follow up before they expire?
- What happens to a quote that is not converted to an order?
- How do returns and credit requests come in, and who tracks them?
IT Director or ERP Manager
Cares about: Keeping the ERP stable and authoritative, limiting custom code and avoiding a second pricing engine that drifts out of sync.
“Which data should never be edited outside the ERP, and which data do your sales teams ask you for that the ERP cannot give them easily?”
- Which ERP do you run, and how do other systems connect to it today?
- How is your customer hierarchy structured: bill-to, ship-to, branches?
- Who would support an integration once it is live?
Purchasing or Vendor Relations Manager
Cares about: Supplier programs, vendor rebates and co-op funds, and showing suppliers the growth that earns better terms.
“When a supplier asks how you are growing their line, how long does it take you to answer?”
- How are vendor rebate and growth programs tracked against your sales today?
- Do suppliers send you leads or project opportunities, and what happens to them?
- Which supplier programs do you think you are under-claiming?
The problems worth solving (7)
Account decline goes unnoticed
Customers rarely leave a distributor in one step. They move a product category to a competitor, then another. Order history in the ERP shows it, but nobody looks until the annual review. By then the buyer has a new primary supplier. Reps who manage 100 or more accounts cannot watch every trend by hand.
Where Salesforce fits: Sync order history from the ERP to Sales Cloud and build alerts or tasks when an account's buying falls below its own pattern. Tableau or CRM reports show decline by category and rep.
Inside and outside sales collide
Outside reps own the relationship while inside reps take the orders and quotes. Neither sees the other's notes. Customers repeat themselves, and reps argue over credit. Managers cannot tell who is actually working an account, and coverage gaps appear in the accounts nobody claims.
Where Salesforce fits: Sales Cloud account teams give each account a primary owner and supporting roles, with shared activity history so both reps see every call, visit and quote.
Order status calls swamp inside sales
Customers call or email to ask about order status, tracking, backorders and invoices. Each call pulls an inside rep away from selling. The answers already exist in the ERP, but customers cannot reach them on their own, and the team ends up acting as a lookup service.
Where Salesforce fits: An Experience Cloud customer portal shows order status, invoices and documents from the ERP. B2B Commerce adds online reorders with contract pricing when the customer is ready for full digital ordering.
Quotes disappear after they are sent
Inside reps send dozens of quotes a day from the ERP or email. Nobody tracks which ones were won, lost or ignored. Follow-up depends on memory. Lost quotes hide useful information about pricing and stock problems that management never sees.
Where Salesforce fits: Bring ERP quotes into Sales Cloud as opportunities or quote records with a follow-up task. Report win rate and lost reasons by product line and rep.
Margin data stays in finance
Reps are paid on gross margin, but they see it only on a monthly commission report. They cannot tell during a negotiation whether a deal is good business. Managers find margin erosion after the fact, when price exceptions have already become the customer's expected price.
Where Salesforce fits: Show margin history by account and product on the Salesforce account record, sourced from the ERP. Tableau dashboards give managers margin trends by rep, branch and customer.
Returns and credits run on email
Return requests arrive by phone, email and through reps. Nobody can see how many are open or why customers return product. Credits are delayed, which irritates customers and leaves disputes on the books. Patterns that point to a supplier quality problem never surface.
Where Salesforce fits: Service Cloud cases for return requests, with the ERP issuing the authorization and credit. Case reasons give purchasing the data to raise problems with suppliers.
Supplier programs are under-claimed
Vendor rebates, growth incentives and co-op funds depend on tracking sales by supplier line. That tracking often lives in a purchasing spreadsheet. Distributors leave money unclaimed and cannot show suppliers the growth that would earn better terms or more leads.
Where Salesforce fits: Track supplier programs and supplier-sourced opportunities in Salesforce, with sales by line reported from synced order data. Leave rebate calculation in the ERP or a dedicated tool.
The numbers leaders run on (7)
Gross margin by account, rep and product line
Distributors live and die on margin, and reps are often paid on it. ERP cost and sales data shown in Salesforce lets reps see it during the conversation, not after.
Share of wallet and category penetration
Growth usually comes from selling more categories to existing accounts. Order history by category in Salesforce shows which accounts buy only one or two lines.
Account retention and decline rate
Leaders watch how many accounts drop below their normal buying pattern. Synced order history plus decline alerts make it visible each month.
Quote win rate and follow-up time
A quote with no follow-up is usually lost. Quote records and tasks in Sales Cloud measure both.
Order status calls per day
Inside sales managers count them because they crowd out selling. Case and call logging in Salesforce gives a baseline before launching a portal.
Online order share
Leadership tracks how much volume moves to self-service channels. B2B Commerce or portal order data reports it alongside rep-entered orders.
Return rate and credit cycle time
Returns cost margin and goodwill. Service Cloud cases tied to ERP credits show volume, reason and time to close.
Product fit (7)
Cross-sell sequence (5)
- Sales Cloud Experience Cloud customer portalInside sales says most calls are order status, tracking or invoice copies.
- Experience Cloud portal B2B CommerceCustomers ask to reorder online, or a competitor has launched online ordering with contract pricing.
- Sales Cloud Service CloudReturns and credits are tracked in email, or customers complain that credits take weeks.
- Sales Cloud with ERP data TableauLeadership asks for margin or category trends that need more than standard reports.
- Service Cloud AgentforceA high share of inbound questions can be answered from order and shipment data alone.
Objections, and what to say (6)
"Our ERP does everything we need."
Agree that the ERP handles orders, inventory and pricing, and say you do not want to change that. Then ask the VP Sales what an outside rep sees before a visit, and how the team spots declining accounts. The ERP records transactions. It does not plan accounts, coordinate inside and outside reps or tell a rep that a customer has quietly moved a category to a competitor. Salesforce sits on top and shows ERP data in a form reps will use.
"Our reps are relationship people. They won't log activity."
Do not lead with logging. Lead with what reps get: order history, margin and open quotes on their phone before a visit. Reps paid on margin will open a system that shows them margin. Keep activity capture light, with email and calendar sync where possible. Then measure adoption by logins to account pages, not by fields filled. The NetSuite case study shows a manufacturer that went from zero adoption to all 99 reps once ERP data was in Salesforce.
"Pricing is too complex to put in Salesforce."
Good, because you should not put it there. Contract pricing and cost belong in the ERP. Salesforce can call the ERP for a price at quote time or show a pricing summary on the account. Rebuilding thousands of customer-specific price rules in a second system is how CRM projects fail in distribution. Say that plainly. It builds trust with the ERP owner and removes the biggest perceived risk.
"We tried a CRM years ago and nobody used it."
Ask what the reps saw in it. Usually the answer is nothing they could not get faster elsewhere, because it had no ERP data. Ask whether the old system had order history, margin or open orders. If not, the failure was about data, not about reps. Suggest scoping phase one around account visibility and decline alerts. Offer the free health check through Abstrakt if they have a dormant Salesforce org that needs an honest assessment first.
"Our customers don't want to order online."
Some will not, and you do not need them to. Start with the portal for order status and invoices, which saves inside sales time even if no customer ever places an order online. Then watch what customers do. If they start asking for reorder buttons, B2B Commerce is the next step. Ask which of their customers already buy online from other suppliers. That answer usually changes the conversation.
"We can't afford a long implementation."
Keep phase one narrow: account hierarchy, order history sync, account teams, decline alerts and a margin view. That scope stays small enough to show results quickly. Portals, commerce and service come later, funded by results from phase one. Ask the owner which single number they want to move this year, and design phase one around it. Abstrakt can outline a phased scope and reply within four business hours.
Implementation watch-outs to raise before signature (5)
Mirror the ERP customer hierarchy
Bill-to, ship-to and branch structures must match the ERP or reports will never reconcile. Store the ERP customer number on every account. Decide upfront how parent companies with many ship-to locations roll up, because changing that later breaks reports, territories and integrations.
Do not rebuild pricing
Customers will ask for pricing in Salesforce. Resist copying price lists and contracts. Call the ERP live or show a summary. A second pricing engine drifts out of sync within months, and every mismatch damages trust with reps and customers.
Define account ownership early
Inside and outside reps, branch staff and key account managers often all claim the same customers. Settle primary owner, team roles and commission credit before the build. Otherwise the project becomes a referendum on compensation and stalls. Get the VP Sales to sign the rules.
Size order history sync carefully
Distributors can have millions of order lines. Decide how much history reps need, at what level of detail, and whether summaries by month and category are enough. Syncing everything slows the org and adds storage cost without helping reps sell.
Phase the portal and commerce work
Start with a read-only portal for order status and invoices. Add reorders and online buying later. Launching full commerce before the catalog, images and contract pricing are clean leads to abandoned carts and frustrated customers. Let portal usage tell you when customers are ready.
Qualify honestly
Strong fit
- The owner or COO can name a growth or retention problem in the existing customer base.
- The ERP owner is engaged and supports showing ERP data in Salesforce.
- Inside sales is overloaded with order status and quote follow-up work.
- Reps are paid on margin and want to see it before they negotiate.
Risky fit
- The buyer wants to replace ERP pricing or order entry with Salesforce in phase one.
- Nobody can describe the customer hierarchy or who owns which accounts.
- The ERP is end-of-life with no replacement chosen.
- Leadership expects full online commerce at launch with an unclean product catalog.
Case studies to send (2)
Questions (4)
Should I pitch Manufacturing Cloud to a distributor?
Usually not as the lead. Most distributors need Sales Cloud with strong ERP integration first. Consider Manufacturing Cloud when the distributor runs long-term volume agreements with customers, since Salesforce describes its sales agreements as covering customers, distributors and suppliers.
What is the fastest way to show value in a distribution deal?
Pick 20 real accounts and show what a rep would see: order history by category, margin trend and an alert for a declining account. Use the customer's own exported data if they will share it. That demo answers the adoption objection before it is raised.
Who signs in a privately held distributor?
Usually the owner, president or COO, often with a CFO or controller reviewing the numbers. The VP Sales champions it and the ERP manager can block it. Meet all three before you send pricing.
How can Abstrakt help on a distribution deal?
Abstrakt has 138 certifications and has connected Salesforce to ERPs such as NetSuite. We reply to AEs within four business hours and can scope a phased plan or run a free health check for customers you refer.