OTA Booking Modifications

When a booking arrives from an OTA, modifications follow rules set by both Argonautas and the originating platform. This guide explains what changes are possible per channel, how modifications sync, and how to handle common scenarios without creating conflicts.

Overview

OTA bookings are not fully editable in the same way as direct bookings. Each platform has its own policies about which fields can be changed, who can initiate changes, and whether modifications require guest approval. Argonautas tracks modifications from both sides -- changes you make locally and changes the guest or OTA initiates externally -- and keeps everything in sync through the distribution network.

Modification Capabilities by Channel

Not all OTAs allow the same types of modifications. The table below summarizes what is supported for each major platform:

Modification	Airbnb	Booking.com	Vrbo
Date change (host-initiated)	Yes -- guest must accept	Yes -- via extranet or API	Limited -- guest must rebook
Date change (guest-initiated)	Yes -- host must accept	Yes -- automatic if policy allows	Yes -- host must accept
Guest count change	Yes	Yes	Yes
Price adjustment	Yes -- as part of alteration request	Limited -- only via extranet	No -- original price stands
Add nights	Yes -- as alteration	Yes	No
Shorten stay	Yes -- treated as partial cancellation	Yes -- may trigger penalty	No -- must cancel and rebook
Room/unit change	No	No	No
Guest name change	No	Yes -- Booking.com allows	No

Airbnb

Airbnb uses an alteration request system. Either the host or the guest can propose changes to dates, guest count, or pricing. The other party must accept the alteration before it takes effect. If neither party responds within 24 hours, the alteration request expires.

When a guest submits an alteration through Airbnb, it arrives in Argonautas as a pending modification. You will see a notification in the Inbox and can review the proposed changes before accepting or declining.

Key behavior: If you modify an Airbnb booking's dates directly in Argonautas, the system sends an alteration request to the guest through Airbnb. The booking does not update until the guest accepts.

Booking.com

Booking.com is more permissive with modifications. Date changes, guest count updates, and even guest name changes can often be processed directly. The platform distinguishes between:

• Free cancellation bookings -- Most modifications are allowed without penalty up to the cancellation deadline.
• Non-refundable bookings -- Date changes and shortening stays may trigger penalties or be blocked entirely.

Booking.com modifications sync automatically. When a change is made on the Booking.com extranet or by the guest, the updated booking data flows into Argonautas within minutes.

Vrbo

Vrbo has the most restrictive modification policies. Most changes beyond guest count require the guest to cancel the original booking and create a new one. This means:

• Date changes typically require a cancel-and-rebook workflow.
• Price adjustments after booking are not supported through the API.
• Guest-initiated changes go through Vrbo's request system, and the host must approve.

If a Vrbo guest needs to change dates, the recommended approach is to coordinate directly with the guest, cancel the original booking (following the cancellation policy), and have them rebook the new dates.

How Modifications Sync

Changes Made in Argonautas

When you modify an OTA booking in Argonautas:

1. The system checks whether the change is supported by the originating OTA.
2. If supported, the modification is pushed to the OTA through the distribution network.
3. The OTA processes the change (which may require guest approval, as with Airbnb alterations).
4. Once confirmed, the booking updates in Argonautas with the final details.

If the change is not supported by the OTA, you will see a warning explaining that the modification applies locally only and will not be reflected on the OTA's platform. This can lead to data mismatches, so use caution.

Changes Made on the OTA

When a guest or the OTA modifies a booking externally:

1. The updated booking data is pulled into Argonautas through the distribution network.
2. The booking record updates automatically -- dates, guest count, pricing, and status all reflect the new information.
3. Availability recalculates across all connected channels.
4. A sync log entry records the modification with a timestamp and details.

These external modifications appear in the booking's activity history so your team can see exactly what changed and when.

Cancellation Handling by OTA

Cancellations also vary by platform:

Platform	Guest Cancellation	Host Cancellation
Airbnb	Follows the listing's cancellation policy (Flexible, Moderate, Strict). Refund calculated automatically.	Possible but penalized -- Airbnb may charge fees and affect Superhost status.
Booking.com	Follows the rate plan's policy. Free cancellation bookings can be cancelled before the deadline at no cost.	Host can request cancellation through Booking.com, but it affects ranking.
Vrbo	Follows the cancellation policy set on the listing. Refund depends on timing.	Host cancellation is possible but discouraged and may incur penalties.

When an OTA cancellation occurs, the booking status in Argonautas automatically changes to Cancelled, and the dates are freed on your calendar and across all connected channels.

Settlement Review

When an OTA booking is modified or cancelled, the amount the property owner actually nets can change in ways the system cannot determine on its own. Settlement review is the workflow for confirming the correct owner payout in these cases, so owner statements and financial reports stay accurate.

Why a settlement needs review

For a normal, untouched booking, Argonautas calculates the owner's net payout automatically from the rate, the OTA commission, and taxes. A booking is flagged for review only when something makes that automatic figure unreliable:

