Salesforce and Acumatica for manufacturing: turn an approved quote into a traceable order

What this looks like in manufacturing

Consider a US manufacturer that sells fabricated assemblies and installation services. Sales closes a quote with two delivery stages. The customer then changes the second destination before order entry finishes. If an integration matches by customer name and copies the latest address into every line, the first shipment can inherit the wrong destination. The order handoff must retain the approved quote version, resolve each delivery location and return the created ERP identifiers. Sales needs to see what operations accepted, including any lines still awaiting review.

Records, ownership, and update rules

Work through the process

1. 01
   Choose the business trigger

   Select the approval state that makes a quote eligible for order preparation. Record which conditions remain outside Salesforce, such as engineering review or a credit hold. Route incomplete cases to an owner with a reason instead of letting an integration infer that every closed-won opportunity is executable.
2. 02
   Resolve identities before copying lines

   Create a reviewed customer and ship-to cross-reference. Compare the quote’s line identifiers and revision with existing ERP links before attempting a create. If the destination already contains the order, reconcile its lines rather than starting another order because the source event was repeated.
3. 03
   Separate requested and accepted values

   Map the requested date from Salesforce into a request field or reviewed staging model. Bring Acumatica’s accepted date and status back into distinct fields. This lets sales explain a gap without a later CRM edit quietly changing a promise owned by planning.
4. 04
   Prove the endpoint and recovery path

   Check the endpoint’s entities, actions and fields with the Acumatica administrator. Exercise a representative draft operation using the intended role. After an uncertain response, look up the external order reference before retrying; record whether the destination accepted the original request.

Handle the exceptions explicitly

Ship-to changes during preparation

Hold affected lines for review and retain the previous destination. Apply the change only to the approved revision and shipments still eligible to change.

A customer exists twice

Present both destination identifiers to the data owner. Do not select the first name match or automatically merge financial customer records.

Only part of an order is accepted

Return line-level outcomes to Salesforce. An accepted header must not mark rejected or unresolved lines ready for production.

What to verify before expanding

• Replaying the approved quote returns the same ERP order and line links without an additional order.
• An unapproved quote revision remains visible as a request and does not alter released work.
• Two ship-to locations on one quote retain their separate references after synchronization.
• Sales can distinguish the customer’s requested date from the date order management accepted.

Technical references

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