Channel-manager administration has three separate parts: import connection settings, external room/room-type mappings and booking-channel reporting rules. Check all three when a booking is missing or classified incorrectly.
Connection and mappings
Use Preferences → Import options for the Channel Manager API configuration. An integration administrator supplies the connection and authentication settings and scheduled job configuration. Review the relevant hotel's external room and room-type identifiers before importing; the channel-manager importer requires those mappings to exist.
ForceGuestSearch changes whether guest matching is repeated during updates. Repeated matching can create or link a different guest when data changes, so review that setting deliberately. Timezone correction (mins) and the hotel's time zone also affect interpretation of imported dates.
Do not copy passwords, connection configuration or cookies into documentation or issue comments. When reporting a failure, provide the hotel, operation and redacted error plus the import time.
Reporting rules
Open Hotel → Booking Channel Configuration, choose New, select Hotel and Ota Type, then set Revenue Channel Group and, if known, Default Commission Percentage. Save the record. Each hotel/channel combination must be unique and the percentage must be between 0 and 100.
An empty default commission is unknown, whereas zero is a known zero rate. The default can be copied to new reservations; changing it does not promise to rewrite historical commission snapshots. This record classifies revenue and commission defaults; it does not establish an authenticated import connection.
Verify synchronization
Run the smallest appropriate reservation import, inspect Import Log and compare the resulting booking's dates, room, guest, meal plan and status. Room Availability is a read-only channel-manager view using room mappings. It should not be treated as proof that every reservation has synchronized.
When a booking fails to update, check import activity, mappings, external identifiers and its import-lock state before creating another local booking. Scheduled imports also depend on the background worker; a saved configuration does not prove the job is running successfully.