Implementation

Roll out the hotel workflow with reconciled source data.

Implementation phases

  1. Agree the operating scope
  2. Configure the responsibilities
  3. Reconcile the opening position
  4. Verify the first operating scope
Phase 1 · Team and ERP.ai

Agree the operating scope

Identify legal companies, properties and the existing PMS. Follow a real booking change and room turnover, then review kitchen preparation, property supplies and the local goods route. Agree who owns each source and decision before configuring the application.

Phase 2 · Team and ERP.ai

Configure the responsibilities

Set property and room mappings, permissions and approved operating rules. Review recipes, units and stock methods. Define how PMS financial components reach company accounts and how actual settlement clears the same source. Test the supported request and response behavior with the chosen connection.

Phase 3 · Team and ERP.ai

Reconcile the opening position

Bring forward current bookings, stay segments, room restrictions and unfinished tasks with their original identities. Reconcile stock and production work alongside local financial detail and the external guest ledgers. Approve one company opening ledger and nonposting source history at the agreed cutoff.

Phase 4 · Team and ERP.ai

Verify the first operating scope

Run the agreed workflows with their owners and review the result. Include a stale PMS update, a room discrepancy, a partial receipt and an unresolved payment outcome. Confirm that changes preserve previous work and that quantities, clearing sources and financial balances reconcile before expanding use.

What the customer provides

Provide the current PMS and property structure, supported connection documentation and representative source records. Include room and guest reference mappings, current staff responsibilities, recipes and product units, stock and open production evidence, supplier and customer balances, and the accounts used for guest/deposit/corporate/payment clearing.

Bring actual exceptions and the decisions used to resolve them. Confirm timezone and business-date conventions, access preferences, room-block meanings and the handling of incomplete source updates. Finance should provide reconciled source balances and settlement evidence for the proposed migration cutoff.

Changing it afterwards

Review configuration changes on a branch before release. A new property, PMS mapping, financial route or recipe policy can affect existing work and needs focused verification. Preserve already performed stays, stock movement and posted source history while changing only the eligible remaining scope.

The implementation quote covers the agreed application scope, connections, migration, training and support.

1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.
ERP•AI workspace

Start now Hospitality ERP

Create your ERP.AI account and get started with Proto.

Start now Download agent

Customize Hospitality ERP. With Proto, your desktop AI agent.

Ask Proto to help you customize Hospitality ERP.

Customize
Hospitality ERP. Ask: “Adapt Bookings & front desk.” ProtoYour desktop AI agent
Download nowFree install · ~1 GB · AI usage extra