Store settings — help

Settings are organised around your stores. Settings › Stores lists every store; open one to reach its settings — it opens straight into General (who and where you are), and the tab row also has Opening hours (when you trade), Charges & tips (service charge and gratuities), Pacing (order throttling), Operations (how you take orders, plus the kitchen-display switch), Online Ordering (what guests see when ordering online), Table Layout (your floor plan), Printers & routing (where tickets print) and Integrations. The store you're in is always the one in the page address. Branding, Feedback, Accounting, AI assistant, AI tokens and Account are organisation-wide, not per-store; Feedback, Accounting, AI assistant, AI tokens and Account have their own guides (Feedback, Accounting, AI assistant permissions, AI tokens, Account). Wherever you are in the hub, the AI assistant can answer questions about your data — including the store you're currently viewing.

Stores

The Stores page is a table of every store in your organisation — name, address, which order types are on, and timezone. Click a row to open that store's settings — it opens straight into the first section (General). Every store page shows the store's name with a row of section tabs beneath it, so you can move between sections without leaving the store; ← All stores takes you back to the list.

Creating a store

New store + opens the create panel:

Name — required; shown to guests and staff everywhere.
Timezone and currency — set here and fixed once the store is created (money and opening hours depend on them) — talk to support if either is wrong later.
Trading address — optional at creation; you can add or change it any time under the store's General section.
Copy settings from — pick an existing store and the new one starts from its setup instead of the defaults. This copies opening hours, charges & tips, order types, pre-orders, pacing, prep time and the till theme. It deliberately does not copy floor plans, printers, integrations or special dates — those are physical or account-specific, so each store sets its own.

On create you land straight in the new store's settings hub, ready to draw floors, add printers and connect integrations.

General

Your store's public identity:

Store name — shown on the ordering app, kiosk and receipts.
Contact email, telephone and website — your public contact details. The phone number must be in international format (07… becomes +447…).
Business address — the store's trading address. This is also the courier pickup point: Nash delivery can't be connected until the address and phone are filled in.
Timezone and currency are shown for reference but fixed when the store is created — talk to support if either is wrong.

Changes save together with the Save settings button.

Branding

Branding belongs to your organisation, not a single store — one brand across every location and channel.

Business logo — replaces the standard mark in the ordering app header, the kiosk welcome screen, and (coming with the till update) the receipt header. Square images look best.
Background image — the kiosk welcome-screen backdrop, shown behind a dark tint so the text stays readable.
Primary colour — buttons, badges and highlights on guest screens. Text on top of it flips automatically between dark and white for contrast.
Secondary colour — the deeper companion shade used for coloured text on white.

Leave everything empty for the standard AccentPOS look. Changes reach guests within a minute. Customer-display theming is a planned follow-up.

Fonts

Pick separate heading and body fonts for your guest screens from a curated menu of free web fonts — classic serifs, modern sans-serifs and display faces suited to hospitality brands. Each option previews in its own face, and the preview block underneath shows your heading and body choices together before you save.

Heading font — store name, category titles and product names on the ordering app and kiosk.
Body font — descriptions and all other guest text.
Fonts are organisation-wide, like your brand colours: one look across every store, applied to the web ordering app and the kiosk. Receipts are printed by the till and keep its fixed print font.
Pick App default (or Clear) to return to the standard AccentPOS type. Changes reach guests within a minute.

Opening hours

When the store is closed, guests can still browse the online menu but can't place an order — the ordering app shows a Closed badge and the kiosk shows a closed screen. (Menu schedules are separate: they control which menus are on sale while you're open.)

Weekly hours

Set your trading times per day. Useful to know:

Multiple ranges per day are fine — add a second range for split service (say 12:00–14:30 and 18:00–22:00).
A close time at or before the open time runs past midnight — 20:00–02:00 keeps Friday's service open into Saturday morning.
A day with no ranges is closed.
No hours set at all means always open — until you add your first range, the store never shows as closed.

Closures & special hours

Date-ranged exceptions to the weekly pattern:

Pick a date (or range), then choose what happens on those dates:

Closed all day — the store is shut those days: bank holidays, refits, annual leave.
Special hours — set an opening and a closing time and the store trades those hours on the covered dates instead of its weekly pattern (e.g. Christmas Eve 10:00–16:00). Both times are required.

On any given date, special hours beat a closure, and both beat the weekly pattern. Remove an exception once it has passed — or leave it; past dates have no effect.

The AI assistant can draft hours, closures, special hours and order-type pauses for you to approve, once an owner raises Store operations under Settings › AI assistant. Each change shows how it affects guests ordering before you confirm it.

Charges & tips

Service charge

