Extract the supplier, item, quantity affected, severity, root cause, disposition, and corrective actions from a non-conformance report (NCR) PDF.
The full guide: Non-conformance report root cause and disposition
Need to scale? Create an API key, then run this from your own code or an agent.
Create an API keyFree account required
Upload a file or pick a sample, and see the fields come back.
No signup · nothing stored
The document number and date, the inspection date and receipt date, the supplier name and id, the buyer name and id, the purchase order number, the item inspected and its identifier, and the quantity inspected and quantity affected.
The severity level (enum, such as Critical, Major, or Minor), the disposition (enum, such as Rework, Scrap, Use-As-Is, or Return to Supplier), and the status (enum, such as Open, In Progress, Closed, or Rejected) each come back as fields, alongside the description and root cause.
Yes. A defect log table returns each defect id, description, class, quantity affected, and disposition; and a corrective action log table returns each action id, description, assignee, target date, actual date, and status.
The assigned owner, the due date, the corrective action, the inspector name, the inspection body, and the inspection location each come back as fields, so the follow-up sits next to the finding.
PDF only, up to 10MB and 100 pages. The report is processed via the Talonic API for extraction only, is not retained for training, and is not shared.
The tool reads a single document. The platform reads the whole estate once and keeps it queryable — the same engine, with a memory.
See PDF to Markdown if you run this for data and platform teams, or the extraction API if you are building it in.