Missing Conversions and Mixed Pack Sizes: Exceptions for Household Order Agents

What this looks like in household consumables

A customer orders two mixed cases of cleaning refills. One warehouse document lists total containers, while another lists cases with no composition. The agent cannot determine whether the shipment matched the order until operations supplies the approved item-level contents of those mixed cases.

Records, ownership, and update rules

Work through the process

1. 01
   Detect unsafe assumptions

   Flag absent factors, conflicting effective dates, and mixed packs treated as uniform units. Separate these data gaps from arithmetic errors so the agent asks the right owner for help.
2. 02
   Preserve candidate interpretations

   List plausible mappings as unresolved candidates with their source context. Do not select the one that makes totals balance; balancing is not evidence that the physical goods match.
3. 03
   Request the smallest missing fact

   Ask for the effective case definition or item-level packing record that resolves the comparison. Include the order and shipment references so operations can answer without reconstructing the entire case.
4. 04
   Resume transparently

   After approval, recalculate the affected figures and show the changed result. Keep any other unresolved line open instead of treating one corrected conversion as closure of the whole dispute.
5. 05
   Hand the Genie two case sizes and confirm it picks neither

   Set up a product whose records carry two customer-specific case definitions, six pouches for one distributor and twelve for another, and remove the test customer's mapping. Run the Genie against a shipment for that customer. The blocked result should name the customer and product it lacks a factor for, list both existing definitions as candidates, and leave the quantity comparison empty. Then record the approved mapping and rerun. The resumed case should show the new factor, its source, and who approved it, next to the earlier blocked state. A shortage figure computed before the mapping existed, or a candidate chosen because it balances, stops the rollout.

Handle the exceptions explicitly

Two customer-specific case sizes exist

Require the correct customer and effective mapping rather than choosing a global default.

Pack changed after the sale

Use the purchased definition unless an approved substitution or repack changes the evidence.

Owner supplies an estimate

Label it as unconfirmed and keep the financial conclusion pending.

What to verify before expanding

• An absent conversion cannot yield an approved quantity conclusion.
• A resumed case records the exact new evidence used in the calculation.
• Two customer-specific case sizes remain separate; resolving one cannot install a global conversion for every customer.
• An estimated factor stays unconfirmed and cannot close the quantity comparison or support a final financial conclusion.

Technical references

• Stacksync Workflows quick start
• Stacksync NetSuite supported objects