Set the service charge for each order type independently — Dine-in, Takeaway (counter and kiosk walk-up), Collection (online collection), and Delivery (online delivery). Turn each on or off, give it its own customer-facing name (rename "Service charge" to Bag fee, Packaging fee, Cover charge, Corkage…), and set its own percentage of the bill (after any discounts) or a fixed amount per order — any amount from £0.01 (a 10p bag fee is fine). The editor shows a live preview of exactly what customers will see, e.g. Bag fee £0.10.

Each charge also has a VAT treatment:

No VAT — a discretionary, VAT-free charge (the default, and how every charge behaved before this setting existed).
Match order items — the charge is taxed like the goods on the order (it takes the rate covering the largest share of the bill).
Tax category — the charge is taxed at a specific tax category's rate.

The charge is applied automatically when an order is placed and shown as its own line — under your chosen name — in the basket, at checkout, on receipts, in the Hub order view and in order history. Orders keep the name and tax exactly as charged at the time, so renaming a charge later never rewrites old orders. Staff can always remove the charge from an individual order at the till, and orders arriving through Deliverect are never charged (those channels price themselves).

Tips

Customer tips — guests can add a custom tip at online checkout. The tip is charged with their card payment and recorded separately from the bill, so your reports show bills and gratuities distinctly.
Card terminal gratuities (Dojo) are configured on the terminal itself and flow into the same reporting automatically.

Bill round-up

Let customers round their total up — for charity, staff gratuity, or another cause. Choose the style (round to the nearest pound, a set of fixed suggested amounts, or a custom amount), the beneficiary name, the wording the customer sees and the wording on the receipt, and which order types and channels it applies to. Round-up is reported separately from tips and the service charge, so charity collections stay distinct in your figures.

Where are payment fees?

Card processing fees are billed by your payment provider, not by AccentPOS. The Reports page has a per-provider breakdown (takings and tips by PayPal / Dojo / Zettle / cash) to reconcile against each provider's statement.

Notices

Store notices are short, customer-facing messages — gratuity or service-charge information, allergen and cross-contamination warnings, collection or delivery instructions, age restrictions, refund policies, or a charity round-up explanation. Add a notice with a title and message, then choose where it shows: online ordering, kiosk, checkout, the till, the customer receipt, or the order-confirmation email. Each notice also carries the same availability controls as everything else — days, a time window, a date range, order types and channels — so you can schedule a seasonal or time-limited notice.

Online, kiosk and checkout notices show to guests immediately. Till, receipt and confirmation-email placements are saved and take effect as those surfaces are wired up.

The AI assistant can add, edit, switch off and switch back on notices for you to approve (Store operations). Notices it adds always show every day; set a schedule here afterwards if you need one.

Pacing

The AI assistant can draft pacing, pacing-wording and service-charge changes for you to approve, once an owner raises Store operations under Settings › AI assistant.

Protect the kitchen at peak times by limiting how much can be ordered per time slot (every 5, 10 or 15 minutes):

Order count — at most N orders per slot.
Category limits — at most N items from a production-heavy menu category per slot (say, 20 sandwiches every 15 minutes). A product counts against every limited category it appears in.

How it behaves:

