Salesforce–NetSuite Sync for Beverage Brands: Connect Distributor Accounts and Delivery Locations

What this looks like in beverages

A distributor adds a new depot with different receiving hours while retaining its central payer. Sales creates a location under the parent account. If the integration copies the headquarters address into every order, a truck can arrive at the wrong site or miss the receiving window despite an otherwise valid customer match.

Records, ownership, and update rules

Work through the process

1. 01
   Map parent and site separately

   List the distributor’s payer and every receiving location. Choose stable references for each level so opening a new depot does not create an unnecessary financial customer.
2. 02
   Define field ownership

   Let sales propose contacts and location changes while finance and logistics approve their respective fields. A CRM address edit should not automatically revise a shipment already released to a carrier.
3. 03
   Surface useful context

   Share approved account status and destination details with the sales team. Label pending location changes clearly so a rep does not promise delivery against unreviewed instructions.
4. 04
   Test location transitions

   Exercise a new depot, an address correction, and a closed location. Confirm that open orders use the approved policy and historical shipments keep their original destination evidence.
5. 05
   Trace a third-party depot order into NetSuite before go-live

   Create a test order in Salesforce for a distributor that receives at a third-party depot. Open the sales order in NetSuite and check that the payer is the distributor's legal customer and the destination is the depot's own ship-to identifier, with the payer unchanged from before the test. Then edit that depot's address in Salesforce and reopen a shipment already released to the site. The historical shipment must still show its original destination. Stop the rollout if the order carries the headquarters address, if the third-party depot was created as a new customer, or if the released shipment picked up the edited address.

Handle the exceptions explicitly

Distributor uses a third-party depot

Confirm the actual receiver and ship-to relationship without changing the legal payer.

Address changes after release

Route a logistics decision and retain the original shipment instructions.

Two depots have similar names

Require stable location identifiers rather than choosing by display name.

What to verify before expanding

• Every distributor order resolves to both a payer and a receiving location.
• A site update cannot erase the destination on a historical shipment.
• Two similarly named distributor depots resolve through distinct location identifiers while retaining the approved payer relationship.
• An address edit after release enters logistics review and cannot silently replace the shipment's accepted instructions.

Technical references

• Stacksync two-way sync quick start
• Stacksync NetSuite supported objects