Skip to main content

Teler for logistics

Why are deliveries running late?

Ask about on-time rates, routes, vans and returns in plain words. Teler finds the cause, shows its work and keeps an eye on every hub.

Works withPostgreSQLSQL ServerMySQLExcel and CSV

Live demoLogistics · Elena Roig, Operations manager at Port Logistics, with sample dataClick anything to look around.

Sample data

01 · Ask. In plain words, from Home or any chat.

  • Teler Cloud runs in the EU, on encrypted disks. Enterprise teams can run Teler on a dedicated machine or on their own servers.
  • Choose Standard, Zero Data Retention or European-only routing. Our AI providers never train on your data.

Analyses that repeat

Ask once. An agent keeps it running.

Three routines logistics teams hand to Teler’s agents. Each one reruns the same checked steps on its schedule and tells the team what changed.

  1. AgentActive

    Weekly hub pulse

    Does
    Tracks on-time delivery per hub and explains every drop.

    Every run

    1. Track on-time delivery for every hub.
    2. Split any drop by cause: linehaul, cut-off or sorting.
    3. Link each cause to its delivery records and post the summary.
    When
    Weekly · Monday 07:00
    Starts
    On its own

    Latest post · week 41 · Two northern hubs are below 92% on time. Late linehaul arrivals explain 71% of the drop; sorting worked as usual.

    Shared with the hub leads

    About 2 credits a run
  2. AgentActive

    Late linehaul alert

    Does
    Watches inbound linehauls every morning and flags arrivals at risk of missing cut-off.

    Every run

    1. Read inbound linehaul positions every morning.
    2. Estimate arrival against each hub’s cut-off.
    3. Flag the arrivals at risk and tell the hub leads.
    When
    Daily · 05:00
    Starts
    On its own

    Today · Three linehauls to Hub North may miss today’s cut-off.

    3 arrivals at risk · sent to Hub North

    About 2 credits a run
  3. AgentActive

    Returns watch

    Does
    Reports returns by reason and client every week.

    Every run

    1. Group last week’s returns by reason, region and client.
    2. Compare them with the previous four weeks.
    3. Post the summary for the returns team.
    When
    Weekly · Monday 08:00
    Starts
    On its own

    Last run · Returns up 22% in the south; size exchanges explain most of it.

    Completed Monday

    About 2 credits a run

Agents run only after you save them. Each run shows its steps, so you can check what changed and why.

Dashboards

Dashboards that keep themselves up to date.

Pin any answer to a dashboard. Teler refreshes it on the schedule you set, so the whole team opens the same numbers.

Hub operationsOn-time rate, volumes and cut-offs for every hub.Updated 2 minutes ago
On-time delivery · this week91.4%−2.1 pts vs last week
Parcels · this week182k+6% vs last week
On-time rate per dayActualForecast, with its range
Late arrivals by hub · this week
  • Hub North214
  • Hub Girona173
  • Hub Centre64
  • Hub South36
Refreshes every hourShared with the teamSample data
  • Hub operationsOn-time rate, volumes and cut-offs for every hub.5 widgets · updated 2 minutes ago
  • Carrier performanceDelays and damage by carrier and route.4 widgets · updated 1 hour ago
  • ReturnsReturns by reason, region and client.6 widgets · updated yesterday · shared with you

Ask it your way

Questions logistics teams ask.

Type them as you’d say them. Teler picks the method, runs it and shows its steps. The answers below are samples.

01 · Routes

“Which linehaul routes arrive late most often?”

Sample answerTwo northern routes cause most late arrivals. Both cross the same motorway works until November.

02 · Vans

“How full are our vans by depot?”

Sample answerVans leave Depot East 61% full on average. The other depots are above 70%.

03 · Returns

“Which products are exchanged most?”

Sample answerFootwear accounts for 58% of exchanges, mostly half sizes from one client’s new collection.

Also askedFind late-delivery causesCompare routes and carriersFill vans betterUnderstand returnsForecast volumesWatch every hub

Your data stays yours

Built for sensitive logistics data.

  • EU cloud or your serversTeler Cloud runs in the EU on encrypted disks. Enterprise teams can run it on their own servers.
  • Only what you authorize reaches the AIOur AI providers never train on your data.
  • Your systems stay untouchedTeler works on its own synced copy of the data you choose, never on your production databases.

Questions

Before you start.

Not covered here? Ask us, or check whether Teler fits your team.

Can Teler use our transport and warehouse data?

Teler connects to PostgreSQL, MySQL and SQL Server databases and reads CSV and Excel exports. If your transport or warehouse system can export to one of these, Teler can work with it.

Is our operational data safe?

Teler Cloud runs in the EU on encrypted disks, and only what you authorize reaches the AI model. Teler works on its own synced copy of the data you choose and never runs on your production databases. Enterprise teams can run Teler on their own servers.

Can hub managers use it?

Yes. Hub managers, planners and customer teams ask in plain words and get charts and tables they can check.

Can it watch the hubs every week?

Yes, once you save it as an Agent. A weekly pulse can check on-time rates for every hub and post the causes to your team.

See what your logistics data can tell you.

Start free with an Excel or CSV export. Connect a database when you’re ready.