An OTA Modification Created a Second Booking in the PMS: How to Resolve It

An OTA modification duplicate booking appears when a change to an existing reservation creates a second PMS record instead of updating the first one. The front desk may see two arrivals for one guest, two room deductions, or one old record and one new record with different dates.

This situation is different from a duplicate created by repeatedly importing a new booking. Here, the key evidence is the modification: the OTA still has one reservation, while the PMS has separated its old and new versions.

Do not cancel either record until the hotel knows which one remains connected to future OTA changes. Removing the wrong record can lose cancellation updates, payment instructions, guest messages, or the correct room assignment.

Confirm the OTA Has One Reservation

Open the current reservation in the correct OTA property. Search by the channel confirmation number and confirm whether the OTA shows one active booking, its latest modification time, and the complete current stay.

Compare the original and current details: arrival, departure, room type, number of rooms, guests, price, payment method, cancellation terms, and status. Save the modification time and time zone.

If the OTA shows two separate confirmation numbers, do not treat the PMS records as a modification duplicate. They may be two real bookings that require guest confirmation before any cancellation.

If the OTA shows one confirmation number and one current reservation, the hotel should finish with one operational PMS record. The second PMS record is an internal duplicate, not a second guest obligation.

Freeze Further Manual Changes

Assign one manager or senior front-desk employee to own the case. Tell the next shift not to move rooms, collect payment, send confirmation messages, or cancel either record until the review is complete.

Protect the guest's current room once. If the modification affects the last room, a same-day arrival, or a room move, record one temporary hold according to hotel procedure. Do not create additional holds for both PMS records.

Pause scheduled guest messages attached to the old record when possible. Two arrival reminders or payment requests can expose the duplicate before the hotel understands it.

A connected hotel channel manager should keep the OTA confirmation and subsequent changes tied to one hotel reservation. For this incident, use the connection history as evidence; do not resend the modification repeatedly.

Compare the Two PMS Records Side by Side

Use the OTA confirmation number as the first comparison point. Then check PMS reservation ID, creation time, last change time, source, dates, room and rate plan, guests, price, payment instructions, deposits, notes, messages, assigned room, and inventory movement.

The older record may contain the original payment or guest conversation while the newer record contains the correct modified dates. Neither should be deleted until the hotel knows which information must be retained.

Look for a clear modification pattern: one record matches the booking before the change and the other matches the current OTA version. Also check whether the newer record has a blank or different OTA reference. A missing reference can make a duplicate look like a manual direct booking.

Search cancelled and archived reservations as well. Staff may already have tried to fix the issue, leaving one visible arrival and another hidden record that still affects inventory or payment reporting.

Choose the Record That Should Remain

Keep the PMS record that can continue receiving future OTA modifications and cancellations. It should retain the correct OTA confirmation number, channel source, current status, and connection to the original booking history.

When the connected record contains old dates but the duplicate has the correct new stay, update the connected record with approved current details rather than choosing the newer record only because it looks accurate. Confirm the safe method with the PMS provider when the connection ownership is unclear.

Preserve the guest-facing history before closing the extra record. Transfer or retain authorized payment notes, deposit references, guest requests, internal comments, room assignment decisions, and staff tasks without copying charges twice.

An effective hotel management software workflow keeps the reservation source, folio, room assignment, and audit history together. That makes the surviving record usable by reception, housekeeping, and finance after the duplicate is removed.

Smart Order helps teams review the OTA reference and both PMS records in one operational flow before deciding which booking survives.

Resolve the Duplicate in a Controlled Order

Follow one sequence so inventory and money do not change twice:

1. Confirm the single current OTA reservation and the latest modified details.
2. Mark the PMS record that will remain and record why it is the connected record.
3. Bring the surviving record up to date with the approved stay, room, price, guests, payment, and policy details.
4. Move only necessary notes, tasks, deposits, and room assignments from the duplicate.
5. Close the extra PMS record using the approved duplicate, void, merge, or non-guest cancellation process.
6. Recalculate inventory and payment totals, then search again for the OTA confirmation number.

Do not cancel the real OTA reservation to remove the extra PMS record. That changes the guest's booking and may trigger a refund, fee, message, or inventory release on the channel.

Do not simply delete the extra record when it contains financial entries. Finance needs a traceable correction that explains why the record no longer represents a separate stay.

Reconcile Inventory, Payments, and Guest Work

Count the physical room inventory before and after the correction. The final reservation should protect the current room type for every current stay night exactly once. Old dates removed by the modification should no longer remain blocked.

Compare the OTA payment instruction with the surviving PMS folio. Check prepaid or channel-collected amounts, pay-at-property balance, deposit, refund, virtual payment notes where applicable, and any charge staff already posted. Never transfer or duplicate sensitive card data.

Review guest communications. Keep one confirmation trail and explain the current stay only if the guest received conflicting messages. Remove duplicate housekeeping tasks, check-in links, payment reminders, welcome messages, and room assignments.

The hotel's mobile front-desk workflow should show one usable arrival to the team on duty. If both records still appear on mobile or operational lists, the incident is not finished.

Verify the Next OTA Event

After the correction, compare the surviving PMS record with the OTA one final time. Confirm status, dates, room, rate, guests, price, payment, cancellation terms, and inventory.

Watch the next supported modification or cancellation carefully. It should update the surviving record rather than recreate the closed duplicate or open a third booking.

Give support the OTA confirmation number, both PMS IDs, original and modified details, creation and modification times, screenshots, inventory impact, and the record chosen to remain. Ask for the reason the modification created instead of updated.

Close the case only when one PMS record remains operational, inventory is correct, money appears once, and future OTA changes have a clear destination.

Prevent Modification Duplicates

Require staff to search by OTA confirmation number before creating a manual booking for a changed stay. A reservation missing from the arrivals list may have moved dates rather than disappeared.

Test booking, modification, and cancellation after adding a new OTA, PMS connection, room type, or rate plan. The modification must update the original reservation ID.

Track duplicate causes separately: manual re-entry, unsupported change, changed mapping, earlier import failure, staff-created copy, or a late modification. The prevention depends on the cause, not on the fact that two records appeared.

Frequently Asked Questions

Which PMS record should the hotel keep?

Keep the record that remains tied to the OTA confirmation and can receive future changes, while preserving the complete current stay and approved financial history.

Should staff cancel one booking in the OTA extranet?

No, not when the OTA shows only one reservation. Resolve the duplicate inside the PMS without changing the guest's real booking.

What if both PMS records contain payments?

Freeze further charges, identify the real transactions, and have finance move or reverse entries through the hotel's approved process before closing the duplicate.

When is the issue resolved?

One current PMS reservation remains, inventory is held once, payments and messages are not duplicated, and the next OTA event reaches that record.