MODR

The POS should help.Not take over.

Take the order. Send to the kitchen. Split the check. Get paid — in one operational surface, built for service.

Operational surface for
RestaurantBarCaféHotelArena & events
01

During service

Everything you need in front of you.

The active check on the left, products in the centre and payment at the bottom. Large planes, sharp edges — the same language as the POS.

On the floor

Check, kitchen and payment in one rhythm

Staff see what is open, what needs to go out and what remains — without changing workspace mid-service.

In the office

Menu and ops without interrupting the house

Prices, permissions and devices are managed centrally. The floor gets what the night needs — nothing more.

After close

The same numbers when you reconcile

Orders, payment status and receipts stay connected, so discrepancies are easier to understand when service ends.

Three moments

Same POS. Different pressure.

01
SalesBar mode

Active check and products on one surface.

02
TablesThe floor

Open tables and what is waiting — at a glance.

03
PaymentSplit check

Multiple payers without losing the rest.

MODR Cloud

An ops signal board — not a SaaS dashboard.

Products, prices, staff and devices are managed from the office. For multiple outlets: what is shared, and what stays local.

Explore the product

What you can use now

A working core. Clear status on the rest.

MODR is introduced together with each pilot operator. That is why we show what is in use, what is being verified and what remains on the roadmap.

IN PILOT

POS & payments

Bar, tables, checks, split payments, payment terminals and clear payment status.

IN PILOT

Quick Sale

Simplified per-device selling surface for fast checkout on iPhone/S1F2/PAX.

IN PILOT

Kitchen & print

Tickets and correction tickets are sent to configured kitchen printers.

IN PILOT

Mews PMS

Room charge to guest folio and optional sales sync — per outlet.

IN PILOT

Open API

Partner REST for menu, Orderhanterare, checks and sales with per-outlet keys and webhooks.

IN PILOT

Cloud & follow-up

Menus, prices, roles, devices, sales and reconciliation in Backoffice.

TECHNICAL PILOT

Accounting records

Account mapping and SIE export are being verified with receiving accounting systems.

See integration status and next steps

MODR Ask · Early access

Ask less. Get the next step prepared.

In Cloud, Ask can summarise operations, explain reconciliation, troubleshoot exceptions, optimise POS layout, simulate pricing and build products and menus from an image, file or instruction — always as a reviewable draft within the user's permissions.

  • Six workflows: operations, reconciliation, troubleshooting, layout, pricing and menu builder
  • Off by default and enabled per organisation
  • Suggestions and drafts — never automatic publishing
01Operations brief

Sales, open checks and exceptions in one prioritised view.

02Reconciliation

Explains verified differences between sales, payments and recovery.

03POS layout

Ranks products from verified sales — as a draft, never auto-published.

04Troubleshoot ops

Open checks, failed payments and what needs action, with links to the right view.

05Price simulation

Shows the effect of a pricing or layout scenario with assumptions stated clearly.

06Build menu

An image, PDF, text or URL becomes products, categories and a POS layout in a reviewable draft.

MODR in brief

Straight answers.

MODR is in early access. We say what works, what is being tested and how a pilot starts.

What is MODR?

A point-of-sale system for restaurants, bars and hotels. Orders, checks, payments and back office in one operational flow.

Who is it for?

Restaurants, bars, hotels, arenas, events and operators with multiple outlets.

Do terminals and split payments work?

Yes. The pilot supports terminal payments, payment status, multiple payers and check splitting.

Can you send kitchen tickets?

Yes. Tickets and correction tickets go to configured kitchen printers. A full KDS comes later.

What does MODR Ask do?

In early access, Ask can create operational briefs, explain reconciliation, troubleshoot exceptions, optimise POS layout, simulate pricing and build products and menus from an image, file or instruction. Everything stays within the user's tenant, outlet and role permissions — as drafts, never automatic publishing.

Is there an Open API?

Yes. MODR Open API v1 gives partners menu, Orderhanterare, open checks and closed sales per outlet via API keys and HMAC webhooks. Payments and fiscal are out of scope for v1.

How do we start?

With a pilot walkthrough. We map your service, payment flows, devices and what is business-critical for you.

Early access

We are starting with a small number of operators.

A pilot starts with your service, payment flows and how you close the night. Then we set up a test environment and a shared plan.

Not self-service. You get a direct contact — and we are clear about what is ready.