Release a specific load
Attach the actual modules and factory evidence rather than relying on a project-wide completion field.
Modular and prefab building supply and installation
Modular Factory-to-Site Delivery Workflows
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.
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.
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.
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 alongside the records, volume, and actions in your process. Use your own operating baseline to evaluate the economics.
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
Keep shared customer, order, and operational records aligned, with clear field ownership.
Explore two-way sync 02Workflows
Move approved work between systems, assign exceptions, and confirm the result.
Explore workflows 03AI agents (Genies)
Investigate cross-system questions, assemble the evidence, and prepare the next action.
Explore ai agents (genies) 04EDI
Connect trading-partner documents to operational records and exception handling.
Explore ediGo deeper
Implementation guides for your team
- 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
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 ↗
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.
