Missing COAs and Batch Mismatches: Exception Handling for Nutrition Brand Agents

What this looks like in nutrition and supplements

A buyer supplies a shortened lot code. The repository contains two plausible COAs, and one is a draft with a later upload date. An unsafe agent chooses the newest file. A useful exception path records both candidates, identifies the missing lot characters, and asks quality to establish the correct approved document.

Records, ownership, and update rules

Work through the process

1. 01
   Define non-negotiable matches

   Require the approved product and lot relationship for batch-specific documents. Fuzzy text similarity can help locate candidates but must not satisfy the final identity check.
2. 02
   Separate missing from conflicting

   A missing file needs a document request; two contradictory approved-looking files need owner review. Give each problem the right state so repeated retrieval does not conceal a version-control issue.
3. 03
   Ask the narrow question

   Request the complete lot code or authoritative document ID that resolves the case. Include the candidate references for the owner, while respecting restrictions on what the external requester can see.
4. 04
   Revalidate the whole packet

   When a corrected file arrives, check its scope, approval, and sharing status again. A resolved filename mismatch does not automatically resolve permission or version conflicts.
5. 05
   Feed the agent a neighboring-batch COA and confirm it holds

   Set up a test where the repository holds an approved COA for the adjacent batch and nothing for the requested one. The case the agent prepares must stay incomplete, with the adjacent file listed as a rejected candidate and the rejection reason stated (batch does not match), and the outgoing evidence request must go to quality without an attachment. Open the case as the reviewer and confirm you can read why each candidate was accepted or rejected without opening the files. Stop the rollout if the adjacent COA appears in the proposed packet, if the reason field is blank, or if the request went out with an unapproved file attached.

Handle the exceptions explicitly

Only another batch has a COA

Keep the request incomplete and ask for the required document; never substitute.

File was superseded

Exclude it and identify the approved replacement or route to the owner.

Request changes to another product

Create a revised scope and rerun identity checks instead of reusing the old approval.

What to verify before expanding

• No unresolved lot match can produce an approved external attachment.
• The reviewer sees the reason a candidate was rejected or accepted.
• A COA for a neighboring batch cannot fill the missing document slot, even when its product name and date appear suitable.
• Changing the requested product invalidates the prior packet approval and reruns product, lot, version, and permission checks.

Technical references

• Stacksync Workflows quick start
• Stacksync NetSuite supported objects