Managing supplier specs and CoAs as ingredient data

Every ingredient you use arrives with paperwork: a supplier specification sheet and, per batch, a certificate of analysis. These documents hold the data your entire formula depends on — composition, actives, allergens, contaminants, identity. Yet in most operations, that data sits trapped in PDFs and email attachments, re-read by hand whenever it is needed. Capturing supplier specs and CoAs as structured ingredient data is what turns that paperwork into something your software can actually use. Here is how.

What supplier documents contain

A supplier specification describes what an ingredient is: its composition, active or elemental content, physical characteristics, allergen status, contaminant limits, and identity. A certificate of analysis reports what a specific batch actually tested at, against that specification. Together, they are the authoritative source of the data that drives your formulas, labels, and compliance.

In other words, the most important ingredient data you have arrives from your suppliers in these documents — and the question is whether that data lives as usable structure or as trapped text.

The trapped-data problem

When supplier specs and CoAs live as PDFs in folders and inboxes, their data is trapped. To use an ingredient's elemental content or allergen profile, someone has to find the right document, read it, and transcribe the figure — every time. The data is technically held but not usable; it cannot flow into calculations, checks, or documents automatically.

This is slow, error-prone, and fragile. A figure transcribed wrong, a superseded spec used by mistake, a CoA no one can find during an audit — all symptoms of data trapped in documents rather than captured as structure.

Capturing the data as ingredient structure

The solution is to capture the key data from supplier specs into the ingredient record — the composition, elemental content, allergens, contaminants, identity — so it becomes structured data the software can use. Once captured, that data flows automatically into every formula using the ingredient: the calculations, the compliance checks, the allergen and contaminant roll-ups, the documents.

The supplier document becomes the source you capture from, and the structured ingredient data becomes what your formulas actually run on — entered once, used everywhere.

Keeping CoAs connected to batches

Certificates of analysis are batch-specific, so they connect to the lots you actually use. Keeping CoAs associated with their ingredient and batch — rather than loose in an inbox — means the evidence that a batch met its specification is findable and tied to where it was used. This matters enormously for audits and traceability: when asked to show the CoA for the lot in a given batch, you can.

Handling spec changes

Suppliers update their specifications, and a changed spec can change an ingredient's data — which affects every formula using it. When supplier data is captured as structured ingredient data, updating it is a single action that flows to every product. When it is trapped in documents, a spec change is easy to miss, leaving formulas running on outdated data without anyone realising.

Because supplier documentation and verification expectations vary, confirm the requirements that apply to your specific situation rather than relying on a general summary.

Where Lemoniq fits

Lemoniq lets you capture supplier specification data into structured ingredient records — composition, elemental content, allergens, contaminants, identity — so it flows automatically into your formulas, calculations, compliance checks, and documents. Certificates of analysis stay connected to their ingredients and batches for traceability, and updating an ingredient's data from a revised spec flows to every product using it. Supplier paperwork stops being trapped in PDFs and becomes usable data your formulas run on.

The takeaway

Supplier specs and CoAs hold the data your formulas depend on — but trapped in PDFs and emails, that data is re-read and re-typed by hand, slowly and unreliably. Capturing it as structured ingredient data makes it flow into everything automatically, keeps CoAs connected to batches for traceability, and lets a spec change update every affected product at once. Put your supplier data to work as structure, not paperwork.

Lemoniq captures supplier spec data as structured ingredient data and keeps CoAs tied to batches — so the data flows into your formulas instead of sitting in PDFs. We solve this exact problem. See how it works