Hotel PMS or restaurant POS: start with the work being sold.

A hotel PMS manages reservations and stays

The PMS needs to understand arrival and departure dates, room or bed commitments, guest allocation, check-in, folios, payments, departure and readiness. The length of a stay affects inventory across several service dates.

For hotel operations, also evaluate housekeeping, maintenance, staff permissions and unresolved booking or payment issues. A restaurant bill alone cannot show whether the guest has a room for tomorrow night or whether that room is ready for the next arrival.

A restaurant POS manages orders and service

Restaurant requirements may include menus, modifiers, tables, order entry, kitchen tickets, bill splitting, discounts, item returns and shift settlement. Stock purchasing, recipes, ingredient consumption and wastage can require an additional inventory scope.

Ask a restaurant-software vendor to demonstrate the exact service pattern: table service, takeaway, delivery or a combination. Do not assume that a system capable of adding an extra charge to a room includes kitchen workflows or ingredient-level stock control.

A room-charge connection needs more than guest lookup

If restaurant charges may be posted to a hotel folio, confirm who can authorize the charge, how the correct in-house guest is selected, what item and tax detail is transferred and how a reversal works. A room number alone may not identify the right guest or folio.

Test a repeated request and an interrupted connection. Staff need to know whether the charge was posted once, remains unresolved or was rejected. Also test a guest who is checking out while an order is being closed, with a documented exception process.

• Confirm which system owns the restaurant sale and its document.
• Define whether the PMS receives an itemized charge or a reviewed summary.
• Keep posting, payment collection and settlement responsibilities clear.
• Review voids, refunds and corrections across both records.

Choose scope for your type of business

A restaurant with no accommodation should evaluate its POS and service workflow directly. A hotel with no food service may not need a restaurant system. A hotel with an independent restaurant should evaluate both operating loops and their connection instead of assuming one dashboard covers everything.

For a small property that only adds occasional packaged items or services to a stay, confirm whether a simpler folio-extra workflow is sufficient. That decision still needs approved item, document and accounting rules; it does not establish a full restaurant POS requirement.

Check stock, permissions and reconciliation separately

If stock control is required, trace a purchase, a sale, a return and wastage through the proposed system. Ask whether it tracks finished items, ingredients or both, and how physical counts and corrections are recorded. Keep this separate from room and bed availability.

Review restaurant cashier, kitchen, reception and manager permissions. At close, staff should be able to reconcile restaurant sales, room postings and payments without treating the same amount as two separate receipts. Bring representative examples to the vendors before agreeing the connection.

What AU Nexus currently offers in this area

AU-PMS is focused on hotel and hostel property workflows. A local implementation exists, and first-client onboarding is upcoming. A production restaurant POS, kitchen-ticket system and ingredient inventory are not confirmed AU-PMS capabilities and are not offered by this page.

AU-Calling Agent is a separate product whose capabilities and availability remain unconfirmed; it is not presented as a restaurant POS. If your property needs restaurant software, retain that requirement explicitly and evaluate a dedicated solution or a separately agreed integration.

Questions to work through.