--- title: "Snack Genie stop rules for case splits and missing receipts" description: "A snack-brand Genie pauses on an unapproved repack or a missing receipt, keeps its partial packet in Postgres, and resumes only on same-shipment evidence." canonical: https://www.stacksync.com/blog/case-splits-and-missing-receipts-exception-handling-for-snack-brand-order-agents last_modified: 2026-09-21 --- # Case Splits and Missing Receipts: Exception Handling for Snack-Brand Order 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 Repacked cartons, receipts from the wrong site, and absent paperwork are the moments a snack order Genie must stop, ask one precise question, and hold its work. Author Ignacio Malpartida · GTM Engineer Published September 21, 2026 Read time 5 min read APP TIPS ## The operating decision Design the snack-brand agent’s stop conditions around ambiguous pack conversions, split deliveries, and missing receipts. The exception path should preserve a partially complete investigation and request the exact missing fact. A Genie must not fill a document gap with a plausible narrative or infer that a case split was approved because the totals appear close. Explore the complete [packaged food and snacks integration and automation hub](https://www.stacksync.com/industry/cpg/packaged-food-snacks) for the systems and processes around this guide. ![Summary card: Snack Genie stop rules for case splits and missing receipts](https://www.stacksync.com/images/blog-highlights/icp-case-splits-and-missing-receipts-exception-handling-for-snack-brand-order-agents.webp) ## What this looks like in packaged food and snacks A retailer receives loose units after a damaged case is repacked. Its receipt uses units, the shipment notice uses cases, and the warehouse note mentions a mixed carton. The agent can calculate a candidate equivalence, but it still needs the approved repack evidence before treating the loose units as fulfillment of the claimed case line. ## Records, ownership, and update rules | Record | Owner | Operating rule | | --- | --- | --- | | Ambiguous comparison | Agent reviewer | Record the competing item or unit interpretations and the evidence needed to choose. | | Repack evidence | Warehouse supervisor | Own the approved carton or case split and its link to the original shipment. | | Missing receipt request | Customer operations | Specify purchase order, shipment, location, and date to obtain the right document. | | Resumed investigation | Case owner | Retain the earlier result and rerun only the affected evidence chain after resolution. | ![Record ownership diagram: Ambiguous comparison, Repack evidence, Missing receipt request](https://www.stacksync.com/images/blog-diagrams/icp-case-splits-and-missing-receipts-exception-handling-for-snack-brand-order-agents.webp) *Define the record owner and the rule before enabling updates.* ## Work through the process 1. 01 Detect uncertainty explicitly Define which missing identifiers, conversions, and receiving documents prevent a conclusion. Separate blocked facts from low-priority context so the agent can still return useful verified findings. 2. 02 Ask a resolvable question Request the exact repack record or receipt reference that would disambiguate the line. Avoid broad requests for all shipment paperwork when one missing relationship is the blocker. 3. 03 Preserve the partial packet Keep verified quantities, source links, and prior calculations while marking the unresolved branch. Another reviewer should be able to continue the case without repeating the whole investigation. 4. 04 Resume with version checks When evidence arrives, confirm that it belongs to the same shipment and revision. Recalculate the affected comparison and show what changed before seeking approval of the updated conclusion. 5. 05 Withhold the receipt, then supply one from the wrong location Run the repacked-carton scenario with the retailer receipt removed from Postgres. The Genie must return a named request stating the purchase order, shipment, location, and date it needs, and its packet must carry no delivery conclusion. A packet that treats the loose units as fulfillment of the case line without repack evidence stops the rollout. Then attach a receipt for a different delivery location that otherwise looks plausible. The Genie should reject the match and ask for the correct site's document. Supply the right receipt last and reopen the case; the resumed packet must show which fact arrived and which comparison it changed, while the earlier verified lines stay intact. ![5-step operating sequence: Snack Genie stop rules for case splits and missing receipts](https://www.stacksync.com/images/blog-diagrams-mermaid/icp-case-splits-and-missing-receipts-exception-handling-for-snack-brand-order-agents.webp) *Follow the operating sequence; unresolved exceptions return to a responsible reviewer.* ## Handle the exceptions explicitly ### Receipt belongs to another location Reject the proposed match and request the correct destination evidence. ### Pack factor changed mid-order Apply the approved effective rule by line or stop for product review. ### Uploaded document contradicts the ERP Present the conflict to the record owner; do not silently choose the most recent-looking document. ## What to verify before expanding - A missing receipt produces a named evidence request rather than a fabricated conclusion. - A resumed case shows which new fact changed the result. - A receipt for another delivery location fails the claim match even when the item, date, and quantity look plausible. - Resolving a repack factor recalculates only the affected lines and preserves the previously reviewed evidence for the other shipments. ## Connect this process to the rest of your operation [Explore Stacksync AI agents (Genies)](https://www.stacksync.com/ai-agents#genies-job-icp-packaged-food-snacks) and scope the records and actions against your actual systems. [Book a demo](https://www.stacksync.com/book-a-demo) with a real ambiguous comparison example and the exception your team handles most often, for example receipt belongs to another location. - [AI Agents for Packaged Food Brands: Investigate Grocery Short-Shipment Claims](https://www.stacksync.com/blog/ai-agents-for-packaged-food-brands-investigate-grocery-short-shipment-claims) - [Grocery EDI for Snack Brands: Keep Case Counts and Advance Ship Notices Consistent](https://www.stacksync.com/blog/grocery-edi-for-snack-brands-keep-case-counts-and-advance-ship-notices-consistent) - [Shopify–NetSuite Sync for Snack Brands: Match Single Units, Multipacks, and Cases](https://www.stacksync.com/blog/shopify-netsuite-sync-for-snack-brands-match-single-units-multipacks-and-cases) - [How to Explain Split Shipments and Missing Tracking](https://www.stacksync.com/blog/how-to-explain-split-shipments-and-missing-tracking) - [Resolve Shopify Order Data Inconsistency with Real‑Time Sync](https://www.stacksync.com/blog/resolve-shopify-order-data-inconsistency-realtime-sync) 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 When should the agent escalate instead of retrying? Escalate the moment progress depends on a business decision or on evidence no system holds. Retrying the same lookup cannot approve a pack conversion or produce a delivery receipt that was never filed. A second pass is only worth running after new evidence arrives, and even then the Genie should rerun the affected branch, not the whole investigation. Should one Genie job handle both the first pass and the resumed case? Yes, one job with two entry points. The first pass starts from the claim; the resumed pass starts from the stored partial packet and the new document's reference. Keeping them in one job means the same evidence rules and stop conditions apply on both passes, so a resumed case cannot quietly relax a check that blocked the original. Version the packet on every pass so the reviewer can diff them. Is a partial packet safe to share with the retailer? Not as it stands. The partial packet is an internal working record: it lists candidate interpretations, unverified quantities, and the brand's own open questions. Sharing that invites the retailer to argue from the brand's uncertainty. The Genie never sends anything outside the company; the case owner decides what leaves, and only after the blocked branch is resolved and the conclusion is approved. Send the retailer the evidence request, not the packet. 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 Packaged Food Brands: Investigate Grocery Short-Shipment Claims 5 min read read](https://www.stacksync.com/blog/ai-agents-for-packaged-food-brands-investigate-grocery-short-shipment-claims) [App tips Automate Co-Packer Receipt Exceptions for Snack Brands Before Inventory Reconciliation 5 min read read](https://www.stacksync.com/blog/automate-co-packer-receipt-exceptions-for-snack-brands-before-inventory-reconciliation) [App tips Identify At-Risk Orders Using Inventory and Incoming Purchase Orders 7 min read read](https://www.stacksync.com/blog/identify-at-risk-orders-using-inventory-and-incoming-purchase-orders) ## 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/)