What must a Xometry Certificate of Conformance include?
The live job controls, but a useful CoC preflight should verify the issuing organization and approval, customer or Xometry part identity, drawing revision or an explicit N/A when appropriate, shipped quantity, serial-number declaration when applicable, purchase-order reference, material and process specifications, and the heat or lot references needed to connect every supporting certificate.
Treat the CoC as the packet index
The CoC should let a reviewer connect the released parts to the order and to the supporting inspection, material, and special-process evidence. A field appearing somewhere else in the packet does not automatically cure an ambiguous or contradictory CoC.
Normalize harmless formatting differences, but do not silently rewrite meaning. For example, “30400115_SW_EAR_RB” may be a supplier or file identifier rather than the controlling customer part number. “30 30” is not a defensible quantity until the source is reviewed and the intended value is clear.
- Issuer legal or business name, certificate date, and authorized approval.
- Customer/Xometry part number and any supplier part number clearly labeled.
- Drawing revision, or N/A only when the job legitimately has no applicable drawing revision.
- Shipment quantity and serial numbers, range, or a clear non-serialized declaration.
- PO or job reference and an unambiguous conformity statement.
- Material, finish, heat-treatment, hardware, and special-process specifications that apply.
- Heat, melt, batch, or lot identifiers matching the source records.
Cross-check, do not merely extract
Compare each critical field with the PO, inspection report, drawing, packing record, material certificate, and process certificate. A value is verified only when the packet’s controlling records agree or a documented, authorized exception explains the difference.
For material traceability, Xometry’s public guidance describes an unbroken ownership chain carrying the same heat lot or material lot through the mill or manufacturer records, transfers, packing slips, and CoCs. A CoC that names the material but loses the lot reference is not complete traceability.
What software should report
A checker should show the exact file and value that caused the exception, distinguish “not found” from “conflict,” and avoid claiming a missing revision when the authorized requirement is genuinely N/A. It should also collapse duplicate OCR tokens rather than presenting an uncertain quantity as though it were two separate quantities.
The reviewer still decides whether the evidence satisfies the live contract. Software can expose the mismatch; it cannot invent an approval or cure a source record.
Check the controlling information yourself
These outside references support the answer above. Open the current page and compare it with the requirements shown on your specific job.
Short answers quality teams can use
Can the revision be N/A?+
Yes when no drawing revision legitimately applies and the live requirement permits it. N/A should be explicit and should not be used to hide a missing controlled revision.
Is a duplicated quantity like “30 30” acceptable?+
It is ambiguous. Review the source layout or OCR, determine the intended shipped quantity, and correct the certificate or extraction before release.
Does the partner CoC replace material certificates?+
Not when the job requires source material or process evidence. The CoC should connect to those records; it does not manufacture the missing traceability.
Continue the packet review
VQC Checker is independent software and is not affiliated with, sponsored by, or endorsed by Xometry. This is general operational information, not customer approval, legal advice, export-control advice, or a substitute for qualified inspection.