Case Splits and Missing Receipts: Exception Handling for Snack-Brand Order Agents

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

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.

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.

Technical references

• Stacksync Workflows quick start
• Stacksync NetSuite supported objects