EPOS ingests provider evidence, normalises trading facts and proposes explainable operational work. Tevalis setup, catalogue reads, Bookings handoff, bill return and customer order-and-pay have separate readiness and publication boundaries.
EPOS work and evidence
| Section | What operators do |
|---|---|
Work, /epos?section=work | Review counts, investigations, transfers, prep, reorder and PO-draft recommendations; approve, edit, snooze, reject, delegate and record outcome. |
| Evidence | Inspect bounded raw batch evidence, normalisation and corrections; replay a batch when authorised. |
| Connections | Create signed close-of-day connectors and inspect freshness/connection state. |
| Mapping | Map source venues, tills, products, units, taxes and modifiers; maintain operational product thresholds. |
| Settings → Connections | Tevalis setup, encrypted credentials, explicit access checks, catalogue/bill refresh and ordering setup. |
Manual work captures action type, optional product, source/destination venues, quantity/unit, action and reason. Reviewable recommendations do not themselves move stock or send a supplier order. Outcomes stay attached to the source action. Booking prep demand enters this same decision workflow, with freshness, uncertainty, pack and shelf-life evidence.
Close-of-day connectors use one-time credentials and a signed versioned input contract. Raw deliveries are append-only; explicit mappings are required before facts become operational. Corrections create new fact versions and supersede undecided work while retaining decided history. Stale/unmapped data remains visible as retry/manual work. Raw payload access checks every contributing Site.
Tevalis setup, catalogue and bills
Save company, candidate site, Soupy venue and optional price groups as a setup draft. Enter credentials through encrypted ingress and explicitly Check connection. Site discovery and selected-site connectivity are separate results; changing setup/credentials invalidates previous readiness. Saving a setup does not create facts, activate imports or prove a till accepted an order.
A manual catalogue refresh stages private immutable source evidence. Scheduled refresh is opt-in at 15, 60 or 240 minutes and pauses when its authorisation or setup changes. Select variants into the existing Bookings menu library, review prices/options and activate/publish deliberately. Scheduled reads do not import, activate or publish menus. Existing menu versions retain their agreed prices. Unsupported/malformed modifier structures block new selections or dispatch.
Booking detail can prepare one stable reservation for each logical visit part, including mapped pre-orders. Preparation freezes sources; manual send requires current whole-visit Bookings permissions, EPOS settings authority and active provider gates. Accepted, rejected and uncertain results stay distinct. An uncertain submission blocks resending and needs reconciliation.
Opt-in bill sync associates retained Tevalis bills with transmitted Booking parts and the canonical customer's Till bills history. Conflicting/unlinked bills have a review screen and reasoned reassociation. Party spend is not a claim that the booker consumed every item. These bills do not create Soupy Orders, customer commerce counters, marketing consent or Loyalty points. Polling choices are 2, 5 or 15 minutes; a bill opened and closed wholly between discovery polls can be missed. Provider callback activation requires separate configuration and confirmation of authentication and money units.
Dine-in and collection setup
At EPOS settings → Connections → Ordering setup, select a published menu, venue and explicit seller Payment Profile. Set permitted dine-in table numbers, collection till table, notice/advance window, service hours/capacity and Tevalis site/price group/tender. Choosing a seller requires Payments management; menu setup requires the associated Bookings and EPOS authority.
Private previews freeze published prices, modifier choices, service destination, venue timezone and collection instant. They may show a blocked till mapping for review. A preview is not an Order, payment or till submission.
Customer order-and-pay provides publication readiness and explicit per-item, per-service food VAT
classification. Publishing freezes the menu, seller, service modes, tables and tax treatment at a stable
/order/{publicId} address. Draft changes do not rewrite the published offer. Missing seller/legal/tax, source
or provider readiness blocks publication or checkout. The implemented initial paid scope is GBP with a GB
seller; till gross prices do not determine food VAT automatically.
Customer checkout and till delivery
The customer chooses dine-in/table or collection/time, provides name/email and optional phone, and builds a server-priced basket. Different modifier choices stay separate lines. Canonical food Orders use EPOS as the source and shared seller payment confirmation. An ambiguous checkout retains its exact request and private token; starting another requires closing the unused attempt safely. Order status uses the same private access and distinguishes unavailable access from a payment result.
Verified payment creates a durable paid-order queue. An authorised operator sends the frozen order only after fresh source/payment/provider checks. The calculation and submission stages are separate. Accepted or uncertain submissions cannot be resent; a calculation-only interrupted attempt can be recorded without pretending a submission occurred. Till acceptance does not prove kitchen printing, preparation or collection readiness.
Tevalis checkout/write/certification gates and provider acceptance remain independent from implementation. Automatic dispatch currently has a simulator adapter for the separate test deployment; it must not be described as live Tevalis automatic ordering. An unavailable public journey does not fall back to an unpriced order, a default table or a second charge.
Permission and settings reference
epos.view reads permitted work/evidence; epos.ingest controls ingestion; epos.operate controls operating
decisions. epos.settings.view and epos.settings.manage govern connection settings. Cross-module booking,
seller, customer and menu permissions remain required at their original source. General, Trading day and
Mappings settings are shells; Connections mounts the implemented Tevalis controls. Connector credentials
disappear from a retained view when their exact authority is lost.