Tracking domain

How the company address on delieta.pl works, how to add your own host, and what to check when the customer cannot open the link.

The customer is waiting for food. The link you send them should look like your company, not like ours. Delieta gives that in two steps: first a subdomain on delieta.pl, then — on the Pro plan — your own host in your domain.

What the customer opens

Every company has an identifier (the same one you see in Settings → Company). In production the tracking link looks like:

https://your-id.delieta.pl/o/CODE

CODE is the order short id, the same as before on /o/…. Whoever knows the link sees that one delivery. Another company’s address with your code shows nothing — that is not a mistake, it is protection.

The old link on delieta.pl/o/… still works. You do not have to revoke it.

Delieta subdomain

You do not add a DNS record. The company identifier is the host. Changing the identifier breaks the link the customer already holds — the same as changing a shop address.

Some names are reserved by the platform (admin, www, app, mail and similar). The panel will say “reserved” outright, not “something went wrong”.

On {id}.delieta.pl the panel (/app) stays on delieta.pl. A verified custom host is different: / is the shop and /app is the same panel.

Identifier or custom host

	When	DNS	Panel `/app`
`{id}.delieta.pl`	Every plan, immediately	None	Stays on delieta.pl
Custom host, e.g. `pizzeria.pl`	Pro plan, after verification	CNAME (or A at apex)	On that host

You change the identifier in company settings. The change breaks the link the customer already holds. A custom host does not replace the subdomain — both can live side by side.

flowchart TD
  diner["Customer opens an address"] --> which{"Which host?"}
  which -->|"slug.delieta.pl"| track["Tracking page /o"]
  which -->|"verified custom"| shop["Shop / and panel /app"]
  shop --> track
  self["Customer-deployed shop, storefront/"] --> api["GET /menu on delieta.pl"]

Custom domain (Pro plan)

On the Pro plan, in Settings → Integrations, you enter a host, for example track.yourshop.pl.

In your domain’s DNS panel add:

Type	Name	Value
CNAME	`track` (or the other host you entered)	`cname.vercel-dns.com`

Do not turn on a proxy cloud (Cloudflare orange cloud) — the certificate will not issue. Leave DNS-only.

Apex (yourshop.pl without track.) is a different record (A, not CNAME). This version supports a CNAME host, like track.yourshop.pl.

After save the panel shows state: pending, verifying, bad DNS, ready. The HTTPS certificate issues itself, usually a few minutes after a correct CNAME. Green “ready” appears only after DNS is checked — not earlier.

What is on your host

When the host is ready:

Path	What you see
`/`	Your shop (catalogue menu). Search engines may index it.
`/app`	The same panel as on delieta.pl. You must sign in again — the delieta.pl cookie is not sent to your host.
`/o/{code}`	Tracking for one delivery. Still `noindex`.

Card checkout on this shop waits on Stripe Connect. The menu is real; nothing charges.

delieta.pl/ stays Delieta marketing. {id}.delieta.pl/app still redirects to the panel on delieta.pl.

What to check when it fails

Typo in the host. trak.yourshop.pl and track.yourshop.pl are two different places.
Wrong DNS name. The CNAME must be on track (or exactly what you entered), not on www, unless www is that host.
Time. A new CNAME can be invisible for minutes, rarely hours. whatsmydns.net shows whether the world already sees the record.
Proxy. Cloudflare / another CDN in proxy mode hides Vercel from the certificate authority.
Plan. A custom host is on Pro. The Delieta subdomain is on every plan — if Pro is not active, the panel will say to change plan, and it will not fake a green status.
Old link. delieta.pl/o/… and your-id.delieta.pl/o/… are the same code. If one works and the other does not, the problem is DNS or the certificate, not the order.

The tracking page is not indexed by search engines. It is a live location, not a landing.

Wider in the panel: Integrations, Tracking link.