Trusted by teams turning documents into production data
Logistics
Delivery orders and proof-of-delivery documents are the closing record of every shipment. They arrive as scanned faxes, photographed mobile uploads, and carrier-system PDFs. Sensible converts any DO or POD format into structured JSON for freight billing reconciliation, OS&D tracking, and TMS automation.
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
Driver signatures, exception codes, and photo-captured deliveries demand more than OCR. Sensible combines layout-aware extraction with deterministic validation against your shipment records.
01
Driver signatures, consignee stamps, and receiver initials need to be detected as present/absent before billing closes the load. Confidence scoring flags missing or ambiguous signatures for AR review.
02
OS&D codes (overage, shortage, damage) handwritten in margins or printed on carrier-specific forms get normalized to a consistent schema. Bill-back disputes get the structured data they need to resolve quickly.
03
Drivers capture PODs on phones in trailer lighting. Some come in as scanned faxes. Hybrid OCR handles low-contrast captures while deterministic rules enforce the output shape your TMS expects.
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
We configure every POD extraction to your exact schema, not a fixed field list. The fields below are the ones logistics teams pull most often — tell us what your TMS or freight-billing system needs and we map the rest.
01
Shipment headers
DO number, BOL reference, shipper, consignee, carrier, delivery date, scheduled vs. actual delivery time
02
Delivery confirmation
Receiver name, signature present, stamp present, pieces delivered, pieces signed for, weight confirmed
03
Exceptions
OS&D codes, damage description, refused pieces, late delivery reason, hold-for-pickup flag
config.json
SenseML
{ /* SenseML: delivery order / POD extraction */
"fields": [
{
"method": {
"id": "queryGroup",
"queries": [
{ "id": "do_number", "description": "delivery order number, DO #" },
{ "id": "delivery_date", "description": "delivery date, date delivered" },
{ "id": "pieces_delivered", "description": "pieces delivered, quantity received" },
{ "id": "exception_code", "description": "OS&D, exception code, damage" }
// + more fields, mapped to your schema
]
}
}
]
}Sensible processes DOs and PODs from any carrier or mobile capture source.
FedEx, UPS, XPO, Old Dominion, R+L, Estes, Saia — pre-built configurations for each carrier's POD format.
Driver-uploaded photos, scanned fax PODs, and warehouse-issued delivery orders. SenseML configures any format in hours.
Answers about POD signatures, OS&D codes, and mobile-captured delivery formats.
Yes. Driver-captured photos from trailer lighting and warehouse environments process through the same hybrid engine as scanned PDFs. OCR handles degraded captures; deterministic rules enforce the TMS-ready output shape.
Overage, shortage, and damage codes get normalized to a consistent schema regardless of how they appear on the form. Handwritten margins and carrier-specific code formats both produce the same structured output.
Yes. Driver signatures, consignee stamps, and receiver initials are detected as present or absent. Confidence scoring flags missing or ambiguous signatures so AR teams can review before billing closes.
Any carrier's. Pre-built configurations cover FedEx, UPS, XPO, Old Dominion, R+L, Estes, and Saia, and those are examples rather than the limit. Regional carriers, mobile-captured PODs, and any layout you haven't sent yet get configured in SenseML.
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.