Concepts

Each heading explains one word from the panel. The ? button in the panel goes to one of these headings.

ETA window

The customer sees a range of minutes, not a single minute. The more certain the GPS and the slower the traffic, the narrower the window. One number on the tracking page would suggest an accuracy that does not exist, and would worry the customer when the minute moves.

An API quote (POST /api/v1/quotes) returns the same as minMinutes and maxMinutes, with guaranteed: false. A partner who shows one number changes the meaning of the ETA window, not just its look.

flowchart TD
  q["API quote, before there is an order"] --> sum["prep + load + travel + pad"]
  sum --> win["Minute window, guaranteed false"]
  live["Order on the way"] --> need{"GPS position and point B"}
  need -->|"either missing"| none["No ETA, page still lives"]
  need -->|"both present"| route{"Google route"}
  route -->|"key and response"| road["Road time"]
  route -->|"missing or error"| hav["Straight line"]
  road --> shown["Customer sees a window, not one minute"]
  hav --> shown

Live ETA on /o/… appears only when the order is on the way and we know the driver’s position and point B. If anything is missing, the page keeps working, just without a window.

Without Fleet there is no window at all: the tracking page then shows the status alone. See Tracking link.

Plan limits

Every plan has a limit for vehicles, drivers and team members. Once you reach the limit, you cannot add a new entry until you change the plan or free a slot. That is not a form error but a company entitlement.

The message in the panel says which limit you reached. The ? button next to the plan leads here, not to pricing.

Tracking link

The /o/… address (order short code) works as long as the order is in the system. The address is on the company host: id.delieta.pl/o/…, or — on Pro — on a custom host after CNAME. After delivery the page opens as finished, not as a 404 error. Whoever knows the link sees that delivery, but the page does not reveal the customer’s name, phone or address.

The link has two variants. With Fleet it shows the map, the driver and the ETA window. Without Fleet — or for a pickup order, where nobody drives — it shows the status alone: the order steps and the company name. The driver position and the destination address never reach the page, so there is nothing to reveal. See Tracking page.

Another company’s address with your code shows nothing. The old link on delieta.pl/o/… still works.

This is not the driver token. You copy the link from the order card and send it to the recipient. How to do it in the panel: How to send a tracking link. The partner gets the same URL as trackingUrl in the 201 response. DNS and diagnostics: Tracking domain.

Driver GPS

The driver’s phone sends its position using a drv_… key. Until the first signal, the fleet shows “Waiting for GPS”. The first signal is an important moment, not a technical detail.

The key stays on the phone. Replacing the key invalidates the old address. Do not send drv_… to the customer — the customer gets the tracking link.

Tracking token

The tracking token is the same drv_… key on the driver’s phone. We use this name in the code and on the phone connection screen. It is not an order identifier, it does not open /o/…, it does not work as a panel password.

These are two different tokens: drv_… identifies the driver, and /o/{shortId} one delivery. Mixing them up would reveal the driver’s location to people who were meant to see only one delivery.

flowchart LR
  drv["drv_ key on the driver's phone"] --> gps["driver position and job"]
  page["/o/ page plus short code"] --> glance["one delivery without name and phone"]
  drv -.->|"does not open"| glance
  page -.->|"does not steer"| gps

Alert severity

Colour says how urgent an alert is. It does not mean the alert was read or resolved.

• Urgent (red): happening now — the driver vanished from the map or they themselves report a problem.
• Risk (amber): it will be too late soon — arrival will miss the promised ETA window.
• Operational (grey): to handle during this shift — idle driver, weak battery, queue without assignment.

Acknowledge, snooze and resolve are three separate actions. A grey alert that has been read is still operational until someone closes it.

Tenant

A tenant is a company: pizzeria, florist, service shop. A person’s account and a company are not the same — one person can be invited; the company has a plan, a fleet and products.

Data is separated between companies, not between roles. A member of company A does not see company B’s data. Inside a company every invitee has full operational access; role is a label.

Partner API does not take a company name in the body. The dlt_live_… key itself identifies the company.

flowchart LR
  session["Panel: signed-in session"] --> doorA["Company door"]
  key["Partner: Bearer dlt_live"] --> doorB["Company door"]
  doorA --> co["Company A"]
  doorB --> co
  co -.-> miss["Company B does not exist for this call"]
  pub["Publishable key"] -->|"catalog:read only"| menu["GET /menu"]
  role["Member role"] -.->|"a label, not a gate"| co

Module

A module is a set of screens and features that a company has or does not have: Shop, Fleet, Reservations, Catering, Translations, Online payments. Shop and Fleet are the paths; the rest are add-ons that need the Shop.

A module is on only when three conditions hold at once: the subscription covers it, the owner switch in Settings → Modules is on, and the modules it needs also work. A module that is off disappears from the menu, and its data stays. Full description: Modules and subscription.

flowchart LR
  plan["Subscription covers the module"] --> on{"All three at once"}
  sw["Owner switch on"] --> on
  need["Required modules work"] --> on
  on -->|"yes"| shown["Module in the menu and on the Dashboard"]
  on -->|"no"| hidden["Gone from the menu, data stays"]

Entitlement

An entitlement is everything the plan allows the company: limits (vehicles, drivers, members) and features (live tracking, analytics, white-label readiness, and the shop features: ordering, reservations and catering). Without an entitlement you do not see a disabled button, because the feature simply is not there. An entitlement is only the first of the three conditions of a module.

Live tracking is in Starter, Growth and Pro. Analytics is in the higher plans. A custom domain works on the Pro plan: you set it up in Settings → For developers in the domain card, step by step in Tracking domain. The other cards in Integrations describe keys and the venue address.

The ? button next to plan limits leads to limits; “entitlement” is the wider word, which also covers features, not only limits. Current limits and prices: Settings → Subscription.

Run

A run is the driver’s current course: the stops they are handling now, in order. On the driver card it shows as “Current run”. An empty run means the driver is on shift but nothing is assigned — a different state from missing GPS.

A run is not an order. An order can wait in the kitchen without a run; a run can have several orders. The public tracking link always belongs to one order, not the whole run.