Knowledge base
Short answers, by family.
67 entries across eight families, each one pointing at the page that explains it properly. This is the starting set and it grows with the product.
Showing all 67 entries.
Service.
The shift itself: the till, the room, the pass and the drawer.
Taking an order at the till
The till opens on the room rather than on an empty basket, so you start from the table, the counter, a takeaway or a delivery order. Items come off a photo tile grid with a category rail and a search box, and the quantity sits on the tile itself. The ticket beside it carries thumbnails, steppers, the guest count and the order type.
Options, required groups and a kitchen note
Tapping an item that has choices opens the options sheet. Required groups have to be answered before the line can be added, which is what stops a ticket reaching the pass without the one thing the cook needs to know. A free kitchen note rides along with the line.
Sending to the kitchen without settling
An order can go to the kitchen the moment it is taken, and be billed later. The ticket stays open on the open-tickets rail until somebody pays it, which is how a table that orders in three rounds ends up as one bill.
Splitting a bill
Choose what goes onto the second bill. It becomes its own order with its own number, so it can be paid and printed on its own. There is also a split evenly option for the times when nobody wants to work out who had the extra side.
Taking the payment
The payment sheet has a numpad, quick tenders and change, tips, and eight tender types. Pushing the amount to a connected card machine, rather than typing it in twice, is coming soon.
Reading the floor
Tables sit in their sections with open, occupied, billed and needs-clearing on the face of them, and each one shows how long it has been sitting. The layout editor is where the plan of the room is drawn, and the waitlist learns its turn times from the same tables.
Seating and moving a table
A party can be moved to another table, and the open ticket travels with them. Nothing is retyped and nothing is lost in the move. Joining two tables is coming soon.
Bookings, the waitlist and no-shows
Reservations are kept by day, with a seated and done flow, no-shows recorded rather than forgotten, and a waitlist for the evenings that run over. Guests can book themselves through an online booking page, and a booking can carry a deposit.
Bumping a ticket on the kitchen display
Tickets arrive by station and age in front of the cook. A line is bumped when it is away and the ticket when it is done, on the screen, a bump bar or the keyboard. Anything bumped in the last thirty minutes can be recalled.
All day, expo and stations
All day is everything still to make, biggest first. Expo is every station on one board. A station filter narrows the screen to one section of the kitchen, and the sound can be turned on so a new ticket chirps.
Prep targets and late flags
Each ticket carries a prep target, and a threshold in minutes decides when it is flagged as late. Kitchen timing stamps are kept against the ticket, which is what the kitchen times report is built from later.
Opening a shift and the float
Count the float in the drawer when the shift opens. That figure is what the close is measured against, so it is the one number worth counting twice.
Closing a shift and the Z reading
The close takes a cash declaration and produces a Z reading, with the variance set against the named person who counted it. An X read can be printed at any point during the shift without closing anything.
What prints, and where
Kitchen tickets and receipts print from the till over USB, Bluetooth or the browser, one ticket per station, so a dessert goes to the dessert printer and a drink to the bar. The station is set once on the category, not per order. The print agent drives the network printers for reprints, X and Z reports, kiosk orders and delivery platform orders.
The customer display
A second screen facing the guest, showing the order as it is rung, line by line, the total with VAT and a QR to pay. Pair any tablet to its till with a six-digit code.
Nothing in Service matches that.
15 entries
Business.
What the shift adds up to: reports, profit, spend, offers and the platforms.
Where the reports are
Reports are grouped as Sales, Products, People, History and Exceptions. Sales holds the business summary, daily and hourly sales, by outlet, order types, payment types and settlements. Every one of them exports to CSV.
Exporting a report
Pick the report, pick the exact dates, and export. The file is a CSV, which means it opens in whatever your accountant uses and leaving delEat costs an afternoon rather than a project.
Reading the P and L
One outlet picker and one month. The lines run from revenue excluding VAT, with a line per order type, through discounts, aggregator commissions, food cost and wastage to gross profit, then through staff, rent, utilities, compliance and maintenance to operating profit.
Why staff costs say estimate
Until a payroll run has been approved for that month, the staff cost line is marked as an estimate. It is not a rounding: it is the system telling you the figure under it has not been run yet.
The cashflow tab, and the VAT indication
Cash in is a row per tender with its settlement note, plus aggregator payouts received. Cash out covers the utilities, rent cheques cleared and payroll paid. The VAT position at the foot is an indication for the quarter, not a filed return, and the screen says so.
Break-even revenue
The profitability tab works out the revenue at which the outlet covers itself, and prints its own assumptions beside the figure: which costs it treated as fixed, which as variable, and which revenue the gross margin was taken against.
Recording an expense
Capture the spend with its receipt, set the category, mark the recoverable VAT, and send it for approval. Recoverable input VAT needs a tax invoice, which is why the receipt is part of the record rather than an attachment to it.
Matching a settlement to your own record
Settlement reconciliation reads the statements your payment providers and delivery platforms issue and lines them up against what the till recorded. It is a reading of documents you already have, and it moves no money.
Building a promotion
A promotion is a rule: by channel, by item and by time, with an approval before it goes live. It is defined once and then enforced at the till, rather than remembered by whoever is on the counter.
Accepting and declining an online order
Delivery app orders flow into the till through UrbanPiper once our team has connected your stores during setup. Anything that cannot be matched, usually a missing item mapping, waits in the exceptions queue rather than disappearing.
Pushing a menu and availability to a platform
Menus go out with their own markup and rounding, and availability is pushed per item, including an until window for the times something is off for the evening only. Go busy pauses the outlet on the platforms when the kitchen is under water.
Asking a question in plain words
Ask delEat answers from the reports you already have, in plain language, with an optional model key of your own. It reads your numbers; it does not invent any.
Nothing in Business matches that.
12 entries
Operations.
The operating record: what is due, what was logged, and who to call.
What is due next
The compliance overview is the front page: certificates, services, contracts and insurance, with whatever is closest to expiry at the top. AMC and licence reminders open sixty days out.
The service calendar
Visits are planned from each schedule’s own frequency over a rolling ninety days, and regenerate when a schedule changes without ever moving a visit somebody has already confirmed. A visit can be confirmed, rescheduled with a reason, cancelled with a reason, or recorded as done.
Nothing is sent on your behalf
Confirming a visit builds a WhatsApp or email message for you to send. The server dispatches nothing: no push, no SMS, no WhatsApp and no email. There is an add-to-calendar export that opens in any calendar app.
Every interval is your own default
Pest control, grease traps, hoods and the AMC visit counts all arrive with a default interval, and every one of them is a default you can change. None of them is a period any authority set, and delEat is not affiliated with any authority.
The staff compliance matrix
One grid: name against occupational health card, food hygiene training, PIC certificate and medical insurance. Each cell is valid, expiring, expired, missing or pending review, so the gap is visible before an inspector finds it.
The inspection file
A printable file with sections for the persons in charge, staff cards and training, the last three services on pest control, grease traps and hoods, the AMCs, the licences and the insurance. It is built for the visit rather than assembled during it.
Logging a temperature round
A round is logged on a large on-screen keypad, one unit at a time. Each unit reads in range, out of range, missed, not yet due or never recorded, so nobody has to remember which fridge was done.
A reading that is out of range
It will not save on its own. The screen asks for a corrective action and a note before it will take the reading, which is the difference between a log and a record somebody can rely on.
The monthly log sheet
A printable sheet per unit for the month, an out-of-range incidents list, and a trend chart with the target band shaded behind the readings.
Food safety, first aid and the emergency list
The food safety and first aid pages are editable and readable by anyone signed in, with a reset to default on each. The emergency tab is a list of tap-to-call numbers, the national ones and your own outlet slots, and it can never be switched off.
Finding a number
The directory is one search box and a category list. Suppliers, service providers and staff are merged in at read time and de-duplicated by phone number, never copied, so a number changed once is changed everywhere.
Taking a contact with you
Every contact carries call, WhatsApp and email links and a copy button, and exports as a vCard, either one contact or every contact in the view.
Nothing in Operations matches that.
12 entries
Catalogue.
What you sell and what it costs you: menu, stock, recipes and members.
One menu, prices per outlet
Categories, items, modifier groups, veg marks and photos are held once. Prices are set per outlet and per channel off that one menu, so a delivery price and a dine-in price are two numbers on one item rather than two menus.
Taking an item off for tonight
Availability is set per outlet and per channel, and a temporary 86 takes an item off without deleting it or touching anybody else’s outlet.
Stock, reorder points and why stock moved
Ingredients carry stock levels and reorder points, and stock moves for four reasons and no others, which is what makes a count reconcile. Sub-recipes roll up into the dishes that use them.
Costing a dish
The recipe book holds costed dishes and their margins, and the cost recalculates as the recipe is typed. It is the same number the item profitability and dish margin reports are built on.
Points, members and redemption
A points programme with member accounts and redemption at the till, applied by the system rather than remembered by the cashier. The guest record behind it carries the order history, tags and campaigns.
Nothing in Catalogue matches that.
5 entries
Team.
People: roles, hours, the roster and payday.
Roles and permissions
delEat is deny by default: a role holds only what it has been granted, and the server checks it rather than the screen. Ten roles are set up out of the box, including owner, manager, supervisor, cashier, waiter and kitchen, and every one of them is yours to edit.
PINs and home outlets
Each person has a PIN and a home outlet, and a role can be scoped so that somebody sees one outlet rather than all of them.
Clocking in from a phone
Attendance is clocked from a phone, with the location checked against the outlet’s geofence and one registered phone per person. A manager reviews and releases what needs it rather than the system deciding quietly.
Building the roster
Shifts by day and by week, with copy last week for the weeks that are the same as the last one, which is most of them.
A payroll run
A run is built off the hours already clocked. Alongside it sit advances, service charge, settlements and gratuity, and each person is paid by their own method: WPS, bank transfer or cash.
The salary file, and who is excluded
The WPS tab builds the salary file from an approved run and shows three lists: included, excluded and paid outside WPS. Nobody is silently dropped. An excluded row names the field that is missing, which is a labour card number, a bank routing code or an IBAN.
Check the first file with your bank
The field order follows the MOHRE SIF layout, and some banks and exchange houses supply their own template, so the first file should be checked with your bank before it is relied on. A payslip is not a WPS file, and it says so on itself.
Nothing in Team matches that.
7 entries
Guests.
The ways a guest orders and pays without a member of staff in between.
Pay at the table by QR
The guest scans the table, sees the bill on a hosted payment page and pays. The order closes itself on capture, so nobody walks a card to a terminal and back.
Your own ordering page
A guest ordering page with pick-up and delivery inside a radius you set, paid at checkout, with order tracking stages the guest can watch. It is your page, so nobody takes a cut of it.
The self-service kiosk
A counter screen the guest drives, on the same menu as the till, on a paired device. The guest pays at the counter; card payment at the kiosk is coming soon. A kiosk order is picked up on the till like any other.
Delivery platforms on the same till
Talabat, Deliveroo, Careem, noon and more come in through UrbanPiper, on the same till and kitchen screen as everything else. Our team connects your stores for you during setup. Your own riders are assigned and settled on the till today, with their cash on delivery counted into the drawer.
Nothing in Guests matches that.
4 entries
Setup.
Configuring an outlet, and coming across from another system.
Finding a setting
Setup is a deep tree with a breadcrumb on every page, covering outlets and brands, sections and tables, courses, discounts, reasons, modifier groups, devices and pairing, invoice numbering and appearance.
Printers, templates and routing
The till prints over USB, Bluetooth or the browser. Network printers are paired through the local print agent for macOS and Windows. Print templates and the kitchen station on each category decide what each printer receives.
Payment types, fees and settlement days
Each payment type carries its own fee and the number of days it settles in, which is what lets the cashflow view show a tender with its settlement note rather than as cash in hand.
Coming off another system
Import from Sapaad, tested, or a CSV, and a menu from a Talabat link or a saved Deliveroo page. Foodics, Square and Lightspeed are mapped but untested, so they are on request. Every import has a map, a preview, a dry run and a rollback.
Nothing in Setup matches that.
4 entries
Platform.
The things underneath all of it: the board, the network, the other outlets.
Building your own board
The dashboard is widgets you choose and arrange, in three materials, with wallpapers, a day and a night mode, a live board that refreshes on a twelve second beat, and its own phone layout.
Every number opens onto the one behind it
A figure on the board is a door. Tapping it opens the detail it was summed from, which is usually faster than going to find the report.
Trading with no network
Offline mode computes order state, totals and the printed slip on the device itself. The queue drains when the connection returns, and replays are detected, so nothing is double-charged.
Handhelds on the floor
The same till in the browser, laid out for a phone, for waiters taking orders at the table. A rider view is coming soon.
Reading it from your own systems
A public API is coming soon. Today every report exports to CSV, and your data can be exported in bulk, so an accounting system can take the same numbers rather than a retyped copy of them.
Several outlets, several sets of books
Head office holds the recipes and the brand standard. Each outlet keeps its own books, with permissions scoped to the outlets a person holds and fee reporting by outlet on top.
Nothing to install beyond a browser
The till, the kitchen screens, the dashboard and every staff screen run in a browser. The only install is the optional local print agent on a Mac or PC in the shop, for the network printers.
Backups and the audit log
Backups are taken nightly and can be restored, sign-in attempts are throttled, payment provider keys are held encrypted, and an audit log records what changed and who changed it.
Nothing in Platform matches that.
8 entries
Not here yet
Ask a person instead.
Live chat is staffed twenty four hours a day, seven days a week, from Dubai, and it answers faster than this page will ever grow.