--- title: "Beverage claim Genie exceptions for damage and timing" description: "A beverage claim Genie that keeps a mixed-pallet damage count and a disputed appointment as separate open questions, each routed to its owner." canonical: https://www.stacksync.com/blog/broken-cases-and-disputed-delivery-windows-exception-handling-for-beverage-claim-agents last_modified: 2026-09-21 --- # Broken Cases and Disputed Delivery Windows: Exception Handling for Beverage Claim Agents > 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 One distributor claim, two uncertainties: the Genie resolves what the evidence supports, names who owns each missing fact, and leaves the rest visibly open. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision Beverage claim agents need separate exception paths for quantity uncertainty and timing uncertainty. Broken cases require item and pack evidence; disputed delivery windows require the accepted commitment and comparable timestamps. Preserve unresolved branches independently so one verified fact does not make the entire claim appear settled. 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: Beverage claim Genie exceptions for damage and timing](https://www.stacksync.com/images/blog-highlights/icp-broken-cases-and-disputed-delivery-windows-exception-handling-for-beverage-claim-agents.webp) ## What this looks like in beverages A distributor reports both late arrival and a damaged mixed pallet. The arrival timestamp is clear, but the appointment was revised, and the damage report lists cases without identifying flavors. The agent can verify part of the timeline while requesting the missing appointment approval and item-level damage evidence. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Quantity uncertainty | Warehouse reviewer | Identify missing item, case factor, or damaged-unit evidence without guessing an average. | | Timing uncertainty | Logistics reviewer | Identify the disputed appointment version or timestamp interpretation. | | Evidence request | Case coordinator | Route each missing fact to the owner who can provide authoritative evidence. | | Updated conclusion | Finance reviewer | Require a revised, sourced result before accepting or disputing the affected portion. | ![Record ownership diagram: Quantity uncertainty, Timing uncertainty, Evidence request](https://www.stacksync.com/images/blog-diagrams/icp-broken-cases-and-disputed-delivery-windows-exception-handling-for-beverage-claim-agents.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Split the exception dimensions Track timing, damage, shortage, and commercial-policy questions separately. A confirmed arrival does not establish the accepted window, and a damage photo does not establish which case quantities should be credited. 2. 02 Preserve original units and times Keep the source figures alongside proposed normalized values. Require an approved conversion or timezone interpretation before using the result in a financial recommendation. 3. 03 Route precise questions Ask logistics for the accepted appointment and warehouse operations for item-level damage evidence. A generic request for more information leaves ownership unclear and encourages repeated agent retries. 4. 04 Reassess only supported conclusions When new evidence arrives, update the relevant branch and show what changed. Keep other unresolved portions open and avoid presenting a partly supported case as fully resolved. 5. 05 Resolve the damage branch and confirm the timing branch stays open Run the Genie on a claim where the damage report gives one case total for a mixed pallet and the appointment exists in two versions. Its first packet should show two open branches: a request to the warehouse reviewer for item-level damaged quantities, and one to the logistics reviewer for the accepted appointment, each naming the record and the person. Supply the item-level counts through Postgres and rerun. The damage branch should close with per-item figures while the timing branch stays open. Stop the rollout if the packet applied an average case factor, if a missing fact has no owner, or if the whole claim reads as settled. ![5-step operating sequence: Beverage claim Genie exceptions for damage and timing](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-broken-cases-and-disputed-delivery-windows-exception-handling-for-beverage-claim-agents.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Damage count uses a mixed pallet total Request item-level quantities instead of applying a single case conversion. ### Two appointment versions conflict Escalate the accepted commitment decision to logistics. ### Evidence arrives after a deadline Flag the timing to the case owner without inventing a backdated submission or approval. ## What to verify before expanding - Partial certainty remains visible rather than becoming a blanket conclusion. - Each missing fact has a named owner and a specific evidence request. - An unresolved appointment version leaves the timing branch open even after the item-level damage quantity is established. - Late-arriving evidence retains its actual receipt time and flags the response deadline without creating backdated approval. ## Connect this process to the rest of your operation [Explore Stacksync AI agents (Genies)](https://www.stacksync.com/ai-agents#genies-job-icp-beverages) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real quantity uncertainty example and the exception your team handles most often, for example damage count uses a mixed pallet total. - [AI Agents for Beverage Brands: Investigate Distributor Delivery Claims](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) - [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) - [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) - [Investigate Freight Invoice Disputes Across NetSuite and Postgres](https://www.stacksync.com/blog/investigate-freight-invoice-disputes-across-netsuite-and-postgres) - [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 Workflows quick start](https://docs.stacksync.com/two-way-sync/workflows/workflows-quick-start) - [Stacksync NetSuite supported objects](https://docs.stacksync.com/two-way-sync/connectors/netsuite) FAQ ## Frequently asked questions Why not let the agent choose the most recent appointment? Because the latest message may be a request rather than an accepted revision. A depot can email a new time on Tuesday, have it declined on Wednesday, and still sit last in a sorted inbox. The Genie treats an appointment as accepted only when it can cite the approval evidence; where it cannot, the timing branch stays disputed and the logistics reviewer picks the binding version. If the depot will not itemize the damage, is a house cases-per-pallet factor acceptable? No. A single conversion for a mixed pallet is the guess this design refuses to make, because two flavors on one pallet can carry different case counts and different unit values. If the distributor cannot itemize, the quantity branch stays open and the finance reviewer decides whether to accept the claim at the level the evidence supports, dispute it, or hold it. The Genie records that choice; it does not make it. What does a partly resolved claim look like to the finance reviewer? A per-branch status rather than one verdict. The packet lists the quantity branch and the timing branch side by side, each with a state (resolved, open, or disputed), its evidence, and the last owner asked. Finance can accept or dispute the resolved portion now and leave the other pending, with the amount split to match. A claim reads as settled only when every branch is closed, and the packet says which ones are not. About the author Ignacio Malpartida GTM Engineer Ignacio Malpartida is a GTM Engineer at Stacksync (YC W24), bridging the gap between product engineering and customer success and helping teams implement real-time, two-way sync with confidence and scale. [All posts by Ignacio Malpartida](https://www.stacksync.com/blog/author/ignacio-malpartida) 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 - [connector NetSuite integrations](https://www.stacksync.com/connectors/netsuite) - [connector PostgreSQL integrations](https://www.stacksync.com/connectors/postgresql) - [connector Gmail integrations](https://www.stacksync.com/connectors/gmail) - [platform AI agent operations](https://www.stacksync.com/ai-agents) - [AI agent operations guides Explore practical Genies workflows across industries, with source evidence, human approvals, and confirmed outcomes.](https://www.stacksync.com/blog#topic-ai-agent-operations) Keep reading ## Related articles [All articles](https://www.stacksync.com/blog) [App tips AI Agents for Beverage Brands: Investigate Distributor Delivery Claims 5 min read read](https://www.stacksync.com/blog/ai-agents-for-beverage-brands-investigate-distributor-delivery-claims) [App tips Investigate Freight Invoice Disputes Across NetSuite and Postgres 8 min read read](https://www.stacksync.com/blog/investigate-freight-invoice-disputes-across-netsuite-and-postgres) [App tips Reconcile Freight Rates and Dwell Times Before Issuing Credits 7 min read read](https://www.stacksync.com/blog/reconcile-freight-rates-and-dwell-times-before-issuing-credits) ## 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/)