--- title: "Salesforce NetSuite sync for configured equipment orders" description: "A Salesforce to NetSuite handoff that keeps the accepted equipment configuration version, links its order lines and returns build milestones to sales." canonical: https://www.stacksync.com/blog/equipment-manufacturers-salesforce-netsuite-configured-order last_modified: 2026-09-18 --- # Equipment manufacturers: connect Salesforce configurations to NetSuite orders > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Equipment builders can tie a sold machine's accepted option set to its NetSuite order lines and route later option changes for review instead of overwriting the build. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 4 min read DATA ENGINEERING ## The operating decision Equipment manufacturers need a Salesforce–NetSuite handoff that preserves the configuration the customer approved. Connect the commercial order to the accepted equipment specification and return production milestones without letting a later sales edit rewrite engineering scope. Two-way sync should carry selected records in their permitted directions, with separate ownership for customer requests, approved options and financial treatment. Confirm the exact destination record and operation before making configured-order creation part of the automated process. Explore the complete [industrial equipment and machinery integration and automation hub](https://www.stacksync.com/industry/manufacturing/industrial-equipment-machinery) for the systems and processes around this guide. ![Summary card: Salesforce NetSuite sync for configured equipment orders](https://www.stacksync.com/images/blog-highlights/icp-equipment-manufacturers-salesforce-netsuite-configured-order.webp) ## What this looks like in industrial equipment and machinery An equipment builder sells a packaging machine with several options and a commissioning service. Sales records a single opportunity amount, while engineering maintains the approved configuration and order management creates the ERP lines. A customer then asks to replace an option after long-lead components have been ordered. If the integration treats the current opportunity description as the entire specification, it can conceal the approved build and purchasing commitments. A useful handoff retains the accepted configuration version, links its commercial lines and routes later changes for review. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Accepted configuration | Application engineering | Retain the approved option set and revision with its customer approval evidence. | | Commercial order line | Sales operations | Identify equipment, optional components and services separately even when sold in one deal. | | ERP transaction link | Order management | Preserve the destination order and line references for reconciliation and later change requests. | | Build milestone | Production planning | Publish accepted operational progress using defined states rather than a free-text sales description. | ![Record ownership diagram: Accepted configuration, Commercial order line, ERP transaction link](https://www.stacksync.com/images/blog-diagrams/icp-equipment-manufacturers-salesforce-netsuite-configured-order.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Describe the sold configuration explicitly Identify the base equipment, selected options and included services. Decide which records hold the approved configuration and how sales references it. A product bundle name is not a substitute for the version that engineering accepted for this customer. 2. 02 Map commercial lines to operational scope Connect each relevant quote line to its ERP representation and configuration reference. Resolve customer, subsidiary and required financial references. Confirm the permitted create or update operation rather than assuming a synchronized item list can execute a configured order. 3. 03 Keep later requests outside accepted scope Store a proposed option change separately from the accepted build. Collect purchasing and production impact before approving a revision. The customer-facing team should see both the pending request and the current commitment. 4. 04 Return milestones with evidence Expose order accepted, engineering released and other approved build milestones with their source time. Keep incomplete prerequisites visible. A milestone should describe a recorded operational decision, not an agent’s interpretation of a recent note. 5. 05 Demonstrate a configuration change Use a test order with an option already purchased and another not yet committed. Revise one option, replay the original handoff and inspect the resulting records. The test should show stable order identity and a review-required change rather than another equipment order. ![5-step operating sequence: Salesforce NetSuite sync for configured equipment orders](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-equipment-manufacturers-salesforce-netsuite-configured-order.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### The customer adds an option after procurement Route its cost and schedule effect for approval before updating accepted scope. ### One machine includes several service visits Represent the visits or obligations separately from equipment quantity so a service update cannot duplicate the machine. ### The configuration document is superseded Preserve the accepted version on the existing order until the approved cutover specifies otherwise. ## What to verify before expanding - The order retains the exact configuration version the customer accepted. - Equipment and service lines keep separate operational meaning. - A repeated handoff resolves the existing ERP order without duplicate demand. - A pending option change remains visible without silently replacing the approved build. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real accepted configuration example and the exception your team handles most often, for example the customer adds an option after procurement. - [Salesforce and NetSuite two-way sync for equipment manufacturers](https://www.stacksync.com/use-case/equipment-salesforce-netsuite-two-way-sync) - [Salesforce and Acumatica two-way sync for equipment aftermarket teams](https://www.stacksync.com/use-case/equipment-salesforce-acumatica-two-way-sync) - [Equipment manufacturers: connect NetSuite and Postgres machine serial history](https://www.stacksync.com/blog/equipment-manufacturers-netsuite-postgres-machine-serial-history) - [Equipment aftermarket: connect Salesforce parts quotes to Acumatica order status](https://www.stacksync.com/blog/equipment-salesforce-acumatica-aftermarket-parts-quotes) - [Equipment commissioning readiness: connect sales promises, site prerequisites and service dispatch](https://www.stacksync.com/blog/equipment-commissioning-readiness-workflow) - [Coordinate Closed-Won Onboarding Across Salesforce and NetSuite](https://www.stacksync.com/blog/coordinate-closed-won-onboarding-across-salesforce-and-netsuite) - [Bi-Directional Sync for Salesforce and Beyond: Ensuring Operational Efficiency](https://www.stacksync.com/blog/bi-directional-sync-for-salesforce-and-beyond-ensuring-operational-efficiency) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Salesforce: change data capture events](https://developer.salesforce.com/docs/platform/platform-events/guide/platform-events-objects-change-data-capture.html) - [Oracle NetSuite: using external IDs](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_156334828635.html) FAQ ## Frequently asked questions Can a sales configurator be the engineering source of truth? Only if the manufacturer has explicitly defined and validated that role. Many processes require a separate engineering approval before the selected options become build instructions. What should a COO see in the demonstration? Follow one sold machine from accepted quote to linked ERP order, then introduce a changed option and show the owner, impact evidence and accepted outcome. Which measure is useful after launch? Track missing-configuration corrections, time to an accepted order handoff and revisions discovered after procurement. Separate administrative improvements from engineering lead time. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [integration Salesforce and NetSuite integration](https://www.stacksync.com/integrations/netsuite-and-salesforce) - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Automotive component suppliers: connect Salesforce program awards and NetSuite demand 4 min read read](https://www.stacksync.com/blog/automotive-components-salesforce-netsuite-program-award-demand) [Data engineering Manufacturing CRM and ERP ownership: decide who controls each order field 4 min read read](https://www.stacksync.com/blog/manufacturing-crm-erp-field-ownership-matrix) [Data engineering Salesforce and NetSuite for manufacturers: share credit and order status without conflicting ownership 4 min read read](https://www.stacksync.com/blog/manufacturing-salesforce-netsuite-customer-credit-order-status) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)