Salesforce SAP integration for manufacturers
What should sync between Salesforce and SAP
| Salesforce | SAP | Direction | Why it matters |
|---|---|---|---|
| Accounts | Customers and partner functions (sold-to, ship-to, bill-to, payer) | SAP → Salesforce | SAP owns credit, terms and partner functions; Salesforce needs to know which ship-to and bill-to to put on the order. |
| Products and price books | Material master and pricing condition records | SAP → Salesforce | Decide which system prices. Sales area (sales org, distribution channel, division) decides which materials are sellable and at what price. |
| Accepted quote | Sales order | Salesforce → SAP | Configured options, quantities, prices and requested dates carried across, with the quote number on the order. |
| Order status | Sales order status, deliveries, shipments | SAP → Salesforce | Reps answer "where's my order" without asking customer service. |
| Invoices and credit | Billing documents, open items, credit blocks | SAP → Salesforce | Read-only in Salesforce, so reps see a credit block before they promise a ship date. |
| Availability | ATP / stock | SAP → Salesforce, on demand | Called at quote time rather than copied in bulk. |
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 SAP
MuleSoft
Salesforce-owned, with SAP connectors for S/4HANA and ECC. The usual choice when Salesforce is the hub and other systems join later.
SAP Integration Suite
SAP's own integration platform (BTP). A good fit when the SAP team runs integrations and wants them in SAP's tooling.
Direct APIs
S/4HANA OData APIs, or BAPIs and IDocs on ECC. Fine for a single flow; harder to monitor and change as flows grow.
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 SAP integrations go wrong
- Partner functions. One Salesforce account rarely equals one SAP customer. Map sold-to, ship-to, bill-to and payer explicitly, usually with an account hierarchy or address records in Salesforce.
- Who prices. If SAP condition records stay the price source, Salesforce must either call SAP for pricing or replicate the conditions. Doing both is how quotes and orders drift apart.
- Sales area. Sales org, distribution channel and division change what a customer can buy and the price they get. Carry them on the account and the quote.
- Configurable materials. If you use SAP variant configuration, the characteristic values on the order must match what the Salesforce quote configured, or production builds something different from what was sold.
- Credit blocks. Show SAP credit status on the account before quoting, not after the order fails.
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 SAP 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 + NetSuite
Quote to order, status and invoices back.
ERPSalesforce + Microsoft Dynamics 365
Quote to order, status and invoices back.
ERPSalesforce + Epicor
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 SAP 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 SAP integration?
Not out of the box in Sales Cloud. Salesforce owns MuleSoft, which has prebuilt SAP connectors, and SAP offers its own Integration Suite. Most manufacturers use one of the two rather than point-to-point code.
Should quotes live in Salesforce or SAP?
Quotes should live in Salesforce, where reps configure and price, and become SAP sales orders on acceptance. Keeping a second quote in SAP doubles the work and splits the history.
Which system should own pricing?
Pick one. Either SAP condition records stay the source and Salesforce calls SAP at quote time, or pricing moves to Revenue Cloud and SAP receives the final price on the order. Running both is the most common source of quote-to-order price mismatches.
How long does a Salesforce SAP integration take?
Core flows (customers, materials, quote to order, status back) can go live in weeks. Variant configuration, multiple sales areas and pricing ownership add time, so they're scoped up front.