Caramel colour specification, TDS and COA serve different purposes. The TDS states product indicators while COA gives actual test data of one batch. Neither replaces destination‑market regulations or formulation trials. Food manufacturers shall approve the documents only after all data are consistent.
What Should Each Caramel Color Document Prove?
Clear‑role documents simplify supplier audits. Brochures are uncontrolled. Specifications define requirements, TDS lists product parameters, COA shows batch test results, and compliance documents supply relevant certifications.
| Document | Primary job | Must not be treated as |
|---|
| Product page or brochure | Commercial introduction | A controlled specification or lot-release record |
| TDS | Product identity, controlled data and use/handling context | Proof that a delivered lot was tested and released |
| Agreed specification | Contractual acceptance criteria and methods | A record of actual batch results |
| COA | Traceable results for one lot | A general marketing sheet or finished-food approval |
| Regulatory or declaration file | Market- or claim-specific evidence | Universal authorization for every food and country |
| Formulation trial report | Performance in the buyer’s recipe and process | Proof of ingredient identity or regulatory status |
The official JECFA caramel-colours specification, EU Regulation (EU) No 231/2012 and US 21 CFR 73.85 show why authority and jurisdiction must remain visible in the review.
How Should Procurement Review a Caramel Color TDS?
Start with document control. Confirm the title, product code, revision, issue date, owner and page count. If the file was copied from an email chain, ask whether it is still controlled. A public supplier sheet for a named Class II grade explicitly warns that a downloaded or modified copy can become uncontrolled; that is a useful document-control lesson, not a specification for another supplier.
Then review product identity and scope:
- caramel-color class or applicable regulatory designation;
- physical form and product code;
- intended document scope and referenced market;
- guaranteed specification fields separated from typical data;
- units, basis, dilution, temperature and other test conditions;
- test method or method reference for critical parameters;
- storage, handling, shelf-life or review-period statement;
- packaging and logistics information needed by the receiving site;
- revision history and change-notification contact.
A statement such as “meets food regulations” is too broad for approval unless it names the jurisdiction, legal source and relevant product scope. A typical value may help R&D plan a trial, but it is not a release criterion until the parties adopt it in the specification.
What Belongs in the Agreed Specification?
A caramel colour specification may use British spelling while a US supplier writes caramel color specification; the review task is the same. Translate both into one controlled requirement table.
For each critical characteristic, record the parameter, acceptance criterion, unit, basis, method, sampling rule, test frequency and responsible release party. Mark whether the item is required by law, required by the customer, or adopted for process performance. That distinction prevents a typical commercial target from being presented as a regulatory maximum.
Keep parameters application-relevant. Identity, color measurement and critical purity criteria usually need explicit methods and bases. Handling or microbiological criteria may be required by the buyer’s risk assessment. The article cannot prescribe one universal list because the class, form, destination market, food category and plant controls change the decision.
The specification should also define what happens when a result is near a limit, missing, retested or outside the criterion. Without an escalation rule, the same result may be released by one reviewer and rejected by another.
What Must a Caramel Color COA Show?
A usable COA links a particular lot to the agreed specification. It should include the supplier and manufacturing identity, product code, lot or batch number, manufacture or test date, specification reference, results, criteria, units, methods or method references, and release authorization.
Review the result column carefully. A copied specification limit is not a measured result. “Pass” can be acceptable only when the agreed procedure permits attribute reporting and the underlying evidence remains traceable. For quantitative criteria, QA should normally be able to see the actual reported value and understand its basis.
Check that:
- the product and lot match the purchase order and container labels;
- the COA cites the current approved specification;
- every critical result has the correct unit and reporting basis;
- method codes match the TDS or agreed specification;
- retests, deviations and corrected documents remain traceable;
- the release signature or electronic approval is attributable;
- the document language and date format cannot create ambiguity.
The COA supports lot release. It does not prove that the material reaches the target shade, clarity or stability in the finished food.
How Do You Reconcile Official, Supplier and Lot Records?
Use a three-column reconciliation instead of copying values into one mixed table. Column one holds the official identity or purity requirement with jurisdiction, source and effective date. Column two holds the agreed supplier criterion and method. Column three holds the delivered-lot result from the COA. Add a fourth column for the review decision and owner.
This structure exposes differences in basis. JECFA, EU and supplier records may use different limits, methods or calculations. A value expressed as supplied cannot be compared automatically with one on a solids or equivalent-color basis. A 560 nm tinctorial-power result cannot be substituted for a 610 nm color-intensity result without an approved equivalence method.
When a gap appears, classify it:
- information gap: a method, unit, basis, revision or result is missing;
- requirement conflict: two applicable criteria cannot both be met as written;
- identity conflict: the class, product code or form is inconsistent;
- performance gap: documents pass, but the formulation trial fails;
- change-control gap: a new document or lot cannot be traced to the approved version.
Assign each gap to procurement, QA, regulatory or R&D instead of leaving it as an email comment.
Which Red Flags Should Stop Approval?
Place the review on hold when a critical file is undated or uncontrolled, the product class changes between documents, typical data is presented as a guaranteed result, or the COA repeats limits without lot values. Other red flags include undefined units, missing solids or equivalent-color basis, an obsolete method, broad “worldwide compliance” language, incompatible revision numbers, and a corrected COA that does not identify what changed.
Supplier-specific examples can help a buyer see how a real TDS is structured. They must never be copied into Qianhe specifications or treated as universal caramel-color values. Likewise, an official maximum is not evidence that a supplier lot was tested at that value.
Do not solve a missing critical record by relying on a sales assurance. Record the question, owner, response, source file and approval date so the decision remains auditable after staff or suppliers change.
How Should the Checklist Feed Supplier Approval and Change Control?
Convert the completed review into an approved-material record. Link the supplier, manufacturing site, product code, class, specification revision, approved TDS, representative COA, declarations, sample-trial report and responsible approvers. Set a review trigger for document expiry, regulatory change and supplier notification.
When the supplier changes a site, raw-material source, process, product code, specification or test method, compare the new package with the approved baseline. Regulatory reviews and laboratory or formulation retesting should be proportional to the identified risk, but the decision must be written before routine purchasing resumes.
Use the general caramel-color page for the product category and the color-selection guide for class selection. Discuss your caramel-color documentation and application requirements with our technical team.