• A cancellation whose payout Airbnb hasn't confirmed yet. Cancellations can leave a partial payout (a non-refundable night, a cleaning fee) that only the OTA can confirm.
• A partial refund. The guest was refunded part of the stay, so the original totals no longer reflect what was collected.
• An edited stay. The dates or price were changed after booking.
• A manually added charge. Someone added an extra charge to the booking.
• A fee the OTA applies late. Vrbo, for example, applies its host payment-processing fee after the traveler pays. Until that fee lands, the payout shown is only an estimate, so the booking stays unfinalized rather than locking in a wrong number. Argonautas re-checks these bookings automatically and resolves them once the real fee arrives.

The four settlement states

Every OTA booking shows one of four settlement states on its price-breakdown card:

State	What it means	Action needed
Clean	Normal booking, payout calculated automatically.	None.
Review required	An anomaly above was detected and no decision has been recorded yet. The owner-net figure shows "Review required" in red.	You confirm the correct payout.
Cancelled -- fully refunded	The booking was cancelled and Airbnb confirmed nothing was retained, so the payout resolves automatically to $0.00.	None (you can still revise it).
Reviewed	You have entered and saved a confirmed payout. Your figure is authoritative and feeds owner statements, reports, and the owner portal.	None, unless a new change re-flags it.

A human decision always outranks the automatic resolution. If a booking changes again after you review it (for example, a new charge is added), it returns to Review required so the figure is re-confirmed.

Reviewing a settlement

1. Find the bookings that need attention. On the Reports page, a warning chip reads "N bookings need settlement review" when any are outstanding -- click it to jump straight to the filtered list. You can also open the Bookings list and choose Needs review from the filter dropdown.
2. Open the booking. Its price-breakdown card shows the owner-net row in red as "Review required", with a short reason ("Partial refund detected", "Schedule was edited", "Cancelled -- payout not yet confirmed by Airbnb", or "Manual extra charge applied").
3. Click "Review settlement…" to open the review dialog. It lists every reason the booking was flagged and, for reference, the management commission and IVA from the original calculation. When Airbnb has confirmed a retained amount, you'll see "Airbnb retained {amount} -- decide the owner's share."
4. Enter the confirmed owner net payout. This is the whole-booking amount after commission and IVA, at full ownership. For a straightforward cancellation with nothing retained, the field is pre-filled with 0.00; otherwise you enter the figure yourself. Argonautas applies the property's ownership share automatically -- you don't need to pro-rate for co-ownership.
5. Add an optional note (for example, "Partial refund verified against the Airbnb ledger") and click Review settlement… to save.
6. The card updates to show your confirmed amount with a "Reviewed by {name} · {date}" stamp. To change a decision later -- including an auto-resolved cancellation -- click Revise to reopen the dialog.

Best Practices

Review Before Modifying OTA Bookings

Before changing an OTA booking in Argonautas, check the booking's source channel. If the modification is not supported by that OTA, consider making the change through the OTA's own dashboard or extranet instead to keep records consistent.

Use the Inbox for Guest Communication

When a guest requests a modification, use the Inbox to discuss details before making changes. This creates a documented communication trail and helps avoid misunderstandings about pricing or dates.

Monitor Sync Logs After Modifications

After modifying an OTA booking, check the sync logs (Distribution > Sync Logs) to confirm the change propagated successfully. If the sync shows an error, investigate before assuming the change took effect on the OTA side.

Handle Date Changes Carefully

Date changes are the most complex modification because they affect availability across all channels. Always verify that the new dates are available before initiating a change, and watch for sync confirmation afterward.

Key Concepts

• Alteration request -- Airbnb's mechanism for proposing booking changes. Requires acceptance from the other party.
• Extranet -- The OTA's own management dashboard (e.g., Booking.com's Partner Hub or Airbnb's Host Dashboard).
• Local-only change -- A modification made in Argonautas that cannot be pushed to the originating OTA. Use with caution.
• Cancel-and-rebook -- The process of cancelling an existing booking and creating a new one, required by some OTAs for certain types of changes.

Common Questions

What happens if I change the price on an Airbnb booking? The change is sent to Airbnb as part of an alteration request. The guest must accept the new price before it takes effect. If declined, the original price remains.

Can I extend a Booking.com reservation? Yes, if the additional dates are available. The extension syncs to Booking.com and the guest is notified of the updated stay. The rate for the added nights follows your current pricing.

A guest wants to change their Vrbo dates. What should I do? Coordinate with the guest directly. They will need to cancel their current booking through Vrbo and rebook the new dates. Make sure the new dates are available before the guest cancels.

Will modifications affect my OTA rankings or reviews? Host-initiated cancellations can negatively impact your standing on most OTAs. Modifications (date or price changes) generally do not affect rankings as long as both parties agree.

How do I know if a modification synced successfully? Check Distribution > Sync Logs for the property. A successful modification will show a "Pull Booking" or "Push Booking" entry with a success status and the updated details.

Related

• Booking Lifecycle -- The full booking lifecycle from creation to checkout.
• Channel Integration -- How properties connect to OTAs.
• Sync Troubleshooting -- Resolving sync issues after modifications.