Building-products manufacturers: connect Salesforce dealer quotes to Acumatica orders

What this looks like in building products manufacturing

A manufacturer sells exterior products through regional dealers. One project quote includes two finishes and separate deliveries for different buildings. The dealer accepts most of the quote but changes one finish and asks to combine the final delivery. If the integration copies only the latest opportunity total and a single ship-to, customer service loses the accepted line detail. The order handoff should retain the approved variant and stage for each line, surface the changed scope, and return what order management accepted before sales confirms the project schedule.

Records, ownership, and update rules

Work through the process

1. 01
   Resolve the commercial parties

   Identify the dealer that purchases, the project receiving the goods and the site contact. Map the approved financial customer separately from descriptive project information. A project name or contractor email should not create a new customer automatically.
2. 02
   Carry variant and unit detail

   Use the reviewed product identifier and selling unit for each line. Preserve the accepted finish or dimension where the catalog model requires it. Route custom or conflicting specifications to product operations rather than selecting a similarly named standard item.
3. 03
   Translate stages into an explicit order model

   Represent the requested delivery groups and quantities using the approved application records. Keep requested dates separate from accepted commitments. Confirm the exact Acumatica endpoint entities and operations needed for the chosen order and schedule structure.
4. 04
   Return accepted scope to the dealer team

   Publish the accepted order reference, line status and unresolved conditions in Salesforce. The account manager should see which part of the project is confirmed and which request still needs review.
5. 05
   Exercise a partial acceptance

   Test a quote where one variant changes and one delivery stage remains unchanged. Replay the accepted handoff and verify stable references. Then request another revision to prove that the existing order becomes a review context rather than a duplicate transaction.

Handle the exceptions explicitly

The dealer changes a finish after acceptance

Preserve the prior accepted variant and route the effect on manufacturing and price for review.

The same project has several dealers

Keep each commercial customer and order distinct while linking the common project context where appropriate.

The site address changes for one stage

Apply the approved destination only to the affected delivery scope, not every line on the project.

What to verify before expanding

• Each accepted line retains its specific product variant and selling unit.
• Dealer identity remains distinct from project and ship-to identity.
• Partial quote acceptance does not create demand for unselected alternatives.
• Sales sees confirmed and review-required delivery stages separately.

Technical references

• Salesforce: change data capture events
• Acumatica: endpoints and contracts