Table of Contents
Join Thousands of Hotels Thriving with roommaster
The transition to roommaster is straightforward and efficient. Our implementation team handles data migration including reservations, guest profiles, and historical information.
Connecting a hotel to Feratel Deskline means securing a direct contract, requesting mapping codes, and matching room categories exactly between your PMS and Deskline. Most of the real work happens in the mapping details.
Connecting to Feratel Deskline refers to three prerequisites: a direct contract, mapping codes, and matching room categories across systems.
Feratel requires a direct relationship before any technical setup begins. Preparation covers three things, each handled slightly differently.
Requesting mapping codes takes the longest lead time of the three. It depends on Feratel's own turnaround time. The request typically includes the service provider's name, full address, and contact information. Many channel manager providers handle this request on the hotel's behalf. It's often part of onboarding a new connection.
Feratel's destination management system overview has more background on how Deskline connects properties. Starting this request early avoids delays once the technical setup is ready to go.
None of these three prerequisites happen inside the PMS itself. They're confirmed by Feratel before the connection can be enabled.
Most PMS and channel manager providers that operate in Feratel's markets already have a built-in connection option.
Check with the hotel's PMS or channel manager provider before assuming setup means custom development. Many platforms already list Feratel Deskline as a supported connection. It's usually inside their integrations or channel manager settings.
A few places to check first:
If that option exists, the next section covers exactly what to configure. If it doesn't exist yet, ask the provider directly. A Feratel connection may be available or planned.
Providers vary by region, since Feratel Deskline serves primarily European and Alpine destination markets. A hotel outside that footprint may find the option isn't offered at all.
Connecting to the Feratel Deskline follows five clearly defined steps once the contract and mapping codes are in place.
Open the integrations, apps, or channel manager section inside the PMS. Look for Feratel Deskline in the list of available connections and select it.
Most platforms label this section clearly rather than burying it in general settings. If Feratel Deskline isn't listed at all, that's a sign the connection isn't supported yet.
Enter the company code, mapping code, and municipal number Feratel issued during the mapping request. Use them exactly as provided. A single typo in any of these fields can prevent the connection from activating.
Set the sync parameters the platform asks for at this stage:
These settings affect how rates calculate once the connection goes live. Double-checking each one before saving prevents a second round of corrections later.
Reload or fetch the property's listings inside the PMS. Link each local room category to its matching Feratel Deskline category. This has to happen manually. Feratel doesn't guess which room type corresponds to which listing.
Room categories rarely match one-to-one by name alone. A hotel might call a room "Deluxe King," while Feratel's system expects a different label. Matching by capacity and amenities avoids most mapping errors.
Save the configuration once every field is entered and every room category is mapped. Most platforms run a validation check automatically at this point.
A successful test shows the same rate and room type on both sides. The matching rate should appear within a few minutes of the update. A failed test usually shows one of two signs. Either no change appears on Feratel's side, or the room type is wrong.
If the status doesn't change to active, check two things first. The most common cause is a mismatched mapping code or an incomplete room category link.
The most common mistakes happen in the mapping details, where small errors quietly break the sync.
A room category left unmapped or mismatched is the most common reason a connection fails to sync rates correctly. Feratel can't sync a room type it doesn't recognize.
A new room type added after initial setup is the usual trigger. The new type never gets mapped on the Feratel side. The fix is straightforward. Revisit the mapping any time room types change.
Saving the configuration isn't the same as confirming it works. A connection can show as saved while still failing to sync live data.
Testing catches problems before a guest ever sees a wrong rate or availability. Skipping it means the first real test happens with a live booking instead. Finding an error that way costs far more.
A quick test rate and a sample booking check take only a few extra minutes. A check this small catches most configuration errors before they reach a guest.
Mapping codes and room category links don't transfer automatically. They don't carry over when a hotel switches PMS or channel manager providers. The new system starts with no Feratel connection at all.
Mid-season provider switches are the most common point where this gets missed. The listing can go dark on Feratel's side without an obvious warning.
Requesting new mapping codes and re-mapping room categories should be part of any transition plan.
Connecting a hotel to Feratel Deskline is a two-part process. The contract and mapping codes come from Feratel directly. The technical configuration happens inside the hotel's own PMS or channel manager.
Most of the actual risk sits in the mapping details. Room categories, company codes, and municipal numbers all need to match exactly. That's what makes the sync work.
Testing the connection before relying on it catches most errors early. A saved configuration isn't proof the sync actually works until it's been verified.
For hotels on a supported PMS, this process compresses to two things: settings and mapping. No custom development is needed.
{{cta-strip}}
Is a direct data link between a hotel's PMS or channel manager and Feratel's distribution system.
Takes longer for the contract and mapping codes than for the technical setup itself, since Feratel controls that timeline.
Requires configuration inside existing PMS settings for most providers already supporting the connection.
Causes usually trace back to a mismatched mapping code or an unmapped room category.
Depends on whether the specific PMS or channel manager has built a supported Feratel integration already.
The transition to roommaster is straightforward and efficient. Our implementation team handles data migration including reservations, guest profiles, and historical information.
See how roommaster's unified platform can work for your property. Our team will walk you through features tailored to your specific needs and operations.