Currency, numbers, date and time
What this is for
Every price, every date and every time in Restodesk — on screen, on receipts, in reports and in emails — is written the way you set here.
Get it right on day one. Changing it later is safe, but every printed menu and every receipt already out in the world says the old thing.
Currency
Under Settings › Currency.
| Setting | What it controls |
|---|---|
| Currency | Which one, and its symbol. |
| Symbol position | Before or after the number — $12.50 or 12.50 kr. |
| Thousand separator | 1,000 or 1.000 or 1 000. |
| Decimal separator | 12.50 or 12,50. |
| Decimal places | Usually 2. Zero for currencies without subunits. |
Getting it right
Follow local convention, not what looks familiar to you. 1.234,56 € is correct in much of
Europe and looks like an error to an American; $1,234.56 is the reverse. Your customers read
whichever they grew up with, and a price that looks wrong reads as untrustworthy.
Decimal places matter for currencies without subunits. Yen and won don't have cents — two decimal places on those looks broken.
Check it on a receipt, not just on screen. That's where a guest reads it most carefully.
Timezone
Under Settings › Timezone.
This is more consequential than it looks. It decides when a day starts and ends for reporting, when scheduled things run, and what time appears on every order and kitchen ticket.
Set it to the restaurant's actual location — not the head office, not where you happen to be. On a multi-site business in more than one timezone, this needs care.
Date and time formats
How dates and times are written throughout.
| Consideration | Notes |
|---|---|
| Date order | DD/MM/YYYY or MM/DD/YYYY — the classic ambiguity. 03/04 is two different days. |
| Time | 12-hour with am/pm, or 24-hour. |
Use whichever your staff read fastest. Kitchens generally do better on 24-hour time — there's no am/pm to misread on a ticket at 7 pm, and no ambiguity about a shift ending at 12.
For dates, follow local convention. Where you have staff or suppliers from different conventions and
it genuinely causes confusion, a format with a written month — 04 Mar 2026 — removes the ambiguity
entirely.
Where this shows up
Everywhere, which is why it's worth a minute:
- Prices on the POS, the menu, the customer site and the kiosk
- Totals on receipts and bills
- Every report
- Order and kitchen ticket timestamps
- Reservation times
- Emails to customers
Business days aren't calendar days
Worth knowing here because it interacts with everything above: report periods follow your operating shifts, not midnight.
A service running 6 pm to 2 am belongs to the day it started. So a "day" in your reports may not match a calendar day, and around month end that can move an order across a boundary.
That's intentional and it's what makes late-night trade report sensibly. See Opening hours and shifts.
Good to know
- All of these are per restaurant, so branches share them.
- Changing the currency does not convert existing prices. A menu priced at 12 becomes 12 of the new currency. Re-price deliberately.
- Changing formats doesn't change stored data, only how it's displayed — so it's safe to adjust.
- Receipts can print in multiple languages; number formatting stays as set here. See Language.