Every reply read the way your QA team would read it
Certificates, statements and specifications are read as they arrive: what the document is, who holds it, when it expires and what it covers. Try it with an example.
This certifies that Bee Co-op Ltd.
Products: Honey, Honey powder
Valid through 31 March 2027
Issued by Northern Kosher Council
- Document
- Kosher certificate
- Holder
- Bee Co-op Ltd.
- Covers
- Honey, Honey powder
- Valid through
- 31 March 2027
- Issued by
- Northern Kosher Council
In reviewProposed for 2 lines
A reading is a proposal
Each document waits in Review with what was read from it. A person on your team accepts or rejects it, and nothing is filed before that.
- What is read: the document type, issue and expiry dates, the holder, the certification body, the standard and the products named.
- Dates only as the document states them. A date that is not there is left empty, never guessed.
- A rejection needs its reason, and both decisions are logged by name.

Filed where it belongs
The reading says which line and which document type it is for. A supplier's certificate is kept once for the supplier, and every ingredient they supply shows it.
- PDFs and pictures: PDF, PNG, JPEG and WebP.
- The older document is kept when a newer one replaces it.
- Uploads work the same way as replies by e-mail: add a file to a cell and it is read.
documents were filed from 265 supplier replies at Stephano Group between 6 November 2026 and 14 November 2026. Its QA team rejected 61 on review.
The rest of the platform
The matrix
Every ingredient from every supplier, and the documents each one needs, built from what you buy.
How the matrix worksSupplier requests
One e-mail per supplier each morning from your own mailbox, with follow-ups and escalation.
How requests workDocument reading
Each reply is read: what it is, who holds it, when it expires and which lines it covers.
How reading worksCertificate checks
Kosher, organic, non-GMO and food-safety certificates confirmed at their certifiers' directories.
How checks workApproval and risk
A named person's approval for each supplier beside a risk flag, and the annual specification review.
How approval worksThe assistant
Questions in plain words, answered from your own records. It reads, and changes nothing.
How the assistant worksSee it on your own suppliers in 30 days
Every plant starts with a pilot on its own supplier list, measured the same way Stephano's results were.
- Week 1
Your matrix, live
Built from your ingredient and supplier list or your ERP. Your document rules are set with you and your QA mailbox is connected.
- Weeks 2 to 4
Suppliers answer
Requests and follow-ups go out each morning. What suppliers send is read and waits in Review for your QA team.
- Day 30
The count, again
Outstanding documents are counted by the same rule as on day one. You see the difference and decide.