A full PMS runs the front office. Apus Platform carries shared company, inventory, procurement, Finance, people and reporting records across the portfolio.
Full PMS front office Shared business records Portfolio control
Built for: Hotel groups · Property operations · Procurement · People · Finance
PMS is a front-office industry application, not a Platform module — and it integrates with Platform whoever supplies it.
HOSPITALITY
Front officeShared coreEnterprise control
ReservationsRooms & ratesFront desk + outlet POS
Master dataInventoryPurchasing
FinancePeoplePortfolio
Stay operated→Group controlled
Front officePMS
CoreShared
ControlEnterprise
One logical core; deployment topology is designed per implementation.
ONE LOGICAL CORE
Front office runs the stay. The shared core carries the business.
PMS and enterprise modules have different product owners and UX, while sharing the business data plane needed to run the group.
1
Front office · PMS + outlet POS
Reservations and guest profiles
Room inventory, rates and availability
Front desk, check-in and check-out
Housekeeping, folios, outlet POS and channels
→↓
2
Shared Platform Core
Tenant, company and master data
Inventory and property consumption
Procurement and suppliers
Finance records and enterprise dimensions
→↓
3
Enterprise control · Apus Platform
Portfolio procurement and stock
Finance and multi-property reporting
People, shifts and shared services
Assets, projects and management control
When the PMS is yours, or another vendor's
The three columns describe one logical business core — true by construction when the front office is a PMS supplied by Apus, and true through integration when it is anything else. These four points are settled before configuration starts.
—Standard data and owning system: stays, guest profiles, room types and service codes stay with the PMS; goods, suppliers and accounts stay with Platform.
—How data travels and who may write: an API, a periodic export or a read-only replica — chosen against the system you actually run, because it sets how fresh reporting can be.
—Integration log and confirmation: every handover leaves a state — received, reconciled or still open. Nothing disappears quietly.
—Control totals before posting: stay revenue, receipts and variances must agree before figures reach group reporting.
The PMS in the first column can be the one you already run, another vendor's, or a PMS supplied by Apus — the handover point is the same, only the integration effort differs. Channel and partner connections belong to the PMS operating domain; physical topology is confirmed per deployment.
OPERATING GAPS
The group loses control when each property becomes an island.
01
Property demand sits outside procurement
Consumption and requests are re-entered into back-office systems.
→↓
Enterprise control
Carry operational demand into shared inventory and purchasing records.
02
Charges and finance diverge
Stay activity and accounting context are assembled late.
→↓
Enterprise control
Define controlled PMS-to-Finance handoffs without a parallel ledger.
03
Portfolio visibility is fragmented
People, assets and site results use different dimensions.
→↓
Enterprise control
Use shared company and master data for enterprise reporting.
A day at one property, and a day in the group's shared functions.
Reservations, the front desk and the folio are run by the PMS. From the property's demand onwards, inventory, purchasing, people and Finance run on shared records.
Property manager
Goal
The property never runs short, and never sits on stock either.
Modules
PMS
Property inventory
01Stays, housekeeping and the folio live in the PMS — that is the front office's system, not a Platform screen.
02Open stock at the property: linen, single-use amenities and technical supplies still on hand.
03Raise a replenishment request against the occupancy forecast for the coming period, straight to group purchasing.
04Record what housekeeping and engineering actually consumed during the day.
05Turn an equipment repair request into a work order with the cost landing on the right property.
Group purchasing
Goal
When several properties buy the same thing, negotiate as one customer.
Modules
Purchasing
Suppliers
01Group the properties' requests by category instead of handling each hotel separately.
02Compare quotes against the framework agreements signed and issue the purchase order per receiving property.
03Track delivery and match purchase order, acceptance and invoice before payment moves on.
04Score suppliers on delivery timeliness and quality, property by property.
05Read spend by category across the portfolio in preparation for the next negotiation.
People & shared services
Goal
Shifts and staff can move between properties when peak seasons do not line up.
Modules
HRM
Shifts & shared service
01Open the headcount structure by property and by department, and see where cover is short.
02Roster against the occupancy forecast; the system flags shifts short of staff or double-booked.
03Second staff temporarily between two properties, with the cost following where they work.
04Close attendance and shift allowances and pass them to Finance without retyping the sheet.
05Track the shared departments' workload to see what each property is consuming.
Group accountant
Goal
One set of numbers for the whole portfolio, not a stack of separate reports.
Modules
Finance
BI
01Take the charges and settlement closed in the PMS on the agreed handoff — no parallel ledger.
02Attach operating, purchasing and people cost to the right property and the shared analysis dimensions.
03Clear what is left after reconciliation before the figures enter management reporting.
04Consolidate results across properties and legal entities on the same shared master data.
05Compare performance across properties in the same segment to find the one drifting.
The PMS carries the front-office journey and the POS carries outlet transactions; Apus Platform holds the shared records, purchasing, people, Finance and reporting. The handoff points between the products are designed per project.
AGENTS ALREADY DO
Reconciling, chasing due dates, summarising and rolling up — the repetitive work running through the day above.
PEOPLE STILL DECIDE
Approving spend, settling on a plan, signing — anything that needs judgement still stops with a person.
IMPLEMENTATION PATH
Design the property-to-enterprise handoffs explicitly.
01
Map product ownership
Separate PMS front-office responsibilities from Platform enterprise responsibilities.
02
Agree shared masters
Define company, property, item, supplier, finance and people dimensions.
03
Pilot bounded handoffs
Test inventory, procurement and Finance flows at a chosen property.
04
Expand by evidence
Resolve exceptions and controls before portfolio rollout.
Topology may vary and a rollout can require integration, relocation or cutover work.
BEST FIT
For hospitality organizations that need property speed and group control.
Hotel groups
Standardize shared records and control while preserving property operations.
Multi-property operators
Connect procurement, stock, people and Finance across locations.
Integrated hospitality businesses
Link stays with shared services and enterprise reporting.
A multi-country hotel group consolidates revenue in the group currency while tax and invoicing stay local. See it by market
CONTROL GATES
Three questions before rollout.
01
Which product owns the interaction?
Keep PMS front-office UX and Platform enterprise UX under their accountable owners.
02
Which records are shared?
Define system ownership and write rights for each master and transaction context.
03
How is the handoff proven?
Agree statuses, exceptions, reconciliation and recovery evidence.
One logical core describes business continuity, not a universal physical topology or cutover promise.
FAQ
Clarifying Hospitality, PMS and Platform.
We already run a different PMS — do we have to replace it?+
That PMS keeps its front-office role. Apus Platform sits behind it and takes the handover, so the project builds an interchange rather than swapping out a running system. How much integration work that takes is surveyed against your actual system and settled during solution design — there is no pre-built plug-and-play package.
Is PMS a Platform module?+
No. It is a separate application family connected to the same logical Platform Core and business data plane.
What if our current PMS has no open API?+
The survey establishes how that system will release data — an API, a periodic export, or a read-only replica. Each option sets the reconciliation rhythm and how fresh reporting can be, so it is agreed before configuration rather than after.
How does the Apus PMS differ from another vendor's?+
The handover point is identical; the difference is workload. A PMS supplied by Apus already stands on the same logical core, so records carry on without a bridge being built; an outside system needs a controlled interchange, and that bridge has to be maintained through upgrades on both sides.
What remains in Platform?+
Shared company and master data, inventory, procurement, Finance, people, assets, projects and enterprise reporting remain in the Platform journey.
Does one core guarantee a zero-downtime rollout?+
No. Architecture, integration, relocation and cutover are designed for each implementation.
Design one journey from stay to enterprise control.
Confirm PMS scope, shared records and rollout boundaries with the Apus team.
