A clear path through
complex travel data.
A mapping decision should be explainable, reversible, and traceable to the record that started it.
Preserve the source
Start with supplier + hotel code. Keep leading zeros, original names, raw addresses and the source status. A comparison copy can be normalized without changing the original record.
Find plausible candidates
Narrow by country and location, then compare identity signals. Existing approved master IDs remain the anchor for supplier relationships.
Check the evidence
Evaluate name, address, city, coordinates and known identifiers together. Missing evidence is different from conflicting evidence. Hard conflicts stop automatic acceptance.
Make a measured decision
Use a conservative match threshold, minimum evidence and a margin over the next candidate. The demonstration uses deterministic scores, not a learned probability.
Review the exception
Inspect competing candidates, record a reason, accept a supported identity or keep the record unresolved. Scope a suspension to the affected supplier profile.
Track every change
A production workflow retains versioned source records and decision history. The browser demo records local imports, rule changes, and reviewer decisions for inspection and export.
Keep these three
questions separate.
Identity does not tell you whether a supplier profile is active or a room is available for a stay.
Which property is this?
Connect a supplier record to a stable master property ID using the available evidence.
Is this supplier profile active?
Pause the affected relationship when a supplier withdraws a record. Other suppliers keep their own status.
Can it be booked for this stay?
Check dates, occupancy, room inventory, rates, and conditions through a booking supplier.
A clearer identity starts here.
Explore the mapping workflow. Build a brief around your data.