Features

This register describes the panel the company works in. The dictionary of on-screen words is in Concepts. The first shift — from account to link — is in For the company.

Every list in the panel has its own page. The ? helper still lands on the headings below — we do not move those hashes.

Dashboard

After sign-in the Dashboard is a picture of the shift: who is riding, what waits in the oven, what is late. Map and list say the same thing; the difference is only density. If the screen raises anxiety with noise, it is wrong — philosophy judges every surface by that criterion.

Orders

Orders is the list of tickets from accept to delivery. Status moves forward: waiting for acceptance → accepted → preparing → on the way → delivered. Rejection is terminal and only possible from the acceptance queue — you cannot “un-deliver”. List handbook: Orders.

A ticket from the shop arrives through the Partner API. A ticket from the phone you type by hand. The company’s acceptance mode decides whether a new ticket starts as accepted or waits until the kitchen says yes.

flowchart TD
  intake["Shop, panel or API"] --> mode{"Company acceptance mode"}
  mode -->|"immediate"| accepted["Accepted"]
  mode -->|"queue"| pending["Waiting for acceptance"]
  pending -->|"kitchen: yes"| accepted
  pending -->|"kitchen: no"| rejected["Rejected"]
  pending -->|"time limit"| rejected
  accepted --> preparing["Preparing"]
  preparing --> way["On the way"]
  way --> delivered["Delivered"]

How to send a tracking link

Open the order card. On the right is a public address with a copy button — in production on your-id.delieta.pl/o/…. Paste it to the customer. The customer does not sign in and installs nothing. Custom host: Tracking domain.

The link works as long as the order is in the system. After delivery the page opens as finished, not as an error. This is not the driver GPS token — that key stays on the driver’s phone. Concept: Tracking link.

Fleet

Vehicles and Drivers are separate lists because the plan limit counts them separately. Assign a driver to a vehicle before they leave. The Map shows GPS position; an order waiting in the kitchen has no car or route on the map — you see a ticket, not a vehicle. Handbooks: Drivers, Vehicles, GPS.

A driver who reports a problem from the phone appears in alerts, not as a silent status on the pin.

Alerts

The Alerts inbox is things happening now: lateness, vanishing GPS, idleness, low battery, a driver report, a plan payment problem. Colour is severity, not “read”. Acknowledge, snooze and resolve record who and when. Inbox handbook: Alerts.

A plan without the alerts entitlement does not show the inbox as a disabled dummy — either it is there, or it is not.

Catalog

The Catalog is the company menu: categories and items, prices in grosz. The same menu is what GET /api/v1/menu returns to the shop. A disabled item vanishes from the API; the shop does not get an “unavailable” flag to honour on its own. Handbook: Catalog.

Analytics

Higher plans add Analytics: promise kept, district load, driver work. Starter has live tracking, not this view. Missing analytics on a plan is a missing door, not an empty table.

Company

The company name and niche land on the tracking page and on invoices. Changing the name does not change the company URL. The niche picks a vocabulary (pizza, flowers, service) — it is not a separate product.

You also record the venue here: address and coordinates. Without them an ETA quote returns venue_not_configured.

Identity and brand

Name, logo and brand colour paint the page a pizzeria customer sees on /o/…. An empty colour leaves Delieta green. This is not white-label of the whole panel — it is the skin of the tracking page.

Default delivery settings

Prep time and delivery radius are the starting point of an ETA quote. On top of that the engine adds load, pad and detour — you do not set those constants on this card. Acceptance mode (immediate or queue) also lives here: it decides whether an API ticket arrives as accepted.

Opening hours

Days and hours when the kitchen accepts orders. Empty hours mean they have not been set yet — the shop can still accept an order. This is the company calendar, not a specific driver’s duty.

Tracking page look

This window shows saved values, not a draft. The customer on /o sees the same name, colour and header. A preview that lies would be worse than no preview.

Integrations

Here you issue /api/v1 keys. The publishable key is for the catalog. The secret key is for orders and quotes — it stays on the shop server. Rotating the publishable one invalidates the old one immediately.

Stripe Connect onboards the shop account in this place. Tracking domain too: every plan has {id}.delieta.pl; a custom host (CNAME) is on Pro. DNS instructions and diagnostics: Tracking domain. API integration: Partner API and storefront contract.

Team

Every invited member has full operational access. The role on the invitation is a label, not a permission — this version has no RBAC inside the company. The boundary is the tenant: a Bella member does not see Parma.

Billing

The plan bills the company, not the person. Starter, Growth or Pro — vehicle, driver and member limits plus flags (analytics, live tracking). After the ceiling a new vehicle or driver will not save until you change plan or free a slot. See plan limits and entitlement.

Invoice and card live at Stripe. After arrears the company first has a short period in which it still works, then the panel goes read-only. The banner above the dashboard says which of those states is on — do not guess from a vanishing button.

Preferences

Language, theme and chrome density are a person on this device, not a company field. Language is saved in the URL prefix and the cookie. Theme is light or dark. Density is glass or solid chrome. Team and billing stay on the company.