Glossary
The words we use in the dashboard, the kitchen app and these docs.
Your business
Section titled “Your business”Organisation : The paying business account. It holds your subscription, your team and your customer list. One organisation can own several shops. In the dashboard it’s the name above each settings page, for example “Joe’s Pizza Group”.
Shop : One trading location with its own storefront, menu, hours, kitchen devices and Stripe account. Also called a location. See Multi-location.
Storefront
: Your ordering website, at yourname.direct.eat or your own domain. Diners order here directly, with no app and no account needed.
Slug
: The short name in your web address, for example joes-pizza in joes-pizza.direct.eat.
Group ordering page : One link for all your shops. Diners enter a postcode or share their location and pick the nearest open shop.
Master menu : A menu shared by several shops in a group. Edit once and every shop updates; each shop can still change prices, hide items or mark them sold out. Pro plan.
People
Section titled “People”Member : Someone on your team, with a role. See Roles and permissions.
Owner, admin, manager, staff : The four roles people can have. The owner runs the business and is the only one who can cancel, transfer ownership or change the Stripe account.
Kitchen device : A paired tablet or screen running the kitchen app. It shows up in your team list as a member with the “Kitchen device” role.
PIN profile : A name and a 4 to 6 digit PIN for staff who share a kitchen tablet and don’t have their own login.
Customer : A diner who has ordered from you. Your customer list belongs to your organisation, not to direct.eat.
Support session : A time-limited, logged visit to your dashboard by direct.eat support. Read-only unless you allow changes.
Orders
Section titled “Orders”86 : Kitchen slang for “sold out”. To 86 an item is to mark it unavailable so diners can’t order it.
ETA / ready time : When the order will be ready for collection, or the time range it should arrive for delivery.
Escalation : What happens when nobody accepts an order: the alarm, then a reprint, push notifications, a phone call to the shop and texts to on-call contacts, at configured timings. See Alerts and escalation.
Missed order : An order nobody accepted in time, so it was cancelled and the diner refunded.
Busy mode / pausing : Adding extra minutes to ready times, or stopping new online orders for a while. See Busy mode and pausing.
Order statuses : Received, Accepted, Cooking, Ready, Out for delivery, Collected or Delivered, plus Rejected and Cancelled. See Order statuses.
Stripe : The payment company that takes card payments for you. Your Stripe account is yours: diners pay you directly and Stripe pays out to your bank. direct.eat takes 0% of each order.
Payout : Money Stripe sends to your bank account.
Dispute (chargeback) : When a diner asks their bank to reverse a card payment. See Payments troubleshooting.
Ex VAT / inc VAT : A price without or with VAT at 20%. direct.eat’s plan prices are set ex VAT.
Founding member : The launch offer: 20% off your plan for 24 months, price locked, for the first 500 paying shops or until 30 June 2027.
Add-on : Something you add to your plan for a price: extra shops, SMS credits, a custom sending domain, AI top-ups or campaign emails.
Dunning : What happens when a subscription payment fails: automatic retries and reminders, then pauses. See Billing and plans.
Exit pack : A full download of your data (menu, customers with consent, orders and VAT) available any time, not only when you leave.
Marketing and consent
Section titled “Marketing and consent”Soft opt-in : The UK rule (PECR) that lets you email a customer about similar products after they’ve bought from you, as long as they were given a clear chance to say no.
Approval : A request from a manager (or direct.eat support) for an owner or admin to approve something that costs money, such as an offer. See Approvals.
Developers
Section titled “Developers”API key
: A secret that lets your own software read (and on Pro, update) your direct.eat data. Starts with de_live_ or de_test_. See API keys and scopes.
Scope
: What an API key is allowed to do, for example orders:read.
Webhook : A message direct.eat sends to your server when something happens, such as a new order. See Webhooks.
Signing secret
: The secret used to sign webhooks, so your server can prove a message really came from direct.eat. Starts with whsec_.
Integration : A connection to another system you use: a till (Square), accounting software (Xero, QuickBooks, FreeAgent), Deliverect or Google. See Integrations.
App : An optional feature you switch on from the Apps library, such as the allergen chart or food hygiene rating. See Apps.
Data protection
Section titled “Data protection”Controller and processor : Under UK GDPR, you (the restaurant) are the controller of your customers’ data: you decide why it’s used. direct.eat is the processor: we handle it on your instructions. See Data processing.
Sub-processor : A company direct.eat uses to run the service that may handle your data, such as our database host.
DSAR : A data subject access request: a person asking for a copy of the data held about them.
Was this page helpful?