Foxello reads bills of lading from any carrier - ocean, straight, commodity, sea or air waybill - and returns structured shipment data in seconds. No templates, no per-carrier setup.
BPO Mode for freight operators: Run a full BOL processing operation with your validation team. Route uncertain extractions to reviewers automatically - process thousands of BOLs per day.
A bill of lading from one carrier looks nothing like one from another - different fields, different layouts, sometimes a different language. Freight teams re-key the same handful of facts - parties, ports, containers, weights - out of every one of them.
Foxello reads BOLs from any carrier without a template, so a new carrier or a new trade lane doesn't mean configuration work. Multi-container manifests come back as one continuous table, not split page by page.
Every field gets its own confidence score, and uncertain values - a smudged container number, an unclear weight - go to Review Hub instead of flowing straight into your TMS or customs platform.
Documents are processed and stored in the EU and never used to train models.
Fixed-layout parsers break whenever a carrier changes a form. A better approach is to describe the fields you need in plain language and let the model find them by meaning, wherever they appear on the page. That is how Foxello works, so container numbers, parties, and commodity lines come out correctly even when the layout changes.
Yes. In Instinct or Mastery workflows you list the fields you want, in your own words, once in the workflow editor. There is no schema file to hand to engineering. If two carriers differ too much for one field list, run a separate workflow for each.
Yes. Ocean, domestic straight, and commodity bills of lading, as well as sea and air waybills, all go through the same workflow. You choose the fields per workflow, so each document type can have its own list.
Line items are extracted as a table field. You define the columns once - for example container number, commodity description, weight, and package count - and every row is returned in that structure, even when the source lists it as a paragraph instead of a table.
A custom parser means template upkeep for every carrier and silent failures when a form changes. Foxello needs no templates and no engineering time, scores every field, and sends only uncertain values to your reviewers. You can also use the REST API if you need to build it into your own product.
Yes. Documents can arrive by email, upload, or API, run without manual steps, and only low-confidence fields go to Review Hub. Plans scale with volume, and Review Hub supports multiple reviewers, each working on separate files - a file is locked to one reviewer while it is open.
JSON, CSV, and Excel, plus webhooks, a REST API, Zapier, and n8n. You can map extracted fields to the keys your TMS or customs platform expects.
In the EU. Documents are processed and stored on EU infrastructure and are never used to train models.
Parse air waybills, commercial invoices, and packing lists from every shipper and carrier into structured data - so bookings, customs filings, and billing start from data, not retyping.
Turn ocean bills of lading, cargo manifests, and bunker delivery notes into structured data - containers, ports, parties, and quantities - through a REST API or a simple upload.
Extract tariff codes, values, origin, and party details from commercial invoices, entry summaries, customs declarations, and certificates of origin - so filings start from structured data.
Foxello reads purchase orders from any supplier and returns structured data ready for matching and approval.
Foxello reads any invoice - standard or non-standard, digital or scanned - and returns perfectly structured data in seconds.
Start extracting BOL data in minutes. Works with any carrier format.
Try free - no setup required