A specialty chemical manufacturer issues a certificate of analysis with every shipment. We built the system that produces them from approved data — and refuses to produce one that isn't.
Specialty & high-purity chemicals
Supplier intake, lot review, customer CoAs
Running end to end on the first product line; more materials rolling out
Raw materials arrived with supplier certificates — PDFs and spreadsheets, each supplier in its own layout. Values were read off those documents and carried by hand into spreadsheets, SPC software, and finally into a customer-specific certificate for each shipment.
Put every lot's quality data on one normalized record. Let software do the collecting and assembling. Keep every quality judgment with a named person — and make it impossible to issue a certificate that skips them.
Scheduled sweeps pick up supplier CoAs and production logs and read each one against that supplier's locked format.
Values are staged with a link to their source document. Anything that won't parse or match opens a numbered exception.
The quality reviewer approves or rejects each lot's full parameter set, with out-of-spec flags in view. One attributable decision.
Sales generates and emails the customer's certificate in one action — only if the pairing is qualified and every value is approved.
Each supplier's CoA layout is locked: expected rows, units, which field is the lot number, which date is the test date. A missing value holds the document; a new row or changed unit raises a watch. Format drift is caught at the door instead of on a customer certificate.
Open exceptions, lots blocked from matching, and lots waiting for approval all sit on one screen. Exceptions are closed by a named person with a required comment and stay attached to their document permanently — a quiet feed and a dead one are easy to tell apart.
Customer CoAs are filled from the client's own document templates, one per customer and product. Once issued, a certificate is a snapshot: a correction produces a new version, and the original stays on file exactly as it was sent.
The client owns the code, the database, and where it runs. It is standard, well-documented technology any competent engineer can maintain, and it runs alongside their existing SPC package rather than replacing it on day one.
Walk us through how a certificate gets made at your plant. In 30 minutes we'll tell you what the first automated product line would look like.
Or email us directly: hello@foundrydatagroup.com