STL Cookbook

DerbySoft Go channel connectivity

Platform contracts, OTA mapping responsibilities, and the standard stages from signing through Go-Live for a new channel.

Read this page when revenue or channel-connectivity colleagues add a new OTA, or add hotels to an existing channel. To list rate plans on channels in Console, see Distribution. This page covers DerbySoft Go contracts, mapping, and go-live stages.

Contracts and products

  • Platform: STL; hotel brands: Stey, Magpie.
  • The DerbySoft contract party is planned to change from Stey to STL; the hotel or STL signs separately with each OTA.
  • Go: interface exchange for CRS; Property Connector (PC): channel management for hotels.
  • Go charges a reservation fee per contract; adding a new channel has no extra connectivity fee.

Mapping rules

Mapping chain: OTA ID ↔ STL external Code ↔ STL internal UUID.

DerbySoft maintains the first layer (OTA ID ↔ STL external Code); STL maintains the second (STL external Code ↔ STL internal UUID). For Booking.com, the current external Code uses the OTA back-office ID.

ChannelOperationsProduct & engineering
Booking.comSubmit Hotel / Room / RP mapping sheetsUpdate Go interface data
Expedia / Ctrip / TripSubmit Hotel mapping; in the channel back office, configure the relationship between STL external RP (rate plan) and the channel RPUpdate Go interface data; DerbySoft pulls the mapping directly

Fill out a separate form for each OTA. Expedia, Ctrip, and Trip do not need a separate RP mapping sheet.

New OTA onboarding process

  1. Contracting: Supply and distribution parties complete the commercial agreement.
  2. Kick-off: DerbySoft opens the project, provides a Connection Overview (CO), and both sides confirm and sign.
  3. Configuration and testing: Finish certification / production configuration and API integration testing.
  4. Pilot: After tests pass, run a limited set of hotels in trial.
  5. Go-Live: After the pilot is stable, roll out fully—usually about two weeks after Pilot starts.

Adding hotels to an existing channel usually only needs mapping configuration.

On this page