Trusted by teams turning documents into production data
Logistics
Waybills document the movement of goods by air, ocean, or ground. Each transport mode has its own format with mode-specific fields for routing, charges, and cargo detail. Sensible converts waybill data into structured JSON for shipment tracking, customs, and freight audit.
Validated JSON
Schema-enforced output; every field matches your contract
Source coordinates
Every value links back to page + bounding box for audit
Per-document pricing
Predictable cost. No token-volatility surprises
Trusted by teams turning documents into production data
Air, ocean, and ground waybills each follow their own standard, and consolidation and multi-leg routing add more structure to untangle. We read each mode and return one consistent schema across all of them.
01
IATA air waybills have flight numbers and airport codes. Sea waybills reference vessel names and port pairs. Ground waybills list trailer numbers and terminal codes. Each mode gets mode-specific field extraction through dedicated SenseML configs.
02
House waybills nested under a master waybill, a common freight forwarding structure. Both levels are processed with the parent-child relationship preserved, critical for consolidation reconciliation and carrier settlement.
03
Waybills for multi-leg shipments encode routing through multiple ports and airports with carrier codes, vessel or flight numbers, and ETAs in compact fields. The sequential relationship between legs is implied by field ordering, not explicitly structured. Sensible extracts each leg with its full routing detail.
Managed services
Solutions engineers handle plan, build, deploy, and adjust on your behalf. You see clean JSON in your API response. Same engine as self-serve, just with the configuration work outsourced.
What's included
01Plan.Engineers review your samples and pick the right method
02Build.SenseML configs written from your samples
03Deploy.Same engine as self-serve, ready for production
04Adjust.We update configs when formats shift or new edge cases appear
05Integrate.Help with custom integration into your downstream systems
Every waybill is different, so we build the config around your exact schema rather than a fixed list. These are the fields logistics teams request most; we map whatever else your freight-management system needs.
01
Routing
Origin airport/port, destination airport/port, intermediate stops, carrier code, flight/voyage number, departure date, arrival date
02
Cargo
Number of pieces, gross weight, chargeable weight, volume, dimensions, commodity description, HS tariff code, declared value
03
Charges
Freight charges, valuation charges, taxes, other charges due agent, other charges due carrier, total, prepaid/collect indicator
config.json
SenseML
{ /* SenseML: waybill extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "waybill_number", "description": "air waybill number, AWB number, waybill #, B/L number" },
{ "id": "origin", "description": "airport of departure, port of loading, origin" },
{ "id": "destination", "description": "airport of destination, port of discharge, destination" },
{ "id": "chargeable_weight", "description": "chargeable weight, billable weight, weight" }
// + more fields, mapped to your schema
]
}
}
]
}Sensible processes air waybills, sea waybills, and ground waybills. Hybrid extraction handles mode-specific conventions while deterministic rules enforce consistent output for your logistics pipeline.
Air waybills (AWB/HAWB/MAWB), sea waybills, ocean bills of lading, ground carrier waybills, multimodal waybills
IATA standard AWB, FIATA multimodal, carrier-specific formats, freight forwarder house documents
Answers about mode-specific extraction, consolidation handling, and weight/dimension parsing.
Freight charges, valuation charges, taxes, other charges due agent, other charges due carrier, and total charges are extracted by default, with prepaid and collect designations captured. The charge fields are defined in configuration, so you add ones specific to your lanes or carriers when a waybill carries something not already mapped.
Yes. Gross weight, chargeable weight, volume, number of pieces, dimensions per piece, and unit of measurement come back, in both metric and imperial. These are the common weight and dimension fields, not a closed set. What gets extracted is defined in configuration and shaped to your schema.
Origin, destination, intermediate stops, carrier codes, flight or voyage numbers, departure and arrival dates, and routing instructions come back by default. Routing data varies by mode and carrier, so these are examples rather than a fixed list. The fields are defined in configuration and extended when a waybill carries routing detail you don't see here.
Yes. Air waybills (AWB), ocean waybills, and ground waybills all run today, each with a configuration that pulls mode-specific fields like flight number, vessel name, or trailer number. These are the variants built so far. When you bring a waybill format Sensible hasn't seen, a configuration is built to fit it.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
Start free
Free 14-day trial. No credit card required. Start extracting in minutes.