--- title: "Salesforce NetSuite sync for beverage distributor depots" description: "Beverage distributor accounts in Salesforce tied to the NetSuite payer and each receiving depot, so orders reach the right dock with no duplicate customer." canonical: https://www.stacksync.com/blog/salesforce-netsuite-sync-for-beverage-brands-connect-distributor-accounts-and-delivery-locations last_modified: 2026-09-21 --- # Salesforce–NetSuite Sync for Beverage Brands: Connect Distributor Accounts and Delivery Locations > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Sales manages the distributor relationship in Salesforce while NetSuite keeps the payer and every depot as separate records, so a new site never becomes a new customer. Author Ruben Burdin · Founder & CEO Published September 21, 2026 Read time 5 min read DATA ENGINEERING ## The operating decision Connect the beverage distributor’s commercial account to the correct NetSuite payer and receiving locations. Salesforce can own relationship activity while finance owns billing identity and operations owns accepted delivery details. A parent account and a warehouse destination should remain different records even when they share a distributor brand name. Explore the complete [beverages integration and automation hub](https://www.stacksync.com/industry/cpg/beverages) for the systems and processes around this guide. ![Summary card: Salesforce NetSuite sync for beverage distributor depots](https://www.stacksync.com/images/blog-highlights/icp-salesforce-netsuite-sync-for-beverage-brands-connect-distributor-accounts-and-delivery-locations.webp) ## 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 | Record | Owner | Operating rule | | --- | --- | --- | | Distributor account | Sales operations | Preserve the parent relationship and approved ERP payer reference. | | Legal customer | Finance | Own billing identity, terms, currency, and account status. | | Receiving location | Logistics | Own the accepted ship-to identifier, address, and delivery instructions. | | Location change request | Account operations | Track proposed updates and approval without rewriting existing shipment evidence. | ![Record ownership diagram: Distributor account, Legal customer, Receiving location](https://www.stacksync.com/images/blog-diagrams/icp-salesforce-netsuite-sync-for-beverage-brands-connect-distributor-accounts-and-delivery-locations.webp) *Define the record owner and the rule before enabling updates.* ## 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. ![5-step operating sequence: Salesforce NetSuite sync for beverage distributor depots](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-salesforce-netsuite-sync-for-beverage-brands-connect-distributor-accounts-and-delivery-locations.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## 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. ## Connect this process to the rest of your operation [Explore Stacksync two-way sync](https://www.stacksync.com/two-way-sync) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real distributor account example and the exception your team handles most often, for example distributor uses a third-party depot. - [Shopify–NetSuite Integration for Beverage Brands](https://www.stacksync.com/use-case/shopify-netsuite-integration-for-beverage-brands) - [Salesforce–NetSuite Integration for Beverage Distributor Accounts](https://www.stacksync.com/use-case/salesforce-netsuite-integration-for-beverage-distributor-accounts) - [Acumatica–Postgres Sync for Beverage Operations: Match Case and Pallet Records Across Warehouses](https://www.stacksync.com/blog/acumatica-postgres-sync-for-beverage-operations-match-case-and-pallet-records-across-warehouses) - [Beverage Distributor Order Workflows: Check Freight Thresholds and Delivery Windows](https://www.stacksync.com/blog/beverage-distributor-order-workflows-check-freight-thresholds-and-delivery-windows) - [Beverage Returns Workflows: Route Breakage Claims From Support to Finance](https://www.stacksync.com/blog/beverage-returns-workflows-route-breakage-claims-from-support-to-finance) - [Unify Customer and Financial Data in NetSuite | Step-by-Step Guide](https://www.stacksync.com/blog/unify-customer-financial-netsuite) - [Reconcile Freight Rates and Dwell Times Before Issuing Credits](https://www.stacksync.com/blog/reconcile-freight-rates-and-dwell-times-before-issuing-credits) The shared architecture guide covers record matching, ownership, and recovery across systems. ## Technical references - [Stacksync two-way sync quick start](https://docs.stacksync.com/start-here/quick-start) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Should each distributor warehouse be a separate customer? Only when the billing structure requires it, for example a depot that pays its own invoices under different terms. Otherwise keep one legal customer in NetSuite and model each depot as a ship-to location beneath it, following the approved ERP hierarchy. A customer per warehouse fragments credit limits and aging reports and leaves finance guessing which record is the payer when a remittance arrives. Which fields can a Salesforce user change on a synced NetSuite customer? Only the fields the account team owns: contacts, relationship notes, and a proposed location change. Terms, currency, credit status, and the ship-to identifier stay with finance and logistics, and the sync carries them into Salesforce as read-only values. A rep who needs a different depot address raises a change request; the address on the NetSuite location moves only after logistics approves it, and the rep sees the pending state in the meantime. How do we spot a duplicate depot before the sync creates it twice? Match on the NetSuite location ID rather than the display name, and give every Salesforce location record that ID before the first run. Export both lists and compare names that differ only by suffix, city, or abbreviation, then resolve those pairs by hand. Reviewers then see one location per dock in both systems, and a later rename on either side does not spawn a second record. About the author Ruben Burdin Founder & CEO Ruben Burdin is the Founder and CEO of Stacksync, the first real-time and two-way sync for enterprise data at scale. Ruben is a Y Combinator alumni with a strong background in software engineering and business. [All posts by Ruben Burdin](https://www.stacksync.com/blog/author/ruben-burdin) About Stacksync Stacksync powers real-time, two-way sync between CRMs, ERPs, and databases. Engineers sync data at scale and automate workflows, not dirty API plumbing. Stacksync ## Explore these integrations and topics - [integration Salesforce and NetSuite integration](https://www.stacksync.com/integrations/netsuite-and-salesforce) - [connector Salesforce integrations](https://www.stacksync.com/connectors/salesforce) - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [platform Two-way sync](https://www.stacksync.com/two-way-sync) - [platform CRM synchronization](https://www.stacksync.com/crm) - [platform CRM and ERP integration](https://www.stacksync.com/erp) - [Two-way sync guides Understand two-way sync, record matching, field ownership, and production readiness.](https://www.stacksync.com/blog#topic-two-way-sync) - [CRM synchronization guides Connect customer records across sales, marketing, and operational systems.](https://www.stacksync.com/blog#topic-crm-sync) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [Data engineering Salesforce–NetSuite Sync for Household Brands Serving Janitorial Distributors 5 min read read](https://www.stacksync.com/blog/salesforce-netsuite-sync-for-household-brands-serving-janitorial-distributors) [Data engineering Two-Way Sync for Construction Service Companies: Which Records to Connect First 5 min read read](https://www.stacksync.com/blog/two-way-sync-for-construction-service-companies-which-records-to-connect-first) [Data engineering Salesforce–NetSuite Integration: Mapping and Setup 8 min read read](https://www.stacksync.com/blog/the-complete-guide-to-salesforce-netsuite-integration-achieving-true-bi-directional-sync) ## You just read how it should work. See it run on your own data. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)