Channex

A pricing model in a spreadsheet or a data warehouse produces a rate for each night of the next ninety days. The agent reads the current position first, calling Get Rates and Restrictions for the rate plan across the range with the restriction types it cares about, and Get Availability for the rooms actually left per room type, so the proposal is compared against reality rather than against last week's export. It builds the diff, converts every price into minor currency units against the rate plan's own currency read from Get Rate Plan, and puts the resulting nightly price in front of a person in plain money. Only after approval does Update Rates and Restrictions run, supplying only the values that change and leaving blank fields untouched. The call returns a task ID rather than a confirmation, so the flow records that ID as evidence the write was queued and does not report the new rate as live on the strength of an HTTP status.

When On Booking fires, or on a short schedule as a backstop, the agent calls Get Booking Revisions Feed to read the revisions nobody has processed yet, oldest first. For each one it calls Get Booking Revision for the exact state the channel sent, and Get Booking for the current consolidated view, which matters because a booking that was created, modified, and cancelled inside an hour arrives as three revisions and only the sequence explains what happened. Each processed revision goes through Acknowledge Booking Revision so it stops appearing in the feed, and only then. The reservation writes into the property system, the arrival posts to the front desk channel in Slack, and cancellations that carry a refund are separated out for a person. Because acknowledgement is explicit, a run that fails partway through leaves the unprocessed revisions in the feed rather than losing them.

A new property comes onto the estate. The agent calls Create Property with its title and currency, noting that contact and address fields are optional at setup but required before a channel can be connected, then Create Room Type for each physical room category with its adult, child, and infant occupancy and its Count of Rooms, and Create Rate Plan for each product sold against those rooms, choosing Sell Mode per_room to sell the whole room or per_person to price per guest and setting a Parent Rate Plan where the plan is derived, cascaded, or automatic. Update Availability seeds the inventory. The mirror of this is the part that waits for a person: Delete Property with Force removes a property that still has room types and rate plans under it, and a deleted property cannot be recovered, so a test property and a live one are separated by a flag rather than by a warning.