98% Model confident
Why: Typed label and value are clear in the document header.
Human check: Confirm the ID matches the supplier portal or email attachment.
Tools/AI scan demo
See how document extraction should ask for human review.
Switch between a sample COA, BOL, invoice, and receipt. Each sample shows the fields a scanner would draft, the confidence state for each value, and the exact places a human should verify before anything becomes a saved food-safety record.
4
sample documents
44
sample fields
0
live API calls
1. Pick a static sample
15
fields
2
review
4.8 sec
sample time
Certificate of Analysis
A clean supplier COA usually extracts well, but the sample keeps one borderline result and one signature flag in review so the workflow does not pretend every field is equally certain.
Review focus
Check the yeast and mold result formatting before accepting the lot.
Source preview
ACME Mycology Labs - Certificate of Analysis
Synthetic sample document for extraction review
COA
Static sample
Schema
coa.v1
Header
Product
Results
Approval
2. Review extracted fields
Confidence is a triage signal, not a signature.
Active source field: Yeast and mold. The mark before 10 could be read as < or <= in the sample image.
96% Model confident
Why: ISO date is printed next to a clear Issue date label.
Human check: Check that this is the issue date, not the manufacture date.
95% Model confident
Why: Supplier name is prominent and not near another business name.
Human check: Match the supplier to the approved supplier list.
92% Model confident
Why: The customer line is visible and separated from the supplier block.
Human check: Check whether this COA is customer-specific or generic.
94% Model confident
Why: Product description is printed as a single line.
Human check: Confirm it maps to the product or ingredient record you receive.
89% Model confident
Why: Lot code is clear, but the trailing B sits near a fold mark in this sample.
Human check: Verify every character before using the lot in traceability records.
93% Model confident
Why: Date is printed in the product block beside the manufacture label.
Human check: Confirm date order if the supplier normally uses MM/DD/YYYY.
91% Model confident
Why: Best before label and value are readable.
Human check: Check whether your receiving log calls this expiry, best before, or retest date.
95% Model confident
Why: The result, unit, specification, and pass state are on one row.
Human check: Compare result against the specification before releasing the lot.
94% Model confident
Why: The pH result appears in a structured test table.
Human check: Confirm this parameter belongs in your supplier verification log.
88% Model confident
Why: The less-than symbol is legible and the unit is on the same line.
Human check: Keep the qualifier with the number; do not record this as 10.
72% Review
Why: The mark before 10 could be read as < or <= in the sample image.
Human check: Open the source COA and confirm the exact qualifier.
97% Model confident
Why: Result is a standard text phrase with a clear sample size.
Human check: Confirm the test method if your customer requires it.
90% Model confident
Why: Lab name is printed below the results table.
Human check: Check whether the lab is internal or third-party for your supplier program.
58% Manual check
Why: Initials appear in the approval box, but the sample signature is faint.
Human check: Manually confirm the signoff before treating the COA as reviewed.
Review gate
0 of 2 review-needed fields checked. The low and amber fields stay visible until a human accepts or edits them.
Ready for real documents?
Move from sample extraction to the saved scanner workflow.
The free page shows the review pattern. Plan Keeper is where Andrew designed the live scanner to save your own COAs, receiving BOLs, calibration certs, pest reports, SDS files, water tests, training certificates, supplier audit certs, shipping BOLs, customer POs, and regulatory IDs with per-field confidence and human verification. Pro raises scan and storage limits; Enterprise is custom.
Why confidence matters
A confidence score is not a release decision. It is a triage cue that tells the operator which drafted fields deserve the first look.
Regulatory hooks
COA review supports supplier verification work such as 21 CFR 117.420 receiving procedures. BOL fields can help reconcile receiving and traceability records.
Source status
Sample document structures come from the scan-demo research file. The 21 CFR 117.420 reference was checked against eCFR on June 5, 2026.