Modular Building Manufacturers: Align Salesforce Project Configurations With NetSuite Orders and Milestones

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

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.

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.

Technical references

• Stacksync Salesforce connector requirements
• Stacksync NetSuite connector and object support