--- title: "Salesforce and NetSuite two-way sync for equipment…" description: "Connect approved equipment configurations and commercial orders across Salesforce and NetSuite." canonical: https://www.stacksync.com/use-case/equipment-salesforce-netsuite-two-way-sync last_modified: 2026-09-21 --- Industrial equipment and machinery # Salesforce and NetSuite two-way sync for equipment manufacturers > 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 ![Industrial equipment and machinery systems connected through Stacksync two-way sync: Salesforce, NetSuite, Acumatica, PostgreSQL](https://www.stacksync.com/images/industry-heroes/icp-industrial-equipment-machinery-800.webp) Connect approved equipment configurations and commercial orders across Salesforce and NetSuite. Stacksync fits builders whose sales, engineering and order-management teams repeatedly reconcile what was sold with what production accepted. Preserve configuration versions and operational ownership while returning the order milestones account managers need. The opportunity says the machine is sold, but its approved options, services and delivery commitment are scattered across separate records. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. When this fits ## Built for this operating problem COOs, service directors and IT leaders at US equipment builders with 100–1,000 employees and a mix of manufacturing, distribution and service. ### Keep the approved build identifiable Link accepted options and commercial lines without relying on the current opportunity description as the specification. ### Return meaningful operational milestones Show the accepted order and release conditions so sales can explain progress without reconstructing it from emails. ### Treat changes as decisions Route later option changes with their impact while validating the exact ERP operations required for execution. The process, end to end ## Follow the work across systems an equipment builder sells machines with options and commissioning services. Evaluate one configured order and a later option change, then inspect whether the original accepted build remains traceable while the requested revision receives the right review. [Salesforce connector](https://www.stacksync.com/connectors/salesforce) [NetSuite connector](https://www.stacksync.com/connectors/netsuite) [Review the integration details ↗](https://www.stacksync.com/integrations/netsuite-and-salesforce) Scope your implementation ## Bring these details to the demo - An accepted configured quote and its governing engineering reference. - Customer, financial and order-line mappings used by both teams. - The approval process for post-acceptance option changes. Review [current platform pricing](https://www.stacksync.com/pricing) alongside the records, volume, and actions in your process. Use your own operating baseline to evaluate the economics. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. From foundation to action ## One connected operating process 01 ### [Two-way sync](https://www.stacksync.com/two-way-sync) Keep shared customer, order, and operational records aligned, with clear field ownership. Explore two-way sync 02 ### [Workflows](https://www.stacksync.com/workflow-automation) Move approved work between systems, assign exceptions, and confirm the result. Explore workflows 03 ### [AI agents (Genies)](https://www.stacksync.com/ai-agents) Investigate cross-system questions, assemble the evidence, and prepare the next action. Explore ai agents (genies) 04 ### [EDI](https://www.stacksync.com/edi) Connect trading-partner documents to operational records and exception handling. Explore edi Go deeper ## Implementation guides for your team - [Equipment manufacturers: connect Salesforce configurations to NetSuite orders](https://www.stacksync.com/blog/equipment-manufacturers-salesforce-netsuite-configured-order) 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. - [Equipment manufacturers: connect NetSuite and Postgres machine serial history](https://www.stacksync.com/blog/equipment-manufacturers-netsuite-postgres-machine-serial-history) Keep the manufacturer's serial stable across owner changes and customer asset tags, with a retrofit history that explains the installed configuration. - [Equipment aftermarket: connect Salesforce parts quotes to Acumatica order status](https://www.stacksync.com/blog/equipment-salesforce-acumatica-aftermarket-parts-quotes) When two employees quote the same urgent component, a shared request reference across Salesforce and Acumatica keeps one accepted order and its compatibility evidence. [Explore all industrial equipment and machinery integration and automation guides ↗](https://www.stacksync.com/industry/manufacturing/industrial-equipment-machinery) ## Common evaluation questions ### Is this suitable for custom equipment? It can be when the approved configuration and handoff records are defined. An undefined engineering process should be clarified before automating its order consequences. ### What should the demo include? A configured machine, a service line, a repeated handoff and a changed option after procurement has begun. ### How should value be measured? Compare handoff preparation time, configuration clarification and corrections discovered after order release, using similar equipment orders. ### Which Stacksync product should an equipment builder start with? Start with two-way sync between Salesforce and NetSuite so the approved configuration, its commercial lines and the order milestones share one order identity, with NetSuite writes limited to the order objects you approve. Add workflows when a post-acceptance option change needs its purchasing and schedule impact routed to an approver before the accepted build changes. Genies come later, when service wants serial and installed-configuration evidence assembled for aftermarket part proposals. EDI is a separate step for distributor purchase orders that carry kits and partial shipments into NetSuite.