Verify the identity layer
Confirm the correct properties, units, channels and responsible people. Check similar names carefully. Preserve the original references and configuration before live changes. Do not treat a populated dashboard as proof that every listing maps to the intended rentable unit. A small naming ambiguity can affect calendars, messages and property tasks simultaneously.
Verify the guest route
Review property information, available dates, a representative price breakdown and a safe pre-payment checkout path. Keep the human contact route visible. Use fictional inputs and do not create a real charge as an incidental acceptance test. Record which parts were visually inspected and which provider-controlled operations remain untested so the result is not overstated.
Verify operating responsibility
Name the person who handles a changed reservation, a failed message, a cleaner handoff and an unavailable application. Keep the supported provider contact and continuity information accessible privately. Check that every unresolved task has an owner. Do not enable optional automation merely because it appears in the interface; understand its inputs, effects and recovery first.
Launch and review a bounded scope
Where the supported process allows, begin with a controlled scope and review actual records before expanding. Stop on an unexplained mismatch rather than interpreting it optimistically. Publication, payment settlement, synchronization and business performance are separate outcomes. This checklist helps organize evidence; it does not certify a vendor, guarantee bookings or remove the need for ongoing host responsibility.
Prepare the final verification record
Keep one concise release note for the host operation: properties covered, connections changed, original references retained, checks completed, unresolved limits, recovery contact and next review date. Do not inflate the checked scope because a representative case passed. If a payment flow or account feature was not exercised, say so. A truthful partial verification is safer and more useful than an unsupported all-clear.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Lodgify channel manager: merchant description, not reliability testing — Merchant documentation · lodgify.com · Merchant-controlled · checked 2026-09-19
- Lodgify existing-site booking widget — Merchant documentation · lodgify.com · Merchant-controlled · checked 2026-09-19
- Smoobu editing responsibilities after connection — Alternative provider · support.smoobu.com · Publisher independence not verified · checked 2026-09-19