Mews POS / ePOS

Product Documentation

Mews POS is the point of sale for hotel food and beverage, purpose-built for hotel restaurants, bars and retail outlets. It runs on Android devices and Mews terminals, posts revenue and room charges directly into Mews Operations and processes payments through Mews Payments. POS Advanced adds digital ordering and inventory management. 

 

In this article you can learn about how to:

 

01 Get started

1.1 Prerequisites

For PMS-integrated deployments, Mews Operations must be live, or onboarding in parallel with a planned setup sequence, and Mews Payments is required for both online and terminal payments at the POS. POS-only deployments without a Mews PMS are possible; automated room charging is not available without the PMS. 

1.2 How onboarding works

  1. Outlet design: Define outlets, such as restaurants, bars, pool bars, shops, floor plans, menus and dayparts. 

  1. Product and accounting mapping: POS product categories are mapped to PMS accounting categories and tax rates. Items sent from the POS must include an AccountingCategoryId; items without one default to the service's accounting category. 

  1. Hardware: Terminals and printers or kitchen display endpoints are connected, and routing is configured per outlet and product group. 

  1. Payments: Mews Payments and Mews terminals are configured for card, room charge and mixed tenders. 

  1. Training and go-live: Staff training on order taking, course firing, tenders and shift management, then live service. 

1.3 Indicative activation timeline

Typically, 2 to 4 weeks from completed intake for standard single-property configurations, driven mainly by hardware lead times and menu build. A restaurant can go live ahead of the hotel PMS where required; this needs a specific setup sequence agreed with the onboarding team.

1.4 What the Partner needs to provide

  • Menu content, pricing, modifiers and recipes; for inventory, where POS Advanced is used 

  • Outlet floor plans and printer/ kitchen display locations 

  • Tax and accounting mapping decisions per outlet and product category 

  • Android devices where staff use their own ordering hardware. Mews terminals can also be used as combined order-and-pay devices 

1.5 Onboarding contact

Team responsible 

Mews POS onboarding team 

Support during onboarding 

Mews Help Center: help.mews.com (Mews POS section) 

2.0 Product Capabilities

2.1 What's included in the license

Capability/ Feature 

What it does for the Partner

Status 

Order taking and floor management 

Tables, floor plans and multi-course orders, with items sent to kitchen and bar in waves controlled by staff. 

Generally Available 

Multi-outlet operation 

A single device can switch between outlets, such as restaurants, bars, pool bars, and shops. Each outlet keeps its own floor plan, menus, printers, and reporting. 

GA 

Kitchen and bar routing 

Tickets routed to printers or kitchen display endpoints based on outlet configuration and product-level mapping. 

GA 

Room charge and PMS posting 

Charges are posted directly to the guest folio in Mews Operations. Guests must be in-house or have Paymaster account classification. The Cashlist customer classification can be used to prevent room-charge postings. Key card room charging is supported with Onity, Salto and Visionline key systems. 

GA 

Mixed tenders 

A single check split between room charge, card and cash, each recorded with its own payment method and accounting mapping. 

GA 

Service charges and tips 

Configured separately with their own tax and accounting mappings, supporting clear allocation of gratuities and mandatory charges. 

GA 

Integrated payments 

Card payments via Mews Payments on Mews terminals, including digital tipping and tableside order-and-pay on all-in-one devices. 

GA 

Multicurrency at the POS 

Guests pay in their home currency on eligible setups; enabled automatically for properties using Mews POS and Mews Payments in eligible markets. 

GA 

Shift and cash management 

Registers and cash drawers per outlet, shift open / close, and per-user shift reporting where required by local rules, for example, Germany. 

GA 

Reporting 

Revenue by outlet, product, time period and staff; top-selling items and F&B performance data. Cross-outlet and multi-property rollups require the POS Open API and an external analytics tool. 

GA 

Fiscal compliance 

Market fiscalization where supported, including German KassenSichV, via Cloud TSE with real-time posting and 10-year record accessibility. 

GA 

Digital ordering, with POS Advanced 

Guests scan a QR code, order and pay online or charge to the room; orders are created in the outlet like staff-entered orders. Requires Mews POS as the fulfilment layer. 

GA – add-on 

Inventory management, with POS Advanced 

Three-layer model of purchasable items, inventory items and sellable products; deliveries increase stock and recipes deplete it on sale, with low-stock alerts and exports. 

GA – add-on 

2.2 Available as add-ons

POS Advanced adds Digital Ordering and Inventory Management on top of core POS. Mews terminals are purchased separately with a minimum 12-month term.  

How to purchase: contact your account manager. 

2.3 Marketplace integrations

For the full integration catalogue, see the Mews Marketplace: https://www.mews.com/en/hospitality-software-marketplace.  

Module-specific integrations include F&B inventory and procurement platforms, for example, FutureLog, Apicbase, and a POS Open API for business intelligence, inventory and table reservation partners.

