Extract waybills to structured JSON
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 extracts waybill data into validated JSON for shipment tracking, customs, and freight audit.
Why waybills need mode-specific extraction
Air, ocean, and ground waybills follow different standards. Consolidation adds another layer.
IATA air waybills, sea waybills, and ground waybills use different layouts. Sensible detects the type and applies mode-specific logic.
Forwarders issue house waybills under a master waybill. Sensible processes both and links them when both are available.
Waybills report gross weight, chargeable weight, volume, and piece count in metric or imperial. Sensible extracts and normalizes units.
Fields we extract
Extract any data you need from waybills into your desired output schema
Origin airport/port, destination airport/port, intermediate stops, carrier code, flight/voyage number, departure date, arrival date
Number of pieces, gross weight, chargeable weight, volume, dimensions, commodity description, HS tariff code, declared value
Freight charges, valuation charges, taxes, other charges due agent, other charges due carrier, total, prepaid/collect indicator
Non-negotiable ocean shipping document used when no title transfer is needed.
IATA standard air waybill for international and domestic air cargo shipments.
Freight forwarder-issued waybill consolidating multiple shipments under one master.
Supported waybill types
Common waybill formats can be found in Sensible's logistics template library. Air, ocean, and ground variants can be custom configured within a couple of hours.
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
Common Questions
Details on waybill extraction across transport modes.
Yes. Sensible extracts freight charges, valuation charges, taxes, other charges due agent, other charges due carrier, and total charges. Prepaid and collect designations are captured.
Yes. Sensible captures gross weight, chargeable weight, volume, number of pieces, dimensions per piece, and unit of measurement. Both metric and imperial units are handled.
Sensible captures origin, destination, intermediate stops, carrier codes, flight or voyage numbers, departure and arrival dates, and routing instructions.
Yes. Sensible processes air waybills (AWB), ocean waybills, and ground waybills. Each variant has a tailored configuration that extracts mode-specific fields like flight number, vessel name, or trailer number.
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.
Documents are deleted after 30 days by default. You can configure shorter retention periods or request immediate deletion via API.
Yes. Sensible offers a free tier with 50 documents per month. 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 PDF, PNG, JPG, and TIFF files. PDFs can be native or scanned.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence scoring.
Most documents process in 2 to 10 seconds depending on complexity and page count.