Technology · Integration operations
Every connection has
a failure shape.
The cheapest integration to launch may ask a person to repair it every morning. The most sophisticated may fail silently if nobody owns its credentials and alerts. Choose from the operating model, not the diagram.
The spectrum
Transport determines when the truth can change and who notices when it does not.
All four shapes can be legitimate. A 40-unit residential roster may not need an event stream. A hotel arrival system depending on same-day reservation changes may not tolerate a weekly spreadsheet.
Evaluate freshness, reconciliation, observability, and the human fallback before comparing build estimates.
Four shapes
From batch handoff to shared conversation
Flat file
A person or scheduled export produces a complete set of rows. The receiving system maps columns and imports them.
Strength
Visible and portable
The file can be inspected, archived, corrected, and replayed without specialized tooling.
Failure
Stale snapshot
Late changes disappear until the next export, and duplicate or partial files need explicit handling.
Labor
Mapping and exceptions
Someone owns column changes, rejected rows, and the question of whether a missing row means deletion.
Email feed
A system sends an attachment or structured message to a dedicated inbox. It automates transport without changing the batch nature of the data.
Strength
Works with existing exports
A property can automate a report it already generates without funding a custom application.
Failure
Mail is not a transaction
Delays, duplicates, changed subjects, and malformed attachments require idempotency and a quarantine path.
Labor
Inbox operations
Someone must receive a clear exception when the attachment stops matching the agreed shape.
Webhook and API
A webhook pushes change. An API lets another system ask or act. Mature integrations commonly use both and reconcile after interruptions.
→Available connections depend on the hotel system and the property’s arrangement. Confirm compatibility and support before committing to a workflow.
Compare total operating cost
Freshness
How late can a change arrive?
Write the acceptable delay for arrivals, cancellations, room moves, and departures.
Repair
Who handles rejects?
Name the team, screen, alert, and response window for records that cannot be applied.
Authority
Which system wins?
Define the owner of each field and the reconciliation rule when two values disagree.
Continuity
What is the fallback?
Keep a documented manual or batch path for credential failures and extended upstream outages.
→Primary source: Oracle Hospitality Integration Platform datasheet, reviewed August 23, 2026.
The selection rule
Use the least complex shape that meets the freshness and recovery requirement.
A file with excellent exception handling can outperform an abandoned API. A well-run event integration can remove hours of daily correction. The difference is not modern versus old. It is whether the whole lifecycle is owned.
The takeaway: integration cost begins after the first successful record crosses the boundary.
