POI Feed
A feed model describing physical properties or businesses with location and metadata. It can serve as the property-identity layer in hotel aggregation.
Why it matters
The same physical travel entity can appear with different IDs, names and metadata across suppliers. If identity resolution is wrong, correct price and availability data can still be attached to the wrong property or product. Canonical identity, source identifiers and mapping confidence need to be designed together.
What does it look like in practice?
An Expedia property ID and a Booking.com property ID can represent the same physical hotel. Internal canonical identity should connect them using evidence and confidence.
Implementation questions
- How is the canonical entity defined?
- Are source-specific IDs retained?
- Which signals drive matching?
- Is there a manual-review path for ambiguous matches?
Common mistakes
- Mapping from name similarity alone
- Overwriting manual overrides
- Creating duplicates after rebrands
Where does it appear in the travel stack?
POI Feed commonly appears across identity layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.
Related terms
Related technical guides
Google Hotel Feeds: Data Contracts and Recovery
Separate Google Hotel List, pricing, ARI, POI and landing contracts; diagnose stale updates and design publication, recovery and monitoring workflows.
Explore →Agentic Travel Authorization, Mandates and Human-in-the-Loop
Design user intent, mandates, delegated authority and human-in-the-loop checkpoints for AI-driven travel purchase and servicing side effects.
Explore →Cendyn CRS: Central Reservations and Distribution Profile
A technical ecosystem profile of Cendyn's central-reservation and hotel-distribution role, including reservation services and live hotel-feed infrastructure.
Explore →Missing Webhook Troubleshooting
Diagnose missing provider webhooks across delivery, signature, endpoint, queue and reconciliation layers.
Explore →Feed Ingestion Failure Troubleshooting
Diagnose travel feed failures systematically across transport, schema, parsing, validation, persistence and downstream publishing.
Explore →Google Hotel Feeds vs Meta Catalog vs Criteo Catalog
Compare Google Hotel Feeds, Meta Travel Catalog and Criteo Catalog across identity, price freshness, event matching and advertising workflows.
Explore →