Lot acceptance
Check every incoming lot against your limits
Compound reads each COA as it arrives and compares its test results with your approved specification. QA sees missing tests, wrong units, lot mismatches, and out-of-spec values before release.
COA-ASH-2419.pdf
Certificate of Analysis
SDS-KSM-2024.pdf
Safety Data Sheet
COA-FSO-0871.pdf
Certificate of Analysis
Why teams use it
Review every lot against the same limits
Incoming lot review is required, but volume turns careful checks into spot checks.
Catch supplier paperwork errors
The COA may say pass while your spec says otherwise. Compound checks against your limits, not the supplier’s verdict.
Backlog hides risk
Lots waiting on review block release, while rushed reads leave a weak acceptance log behind.
What changes
Turn deviations into the worklist
Missing tests, wrong units, mismatched identifiers, and out-of-spec values surface with source context.
Keep every pass recorded
Compound logs passing lots with the same evidence and keeps the acceptance trail complete.
Manage the queue in Tables
Keep every lot, result, deviation, and source in one live view that QA can filter and review.
Who is it for
Operations leaders
Teams trying to release received lots faster without lowering the QA bar.
Quality leaders
Owners of specifications, acceptance criteria, and release decisions.
Supplier quality and procurement
Tables exposes recurring supplier issues instead of burying them lot by lot.
Lot acceptance, in practice
What teams ask before running COA checks.
What does Compound check on a COA?
Whatever your SOP and spec require: identity, assay, micro, heavy metals, required tests, units, product and lot identifiers, result presence, and limits. Every finding quotes the relevant rule and the source line behind it.
How do COAs get in?
Uploaded, emailed straight in, or forwarded from receiving. The check runs when the COA arrives, without a separate step for the team to remember.
Does this replace our QA review?
No. Compound checks each COA against the spec, puts the deviations and source evidence in front of QA, and leaves the release decision with the reviewer.
What about the lots that pass?
Logged with the same evidence. When an auditor samples the acceptance log, you have a per-lot run history — every check, every citation — not just the deviations.
How does this reduce review time?
Compound extracts the values, runs the calculations, attaches citations, and highlights the places that need attention: missing tests, mismatched values, unit issues, and out-of-spec results.
Our specs live in Word documents and spreadsheets today.
Many teams start there. We map the first set of acceptance criteria with you, encode them as checks, and test them against past COAs before they run in the workflow.
See Compound in action
Purpose-built for regulated product teams. Find out how Compound can expand review coverage, reduce mistakes, and help your team handle more work.