Extract data from product specifications
Unstract reads finished product specifications, supplier spec sheets and datasheets, as PDFs or scans, extracts every attribute with its tolerance and sends the checked record to your ERP or MES.
body length ±0.3 — our drawing says ±0.2, ask Brandt
PDS-4471 REV C · SUPERSEDES REV B · PAGE 1 OF 3
{ "supplier": "Brandt-Cove Sensing", "part_number": "CS18-PNP-08N", "revision": "C", "supersedes": "Rev B", "body_length_mm": 60, "length_tol_mm": 0.3, "housing_material": "Stainless steel 316L", "operating_temp_c": "-25 to +70", "supply_voltage": "10-30 V DC", "compliance_marks": "CE, UL Listed, RoHS, IP67", "approved_by": "R. Okafor", "confidence": 0.94}
Trusted by manufacturing and quality teams around the globe
Each supplier writes its spec sheet its own way
A clean datasheet PDF from the supplier's website is the easy case. Engineering inboxes fill up with these.
Printed, marked up at the line, then scanned back in
Three suppliers, three names for one temperature range
A tolerance crossed out and rewritten during review
Data sheet, drawing, compliance declaration and product information form in one file
A configuration report with every variant on its own row
An engineer keys each attribute into the item master by hand and compares every tolerance with the drawing, so a new part waits weeks before planning can schedule it.
Unstract reads each spec sheet in the supplier's own layout, pulls every attribute with its unit and tolerance, compares them with your specification and sends the record to your ERP or MES.
Parse, extract and check product specifications on one platform
Read the spec sheet, turn every attribute into data, then run the revision check around it. Each product works alone, and the three together run the whole release.
Parse every product specification with its attribute tables intact
Capture the full text of a finished product specification, a supplier datasheet or a product information form, whether it arrived as a vector PDF or a marked-up scan. Attribute tables keep their rows: a tolerance stays beside its own dimension, a unit stays beside its value, and a rating in a footnote is read with the line it qualifies.
Send the text to your own LLM, or make parsing the first step of a spec review workflow.
Learn more about LLMWhispererAI specification extraction that checks each product specification against yours
Name the attributes you track for each product family, and every spec sheet comes back in one JSON structure, whether the supplier writes "OP TEMP", "ambient" or "T oper". Each value carries its unit and tolerance, so a band that is looser than your drawing, a missing rating or a revision newer than the one on file arrives flagged with the reason.
Call it as an API from your PLM, run it as an ETL pipeline from an engineering inbox or shared folder, or make it one step in an orchestrated release.
Learn more about Document StudioRun the spec review from supplier email to item master
Describe your product specification review in plain English and Flow's agents build the workflow. Spec sheets are picked up from engineering or supplier inboxes, each one is read, every attribute is compared with the current revision on file, and any change is marked line by line. Approved data goes to your ERP or MES. You approve the workflow once, and it runs the same way on every spec sheet.
Set the points where a manufacturing engineer steps in: a tolerance wider than your drawing, a new revision, a missing compliance mark, a material substitution. Only those parts stop, with the old and new values side by side. Unstract reads and compares; your engineers still release the part.
Learn more about FlowRead your spec sheets today. Run the full review when you're ready.
Start for free to parse and extract your own product specifications now. Automating the spec review begins with a consultation.
Product specifications, datasheets and the forms that travel with them
Documents
- Finished product specifications
- Supplier specification sheets
- Product data sheets
- Technical datasheets
- Product configuration reports
- Product information forms
- Material specifications
- Packaging specifications
- Customer product specifications
- Specification change notices
- RoHS and REACH declarations
- Drawing title blocks and notes
Fields captured
Processes these specifications feed
For the teams that release parts into production
New parts reach the item master with every attribute filled in, so routings and schedules don't wait on someone keying a datasheet.
Each supplier spec compared with your drawing, with the looser tolerance or the changed material named before the part is released.
Revisions tracked part by part, so the line builds to the current spec and an outdated sheet never reaches the floor.
Customer specifications turned into one structured record per product, ready to load into your ERP or MES before the first run is quoted.
Parts released sooner, fewer spec mismatches
Unreleased designs and supplier specs stay private
A product specification can describe a part that hasn't launched yet, and a supplier's spec sheet shows its materials and tolerances. An unreleased design in the wrong hands gives away your next product, and a leaked supplier spec breaks the confidentiality terms you signed.
- Encrypted in transit and at rest.
- Product specifications are never used for model training.
- Access by role, plant and product line, with every correction and approval recorded against the part.
- You set retention: spec sheets are kept as long as your document control requires, then deleted.
- Self-hosted deployment for manufacturers that keep product designs inside their own network.
What engineering and production teams ask before they start
Send the PDFs to Unstract from an engineering inbox, a shared folder or an API call. LLMWhisperer reads each one with its attribute tables intact, and Document Studio returns the part number, revision and every attribute with its unit and tolerance as JSON, ready for your ERP or MES.
It reads a specification the way an engineer does: it finds each attribute by what it means, not where it sits on the page. Document Studio uses LLMs to map "OP TEMP", "ambient" and "T oper" to the same field, so specs from different suppliers land in one schema.
A datasheet extraction tool should keep each value beside its unit and tolerance, read scans as well as clean PDFs, handle a new supplier's layout without a template, and show where on the page each value came from. Unstract does all four, and it compares the result with your own spec before anyone loads it.
Yes. Rows and columns stay intact through parsing, so a dimension, its nominal value and its plus and minus limits come back together. Split tolerances and footnoted ratings are read with the line they belong to.
Yes. You give it your drawing values or the revision on file, and every extracted attribute is compared with them. A wider tolerance, a changed material or a missing rating comes back flagged with both values.
Most specification extraction software stops at pulling text into a spreadsheet. Unstract returns a structured record in your schema, checks it against your current revision, and can run the full review through Flow, with an engineer stepping in only on exceptions.
Yes. A configuration report with one row per variant comes back as one record per SKU, and a product information form is read field by field, checkboxes included.
Yes. LLMWhisperer reads long specification documents with their section numbering and tables kept, and Document Studio pulls the products, materials and performance values you name.
No. Unstract reads the spec and compares it with yours. Your engineers approve the part, and values reach your ERP or MES only through the workflow you approved.
Yes. Document Studio deploys an endpoint per document type: POST a spec sheet and get the attributes back as JSON. A backlog of supplier datasheets can run through the same extraction as a folder-to-database pipeline.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Spec sheets are encrypted in transit and at rest, never used to train models, and kept only as long as you set. Teams that keep designs on their own network can self-host; see the Trust Center.
Bring the spec sheets for your next part release
Supplier datasheets, product information forms and your own drawings. We read them together in the session and point out every attribute that differs from your spec.