Data scattered across systems
TMS, WMS, telematics, fuel cards and spreadsheets never quite line up, so every report starts with a manual stitch.
Industries / Logistics
Agentic BI for LogisticsThe agentic BI platform for logistics teams. Your AI analyst investigates late deliveries, fuel burn and lane margins across your TMS, WMS and telematics data. Every number cited, never guessed.
No credit card · 14-day team trial
Question
Why is on-time delivery dropping this month?
On-time delivery by hub%
Root cause
Denver loses 3.8 hrs per route to dock detention at two shippers — and 61% of its late drops start there.
60s
to connect your database and start asking
100%
of numbers cited to a query that ran
24/7
monitoring on the lanes and KPIs you put on watch
Dispatch, telematics, fuel cards and carrier invoices each tell part of the story. Spotting that a number moved is easy. Knowing why takes an analyst a week — by which time the shipments are long gone.
TMS, WMS, telematics, fuel cards and spreadsheets never quite line up, so every report starts with a manual stitch.
On-time rate is down two points. Is it the carrier, the dock, the driver, the weather or the lane? Nobody can say quickly.
Cost per km creeps up, idle time hides inside route averages and exceptions surface only at month-end.
Revenue per lane is easy. Fully loaded margin after fuel, detention, claims and empty miles is not.
Accessorials, re-bills and rate mismatches get paid because nobody has time to check every line.
Static exports are out of date the moment they’re emailed, and two reports rarely agree on the same KPI.
No SQL, no ticket to the data team. SchemaChat does the heavy lifting.
Four real-world questions, answered the way SchemaChat answers them: the number, the why, and a chart of what it found.
Ask
Why did on-time delivery fall to 91% last week?
SchemaChat
On-time delivery fell from 95.2% to 91.0%. Three-quarters of the drop sits in two lanes out of the Denver hub.
Root cause
Dwell time at two shippers rose from 1.1 to 4.9 hours, which pushes 61% of late drops past their window.
Ask
Which vehicles are driving up our cost per km?
SchemaChat
Fleet cost per km is $1.42, up 6.1% in 8 weeks. 14 of 212 vehicles account for 38% of the increase.
Root cause
The outliers are all older diesel units on short urban drops, idling an average of 2.6 hrs per shift.
Ask
Which lanes lose money after empty miles?
SchemaChat
9 of 64 active lanes run at negative contribution margin once deadhead and detention are included.
Root cause
Seven of the nine are one-way backhaul gaps: the lane is priced as if the truck returns loaded.
Ask
Are any carrier invoices out of line with contracted rates?
SchemaChat
212 invoice lines across 6 carriers exceed contract rate, totalling $48,300 above agreed terms this quarter.
Root cause
Fuel-surcharge tables are out of date for two carriers, and 41 detention charges have no supporting scan.
From the dispatch desk to the CFO, the same governed numbers answer every team.
OTIF · Dwell time · Late-stop reasons
See where, when and why deliveries miss their window, and which customers, carriers or docks cause it.
Cost / km · Idle % · MPG / L per 100 km
Cost per km, idle waste and consumption trends across every vehicle, driver and depot.
Margin · Deadhead · Revenue
Fully loaded margin per lane, including empty miles, detention and claims, so pricing follows reality.
Dock turn · Pick rate · Dwell
Spot dock congestion, pick-rate dips and dwell build-ups before they delay outbound trucks.
Carrier score · Invoice variance · Claims
Score carriers on service and cost, and catch invoice lines that don’t match contract.
Volume / lane · Utilisation · Seasonality
Understand volume patterns by lane and season so capacity is booked before it gets expensive.
Try it: click a hub on the map.
Hubs & lanesColour = on-time rate
Cost per km by depot
On-time delivery, last 12 weeksNow 93.4% · was 95.1%
SchemaChat reads the database your logistics systems already feed. There’s no new tracking to install and no data to re-enter.
Your database read-only
SchemaChat reads from
Read-only, credentials encrypted.See all integrations →
SchemaChat connects to the database your systems write into: PostgreSQL, MySQL, BigQuery, Snowflake or MongoDB. If your TMS, WMS or telematics data lands in one of those, or in a CSV export, you can start asking questions straight away.
No. You ask in plain English. SchemaChat writes and runs the queries, and shows the exact SQL behind every answer, so your data team can check it any time.
Yes, if the tables are in the same connected database, SchemaChat can join them. For example it can link fuel-card transactions to telematics idle events by vehicle and date, and define the join once as a governed metric.
Every figure comes from a query that actually ran, with the step behind it cited. If the data isn’t there to answer a question, SchemaChat says so rather than guessing.
All AI queries are SELECT-only, enforced at the SQL parser layer, so SchemaChat cannot modify or delete your data. Database credentials are encrypted at rest with AES-256-GCM.
Yes. Put any finding on watch, for example on-time delivery on a lane or cost per km for a depot, and you’ll be alerted when it crosses a threshold, along with a digest of what changed.
Yes. The REST API lets you ask questions, run read-only queries and pull charts from your own backends, Slack bots and automations using a Bearer token.
The 14-day team trial lets you connect your own database (read-only) or upload CSVs, run deep analyses and build dashboards, with no credit card and up to 3 seats. After the trial, Premium and custom plans for larger teams are on the pricing page.
Connect a database or upload a CSV of recent shipments and ask your first question in about a minute.