VELA Dhi Nakhon Phanom Data sources
Proof of concept · synthetic data
Data sources

Start with the exports the hotel already has

Phase 0 runs on uploaded Excel or CSV reports. API connections replace uploads one system at a time, and the engine doesn't care where a row came from.

PMS · reservations

3 years uploaded · 98.6% rows clean Level 1 · upload

PMS · on-the-books snapshot

Daily export · 41 snapshots so far Level 1 → 2

Channel manager · rate push

Partner request sent, awaiting pilot slot Level 3 · pending

POS · F&B

Last upload 31 hours ago Level 1 · upload

Rate shopper · comp set

5 hotels · 365 nights forward Licensed feed

Event calendar

13 events · 4 awaiting confirmation GM signs

Thai holidays & weather

Pulled automatically Ours

Website / GA4

Not connected Optional

Connection statuses are mock examples of what the hotel would see during phase 1.

Try the upload mapper

A sample PMS export is loaded. Drop in any reservations CSV to see how its columns map. The file never leaves your browser.

  1. 1 Read · 4 rows
  2. 2 Map columns · 12 matched
  3. 3 Strip personal data · 2 columns dropped
  4. 4 Validate · ready to import
File
sample_pms_export.csv
Rows read
4 bookings · 1 cancelled
Required fields
All required fields found
Column in your fileMaps to
Conf Nobooking_id
Guest NamePersonal data · dropped
Booked Oncreated_at
Arr. Datearrival_date
Dep. Datedeparture_date
Room Catroom_type
Rate Planrate_code
Marketsegment
Sourcechannel
Adultsadults
Room Revenueroom_revenue_thb
Statusstatus
Nationalitycountry
MobilePersonal data · dropped

Names, phone numbers and emails are dropped at upload and never stored. Target schema: booking_id, created_at, arrival_date, departure_date, room_type, rate_code, segment, channel, adults, room_revenue_thb, status, cancelled_at, country.