A pre-order counts against the slot of its collection time, not when it was placed — so orders for later book kitchen load where it actually lands.
When a slot is full you choose what happens: Stop taking orders (the default) tells the guest and offers the next slot with room (they can pre-order for it) — and on the online schedule-for-later picker, full slots show as Full and can't be selected. Or Keep accepting with a wait-time warning — every order still goes through (and every slot stays selectable), the guest is just told it may take longer than usual.
Order types pacing can stop picks which orders a full slot may refuse: dine-in, takeaway (the kiosk's walk-up orders), collection and/or delivery. Anything unticked is never stopped — it always goes through, with the wait-time warning when the slot is full. Tick Collection but not Takeaway and pre-order collection slots fill and close while the kiosk keeps taking walk-up orders — those customers just see "your order may take longer than usual" before they pay.
The till is never blocked. Walk-in and staff-taken orders always go through — but they do count towards the load, so a busy shop floor slows online ordering, which is the point.
Deliverect channel orders also count as load but are never bounced (those platforms manage their own throttling).

Leave everything empty to switch pacing off.

A status banner at the top of the page tells you what pacing is actually doing right now, from the saved settings — off, active with a wait-time warning only, or an active hard limit (with the order types it stops and the configured capacity). It updates the moment you save, and flags unsaved changes while you're mid-edit.

Message wording

Below the pacing settings, Message wording lets you customise the exact words guests see when pacing affects their order. Each message has a sensible default (shown as the placeholder in each box) — leave a box empty to use the default, or type your own to override it. The messages cover: a slot nearly/fully full, the longer-wait warning, the "next available slot" suggestion, and the kiosk/online variants. Only Next available slot has a placeholder — {nextSlot} — which is replaced with the suggested time (e.g. "14:30") when the message shows. Wording is saved on its own, separately from the pacing limits above.

Operations

Order types

Switch each way of ordering on or off for this store:

Dine in — table-QR ordering and the kiosk's "eat in" option. Switching it off shows table QR codes a polite "order with a member of staff" message.
Takeaway & collection — kiosk walk-up orders and online orders collected in store.
Delivery — courier delivery at online checkout. This also needs the Nash integration connected (see Integrations).

When dine in and takeaway are both on, the kiosk asks every customer "eat in or take away?" before they order. With only one on, it skips the question. Changes apply to new orders immediately — the server refuses order types that are switched off, so a stale browser tab can't sneak one through.

Pre-orders

Control when customers may place an order for later (this is about placing, not your trading hours):

There are two separate windows here — keep them straight:

The collection/delivery time the guest books (the "collect window") always has to be inside your opening hours. The slot picker only ever offers times you're open, so a closed day or a closed hour simply never appears.
When the guest is allowed to press pay (the "place window") is what the settings below control. Normally they can only order while you're open; Accept orders while closed lifts that so they can order ahead even while you're shut.
Orders for later — on by default. At online checkout guests choose ASAP or Schedule for later — scheduling is date-first: pick a date, then a time slot (see Ordering ahead under Online Ordering). Only dates and times inside your opening hours are ever offered, so a closed day simply doesn't appear.
Accept orders while closed — the spec's "24 hours a day" option. With this on, a guest can place a pre-order even while you're shut — e.g. late on Sunday evening they book a Tuesday-lunch collection. The collection time still has to be inside opening hours; this only lifts the "we're closed right now" block at checkout, it does not let anyone collect while you're shut. With it off, ordering is only possible while you're open. (The menu shows "Closed · order ahead for later" and checkout goes straight to the schedule picker.)
How far ahead — bookings accepted up to this many days in advance (1–60, default 7).

Pre-ordered items still reach the kitchen when the order is paid — a "fire at the right time" schedule for the KDS is a planned follow-up, so keep an eye on the fulfilment time shown with each online order.

Kitchen display (KDS)

Use kitchen display screens — the store-wide switch. Off means this store runs no kitchen-display: nothing shows on a prep screen, kitchen wait-time stops recording, and orders never wait on the KDS to be marked "ready". Printed tickets are unaffected — turning the KDS off does not stop tickets printing.
Per station — which items appear on kitchen screens is decided by their station (the same concept that routes printing), in Settings › Printers & routing: each station has a KDS switch. One mechanism, no conflicting settings — an item shows on the KDS when the store switch is on and its station's KDS is on. Items with no station follow their kind (drinks → BAR, everything else → KITCHEN). Hidden items don't appear on prep screens, don't count toward kitchen wait-time, and don't hold an order back from "ready" — while their tickets still print exactly as before.

Devices

Every till and KDS screen that signs in at this store appears in the roster with when it was last seen. There's no screen limit — to add a screen, just sign the device in. When hardware is replaced or lost, Retire it here; a retired device can be reactivated if it comes back.

Retiring takes a device off the roster but doesn’t cut it off: anything it has already captured — orders, card payments taken on its reader — still syncs, so nothing is lost. If a retired device keeps being used, it shows Retired · still syncing in red. That usually means the wrong till was retired, or the old one is still in service: reactivate it, or take it out of use. “Last seen” updates whenever a device syncs, not just when it starts up.

Till

The home screen of every till device, configured per iPad — different tills do different jobs.

Order-type buttons — Quick sale, Collection, Delivery and Dine in. Tick what each device shows, set the order with the arrows, and pick a size (S/M/L). A collection till might show only Quick sale and Collection; a floor iPad might lead with Dine in.
Venue default vs per-device — the venue default applies to every device without its own layout; give a device its own layout to override it, or Use venue default to fall back. Copy from pulls another device's layout across in one tap.
Devices appear by the names on the Operations roster (Main Till, Bar Till, …), so you always know which iPad you're configuring. Tills pick up changes on their next launch and keep the layout cached for offline.

How the menu category buttons are arranged on the till — separate from the order-type buttons above.

Layouts — create named arrangements (e.g. "Service", "Bar till"): drag categories into order, size each button S/M/L, and star the prominent ones (highlighted on the till). Top-level categories only — subcategory rows and the products inside a category keep their menu order.
Preview & publish — the preview pane shows your unpublished changes exactly as the till will render them; nothing reaches a till until you press Publish, and then every affected till updates within seconds.
Who uses which layout — one layout is the store default (applied to every till); assign a different layout to specific tills in the table beneath, or set a till back to the store default. A removed layout's tills fall back to the default automatically.
A category the layout doesn't know (added later) still shows, appended at the end — a layout can never hide a category.

Light or dark theme is no longer set here — the till automatically follows each device's own appearance setting (the iPad's system light/dark mode), switching live when the device does. There's nothing to configure.

