--- title: "Beverages: two-way sync and automation | Stacksync" description: "Connect beverage ecommerce, distributor accounts, case and pallet records, delivery exceptions, and EDI." canonical: https://www.stacksync.com/industry/cpg/beverages last_modified: 2026-09-21 --- Beverages # Two-way sync and automation for beverages. > 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 ![Beverages systems connected through Stacksync two-way sync: Shopify, NetSuite, Salesforce, Acumatica, PostgreSQL, Zendesk](https://www.stacksync.com/images/industry-heroes/icp-beverages-800.webp) Connect beverage ecommerce, distributor accounts, case and pallet records, delivery exceptions, and EDI. Bottle, case, and pallet quantities lose their meaning between sales, warehouses, carriers, and distributor receipts. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide. Make shared records dependable Keep distributor orders traceable to the correct delivery location and actual case or pallet evidence. 1. **Sellable beverage pack** Product operations · Keep bottle, case, and variety-pack definitions explicit and versioned. 2. **Distributor location** Account operations · Distinguish the legal payer from each receiving location and its instructions. 3. **Delivery commitment** Logistics · Own the approved delivery window, freight conditions, and change history. 4. **Breakage evidence** Customer operations · Connect reported damage to the actual order and shipment before a finance decision. The platform, in operating order ## Start with live data. Put it to work. 01 ### [Two-way sync](https://www.stacksync.com/two-way-sync) Keep shared customer, order, and operational records aligned, with clear field ownership. Explore two-way sync 02 ### [Workflows](https://www.stacksync.com/workflow-automation) Move approved work between systems, assign exceptions, and confirm the result. Explore workflows 03 ### [AI agents (Genies)](https://www.stacksync.com/ai-agents) Investigate cross-system questions, assemble the evidence, and prepare the next action. Explore ai agents (genies) 04 ### [EDI](https://www.stacksync.com/edi) Connect trading-partner documents to operational records and exception handling. Explore edi Built around your operations ## For teams managing more than one business model Beverage brands combining production, DTC sales, distributor networks, and retail delivery. ### Distributor delivery review Check approved freight thresholds and delivery windows before releasing a distributor order. [Explore workflows ↗](https://www.stacksync.com/workflow-automation) ### Breakage claims Gather reported damage, receiving evidence, and the approved remedy for finance review. [Explore workflows ↗](https://www.stacksync.com/workflow-automation) ### Beverage delivery-claim investigation A customizable Genie job that compares distributor claims with shipment, appointment, and receiving evidence. [Explore Genies ↗](https://www.stacksync.com/ai-agents#genies-job-icp-beverages) Your systems and records ## Agree on ownership before automating actions | Record | Owner | Operating rule | | --- | --- | --- | | Sellable beverage pack | Product operations | Keep bottle, case, and variety-pack definitions explicit and versioned. | | Distributor location | Account operations | Distinguish the legal payer from each receiving location and its instructions. | | Delivery commitment | Logistics | Own the approved delivery window, freight conditions, and change history. | | Breakage evidence | Customer operations | Connect reported damage to the actual order and shipment before a finance decision. | [Shopify](https://www.stacksync.com/connectors/shopify) [NetSuite](https://www.stacksync.com/connectors/netsuite) [Salesforce](https://www.stacksync.com/connectors/salesforce) [Acumatica](https://www.stacksync.com/connectors/acumatica) [PostgreSQL](https://www.stacksync.com/connectors/postgresql) [Zendesk](https://www.stacksync.com/connectors/zendesk) [Shopify + NetSuite integration](https://www.stacksync.com/integrations/netsuite-and-shopify) [Salesforce + NetSuite integration](https://www.stacksync.com/integrations/netsuite-and-salesforce) Pallet shipments, advance ship notices, distributor locations, and receiving discrepancies. Evaluate your next process ## Find the right fit for your systems - Two-way sync [Shopify–NetSuite Integration for Beverage Brands](https://www.stacksync.com/use-case/shopify-netsuite-integration-for-beverage-brands) Connect beverage ecommerce orders to the ERP representation of bottles, cases, and variety packs. - Two-way sync [Salesforce–NetSuite Integration for Beverage Distributor Accounts](https://www.stacksync.com/use-case/salesforce-netsuite-integration-for-beverage-distributor-accounts) Connect beverage distributor relationships to the correct payer and receiving locations. - Workflows [Distributor Delivery-Window Automation for Beverage Brands](https://www.stacksync.com/use-case/distributor-delivery-window-automation-for-beverage-brands) Coordinate beverage order release around the accepted freight terms and distributor receiving window. - EDI [EDI Integration for Beverage Pallets and Distributor Shipments](https://www.stacksync.com/use-case/edi-integration-for-beverage-pallets-and-distributor-shipments) Connect beverage distributor documents to actual case and pallet contents. Implementation and operating guides ## Work through the details - Two-way sync [Shopify–NetSuite Sync for Beverage Brands: Align Bottles, Cases, and Variety Packs](https://www.stacksync.com/blog/shopify-netsuite-sync-for-beverage-brands-align-bottles-cases-and-variety-packs) Map each Shopify variant to an approved NetSuite item recipe with an effective date, so a twelve-bottle variety pack never turns into two cases of one flavor. - Two-way sync [Salesforce–NetSuite Sync for Beverage Brands: Connect Distributor Accounts and Delivery Locations](https://www.stacksync.com/blog/salesforce-netsuite-sync-for-beverage-brands-connect-distributor-accounts-and-delivery-locations) 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. - Two-way sync [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) A Postgres operations model that keeps a full pallet, a partial pallet, and a mixed pallet as different things, fed from the Acumatica entities the tenant exposes. - Workflows [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) Under-threshold freight and unconfirmed depot windows go to a named approver in Slack, and the order leaves NetSuite for the warehouse only with both decisions attached. - Workflows [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) Support logs the claim in Zendesk, logistics confirms which shipment broke, and finance approves one remedy in NetSuite with the damaged bottles counted, not assumed. - AI agents (Genies) [AI Agents for Beverage Brands: Investigate Distributor Delivery Claims](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) The Genie lines up the requested date, accepted appointment, and receipt timestamp in their original time zones, then hands logistics and finance a case with the gaps named. - AI agents (Genies) [Broken Cases and Disputed Delivery Windows: Exception Handling for Beverage Claim Agents](https://www.stacksync.com/blog/broken-cases-and-disputed-delivery-windows-exception-handling-for-beverage-claim-agents) One distributor claim, two uncertainties: the Genie resolves what the evidence supports, names who owns each missing fact, and leaves the rest visibly open. - EDI [Beverage EDI: Reconcile Pallet Shipments, Advance Ship Notices, and Distributor Receipts](https://www.stacksync.com/blog/beverage-edi-reconcile-pallet-shipments-advance-ship-notices-and-distributor-receipts) The advance ship notice describes the mixed pallet the warehouse loaded, not the pallet count on the order, and a distributor receipt is matched to it rather than replaced by it. ## Questions from beverages teams ### Does each distributor receiving location need its own Salesforce account? No. A distributor location is a separate record from the legal payer, and account operations owns that distinction. Salesforce keeps the distributor relationship and NetSuite books the payer; two-way sync carries the account identity between them while each receiving location keeps its own delivery instructions. That way a distributor with several warehouses has one payer and several ship-to records, and a location change never edits the payer. Account operations approves new locations before an order can reference one. ### What stops a distributor order from shipping outside its approved delivery window? The distributor delivery review workflow, which checks the delivery commitment before release. Logistics owns that commitment, including the approved window, freight conditions, and change history, so the workflow reads it rather than recalculating it. An order that misses the freight threshold or falls outside the window is held and routed to logistics with the reason attached. The sellable beverage pack version is checked at the same step so bottle, case, and pallet counts match what the distributor ordered. Release happens only after the hold is cleared. ### How does the delivery-claim Genie use EDI shipment and receiving records? It reads them as evidence and compares them with the distributor's claim. The Genie takes the pallet shipment and advance ship notice sent through EDI, the receiving discrepancy the distributor reported, and the breakage evidence customer operations logged in Zendesk, keeping bottle, case, and pallet units intact throughout. It cites each source record and flags what is missing. Approving a credit, amending a freight commitment, or contacting the distributor stays with the people who own those decisions; the Genie prepares the comparison for them. Bring one real process ## See how your records and handoffs fit together. Bring the systems, record types, and exceptions your team handles today. We’ll scope the connections and actions, then walk through the path to a confirmed result. [Book a demo](https://www.stacksync.com/book-a-demo) Explore your process in a demo, or get our shared two-way sync architecture guide.