--- title: "Salesforce NetSuite sync for modular orders and milestones" description: "Link Salesforce module options to the released design and NetSuite order so sales edits cannot rewrite released scope or blur factory and site milestones." canonical: https://www.stacksync.com/blog/modular-building-manufacturers-align-salesforce-project-configurations-with-netsuite-orders-and-milestones last_modified: 2026-09-18 --- # Modular Building Manufacturers: Align Salesforce Project Configurations With NetSuite Orders and Milestones > 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 Link Salesforce module options to the released design revision and NetSuite order so sales edits cannot rewrite released scope or blur factory and site milestones. Author Ruben Burdin · Founder & CEO Published September 18, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision Modular building manufacturers should connect Salesforce commercial configuration to NetSuite orders and project milestones through approved revision references. Preserve module quantities, configuration choices, factory scope and site-installation scope separately. Sales owns proposals, technical and production teams own design release, and finance owns the accepted commercial order. Two-way sync should return the approved state to customer-facing teams without allowing an evolving sales configuration to rewrite released production or billing milestones. Explore the complete [modular and prefab building supply and installation integration and automation hub](https://www.stacksync.com/industry/construction/modular-prefab-building-installation) for the systems and processes around this guide. ![Summary card: Salesforce NetSuite sync for modular orders and milestones](https://www.stacksync.com/images/blog-highlights/icp-modular-building-manufacturers-align-salesforce-project-configurations-with-netsuite-orders-and-milestones.webp) ## What this looks like in modular and prefab building supply and installation A modular building supplier sells a package that includes factory production and onsite installation. Salesforce holds the opportunity and customer options, while NetSuite holds the accepted order and project context. The customer adds a module after the initial design is released. That change affects procurement, factory sequencing, transport and the commercial schedule. The integration needs a versioned comparison rather than replacing the original module count on every downstream record. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Commercial configuration | Sales | Maintain proposed options and the customer conversation. | | Released design revision | Technical and production owners | Identify the accepted module configuration for factory work. | | Order and project reference | Order administration | Retain approved commercial quantities and their originating opportunity. | | Milestone definition | Project management and finance | Describe the evidence required for each approved commercial milestone. | ![Record ownership diagram: Commercial configuration, Released design revision, Order and project reference](https://www.stacksync.com/images/blog-diagrams/icp-modular-building-manufacturers-align-salesforce-project-configurations-with-netsuite-orders-and-milestones.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Separate factory and site scope List which deliverables belong to manufacturing and which belong to transport or onsite installation. Keep them identifiable in the commercial model. A factory-complete milestone does not mean the site has accepted the building, and the integration should not collapse those states into one completed field. 2. 02 Join configuration to a revision Capture the approved option set and design reference alongside the Salesforce opportunity. Preserve subsequent customer requests as proposed changes. This makes it possible to compare a new module count or finish choice with what production was actually authorized to build. 3. 03 Map orders and milestones deliberately Connect the approved scope to the relevant NetSuite records and return their identifiers to Salesforce. Validate the selected order, project and custom milestone operations. A custom field that displays a milestone does not establish that the associated financial or production action is supported. 4. 04 Control postrelease changes When sales records a new request, route the affected design, quantity and timing differences to the project owner. Keep released work stable until the approved revision is applied. Show production and procurement commitments so reviewers understand the consequence of changing scope already in progress. 5. 05 Validate customer-facing status Test whether sales can explain factory progress, transport readiness and site acceptance separately. Reconcile the same project across both systems, including a partial delivery and an approved design change. Confirm that repeated updates reuse the existing order and revision relationships. 6. 06 Keep customer options separate from production evidence A selected option in the commercial configuration describes what was agreed, while the production record describes what was built. Preserve both until the responsible team confirms conformance or records an approved difference. This matters when the customer requests options that affect only certain modules. Sales needs the accepted configuration for conversations, and project management needs the actual completion evidence before presenting those options as delivered scope. ![6-step operating sequence: Salesforce NetSuite sync for modular orders and milestones](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-modular-building-manufacturers-align-salesforce-project-configurations-with-netsuite-orders-and-milestones.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Customer adds modules after release Create a reviewed scope revision with downstream impact rather than overwriting the original quantity. ### Factory is complete but site is delayed Return separate milestone states and keep the customer-facing summary accurate. ### Milestone definition changes Require project and finance review before applying the new rule to existing work. ## What to verify before expanding - Approved configuration identifies the released design revision. - Factory and site milestones remain distinct. - Sales changes cannot silently alter released production scope. - Order and project references remain stable across retries. ## 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 commercial configuration example and the exception your team handles most often, for example customer adds modules after release. - [Salesforce–NetSuite for Modular Building Manufacturers](https://www.stacksync.com/use-case/salesforce-netsuite-modular-building-manufacturers) - [NetSuite–Supabase for Modular Delivery and Acceptance](https://www.stacksync.com/use-case/netsuite-supabase-modular-delivery-acceptance) - [Module Serial Numbers From Factory to Site: Connect NetSuite With a Supabase Delivery and Acceptance Register](https://www.stacksync.com/blog/module-serial-numbers-from-factory-to-site-connect-netsuite-with-a-supabase-delivery-and-acceptance-register) - [Prefab Dealer and Contractor Portals: Align HubSpot Buyer Records With Supabase Project Access](https://www.stacksync.com/blog/prefab-dealer-and-contractor-portals-align-hubspot-buyer-records-with-supabase-project-access) - [Prefab Design Freeze to Factory Release: Route Approved Revisions Through Procurement and Scheduling](https://www.stacksync.com/blog/prefab-design-freeze-to-factory-release-route-approved-revisions-through-procurement-and-scheduling) - [Eliminating Duplicate Records When You Sync CRM Systems: Best Practices for Clean Data](https://www.stacksync.com/blog/eliminating-duplicate-records-when-you-sync-crm-systems-best-practices-for-clean-data) - [Connecting Salesforce and HubSpot to Databases with Stacksync](https://www.stacksync.com/blog/connecting-salesforce-and-hubspot-to-databases-with-stacksync) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync Salesforce connector requirements](https://docs.stacksync.com/two-way-sync/connectors/salesforce) - [Stacksync NetSuite connector and object support](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Should Salesforce contain every production detail? No. Share the approved configuration and milestone context needed for commercial decisions, while detailed production control remains with its owning process. Can one order cover factory and installation work? It can if the model preserves the separate deliverables and milestone evidence. The integration should reflect the company's actual commercial structure rather than impose a universal order pattern. What should a modular integration pilot include? Use an order with a design revision, partial module delivery and separate site acceptance. Those cases reveal whether the model distinguishes commercial, factory and installation states. 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 Construction Company Acquisitions: Unify Customer and Job IDs Across Branch Systems 5 min read read](https://www.stacksync.com/blog/construction-company-acquisitions-unify-customer-and-job-ids-across-branch-systems) [Data engineering Construction Job-Cost Visibility: Define Ownership Across CRM, ERP, and Field Records 4 min read read](https://www.stacksync.com/blog/construction-job-cost-visibility-define-ownership-across-crm-erp-and-field-records) [Data engineering Fence Fabricators and Installers: Align Salesforce Approved Configurations With NetSuite Sales Orders 5 min read read](https://www.stacksync.com/blog/fence-fabricators-and-installers-align-salesforce-approved-configurations-with-netsuite-sales-orders) ## 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/)