CRM for Manufacturers and Wholesalers
By CodexierPublished 6 min read
A manufacturer or wholesaler already has a system of record: the ERP or business system that holds customers, articles, prices and every order ever shipped. The sales team, meanwhile, works from memory, email and a spreadsheet of visits. A CRM only earns its place in this business when it shows the salesperson what the ERP knows, in the moment they are talking to the customer. This guide explains what to connect, what to leave in the ERP, and where these integrations go wrong.
Why B2B product sales need a CRM
B2B product sales are repeat sales. The question that matters at every customer is not whether they will buy, but whether they are buying less than last year, less than they could, or from someone else for part of the range. That answer lives in order lines in the ERP, and without it the sales team is managing relationships blind. The CRM's job is to put the pattern in front of the person who can act on it and to record what they did.
Order history from the ERP
The most valuable integration is also the simplest: a one-way sync of customers and order history from the ERP into the CRM. Sales sees each account's volume by month, by product group and against last year, on the company record, before a visit. Nothing is written back, so nothing in the ERP can be corrupted by the CRM.
| Data | Direction | Frequency | What sales does with it |
|---|---|---|---|
| Customer master: name, org number, terms, sales rep | ERP to CRM | Nightly, or on change | One company record per customer, no duplicates |
| Order history by article group and month | ERP to CRM | Nightly | Spot declines, lapsed products and seasonal gaps |
| Open orders and backorders | ERP to CRM | Hourly or on change | Answer delivery questions during the call |
| Price list and customer-specific prices | ERP to CRM, read-only | On change | Quote correctly without asking the office |
| Contacts, visits, notes, opportunities | CRM only | Not synced | Everything the ERP does not know |
Price lists and quotes
Pricing in this sector is layered: list price, customer group, customer-specific agreements, volume breaks, campaign prices. The ERP already implements those rules, and rebuilding them in the CRM is the fastest way to create two answers to what does this cost. The workable pattern is that the CRM shows prices and drafts quotes, but a quote that is accepted becomes an order in the ERP, created there through the integration or by the office.
- Show the customer's actual price on the article in the CRM, sourced from the ERP, with the date it was last updated.
- Draft quotes in the CRM for the pipeline and the follow-up; convert to an ERP order on acceptance so stock, credit and invoicing are handled where they belong.
- If quotes must be produced from the ERP for accuracy, sync the quote header back to the CRM so the pipeline still reflects it.
- Agree who may change a customer-specific price, and make the change in one system only.
Key accounts and visit planning
Once order history is in the CRM, visit planning changes from a fixed round to a triggered one. A customer whose volume is down against last year, a customer who stopped buying one product group, a customer whose open orders are stuck on backorder: each is a reason to call this week. The CRM should surface those signals as a list, and the sales meeting should work from that list.
Decline alerts
A view of accounts down against the same period last year, sorted by the size of the gap. The biggest gap is Monday's first call.
Range gaps
Customers buying from two product groups where similar customers buy from four. The upsell list writes itself from order lines.
Account plans
For the top twenty accounts: goals, contacts by role, agreement end dates and a visit rhythm. Kept in the CRM, reviewed quarterly, visible to the managing director.
Integration pitfalls
Most CRM projects in manufacturing fail at the integration, not at the CRM. The causes repeat, and each is avoidable if it is decided before anyone builds.
- Two-way sync of customer data. Decide the master for every field; if both systems can edit the same field, they will disagree within a month.
- Duplicates on import. Match on organisation number, not on name, and clean the ERP customer list before the first load.
- Article and price structures that do not map. Product groups in the ERP rarely match how sales thinks; agree the grouping first.
- Too much detail. Syncing every order line into the CRM makes it slow and expensive; aggregate by month and product group, and link to the ERP for the detail.
- No owner for the integration. Someone must watch the sync log and fix the failed records, or the CRM slowly stops being true.
When you do not need this: a company with a handful of customers and one salesperson who knows them all gets more from a clean ERP and a shared calendar than from a CRM. The integration pays for itself when several people sell, when the customer base is too large to hold in memory, and when declines go unnoticed until year-end. That is the scope of a CRM implementation with us, including the ERP sync design and the decision on masters and direction; it is priced on the pricing page. If you already have a CRM that nobody trusts, an audit of the sync is often the cheaper first step, so book a call and describe what is out of sync.
Frequently asked questions
Which CRM works best with our ERP?
The one with a maintained connector or a documented API for your specific ERP. HubSpot, Pipedrive, Dynamics and Salesforce all integrate with the common Swedish and Nordic business systems through connectors or middleware, and the deciding factor is usually who will own the integration, not the CRM brand.
Should quotes be created in the CRM or the ERP?
Draft in the CRM if you want pipeline visibility and follow-up; create the binding order in the ERP because it owns stock, credit checks and invoicing. If accuracy demands ERP quotes, sync the quote header back so the pipeline is complete.
How much order history should we load?
Two to three years, aggregated by customer, product group and month, is enough for decline and gap analysis. Full order lines belong in the ERP; link to them rather than copying them.
What about GDPR for contact data at customers?
Business contacts at customer companies can be held under legitimate interest for the customer relationship. Keep it to role-relevant contacts, record the source, delete contacts who have left, and do not sync them into marketing tools without a lawful basis for that separate purpose.
Want sales to see what customers actually buy?
Fifteen minutes: tell us which ERP you run and how sales works today, and we will outline the sync, the masters and the pitfalls specific to your setup.
Book a free 15-minute call