Automate shipment document intake
Unstract reads the label, packing list and bill of lading on every inbound shipment, checks them against the ASN and the open PO, and posts the receipt to your WMS or ERP before the pallets leave the dock.
Trusted by logistics and supply chain teams around the globe
The truck is at the door and the paperwork is in four places
The ASN already sits in your WMS. The rest arrives with the freight: a label photographed at the dock, a packing list in the shipper's email, a BOL faxed by the carrier. A receiving clerk keys it all while the next trailer waits for the door.
Packing list lines keyed by hand before the next appointment
A faxed BOL, skewed, with a stamp across the weight
A carton count that doesn't match the ASN
A packing list that reached the dock after the truck did
The same shipment received twice, stock counted double
Every document has to be read, matched to the ASN and the PO and keyed into the WMS before a single carton can be put away.
Unstract reads every document on the shipment as it arrives, checks the counts against the ASN and the open PO, and posts the receipt. A receiving clerk sees only the shipments that don't add up.
From the receiving dock to the WMS, without the keying
Four steps, run on their own for every shipment. Parsing by LLMWhisperer, extraction by Document Studio, the whole run by Flow.
Pick up the shipping paperwork wherever it lands
The label is photographed at the dock, the packing list comes in the shipper's email, the carrier faxes the BOL, and the ASN is already in your WMS. Each one is picked up where it arrives and tied to the same shipment, so one record holds every document for that delivery.
Nobody has to find the packing list in an inbox while the driver waits at the door.
Read every label and packing list, then pull the fields that matter
LLMWhisperer reads each document as text with its layout kept, so a crooked label photo or a faxed BOL comes out as cleanly as a PDF from the shipper. Document Studio then extracts the fields you defined: carrier, tracking number, PO number, SKU lines and quantities, weights and seal numbers, from every document on the shipment.
The same field definitions run on every shipper's packing list, whatever its layout.
Check every count against the ASN and the PO before anyone touches it
Packing list quantities are checked against the ASN line by line, the PO on the label against the open PO in your ERP, and the BOL against what the driver presents. A shipment that agrees keeps moving. One that doesn't stops in a review screen with the packing list, the ASN and the PO side by side.
The run stops for a receiving clerk on a short quantity, a PO that isn't open or a low-confidence read, and on nothing else.
Post the receipt where the receiving team already works
The receipt lands in your WMS, such as Manhattan Active WM or Blue Yonder. The carrier record goes to your TMS, such as Oracle Transportation Management or SAP Transportation Management, and the received lines post against the PO in your ERP, such as NetSuite or SAP S/4HANA. A clerk's count and decision are recorded against the shipment.
Stock is available to put away as soon as the receipt posts, and nobody keys the same shipment twice.
Watch it receive a day of your inbound shipments.
Send the labels, packing lists and BOLs from one dock door. You see every field read, every count checked against the ASN and every shipment that stops for a clerk.
Everything that arrives with an inbound shipment
Documents
- Bills of lading
- Packing lists
- Delivery notes
- Shipping labels
- Air waybills
- CMR documents
- Cargo manifests
- ASNs and open POs from your WMS and ERP
Fields captured
Our agents are extroverts.
Cloud storage like S3, Google Drive, Dropbox and Box. Databases and warehouses like Snowflake, BigQuery, Postgres and SQL Server. Accounting, ERP and CRM systems like QuickBooks, Xero, SAP, NetSuite, Salesforce and HubSpot. Project trackers like Jira, Asana, ClickUp and Linear. And anything with an API.
Live on one dock door first
No developers on your side and no change to how the dock runs. The intake is built on your own shipping paperwork and proven at one door before the other doors follow.
Book a consultation
We go through a day of inbound shipments with you: which shippers and carriers send what, how each document reaches the dock, and what a clerk checks before a receipt posts.
Built on your documents
The fields, the checks against your ASNs and open POs, and the connections to your WMS, TMS and ERP are set up on your own labels and packing lists, not samples.
Pilot on one door, then roll out
One dock door runs live within days. When the counts hold, the other doors and sites join, and the hold rules carry over.
Built for the people who receive the freight
Receipts post while the trailer is still at the door, and only the short counts and closed POs reach a clerk's screen.
Every client's packing lists and ASNs read the same way, each client with its own hold rules and its own WMS.
Bill of lading automation across every supplier's carrier, so received quantities reach the ERP the day the freight lands.
Shipping document AI that reads the marketplace and carrier labels on returns and inbound stock without anyone keying them.
Receipts posted at the door, short counts caught before put-away
Your inbound paperwork stays yours
Packing lists and bills of lading name your suppliers, your customers and their delivery addresses, the SKUs and quantities on each order, and the seal number on each trailer. Together they map who supplies you, what ships and where it goes.
- Encrypted in transit and at rest.
- Shipping documents and receipts are never used to train models.
- Access by role, site and document type, with every count and correction recorded against the shipment.
- Retention you set: processed labels and packing lists are deleted on your schedule.
- Self-hosted deployment for warehouse operators whose controls keep document processing inside their own network.
What receiving managers ask before they start
Bills of lading, packing lists, delivery notes, shipping labels, air waybills, CMR documents and cargo manifests, as PDFs, faxes, scans or phone photos taken at the dock. The ASN and the open PO come from your WMS and ERP, and you can add any other paperwork that travels with a shipment.
Freight document processing needs three things: something that reads faxes and label photos without losing the layout, something that pulls the same fields from every shipper's format, and something that checks those fields against the ASN and the PO and posts the result. Unstract covers all three: LLMWhisperer reads, Document Studio extracts, and Flow runs the checks and posts the receipt.
Start from the run your receiving team already follows: capture the documents, read them, check them against the ASN and the PO, and post the receipt. Describe that run in plain language and Flow's agents build the workflow from it. You review the spec, approve it, and it runs the same way on every shipment, stopping only where you told it to.
Unstract reads each BOL as it arrives, by fax, email or scan, and extracts the carrier, BOL number, PO, piece count, weight and seal number. It checks the BOL against the shipment record and what the driver presents, then sends the carrier record to your TMS. A BOL that doesn't match stops for a receiving clerk.
Yes. LLMWhisperer turns each label, packing list or BOL into text with its layout kept, including handwriting and stamps. Document Studio then extracts the fields you defined, each with a confidence score, and Flow's agents act on them: checking counts, holding exceptions and posting receipts. A low-confidence read waits for a person instead of posting.
The WMS stays as it is. Unstract reads the ASN and the open PO from the systems you run and writes the receipt back to them, so the receiving screens your team uses don't change. Only the keying goes away.
The shipment stops in a review screen with the packing list line, the ASN line and the PO side by side, and the page each value was read from. A receiving clerk recounts, accepts the shorter quantity or refuses the line, and the decision is recorded against the shipment. Every other shipment keeps moving.
The receipt goes to your WMS, the carrier record to your TMS and the received lines to your ERP. Teams send them to Manhattan Active WM, Blue Yonder, Oracle Transportation Management, SAP Transportation Management, NetSuite or SAP S/4HANA, among others. Flow posts each one as part of the run.
Unstract is SOC 2, ISO 27001, GDPR and HIPAA compliant. Shipping documents are encrypted in transit and at rest, never used to train models, and kept only as long as you choose. Self-hosted deployment keeps processing inside your own network; see the Trust Center.
No developers are needed. In a consultation we build the intake around your own shipping paperwork, your hold rules and your systems, run it at one dock door, and most teams are live there within days. The other doors follow when the counts hold.
Bring a day of inbound paperwork to the consultation
Labels, packing lists and BOLs from one dock door, the faxed ones included. You watch each shipment get read, checked against its ASN and received.