What the buttons do on the till: Quick sale opens a counter order immediately, as now. Dine in opens the table plan — a table must be chosen before the order exists. Collection and Delivery first capture the customer (name, phone — plus a verified address for delivery) and the requested time in a pacing-aware slot picker: free slots are plain, busy slots show amber, full slots show red and need a manager override, which is recorded on the order. The details stay visible on the check and print on tickets and receipts per your ticket layouts.

Shared tables

Any till can open any table — orders aren't tied to the device that started them. The floor plan updates live across every till (occupancy, running total, covers), and while someone is actively working on a table the other tills see "OPEN · name" on its tile. Opening that table shows who has it and since when; a manager can take it over, and the override is recorded. The hold releases automatically when the order is saved, paid, closed — or within about 90 seconds if the other till loses connection or goes to sleep. Offline tills can't be blocked (the till keeps working without internet by design); their changes merge safely when they reconnect.

Coursing

Dine-in table service runs on flexible courses — Course 1, Course 2, … with an Add course button on the till, instead of fixed Starter/Main/Dessert labels. That suits tasting menus, sharing plates and casual service equally. Staff fire each course when the table's ready, move items between courses (long-press an item on the check), and can rename a course on a live order (long-press its chip — "Course 2" becomes "Cheese").

Course-based table service — the master switch. On (the default): tables get the full course workflow — course chips, held courses, Fire away. Off: the till never shows courses and Save & Send sends everything to the kitchen straight away, for stores that plate and serve without coursing. Turning it off loses nothing below — names, drinks position and exclusions all return when you switch back on. Tills pick the change up within a few minutes, so flip it between services, not mid-shift.
Default course names — preset labels for the till's chips, in order (the first is Course 1). Leave empty for plain "Course 1, Course 2, …". A rename on a live order always wins over the preset for that order.
Drinks position — drinks (and anything else outside courses) group into one block on the virtual check so staff can reference them at a glance; choose whether that block sits at the top or bottom. The same position applies on kitchen tickets when drinks print to the same printer as food — drinks routed to their own bar printer are unaffected.
Products outside courses — drinks and BAR-routed products always sit outside the course structure. Add prep stations or menu categories (retail, merchandise) to exclude more. Individual products can be forced either way from their edit drawer on the Products page (Dine-in coursing: Automatic / Always in courses / Never).

Kitchen tickets separate each course under a bold heading, so the kitchen sees course breaks at a glance. Fuller control of ticket formatting is coming with the ticket layout editor.

Online Ordering

What guests see when ordering online:

Preset preparation time (minutes) — the expected preparation time for ASAP orders. Guests see it as "Ready in ~N min" in the ordering app header, again at checkout when ASAP is selected, and on their order confirmation. Leave it blank to show no time. This is a promise to the guest, not a kitchen schedule — pick a number you comfortably hit at your busiest. (Orders scheduled for a later time show that time instead.)

Links & embed

Each store has separate live URLs for online ordering (this page) and the kiosk (its own Settings › Stores › Kiosk section), each with:

Open live site — the customer-facing page exactly as guests see it, with your current menu, branding, opening hours and availability.
Copy link — for your website navigation, socials, Google Business profile or emails.
Copy embed (full page) — a responsive iframe for full-page website integration.
Copy embed (button) — a styled "Order online" button/link that opens the ordering page in a new tab; the best fit for app web-views and mobile.
QR code — view and print (table QR codes for dine-in live under Table layout).

Keep the two links separate: the kiosk URL is for the in-venue self-serve device (it resets between customers) — don't publish it on your website. Links always reflect the live configuration; changes to menus, branding or hours show as soon as they're saved.

Ordering ahead — the date-first flow

When pre-orders are on, online checkout asks when: ASAP (the default, showing your ready-in estimate) or Schedule for later. Scheduling is date-first:

The guest picks a date — only dates you're actually open within your "how far ahead" window are offered. Closures and special hours are respected automatically, so a bank holiday you've closed simply isn't listed.
Then a time slot for that date, at your pacing slot size (5/10/15 minutes) and only within that day's opening hours. With pacing set to Stop taking orders, slots already at capacity show as Full and can't be picked; with the wait-time warning behaviour they stay selectable and the guest is warned before paying.
The menu updates to the chosen date and time — menu and category schedules, product time windows and daily stock limits are all evaluated for that moment, so a Saturday-only special can be ordered on Thursday for Saturday. Anything in the basket that isn't available at the newly chosen time is removed with a message. Live stock counts stay current: a product out of stock right now still shows sold out whatever date is picked.

The confirmation page shows the booked collection time, and the order counts against the pacing slot and daily limits of its collection/delivery date — not the day it was placed. The server re-checks the chosen time at placement, so a slot that filled while the guest was paying is politely refused with the next free slot suggested.

Email order updates

