Salesforce Epicor integration for manufacturers
What should sync between Salesforce and Epicor
| Salesforce | Epicor | Direction | Why it matters |
|---|---|---|---|
| Accounts | Customers, ship-tos and bill-to relationships | Epicor → Salesforce for terms and credit | Epicor customers often carry many ship-tos; Salesforce needs to choose the right one on the order. |
| Products and price books | Parts and price lists (including customer price lists) | Epicor → Salesforce | Decide whether Epicor price lists or Salesforce price books are the source. |
| Accepted quote | Sales order | Salesforce → Epicor | Lines, quantities, prices, need-by dates and configured options, with the Salesforce quote number stored on the order. |
| Order status | Order releases, jobs, shipments | Epicor → Salesforce | Make-to-order lines may create jobs; reps see job and ship status. |
| Invoices and credit | AR invoices, credit hold | Epicor → Salesforce | Read-only, so a credit hold shows before the next quote. |
| Availability | On-hand and available-to-promise | Epicor → Salesforce, on demand | Called at quote time. |
Start with the quote-to-order flow. That's where manufacturers lose the most: orders retyped into the ERP at a different price, the wrong ship-to, or options left off. Everything else can follow.
Ways to connect Salesforce and Epicor
Epicor REST APIs and BAQs
Kinetic exposes REST services, and Business Activity Queries can be published as REST endpoints. Full control over what moves.
Middleware
MuleSoft, Boomi or Jitterbit with Epicor connectivity. Monitoring, retries and room for other systems.
Packaged connectors
AppExchange sync apps for Epicor, and a Data Cloud (Data 360) connector for Kinetic that brings Epicor data into Salesforce's data platform. Quick to start; check how each handles quotes, configured parts and ship-tos.
We're tool-agnostic. The right choice depends on what your IT team already runs and how many systems will join later. MuleSoft is the common choice when Salesforce is the hub.
Where Salesforce Epicor integrations go wrong
- Two quote screens. Epicor has its own quote entry. Keep quoting in Salesforce and create the Epicor sales order on acceptance, or estimators and reps end up maintaining two quotes.
- Ship-tos. One Epicor customer with many ship-tos is common. Model them in Salesforce (child accounts or address records) so the order lands at the right site.
- Configured parts. If you use Epicor's configurator, the inputs on the order must match what the Salesforce quote configured. Mismatches show up as the wrong build.
- Price lists. Epicor customer price lists and Salesforce price books will drift unless one is the source.
- Prophet 21 vs Kinetic. P21 (distribution) and Kinetic (manufacturing) have different data models and APIs. Name the product before scoping.
Quote to order: the flow that pays for the integration
For a manufacturer, the integration isn't about syncing records; it's about the quote the customer accepted becoming the order you build and bill. With Revenue Cloud or CPQ in Salesforce, the accepted quote creates the Epicor order with the same configuration and price, and the order and invoice come back linked to it. That's what lets you check, deal by deal, that what was quoted is what was ordered and billed. We call that check a Leak Ledger.
Our experience. We've connected Salesforce to SAP, NetSuite, Microsoft Dynamics, Epicor and Infor in delivered projects.
Moving off Salesforce CPQ at the same time? Design the ERP handoff into the Revenue Cloud build, not after it. See Salesforce CPQ end of sale.
Other ERP integrations
Salesforce + SAP
Quote to order, status and invoices back.
ERPSalesforce + NetSuite
Quote to order, status and invoices back.
ERPSalesforce + Microsoft Dynamics 365
Quote to order, status and invoices back.
ERPSalesforce + Infor SyteLine
Quote to order, status and invoices back.
ERPSalesforce + SYSPRO
Quote to order, status and invoices back.
ERPSalesforce + Acumatica
Quote to order, status and invoices back.
All of this sits within our Salesforce practice for manufacturers and our CRM-to-ERP integration work.
Who we are
Nteli is a Salesforce Premier Partner headquartered at Capital Factory in Austin, specializing in Quote-to-Order for specialty manufacturers, sold direct and through dealers. We implement Manufacturing Cloud, Revenue Cloud and CPQ, Experience Cloud dealer portals and MuleSoft, with 58 certifications across the team and a 4.93-star average across 10 AppExchange reviews. Before Nteli, our team built product configurators and pricing systems at Cisco, Dell and IBM.
Map your Salesforce Epicor handoff.
A 30-minute call: what should sync, which system owns pricing, and where your quotes and orders drift today.
FAQ
Does Salesforce have a native Epicor integration?
Not in Sales Cloud. Options are Epicor's REST APIs and BAQs, middleware such as MuleSoft or Boomi, AppExchange connectors, or the Data Cloud (Data 360) connector for Epicor Kinetic, which brings Epicor data into Salesforce's data platform rather than creating orders.
Should quotes live in Salesforce or Epicor?
For sales-led quoting, in Salesforce, with the Epicor sales order created on acceptance. If estimating stays in Epicor for engineered jobs, decide which quote is the customer-facing one and link the two.
How do we handle configured parts?
The configuration chosen on the Salesforce quote has to arrive in Epicor as the same configuration. That means mapping configurator inputs explicitly, not just passing a part number.
How long does a Salesforce Epicor integration take?
Core flows (customers, ship-tos, parts, quote to order, status back) can go live in weeks. Configured parts and price list ownership add scope.