Tutorial

Link a lodging maintenance request to MRO

Coordinate food, catering, room service, housekeeping and maintenance requests. Record charges and create linked ERP invoice or stock drafts; use MRO and Helpdesk links where configured.

Updated 14 October 2026 · Native ERP foundation

The native ERP foundation is published: properties, rooms, stays, service requests, charges and physical-key custody. The hotel engine and electronic lock connectors are not commissioned. Food, catering and room service are request and ERP-order workflows; a restaurant POS, kitchen display, online booking engine and automatic keycard encoding are not provided by this release.

Use your own authorized ERP account. These text tutorials describe the published native fields and actions. Screenshots and click markers for this new app will be added in a later documentation pass.

Step 1 of 4

Step 1

Open the room and link the correct existing Asset. If it cannot be occupied, set Room condition to Out of Service.

Expected URL expression{ERP_URL}/desk/nexcom-lodging-room/{RECORD_ID}

Open the list without /{RECORD_ID}. New forms use a temporary new-record identifier. ERP_URL is your organization’s ERP origin.

Expected result: The maintenance request can identify the maintained asset.

Step 2 of 4

Step 2

Create and save a Maintenance service with the stay, request and failure details.

Expected URL expression{ERP_URL}/desk/nexcom-lodging-service/{RECORD_ID}

Open the list without /{RECORD_ID}. New forms use a temporary new-record identifier. ERP_URL is your organization’s ERP origin.

Expected result: A source service exists for the repair.

Step 3 of 4

Step 3

Choose Integrations → Create / open MRO repair. Review required fields in the resulting Asset Repair.

Expected URL expression{ERP_URL}/desk/nexcom-lodging-service/{RECORD_ID}

Open the list without /{RECORD_ID}. New forms use a temporary new-record identifier. ERP_URL is your organization’s ERP origin.

Expected result: A linked repair draft is created or the existing repair is opened. Native MRO validation and permissions remain applicable.

Step 4 of 4

Step 4

Complete the authorized MRO process and verify the repair and service links. Return the room to Ready only after operational inspection.

Expected URL expression{ERP_URL}/desk/asset-repair/{RECORD_ID}

Open the list without /{RECORD_ID}. New forms use a temporary new-record identifier. ERP_URL is your organization’s ERP origin.

Expected result: Repair, service completion and room readiness remain explicit actions. This connector still requires site-specific end-to-end acceptance with real asset configuration.

If the action is blocked

Check required fields, current status, linked company and record permissions. Return outstanding keys before checkout. Room and key conflict checks cannot be bypassed by editing their identifiers. For Finance and stock drafts, review native validation messages before submitting.