Machine-translated. Polish is the canonical documentation.

Features

How a company uses Delieta day to day — modules, dashboard, orders, fleet, alerts, analytics, settings.

This section describes the panel the company works in. Concepts explains the words on screen. The first shift, from creating an account to sending a link, is on the For business page. For modules and the plan, see Modules and Subscription.

Every list in the panel has its own page. The ? button still goes to the headings below, and their addresses stay the same.

Modules

What you see in the panel depends on the modules that are on. There are two paths: Shop (orders and sales) and Fleet (map, drivers, ETA). You can turn on add-ons for the Shop: Reservations, Catering, Events, Translations and Online payments. At least one path must stay on.

A module works when three conditions are met: your subscription covers it (or Delieta granted it to your company separately), your switch in Settings → Modules is on, and the module it needs is working too. Add-ons need the Shop. Switching off deletes nothing — the data comes back when you switch on.

ModuleWhat you get in the panelPage
ShopProducts, Ingredients, shop orders, sales amountsProducts, Ingredients, Shop
FleetMap, Vehicles, Drivers, the Driver app and the live tracking linkDrivers, Vehicles, GPS, Tracking page
ReservationsReservations in the menu, floor and table plan, form in the shopReservations
CateringCatering in the menu: enquiries, jobs, formatsCatering
EventsWorkshops and events in the menu, sign-up by inquiry or phoneEvents
TranslationsExtra shop languagesTranslations
Online paymentsStripe card in the Shop settings, payment at checkoutOnline payments

Pages that always work:

ListPage
OrdersOrders
AlertsAlerts
Analyticsdescribed below, in the Analytics section
SettingsCompany settings
HelpHelp
DomainTracking domain

Dashboard

After sign-in the Dashboard shows what is happening on the shift: who is out, what waits in the oven, what is late. The map and the list show the same thing; they differ only in how much detail they show. We consider a screen that worries you with too much information a bad screen. We judge every screen by this test, see the philosophy.

The cards on the Dashboard depend on modules. You always see the metric tiles and the Needs attention card (the most important open alerts). The rest:

ModuleDashboard cards
ShopSales — sales, after fees, to pay, disputed
FleetMap, Active deliveries, District load
Shop without FleetOrder queue — to accept, in preparation, ready
ReservationsReservations today
CateringCatering — new enquiries and scheduled jobs

The date range switch (Today, 7 days, 30 days) sits in the header. With Fleet, the header also has an Operations view link to /app/dashboard/dense — a denser Operations dashboard: map, deliveries, oven queue, free drivers and alerts side by side.

When you switch one path off, the Dashboard leaves a subtle hint (for example “Fleet off · map, drivers, ETA”) with a Switch on in Modules link. When both are off, the screen asks you to switch on the Shop or Fleet.

Orders

Orders is the list of orders from acceptance to completion. The status only moves forward: awaiting acceptance → accepted → preparation → then it depends on how the customer gets it. Delivery goes through “On the way” to “Delivered”. Pickup goes through “Ready for pickup” to “Handed over” — nobody drives such an order, so it has no “On the way”. Delivery, in turn, has no “Ready for pickup” step.

Rejection is final and possible only while the order is waiting for acceptance. A delivered order cannot be undone. More about the list: Orders.

An order from the storefront reaches the panel through the Partner API. An order taken by phone you enter by hand. The order intake mode decides whether a new order is accepted at once or waits for the kitchen to accept it.

flowchart TD
  intake["Storefront, panel or API"] --> mode{"Company intake mode"}
  mode -->|"at once"| accepted["Accepted"]
  mode -->|"queue"| pending["Oczekuje na przyjęcie (awaiting acceptance)"]
  pending -->|"kitchen: yes"| accepted
  pending -->|"kitchen: no"| rejected["Odrzucone (rejected)"]
  pending -->|"time ran out"| rejected
  accepted --> preparing["Preparation"]
  preparing --> kind{"Delivery or pickup?"}
  kind -->|"delivery"| way["W drodze (on the way)"]
  way --> delivered["Dostarczone (delivered)"]
  kind -->|"pickup"| ready["Ready for pickup"]
  ready --> handed["Handed over"]

Open the order card. On the right is the public address with a copy button, in the form your-id.delieta.pl/o/…. Send it to the customer. The customer does not sign in and installs nothing. Custom domain: 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. The concept: Tracking link. Without Fleet the link still works but shows status only — see Tracking page.

Fleet

In the menu, the Fleet group has Map, Vehicles and Drivers. 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 the GPS position; an order waiting in the kitchen has no car or route on the map — you see the order itself, not a vehicle. More: Drivers, Vehicles, GPS.

When a driver reports a problem from their phone, you see it in alerts, not as an easy-to-miss status on the pin.

When Fleet is off:

  • Map, Vehicles and Drivers disappear from the menu, and their addresses show “Fleet is off” with a button to Modules.
  • The server rejects GPS positions. Driver keys stay valid and work again once Fleet is on.
  • The customer gets a tracking page with status only, no map and no ETA window.
  • Alerts about drivers are not created; alerts about orders, plan payment and catering enquiries keep working.
  • The Driver app shows “Fleet off” instead of the job.

