--- title: "Salesforce–NetSuite for Modular Building Manufacturers" description: "Align modular customer configurations with approved orders, project revisions and meaningful milestones." canonical: https://www.stacksync.com/use-case/salesforce-netsuite-modular-building-manufacturers last_modified: 2026-09-21 --- Modular and prefab building supply and installation # Salesforce–NetSuite for Modular Building 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 ![Modular and prefab building supply and installation systems connected through Stacksync two-way sync: Salesforce, NetSuite, Supabase, HubSpot](https://www.stacksync.com/images/industry-heroes/icp-modular-prefab-building-installation-800.webp) Connect Salesforce commercial configuration with NetSuite order and project context for modular and prefab building companies. Keep factory scope, delivery and site installation distinguishable, and preserve the approved design revision. Customer-facing teams receive verified status while technical, production and finance owners retain their decisions. A sales option change, factory completion and site acceptance can all appear as one updated project status. [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 US modular and prefab building companies with 100–1,000 employees that combine manufacturing or supply with onsite delivery and installation. ### Preserve approved configuration Connect accepted options and module quantities to the released design and order references. ### Make milestones meaningful Show factory, shipment and site states separately so a customer summary does not imply more progress than the evidence supports. ### Control postrelease changes Route new requests with procurement and production commitments before changing released scope. The process, end to end ## Follow the work across systems a modular supplier manufactures buildings and installs them onsite. The customer adds an option after factory release. The connection preserves the accepted baseline and exposes the proposed revision for the required reviews. [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 - Commercial and design revision model - Factory versus site deliverables - Order and milestone records - Supported object actions and ownership 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 - [Modular Building Manufacturers: Align Salesforce Project Configurations With NetSuite Orders and Milestones](https://www.stacksync.com/blog/modular-building-manufacturers-align-salesforce-project-configurations-with-netsuite-orders-and-milestones) 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. - [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) Track module identity through factory release, shipment, site receipt and acceptance without treating those events as equivalent. - [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) Connect prefab buyer and project context to a portal with explicit dealer, contractor and owner access. [Explore all modular and prefab building supply and installation integration and automation guides ↗](https://www.stacksync.com/industry/construction/modular-prefab-building-installation) ## Common evaluation questions ### Does sales need every factory detail? No. Share approved configuration and decision-relevant status while production control remains with its owning process. ### Can one project have partially delivered modules? Yes. Preserve module or deliverable scope beneath the project summary. ### What should the demo include? A design revision, partial delivery and separate site acceptance, all linked to the same commercial project. ### Which Stacksync product should a modular building manufacturer start with? Start with two-way sync between Salesforce and NetSuite so the approved configuration, released design revision, order and project references and milestone states share one identity in both systems. Add workflows when a postrelease option change needs routing through procurement and production before released scope moves. Genies come next, assembling factory, shipment and site acceptance evidence into a progress-billing packet that finance approves. EDI arrives last, as a separate transport for component supplier documents that reach NetSuite purchase lines and receipts.