retries make our coupon batch look bigger

We have coupon labels but reuse them between batches. Attempts have their own sequence numbers.

Then include batch context in the item identity. Also check when those attempt numbers restart. Otherwise a correction to the count may accidentally merge different batches instead of only removing duplicate deliveries.

Yes. Quality can reopen it. Current report never removes its old pass from the total.

Then quality needs to define the current disposition rules, including reopened work, before anyone chooses a clever query to count them.

Ask for that rule in examples: failed then approved retry, repeated delivery of one result, and accepted then reopened. They are different histories even if the current report adds them all happily.

Quality supplied examples. Reopened means pending review, outside accepted total. Previous decisions stay in history.

Try an out-of-order result too. Newest arrival needn't be newest inspection.

Yes, and use the documented attempt and review relationships to apply dispositions, not arrival time alone. That avoids an old delayed result changing the current item decision by accident.

Developer has that case. Duplicate deliveries now leave the offline total unchanged. Reopened coupons disappear from accepted.

Where do results with an unreadable coupon label go?

Separate unmatched queue. They aren't assigned to a coupon by guessing the nearest time.

Can somebody see that queue without accidentally accepting its contents?

Keep viewing separate from disposition actions. Also check that replaying the saved history rebuilds the same current item list, not only the same total; two different mistakes can cancel in a number.

Has the responsible inspector compared that rebuilt list with the batch disposition records yet?

Yes. Lists match after the replay tests. Inspector approved the report; unmatched remains visible and separate.

Thanks, Thomas. The delayed-result example exposed a mistake our duplicate test never touched.

Retain those examples with the report checks. The next developer needs to know why a late pass is not automatically permission to change the current disposition.