Define the data before naming the connector
A hotel may exchange reservations with online travel agencies, send operational or financial data to another platform, and handle guest information under Saudi operating requirements. These are separate flows; one working connection does not make the others ready. Map each data source, destination, transfer time and person who checks transmission errors.
Saudi Ministry of Tourism materials discuss NTMP and Shomoos connections for accommodation facilities and provide NTMP connection guidance. Check the current official source for requirements affecting your property. Procedures may change, and a product description cannot replace guidance from the responsible authority.
NTMP: keep financial and operational flows distinct
Ask separately about operational and financial NTMP data: which fields are involved, where they originate, when they are sent and how errors are handled. Stay data may be complete at front desk while accounting still needs to review a financial record. Test both flows with representative samples rather than relying on a single connection indicator.
Flowtel's integration scope includes financial and operational NTMP flows, but activation and configuration depend on the property's setup and the receiving party's current requirements. Request an acceptance plan before use.
Shomoos and booking channels
For Shomoos, identify where guest information is entered, which fields are checked before transfer and who follows up on a rejection or missing value. For online travel agencies such as Booking.com, Agoda and Expedia, test what moves from a booking and how changes, cancellations and availability are handled. Each connector's scope depends on its configuration and the other party.
Do not assume every rate, policy or additional channel synchronizes automatically. Use common changes from your own operation as test cases and assign someone to monitor differences after launch.
E-invoicing is a separate flow
An invoice may arise from a stay or an extra service, but an NTMP or Shomoos connection does not by itself complete e-invoicing requirements. Test the generation, correction and transmission or storage of invoices within the phase that applies to your business. Check current ZATCA materials with your finance or tax lead, and assign someone to verify invoice type, data and result.
When evaluating a provider, request a demonstration of an ordinary invoice and a related correction or note. Record what the system performs and what needs configuration or an external procedure. Do not rely on a broad compliance claim without a defined scope and documented test.
Acceptance test before relying on a connection
Use test data that does not expose real guest information during evaluation. Compare records at the source and destination, verify error handling and document the boundaries between the hotel, system provider and external party.
- What financial and operational data does each NTMP flow need?
- How does the team review rejected or incomplete Shomoos records?
- Have you tested an agency booking, change and cancellation?
- Who monitors and retries failed transfers?
- Who checks the current official requirements before launch?