Alerts

The Alerts inbox shows what is happening now: lateness, vanishing GPS, idleness, low battery, a driver report, a plan payment problem, a new catering enquiry. The colour shows the severity, not whether the alert was read. When you acknowledge, snooze or resolve, we record who did it and when. More: Alerts.

Products

Products is the company menu: categories and items, with prices in grosze. The storefront gets the same menu from GET /api/v1/menu. A switched-off item disappears from the API; the shop does not get an “unavailable” flag it would have to handle itself. More: Products.

Analytics

Analytics is a separate menu item, under Alerts. It has a header with the same date range switch (Today, 7 days, 30 days), a strip of tiles with numbers for the chosen period and — with Fleet — two comparison tables: Drivers and Vehicles. The tables show distance, punctuality and ETA accuracy. Without Fleet only the strip of order tiles remains.

Analytics is part of the subscription: the plan card calls it “Analytics and alerts”. If your plan does not include it, it is not in the menu, and opening its address directly takes you to the Dashboard, so you do not see an empty table. You can check this in Settings → Subscription.

Company

The company name and niche go to the tracking page and to invoices. Changing the name does not change the company URL. The niche decides the words used in the panel (pizza, flowers, service), but it is not a separate product.

Here you also save the venue: address and coordinates. Without them an ETA quote returns venue_not_configured.

Identity and brand

Name, logo, banner and brand colour appear on the page the pizzeria’s customer sees at /o/…. If you do not choose a colour, the Delieta green stays. The owner or an admin changes the logo and banner. This is not white-label of the whole panel, only the look of the tracking page.

Delivery defaults

Prep time and delivery radius are the starting point for the ETA quote. The system adds loading, buffer and detour on top — you do not set those values on this card. You also set the intake mode (at once or queue) here: it decides whether an order from the API is accepted at once.

Opening hours

The days and hours when the kitchen takes orders. Empty hours mean they are not set yet — the shop can still take an order. This is the company calendar, not a particular driver’s duty.

Closed days

Holidays, leave, renovation. On the chosen days (from–to, with a short note) the shop will not take orders or table reservations. You add them on the same card as the hours, in the Closed days section.

Tracking page appearance

The preview shows saved values, not an unsaved draft. The customer at /o sees the same name, colour and header. A preview that shows something different from the customer’s page would be worse than no preview.

Online payments

Settings → Shop. Customers pay by card or BLIK, and the money goes straight to the company account through Stripe. Delieta takes a commission per order and shows it on this card.

Before you move to Stripe you enter the tax ID (NIP) and phone. Both are optional. Using the NIP we check the public VAT taxpayer register and fill in the Stripe form: company name, address, REGON, VAT number, industry and the bank statement descriptor. Stripe keeps the owner’s details, the bank account number and the acceptance of terms. Delieta does not store the NIP or the phone.

Payouts, refunds and documents are in the Stripe panel. On the same tab you set the delivery fee, in zloty.

The Orders section decides what the customer chooses in the shop cart: delivery and pickup, online payment and cash on collection, the minimum order value (dishes only, no delivery), prep time, and the step and reach of the time slots. You also enter the Facebook, map and e-mail links the shop shows customers. Online payment appears in the shop only once the Stripe account can take payments. A cash order reaches the panel as unpaid; after you collect the money you mark it as paid. Changes reach the shop without a redeploy. The whole topic: Online payments.

For developers

Here you issue the /api/v1 keys. The publishable key is for public product reads. The secret key is for orders and quotes — it stays on the storefront server. Replacing the publishable key invalidates the old one at once.

Shop address is where Stripe sends the customer after payment. A shop set up by Delieta has it filled in. Tracking domain: every plan has {id}.delieta.pl; an own host (CNAME) is on a plan with the White-label item. DNS instructions and diagnostics: Tracking domain. API integration: Partner API and the storefront contract.

Team

Every invited member has full operational access. The role on the invitation is only a label and does not change permissions — this version has no RBAC inside the company. The boundary is the company: a member of Bella does not see Parma’s data.

Subscription

The plan is billed per company, not per person. Starter, Growth or Pro — limits of vehicles, drivers and members plus plan items: Live tracking, Analytics and alerts and White-label / own domain. Extra modules have their own items (Shop, Reservations, Catering); a module outside the plan shows “Not available in your subscription” in Modules and an Add in Subscription link. Once you reach the limit, you cannot add a new vehicle or driver until you change the plan or free a slot. See plan limits and entitlement.

Invoice and card are at Stripe. When a payment is overdue, the company can keep working for a short time, then the panel becomes read-only. The banner above the Dashboard says which of these states applies, so you do not have to work it out from disappearing buttons.

Preferences

Each person sets language and theme for themselves, on their own device. These are not company settings. Language is stored in the address (prefix) and in a cookie. Theme is light or dark. Translucent, blurred panels over the map turn on by themselves where the browser supports them; on older devices and with the system “reduce transparency” setting the panel is solid. Team and subscription stay with the company.