2.4 Known limitations

  • Mews POS focuses on hotel-centric F&B; it does not cover fine-dining course orchestration, wine pairing engines, deep kitchen display priority rules or drive-thru concepts. 

  • Mews Payments is required; third-party payment providers are not supported at the POS. 

  • Native reporting is per outlet; multi-property and cross-outlet rollups require the POS Open API and an external analytics tool. 

  • Digital Ordering requires Mews POS as the fulfilment layer; it cannot front a third-party POS. 

  • Key card room charging is limited to Onity, Salto and VisiOnline key systems. 

  • Outlet bills sent from POS to Mews cannot be reopened or corrected; corrections must be sent as new items with negative values to balance the original. 

  • Items posted from POS without an accounting category are reported under 'None' in the Mews Accounting Report. Correct mapping in the POS is the property's responsibility. 

  • North America: Mews POS is in beta, with general availability planned for September 1, 2026. Quebec excluded at launch. Inventory management and digital ordering are not part of the initial North America launch. 

  • Country availability varies; check the published availability information for market-specific exclusions and fiscal requirements. 

03 User Interface

3.1 Interface overview

Staff use the Mews POS app on Android devices or on all-in-one Mews terminals; guests interact through digital ordering, via QR code where enabled. Configuration, mapping and reporting are managed alongside Mews Operations.

3.2 Key Partner workflows

  1. Open a table, take a multi-course order and send tickets to kitchen and bar 

  1. Settle checks by room charge, card or mixed tender, with digital tipping 

  1. Manage shifts, registers and cash drawers per outlet 

  1. Track stock and run F&B performance reports, with POS Advanced

3.3 Access methods

Web app 

Configuration and reporting via Mews Operations; service operation runs on devices 

Mobile 

Yes. Mews POS app on Android; all-in-one Mews terminals run the POS app natively 

Embedded in Mews OS 

Yes. Revenue, room charges and accounting post into Mews Operations 

API access 

Yes. POS Open API. See Section 06 

3.4 Accessibility

WCAG 2.1 AA is the Mews default standard for web surfaces. 

04 Deployment & Updates

4.1 Deployment model

Deployment type 

Mews-managed cloud with the POS app installed on property-owned Android devices and Mews terminals. 

Deployment regions 

Available across EMEA with North America in beta; General release planned September 1, 2026.  

For Country-level availability and exclusions, see the published availability page. [Confirm live link with Legal Ops before publishing.] 

Environment types 

Production and Demo/ sandbox 

4.2 How updates are delivered

Cloud services update continuously with no Partner action. The POS app updates via managed distribution to devices; terminal firmware is managed by Mews and the payment processor.

4.3 Update cadence

Feature releases: Continuous for cloud services; app releases ship regularly.  

Security patches: As required, applied by Mews without advance notice.

4.4 Does the Partner need to do anything after an update?

No Partner action is required for standard updates. Properties should keep POS devices powered and connected, so app updates apply; any release requiring configuration review is flagged in the release notes.

05 Release Notes

5.1 Current version

Current version 

Continuous delivery. Mews POS does not carry Partner-facing version numbers 

Release date 

Rolling; latest release notes at https://releases.pos.mews.com (Release notes) 

Type 

Continuous. Feature, minor improvements and security releases 

5.2 Release history

Version 

Date 

Type 

What changed 

Partner action? 

– 

May 26 

Minor 

Four new terminal models; kiosk, countertop, and portable form factors, became available alongside the existing all-in-one lineup. 

No – existing hardware unaffected 

– 

Mar 26 

Minor 

Multicurrency for POS payments launched; enabled automatically for properties using Mews POS and Mews Payments in eligible markets. 

No 

– 

Early 26 

Minor 

Availability extended to Sweden. 

No 

– 

2025 

Minor 

Flat-fee pricing model introduced, allowing unlimited F&B outlets per property under one subscription. 

No – legacy contracts handled by account team 

5.3 Known issues

When a POS invoice is transferred to the PMS, the invoice number passes to the revenue entry via the Notes field, but is not inherited by the processor fee booking.  

Workaround: in the Accounting Report, match fee lines by amount and date. No committed fix date.

06 API & Integrations

6.1 Mews Open API

API available? 

Yes 

API type 

REST, POS Open API designed for business intelligence, inventory management and table reservation integrations, with item-level, timestamped and multi-property data 

Documentation 

Authentication 

Access tokens issued per integration 

Rate limits 

Applied per environment.  

6.2 Standard integrations

FutureLog including inventory deduction, recipes, F&B financial reporting and stock transfers: Partner-configured.  

Apicbase and ProcureWizard for advanced recipe costing and procurement: Partner-configured.  

6.3 Third-party integrations

Integrations with third-party products and services are provided and operated by the relevant third party. Mews does not warrant the availability, performance or continuity of any third-party integration, and third-party integrations are not covered by the Mews SLA. 

07 Related Documents

7.1 Training, specific guidance & additional resources

Mews University learning paths and the Mews Help Center at help.mews.com (Mews POS section).

7.2 Living documents incorporated by reference

Document 

Where to find it 

Terminal comparison and availability 

08 Sub-processors

As contained at https://www.mews.com/en/legal/mews-sub-processors

Was this article helpful?
00



Feedback