--- title: "Modular Factory-to-Site Delivery Workflows | Stacksync" description: "Coordinate factory readiness, site release and confirmed transport before committing a modular shipment." canonical: https://www.stacksync.com/use-case/modular-factory-site-delivery-workflows last_modified: 2026-09-21 --- Modular and prefab building supply and installation # Modular Factory-to-Site Delivery Workflows > 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) Bring factory, logistics and site evidence into one owned delivery-release decision. The workflow identifies the modules in scope, confirms the current site window and transport commitment, and routes missing prerequisites. Receipt and customer acceptance remain separate downstream events. Modules are complete, but the site window or transport plan changed while customer-facing dates stayed the same. [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. ### Release a specific load Attach the actual modules and factory evidence rather than relying on a project-wide completion field. ### Recheck changed dependencies A moved site window should reopen the affected transport and release decisions before another promise is made. ### Track receiving exceptions Keep partial arrival and condition evidence visible without turning physical receipt into automatic acceptance. The process, end to end ## Follow the work across systems a supplier has most modules ready but the site delays one receiving window. The workflow shows which load is affected and routes the logistics decision while preserving the readiness of unrelated scope. [NetSuite connector](https://www.stacksync.com/connectors/netsuite) Scope your implementation ## Bring these details to the demo - Factory release requirements - Site confirmation and receiving owner - Transport booking states - Authorized release and communication roles 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 - [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) Coordinate prefab design release with approved scope, material commitments and factory scheduling decisions. - [Modular Building Delivery Releases: Coordinate Site Readiness, Transport Booking, and Receiving Acceptance](https://www.stacksync.com/blog/modular-building-delivery-releases-coordinate-site-readiness-transport-booking-and-receiving-acceptance) Connect modular factory readiness to site, transport and receiving decisions without treating delivery as project acceptance. [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 ### Can it make technical site-readiness decisions? No. Qualified site and project personnel provide the decision; the workflow coordinates the evidence. ### Can deliveries be released partially? Yes, where the operating plan permits it and the authorized owner approves the specific scope. ### What should the COO measure? Track releases changed by stale evidence, missing receipt records and coordination effort around those exceptions. ### Should we deploy this delivery-release workflow before or after two-way sync? When factory readiness, site windows and transport bookings sit in systems other than NetSuite, put two-way sync in place first so the workflow reads current module and project records rather than copies. When NetSuite already holds them, start with this workflow and give the release decision a route to the logistics, site and production owners. Genies come later to assemble receipt and acceptance evidence for a billing review that finance approves. EDI remains a separate transport for supplier shipment documents into NetSuite receiving.