Guests ordering collection online can leave an email address at checkout (it's optional — the field says "we'll email you order updates"). When they do, they're emailed automatically at three moments:

Order confirmed — when their payment goes through, including the collection time or the ready-in estimate.
Being prepared — when the kitchen starts their ticket on the KDS.
Ready for collection — when every item on the order is marked ready.

Each update is sent at most once per order. Guests who leave the email field blank simply get no emails — nothing else changes. Walk-up kiosk orders, dine-in and delivery orders don't send emails. A per-store on/off switch for these emails is a planned follow-up.

Whether guests can order at all (dine in, takeaway, delivery) is controlled under Operations; delivery radius and cut-off times are planned follow-ups for this page.

Kiosk

Settings › Stores › store › Kiosk holds the in-venue self-serve kiosk's live link, embed code and QR, plus what the kiosk asks for at checkout.

Checkout

Require customer name — off by default. When on, the kiosk asks the customer for a name before the pay buttons unlock, and the order can't be placed without one (the server checks too, so an older kiosk page can't skip it). The name is saved against the order and shows wherever a collection customer's name already does: the Hub orders list, the till's order view, kitchen screens ("Kiosk — Eat in · Sam") and the Customer name field on kitchen tickets and receipts. Kiosk orders stay kiosk orders in reports and filters — they don't become online collection orders.
Offer "Pay at counter" — on by default. When on, a kiosk with no card reader linked offers Pay at counter next to Pay by phone: the order is placed unpaid and the customer takes the order number to the till, where staff settle it. Switch it off and the kiosk offers Pay by phone only. If a card reader is linked, the kiosk always shows Pay by card in that slot instead, so this switch makes no visible difference. Reload the kiosk page after changing it. Unpaid kiosk orders (for example, a customer who gave up on phone payment) still appear in the till's counter queue either way.
Use the name setting for collection-style service where staff call names rather than numbers. The order number still prints and shows on the kiosk's confirmation screen.
Tickets: an eat-in kiosk order prints on the store's dine-in printer routes and ticket layouts under a "Dine-in" heading; a take-away kiosk order prints on the takeaway ones. (The till's own counter sales keep printing on takeaway rules.)
Tills and "Pay at counter": a kiosk order that was given a name now carries customer details, and till builds older than the kiosk-name update don't list named orders in their counter-payments queue. Those older builds also print named kiosk orders with a collection-style heading. Update the tills before switching this on.

Table Layout

Draw your restaurant floors so the till shows tables where they really are.

Floor plans

The page lists the store's floor plans — Ground floor, First floor, Terrace… Add, rename or remove plans here, and open one to draw it. Every table lives on exactly one plan; a plan that still has tables can't be removed (move or delete them first). Plans are the physical pages of your store; zones stay as service-section labels within them.

The floor editor

Each plan is a scale canvas that always fits your screen — faint squares are 25 cm, bold lines mark 1 m. Zoom in for fine work.

Add table + drops a new table on the plan; drag it into place (movements snap to 5 cm, so dragging feels free but stays tidy).
Select a table to get corner handles (resize) and a stalk above it (rotate, in 15° steps — hold Alt for free rotation). Arrow keys nudge the selected table; hold Shift for centimetre moves. ⌘Z / Ctrl+Z undoes your last change.
The panel on the right edits the selected table: label, zone, seats, shape (square / rectangle / circle), exact size and position in centimetres, rotation — and, when you have several plans, a Floor plan selector that moves the table to another floor immediately.
Every table shows its seat count under its label on the canvas, so you can check covers across the whole floor at a glance without selecting each table.
Duplicate copies the selected table (next free number, same shape and size). Delete removes it from the floor — its order history is kept, and a table with an open order can't be deleted until the order is settled.
Moves, resizes and edits are not live until you press Save layout — the "Unsaved" marker reminds you. Adding, duplicating, deleting and moving between plans apply immediately.

