--- title: "EDI Integration for Beverage Pallets and Distributor…" description: "Connect beverage distributor documents to actual case and pallet contents." canonical: https://www.stacksync.com/use-case/edi-integration-for-beverage-pallets-and-distributor-shipments last_modified: 2026-09-21 --- Beverages # EDI Integration for Beverage Pallets and Distributor Shipments > 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 distributor documents to actual case and pallet contents. This fits brands handling full pallets, partial pallets, mixed loads, and partner-specific receiving requirements. Scope the EDI transaction chain around real warehouse evidence and retain distributor location and item identities throughout. Shipment documents describe planned pallet counts while the actual truck contains a different mixture of cases and products. [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. When this fits ## Built for this operating problem Beverage brands combining production, DTC sales, distributor networks, and retail delivery. ### Describe the physical shipment Use actual item and case contents for each required handling unit rather than a universal cases-per-pallet assumption. ### Connect the document chain Preserve partner order and location references through shipment, invoice, and later receiving reconciliation. ### Document delivery is not receipt Orderful carries the ship notice to the distributor and records the acknowledgment that the file was received. That acknowledgment proves transmission, not what the depot counted on the dock. The distributor receipt stays a separate record owned by accounts receivable, and any shortage it reveals goes to operations or finance for a decision. Moving a document through EDI does not create two-way sync of NetSuite orders or pallet contents. The process, end to end ## Follow the work across systems A distributor order becomes a mixed pallet plus loose cases during packing. The ERP contains order lines, the warehouse knows the final contents, and the partner expects a specific shipment hierarchy. A demo should show the final physical configuration flowing into the required document without treating transmission as proof of receipt. [NetSuite connector](https://www.stacksync.com/connectors/netsuite) [Orderful connector](https://www.stacksync.com/connectors/orderful) Scope your implementation ## Bring these details to the demo - The distributor’s EDI and handling-unit requirements. - Examples of full, partial, and mixed pallet shipments. - Product-specific case and pallet configurations. - Available warehouse contents and receiving references. Review [current platform pricing](https://www.stacksync.com/pricing) alongside the records, volume, and actions in your process. Use your own operating baseline to evaluate the economics. [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. From foundation to action ## One connected operating process 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 Go deeper ## Implementation guides for your team - [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. [Explore all beverages integration and automation guides ↗](https://www.stacksync.com/industry/cpg/beverages) ## Common evaluation questions ### Can one pallet factor work for every beverage product? No. Product, loading configuration, and mixed or partial contents determine the actual case quantities. ### What happens when the warehouse rebuilds a pallet after the ship notice is prepared? The notice must describe the truck, not the plan. When packing turns a full pallet plus loose cases into one mixed pallet, the prepared document is regenerated or corrected under the distributor’s process before it is sent through Orderful. The corrected notice lists item-level case contents for the mixed pallet and keeps loose cases explicit rather than rounding them into a whole-pallet count. Its totals are reconciled to the NetSuite order lines and remaining balance, and it is validated against the partner’s guidelines before release. ### Should EDI be our first Stacksync product for distributor shipments? It can be the entry point when a distributor mandate is the pressing problem, but the layers stack in order. Two-way sync keeps NetSuite order lines and the warehouse’s pallet contents on the same item and destination identifiers the documents will carry. Workflows hold the ship notice until final packing is confirmed and block release when loose cases are missing. Genies compare a pallet-only distributor receipt with the transmitted notice and draft the item-detail request for a shortage. EDI through Orderful is the partner document layer on top.