Charge it to the unit. That’s the whole process.
Two systems means two logins, two settlements and someone reconciling them at midnight. In ApexOS the register and the reservation are the same system. Room charges land on the guest’s folio when they’re rung, and you close one set of books.
Animation: a cashier at the property shop rings up a welcome basket, coffee beans and a bottle of wine, chooses Charge to Room, finds unit 4B, picks the guest’s primary folio and confirms. The same sale then appears on the guest’s reservation, beside their lodging charges.
Shop, restaurant and lodging revenue land on the same ledger the moment they’re rung. One set of books to close. Taxes stay where they belong.
Animation: a day of postings arriving on one ledger, from the front desk, the shop, the grill and the camp store, with lodging tax and sales tax adding up separately.
The family in Cabin 7 buys firewood every night. On a standalone register that’s a receipt, then it’s gone. In ApexOS every room charge sits on their reservation, next to the lodging.
Animation: over a photo of a lit cabin with a fire pit at dusk, the Okafor family’s reservation for Cabin 7, with a shop charge added each night of their stay.
The kitchen runs on the same system as the register. Orders route to the right station, and inventory moves when the food does.
Animation: the kitchen display, with each ticket’s timer turning from green to amber at five minutes and red at ten, and a finished ticket being bumped.
Decide who rings sales, who voids them and who touches the cash. Set it once, by role.
Animation: over a photo of two staff working a wooden counter, point of sale roles for a cashier, a line cook, a server and a manager, each allowed a different set of actions: build orders, pay and void, kitchen, 86 items, cash and setup.
The shop, the restaurant and the bar each get their own menus, kitchen routing and cash drawers. Three operations. Not one generic register.
Menus switch by hour and day, on the register and your public online menu. Breakfast ends on time. Nobody has to remember.
Modifiers route to the station that makes them. Tickets turn amber, then red, when they run long. The kitchen notices before the guest does.
Sell by the unit, by weight or by volume. Recipes pull stock as items sell. 86 something and it disappears from the register and the online menu.
Counter, pickup or delivered to the unit. Seat numbers, kitchen notes and upsell prompts go on as the order is taken, not on a screen someone finds later.
Drawers per revenue center, with drawer or server banking. Access by role, so whoever rings the sale isn’t automatically whoever voids it.
Reverse a sale and the refund goes back through the original payment. The accounting follows on its own.
Ask for sales by location or by category. Apex runs the report and shows the numbers. Changing a menu works the same way.
Revenue centers
The register, the reservation, the folio and the books are one system. No POS connector to maintain. No two sets of numbers to reconcile.
See all integrationsA hospitality point of sale system is the register a lodging property uses to sell everything that isn’t the stay: shop and sundry items, restaurant and bar orders, firewood, welcome baskets, camp store goods. Unlike a retail register, it has to know about reservations. Guests expect to say “charge it to my unit,” and the property expects that charge to reach the right folio and the same books as lodging revenue.
It doesn’t integrate with the PMS. It is part of it. ApexOS point of sale and ApexOS property management are one system on the same records, so there is no connector to install, no overnight sync and nothing to fail on a holiday weekend. A room charge posts to the guest’s folio the moment it’s rung, on the same reservation your front desk has open.
Two things. The register is part of the property management system rather than connected to it, so there is one folio, one ledger and one set of books. And you change it by asking: adjusting a menu or building a report is a plain-language request, not a support ticket.
For a vacation rental or other lodging property, look for: charge to folio, posting to the reservation itself; revenue centers, so the shop, the restaurant and the bar each run their own menus and kitchen routing; menu scheduling by hour and day; kitchen routing by modifier, with an alert when a ticket runs long; recipe-level inventory; cash drawers and access set by role; and retail and lodging tax kept separate.
