Salesforce NetSuite integration for manufacturers
What should sync between Salesforce and NetSuite
| Salesforce | NetSuite | Direction | Why it matters |
|---|---|---|---|
| Accounts and contacts | Customers, contacts, subsidiaries | Both ways, with a clear master | New customers often start in Salesforce; terms, credit limits and subsidiary are owned in NetSuite. |
| Products and price books | Items (inventory, assembly, kit, non-inventory) and price levels | NetSuite → Salesforce | Item type matters: kits and assemblies need their components handled on the order. |
| Accepted quote | Sales order (or estimate, if you use them) | Salesforce → NetSuite | Lines, quantities, prices, discounts and ship dates, with the Salesforce quote ID stored on the order. |
| Fulfillment | Item fulfillments and shipping | NetSuite → Salesforce | Status and tracking visible on the opportunity or order. |
| Invoices and balances | Invoices, payments, open balance | NetSuite → Salesforce | Read-only, so reps see overdue balances before quoting. |
| Tax | Tax codes or Avalara | Calculated in one place | Decide whether tax is calculated in NetSuite, in Salesforce, or by Avalara, and keep it there. |
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 NetSuite
Integration platform
Celigo, MuleSoft and Boomi all have NetSuite connectors. The fastest route for standard flows, with monitoring built in.
SuiteTalk and RESTlets
NetSuite's REST and SOAP web services, plus custom RESTlets in SuiteScript. Full control; you own the maintenance.
AppExchange connectors
Packaged sync apps. Quick to start; check how they handle your item types and subsidiaries before committing.
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 NetSuite integrations go wrong
- Subsidiaries and currencies. In NetSuite OneWorld, a customer belongs to a subsidiary and currency. Salesforce needs to know which, or orders land in the wrong books.
- Item types. Inventory items, assemblies, kits and matrix items behave differently on a sales order. Map each type, not just "products".
- Price levels. If NetSuite price levels and quantity pricing stay the source, Salesforce price books must follow them, or the order changes the price the customer accepted.
- Estimates vs sales orders. Don't keep quotes in both systems. Quote in Salesforce; create the NetSuite sales order on acceptance.
- Revenue recognition. If you use NetSuite revenue arrangements, the order needs the fields that drive them, set at the quote.
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 NetSuite 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 + 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 NetSuite 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 NetSuite integration?
No. Most companies use an integration platform such as Celigo, MuleSoft or Boomi, an AppExchange connector, or custom SuiteTalk and RESTlet work.
Should quotes live in Salesforce or NetSuite?
In Salesforce, where reps configure and price. Create the NetSuite sales order when the quote is accepted, and send status and invoices back.
Which system should own pricing?
One of them. Either Salesforce price books follow NetSuite price levels, or pricing moves to Salesforce (Revenue Cloud or CPQ) and NetSuite receives the final price. Splitting it is how orders end up at a different price than the quote.
How long does a Salesforce NetSuite integration take?
Standard flows can go live in weeks. Multiple subsidiaries, kits and assemblies, and revenue recognition fields add scope.