The till shows the same plans: a chip per floor (hidden when there's only one), each table at its drawn position, size and angle, coloured by whether it's free or has an open order. A store with no drawn layout falls back to a simple grid of tables on the till. Tills need the current app update to show multiple floors — until every till is updated, stick to one plan per store.

The table list

Switch to Table list for a bulk overview: every table with its zone and seats, a quick Print QR for table-ordering codes (also available from the floor editor's side panel), and an add-table row for quickly entering many tables — then arrange them on the floor.

Printers & routing

Where order tickets print. The page has four tabs, in the order you set a store up: Hardware (what's in the building), Routing (where does this order print), Tickets & receipts (what it looks like on paper) and, for kitchen-screen stores, Prep stations. A store with no printers yet opens on Hardware; otherwise on Routing. The status at the right of the tabs — 3 printers · all printing or 1 printer failing — comes from the tills' print history, the same signal as each printer's Status.

Stations

The places tickets are prepared — Kitchen, Bar, Pass, Dessert, Front Counter. Stations are shared across all your stores; every product picks its station on the product page (products without one route by kind: dishes to Kitchen, drinks to Bar). Renaming a station updates every product that uses it — tickets already on the kitchen screen keep the old name until they clear. Removing a station leaves its products routing by kind until you re-assign them.

Printers

Each store's receipt and ticket printers. Connect and test printers on a till — open Printers & setup on the device, scan, and bind; the printer then appears here automatically. The admin can't reach your store's network, so test prints always run from a till. You can also add a printer by IP address here if you know it (Star and Epson LAN printers).

Give each printer a fallback: if it's offline when a ticket is sent (after the till's retries), the ticket automatically re-prints on the fallback instead — one hop only, and the failed job stays visible in the till's print queue.

Set each printer's paper width (80 mm or 58 mm) to match the roll it takes — tickets, receipts and branding images then print at the right size for that roll, and the layout preview can show you the true width.

Is it printing?

The Status column shows what actually happened to the store's tickets, taken from the tills' print history:

Last print OK 2 min ago — the most recent ticket sent to this printer came out.
FAILING — 12 failed since 17:11 · Connection refused — the most recent tickets did not print, with the reason the till reported. Check the printer is switched on, has paper and is on the network — and that its address hasn't changed (below).

The last test print result is shown underneath as a secondary line. A printer with no tickets yet shows its test print result only. If any printer has failed three or more times in the last 30 minutes, a banner says so at the top of this page and on the Today dashboard, until a ticket prints again. The organisation's owners are also emailed — what failed, since when, and what to check — at most once an hour per printer while it keeps failing, so you hear about it even when nobody is looking at the Hub.

When a printer's address changes

Printers get their network (IP) address from your router, and a router restart or a few days switched off can hand a printer a new address. Tickets then can't reach it and every print fails.

It usually fixes itself (with the latest till app). Each printer is recognised by its hardware (MAC) address, shown under its IP address once a till has scanned it. When a till scans the network and finds a known printer at a new address, the printer is updated in place — its name, function type, fallback, menu routing and paired tablets are all kept — and every online till switches to the new address straight away. Scanning never renames your printers.
To fix it by hand, use Edit address on the printer's row and enter its new IP address (print a self-test page from the printer to find it). Online tills switch to it straight away. Don't add it again with Add by IP — that creates a second printer with none of the first one's settings.
To stop it happening, ask whoever manages your router to reserve each printer's address (a "DHCP reservation") using the MAC address shown here.

Routing

Every order prints by how it's served, not which device took it. There are four rule sets — Eat in, Take away, Collection, Delivery — and the Where orders come from map at the top of the Routing tab shows which one each surface lands on at your store:

Where the order comes from	Choice	Rule set
Till	table order	Eat in
Till	counter sale (no table)	Take away
Till	Collection (phone order)	Collection
Till	Delivery	Delivery
Kiosk	Eat in	Eat in
Kiosk	Take away	Take away
Online ordering	pickup / scheduled pickup	Collection
Online ordering	delivery	Delivery
Online ordering	dine-in pre-order	Eat in
Table QR	—	Eat in
Deliverect	—	Delivery

Rows only appear for surfaces that are live at the store (the order types under Operations; Deliverect when connected). Click a rule to edit it; every chip that shares the rule lights up, so you can see that editing Take away also changes kiosk take-away orders. Each rule set's editor says the same under Applies to.

Menu routing per rule set: for each Production Centre, tick the menus, categories or products that print there (new products added to a ticked category follow automatically). Ticket behaviour per rule set:

Grouping — a ticket per Production Centre (the standard flow), one consolidated full-order ticket per printer, or a ticket per item.
Summary ticket printer — one full-order ticket on top of the station tickets: the pass for eat in, the packing bench for take away and delivery.
Production tickets print automatically — whether tickets print when items are fired.
Auto receipt — whether a receipt prints automatically when the order is paid. Delivery orders arrive already paid, so their receipt prints alongside the tickets as a docket. Receipts always come out of the till's own receipt printer.

Same as Take away. Collection and Delivery each have this switch. While it's on, the rule set uses Take away's menu routing and ticket behaviour, and its editor is read-only — tills get the combined rules automatically, whatever version they run. Switch it off to give the rule set its own routing: Take away's current routing and behaviour are copied across as a starting point (nothing is lost; per-till overrides are never copied), and from then on the two are independent. Until you set Collection up, it is the same as Take away; Delivery starts independent.

Per till station — the Summary Tickets and Auto receipt matrices under the editor are overrides for one tablet and one rule set; they are never inherited or copied.

Tills pick up routing and behaviour changes within seconds of a save; mid-service changes may take a moment to reach the kitchen.

Keeping routing honest. Menu routing is saved as the menus, categories and products you tick. When one of those is later archived — or a printer is removed — it drops out of every order type's routing automatically, and a cell left with nothing live is cleared (so collection falls back to the takeaway rules as normal). A Production Centre whose badge reads 0 products · archived selection was saved against menus that no longer exist: open Select menu routing, tick what should print there and Save — or Save with nothing ticked to clear it.

Online, kiosk, table-QR and Deliverect orders print automatically through these same rules as soon as they're confirmed, via any signed-in till — see Printing orders from other channels.

Receipt branding

The images this store can print on customer receipts: a business logo, an optional secondary logo (an award, a sister brand) and an optional promotional image. Upload a JPEG, PNG, WebP or SVG (2 MB max) — or press Use organisation logo to bring the logo from Settings › Branding across in one click.

Receipt printers are one-colour devices, so every upload is automatically optimised for thermal printing: resized to the print head and converted to pure black and white. The preview you see is that print version — exactly what comes off the roll. Bold, high-contrast artwork prints best; if an image is likely to print poorly (too small, too light, or photo-like), a warning tells you at upload rather than after a wasted roll.

Uploading an image doesn't print it anywhere by itself — place it on a receipt in Ticket layouts below. Images never appear on kitchen or station tickets unless you deliberately add them to those layouts. Tills download the images when they sync, so branded receipts keep printing offline.

Receipt QR codes

QR codes to print on customer receipts — for Google/TripAdvisor reviews, a mailing-list sign-up, a loyalty programme, online ordering, or any web address. Codes are generated from the web address you enter (you don't upload an image), so the preview is exactly what prints and we can tell you precisely when a code is too small to scan.

For each code, set:

Name — how you'll recognise it in the list and pick it on a layout.
Web address — where the code sends the customer (any http(s) address).
Position — top of the receipt, beneath the order details, above or below the totals, or the very bottom.
Size — the printed width. The preview shows a warning if the code would be too small to scan reliably on your printers' paper — make it bigger, or shorten the web address.
Text above / below — an optional prompt like "Leave us a Google review" or "Scan to view your receipt".
Active and an optional campaign start / end — pause a code without deleting it, or run one only for a date range.

Save as many as you like — a review code, an online-ordering code, a seasonal campaign — then choose one per receipt in Ticket layouts below (dine-in receipts might show a review code, collection receipts an online-ordering code). One QR per receipt keeps it uncluttered. Tills generate the code themselves, so QR receipts keep printing offline and campaign dates are honoured at print time.

Ticket layouts

What actually prints on each ticket — and how it's sized. Pick an order type (dine-in / takeaway & collection / delivery) and a ticket (station tickets, the customer receipt, or the summary ticket); station tickets can additionally have a layout per station (a big-type kitchen layout, a compact one for the bar). Everything starts on a sensible default — the badge shows Default until you save a customisation, and Reset to default takes you back. The customer receipt starts on a complete recommended layout (store name and contact, the order, itemised purchases and totals, payment method) so you're customising a real receipt rather than building one from scratch.

Information on the ticket — every field (order number, table, covers, staff, store address, store phone, customer details, collection/delivery info, payment status…) can print in the ticket header (above the items), in the ticket footer (below the items — after the totals on receipts), or not at all. Store address and phone come from the store's own details (Stores); leave them off a kitchen ticket and on a customer receipt. Use + Header / + Footer to place a field, the Header/Footer button on a row to move it between sections, and the arrows to set the order within each section. A kitchen ticket can lead with the table and order number while the waiter, order time and till name sit at the bottom. The fields on offer follow the order type — collection tickets offer collection time and phone number, delivery tickets the address and delivery time. A field with no data on a given order is skipped, never printed blank.
Footer message (customer receipts) — a short message printed at the very bottom of the receipt, replacing the standard "Thank you". Leave it empty to keep the default.
Branding images — place the store's receipt branding images on this ticket: top or bottom, left/centre/right, and how wide they print. One tick per image; a slot with nothing uploaded can't be placed.
QR code (customer receipts) — choose one receipt QR code to print on this receipt. Its position, size and text come from the code itself, so different receipts (dine-in, collection, delivery) can carry different codes.
Sizing & spacing — font size, line spacing, spacing between sections, and space at the top of the ticket. The top space matters most: it's blank paper above the print so a ticket-rail clip never covers the order.
Font weight — Normal or Bold for the whole ticket. Thermal printers can render normal-weight text faintly; switch a layout to Bold and every line prints heavier and darker, with headings and totals stepping up further so they still stand out.
Drinks position & course separator (station and summary tickets) — where the drinks block sits and how courses divide: a bold heading, a line, just spacing, or nothing.
Item order (station and summary tickets) — As entered prints items in the order staff rang them; By category prints them in your menu's category order so the ticket reads like the menu: on coursed orders items sort by category within each course, and on non-coursed orders they group under category headings. Customer receipts always keep entry order.
Also apply to — save the same layout to other order types or stations in one go, the quick way to keep layouts consistent.

The preview updates live as you change things and is a faithful guide to structure and proportions — the Preview roll toggle shows it at 80 mm or 58 mm width to match your printers. For ground truth, run a test print from a till (Printers & setup on the device): test prints use the store's active layout and branding, so what comes off the printer is exactly what orders will look like.

Integrations

Each store connects to outside services from its Integrations section — accounting (Xero), delivery channels (Deliverect), payments (PayPal, Dojo, Zettle) and couriers (Nash). API keys and secrets are never entered here — they live in the platform environment; this screen only holds public identifiers (a merchant ID, a location ID). Where you sign in to a provider (PayPal, Xero), you do it on the provider's own pages, and AccentPOS keeps the resulting sign-in encrypted — it's never shown on screen.

The section is a catalogue of every integration AccentPOS offers, grouped by category — including ones that are Locked, Coming soon or Disabled by AccentPOS, with a way to request them. Those states and the request form are explained in Integrations; the statuses below are for the integrations available to you.

The status column always tells the truth about what the system has actually verified:

Not connected — nothing is set up.
Reference saved — you've stored the provider's identifier, and it will be verified on first use (for example, the first Deliverect order arriving). Saving a reference never claims a connection that hasn't been proven.
Onboarding started — a provider sign-up is under way but not finished: PayPal's onboarding, or a Xero sign-in waiting for you to choose an organisation.
Connected — the system has genuinely completed a connection: PayPal finished its onboarding, Nash accepted the store as a pickup point, Xero signed in and its organisation was read back, or a saved reference was verified by real use.
Error — the last attempt failed; the note on the row says why (for Xero, usually that the sign-in expired and needs reconnecting).

Refreshing the page always shows the true state — there's no way to mark something connected by hand.

How each provider connects:

PayPal — Connect with PayPal opens the seller-onboarding panel: you sign in on PayPal's own secure pages and approve the connection; we never see your PayPal password. Once complete, the row shows your merchant ID, whether it's the live or sandbox environment, and the connection date. Disconnecting (manager PIN) stops online and kiosk PayPal payments for the store. The row also shows whether Apple Pay and Google Pay are Active on the store's PayPal account — a wallet that isn't Active won't appear as a working button on the scan-to-pay page. If one isn't Active, press Update PayPal permissions (the store signs in to PayPal and approves again), then Refresh status.
Nash — Connect → registers the store's address and phone as the courier pickup point; General must have both filled in first. The drawer holds the delivery toggle and kitchen prep time.
Xero — see Xero below.
Deliverect / Dojo — save the reference; it's verified the first time it's used.
Zettle — the card reader pairs at the till (Hardware setup on the device). This row only stores your account reference for reporting — there's no sign-in here.

Disconnecting any provider needs a manager PIN, and the row records who did it.

Xero

Xero receives each trading day's sales as one invoice from the contact POS System: a line per accounting group and VAT rate, plus service charge.

Connecting

Press Connect with Xero on the Xero row. Xero's sign-in page opens.
Sign in to Xero, tick the Xero organisation for this store and press Allow access.
You come back to Integrations and the Xero drawer opens. If you ticked more than one organisation, choose the one this store posts to and press Use this.

The row then reads Connected with your Xero organisation's name. Cancelling at Xero changes nothing. If the row later shows Error — Xero sign-in expired, press Reconnect Xero and sign in again; your settings are kept.

Account checklist

The drawer lists every Xero account code the cash-out will post to and checks each one against your Xero organisation:

Found — the account exists and is set up correctly.
Missing — there's no active account with that code in Xero. Add it in Xero, or change the code under Accounting.
Tax rate differs — the account's default tax rate in Xero isn't the VAT rate of the sales posted to it, so Xero would record the wrong VAT. Change the account's tax rate in Xero.
Payments off — a cash, card or voucher account doesn't accept payments. In Xero, turn on Enable payments to this account for it.

AccentPOS never creates or changes accounts in your Xero. Cash (40600), card (40610) and voucher (40620) accounts only matter when Approve and record payments is on.

Sending days to Xero

Send each day to Xero automatically — off until you switch it on. Once on, each trading day goes to Xero about 30 minutes after the store's day closes (set by Day closes at under the store's Z report settings — see Z reports). It starts with the day you switch it on. If AccentPOS couldn't reach Xero for a while, it catches up the last three days.
Approve and record payments — off: each day arrives in Xero as a draft invoice for your bookkeeper to check and approve. On: the invoice arrives approved, with the day's cash, card and voucher takings recorded as payments against it.
Push cash-out to Xero — sends the last closed trading day now. Before you connect, the same button previews the invoice without sending anything.

Each day is sent once. Pressing the button again, or the nightly run, never creates a second invoice for the same day. Last push shows the most recent day sent, whether it went as a draft or approved, and the reason if it failed.

Disconnecting (manager PIN) removes this store's connection in Xero, deletes the stored sign-in and stops the nightly push. Invoices already in Xero stay there.