Trusted by teams turning documents into production data
Logistics
Rate confirmations document the agreed terms for a freight move: origin, destination, rate, pickup date, and requirements. Every broker uses a different format. Sensible converts rate confirmation data into structured JSON for TMS integration, audit, and carrier payment.
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
Every broker and carrier lays out a rate con differently, and accessorial charges and multi-stop legs hide in the fine print. We map each format to one schema, so a confirmation from any partner comes back as the same structured fields.
01
Every broker and carrier generates rate confirmations with different field placement, terminology, and structure. Each gets its own SenseML configuration that maps to your TMS schema. Consistent output regardless of source.
02
Detention, lumper, fuel surcharge, TONU: accessorial charges hide in varied table formats and fine print. Each charge type gets extracted with its amount and conditions, regardless of where the document places them.
03
Pickup and delivery locations, per-stop instructions, appointment times, reference numbers: multi-stop shipments carry detail for each stop. Each stop returns as a separate structured item with its full 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 rate confirmation 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 TMS needs.
01
Shipment details
Broker name, carrier name, MC number, DOT number, BOL reference, load number, equipment type, commodity description
02
Rate and charges
Linehaul rate, rate type (flat/per mile/per CWT), fuel surcharge, detention, lumper, TONU, total rate, payment terms
03
Pickup and delivery
Origin address, origin contact, pickup date/time, destination address, destination contact, delivery date/time, special instructions
config.json
SenseML
{ /* SenseML: rate confirmation extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "total_rate", "description": "total rate, all-in rate, total charges" },
{ "id": "pickup_date", "description": "pickup date, ship date, load date" },
{ "id": "origin", "description": "origin, pickup location, ship from, origin city" },
{ "id": "destination", "description": "destination, delivery location, ship to, destination city" }
// + more fields, mapped to your schema
]
}
}
]
}Pre-built templates cover common broker and carrier formats. SenseML extraction logic adapts to each broker's layout while deterministic rules guarantee your schema compliance. New formats build on existing configs.
Full truckload (FTL), less-than-truckload (LTL), intermodal, flatbed, reefer, expedited
Major brokerages (C.H. Robinson, XPO, Echo, TQL), carrier-direct confirmations, spot market, contract freight
Answers about broker format support, accessorial parsing, and TMS integration.
Yes. Sensible captures origin and destination addresses, contact names, phone numbers, pickup and delivery dates/times, and any special instructions for each stop.
By default Sensible extracts linehaul rate, fuel surcharge, total rate, rate type (flat, per mile, per CWT), and effective dates, with accessorial charges like detention, lumper, and TONU captured separately. The rate fields are defined in configuration, so you can add or reshape them to match how your TMS books a load.
Yes. Sensible extracts each accessorial charge with its type, amount, and any conditions. Common accessorials include detention, layover, truck order not used, lumper, and fuel surcharge.
Yes. Rate confirmation formats vary by carrier and broker. Sensible's configurable extraction handles each format, pulling rates, lanes, and terms regardless of layout.
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.