How it works

From scanned BOL to structured data

Upload a bill of lading, extract a defined set of fields with per-field confidence, review flagged exceptions, and export approved data as a structured file for import into your existing systems — the interactive tour below walks through each step.

The three-step loop

One product. One loop. Repeatable on every document you receive.

Tap a step to read more. On larger screens, all three open side by side — the highlight auto-advances until you take over.

Step 1 · Upload

Drop a bill of lading (BOL).

PDFs, photos, or scans — encrypted in transit and at rest. We never train on your data. Uploaded documents are accessible only to your account and are automatically deleted after 24 hours.

  • PDF, PNG, JPG
  • Drag-and-drop upload
  • Bills of lading (first cycle scope)

Built for the people closest to the load

The capability set, on one page.

Each card is one lever Linerayl pulls on its own — together they reduce repetitive manual BOL data entry alongside your existing team.

Per-field confidence scoring

Every captured field comes back with a score. The exception queue surfaces rows under threshold so review goes from "every line" to "the fields that need a human".

Built-inreview layer

BOL-aware schema

Shipper, consignee, line items, weights, charges, references, signatures. Linerayl knows the freight document, not just the page.

BOLfirst-cycle scope

Structured file export

After explicit human approval, export approved data as CSV, JSON, or XML for import into your TMS or other systems — no middleware vendor required.

3export formats

Exception queue

Low-confidence rows pool into a single review surface with side-by-side document and field. Reviewers approve or correct before anything moves downstream.

Humanapproval required

Full audit trail

Every change is captured with the actor, timestamp, prior value, and reason. Finance, ops, and compliance share a single timeline they can each trust.

Fullchange-level traceability

Multi-format ingest

PDF, photo, or scan — the same BOL workflow handles whatever shape the document shows up in.

PDFPNG · JPG
Before / After

Drag to see the difference for yourself

Left: the world without Linerayl. Right: the world with it.

142 docs

processed by lunch

~30s per BOL

structured extraction

Exception queue

review flagged fields

Friday at 4pm

clerical burden down

Auditable export

CSV / JSON / XML

Without Linerayl
With Linerayl

Drag the handle to compare both sides.

Security architecture

Where your data goes — and what guards it

Freight documents contain sensitive shipper, consignee, and rate data. Linerayl is built assuming yours is too.

  1. 1

    Upload

    TLS 1.3 in transit

  2. 2

    OCR

    Sandboxed extraction

  3. 3

    AI structuring

    No training on your data

  4. 4

    Storage

    Encrypted at rest

Encryption end-to-end

TLS 1.3 in transit and AES-256 at rest, applied uniformly to documents, extracted fields, and audit logs.

Token-based auth

JWT access + refresh with short-lived tokens, bcrypt-hashed credentials, and least-privilege database roles.

Your data, not ours

We never train models on your documents. Uploaded documents are accessible only to your account and are automatically deleted after 24 hours.

Defense in depth

Parameterized queries, strict file validation, sandboxed extraction, and a fast incident-response loop.

SOC 2 Type IIin progressISO 27001in progressGDPR alignedEncrypted at restTLS 1.3 in transit

Ready to get started?

Book time with our team for a walkthrough scoped to your BOL workflow and export needs.

Schedule a DemoOr try it free first