1. Overview
Content Rules let you condition supply offers (accommodation and transportation) shown in TripBuilder Planner, using include/exclude filters based on hotel, area, country, supplier, rating, cancellation policy, and more.
Extended Content Rules is a rebuilt version of the same feature, keeping the same underlying purpose but changing how rules are structured and combined, removing several workarounds the original version required.
Extended Content Rules currently covers Accommodation rules only. Transport/flight content rules are not part of this improvement, maintaining the same UI and logic.
2. What's Changing
Area | Content Rules (current) | Extended Content Rules |
Rule structure | Action type set per filter, fields scattered through the form | Action type (Exclude / Include Only) sits at the top of the rule header, defined first |
Distribution Channel | One rule per Distribution Channel — duplicate the rule if it must apply to several DCs | A single rule can target one, several, or all DCs — no duplication needed |
Content source | Fixed supplier picker; "Inventory" listed as its own source | Unified source selector covering all suppliers plus Inventory (renamed Nezasa); select any combination, with search-as-you-type |
Combining conditions | Conditions inside one rule are independent; no way to combine multiple filters with AND logic in one rule | Conditions can be combined with AND to build one complex rule (e.g. supplier + area + star rating in a single rule). There is still no OR — every added condition joins the same AND chain. |
Per-condition Include/Exclude switch | Country, Area, Hotel List and Supplier conditions each carry their own Include/Exclude switch, independent of the rule's own type | Removed. Only the rule-level Action Type (Exclude / Include Only) controls direction — individual conditions no longer have their own switch |
Location scoping (Pre-Condition) | Not available | Include Only rules only: an optional Pre-Condition field (Country or Area) that limits where the rule fires at all. Outside the chosen location, the rule does not apply — not even its source restriction. Exclude rules do not get this field. See §3 and §6 for how this changes behaviour. |
Rule collision handling | Every matching rule is applied; if an Exclude condition matches, the offer is removed regardless of any Include Only rule | If an Include Only rule matches an offer, it is kept even if a matching Exclude rule would otherwise remove it. Exclude rules now only take effect when no Include Only rule has already granted inclusion. |
Cancellation filter options | 2 categories: No Free Cancellation, No Cancellation Info | 4 categories: Non-Refundable, No Cancellation Info, Fees Apply, Free Cancellation |
Use Case / User Type | All, Instantiation, Planning / All, Agent, Consumer | Unchanged |
3. Migration Steps
Go to Settings > Content Rules (under the Supply menu).
Use the "Switch to V2" toggle to move from the old rule-creation UI to the new one. As soon as you use this toggle, every existing (old) rule for that Distribution Channel stops being enforced immediately — the switch is an instant, all-or-nothing cutover, not a gradual migration. If you have no Extended rules built yet, the DC will run with no accommodation content-rule enforcement at all until you create some. Plan your rebuilt rule set before flipping the toggle in production to keep this gap as short as possible.
Click Create New Rule for Accommodations
Re-create each existing rule in the new UI
Set the Action Type (Exclude / Include Only) at the top.
Set Use Case and User Type as before — nothing changes here.
Set Distribution Channel(s). If you previously duplicated the same rule across multiple DCs, this is where you consolidate: select all the relevant DCs in one rule instead of keeping the duplicates.
Set Content Source: pick the supplier(s) the rule should apply to. Inventory now appears as Nezasa in this list. You can select one, several, or all-but-one source.
Configure the rule details (hotel, area, country, stars, rating, cancellation filter, travel period, supplier filter). Where the old rule needed several separate rules to express one business need, use AND to combine conditions into a single rule. Remember individual conditions no longer have their own Include/Exclude switch — the whole rule follows the single Action Type set in step a)
Include Only rules only: if you want the rule to apply within a specific country or area, add that location via the separate Pre-Condition field rather than putting it in the main rule details. See the panel below for why this matters.
Save and enable the new rule via its checkbox.
Once the new rule is verified in Planner, disable or delete the old duplicate rule(s) it replaces (bin icon) to avoid conflicting logic.
Choosing Exclude vs. Include Only: for simple, single-condition rules either works. For complex, combined (AND) rules, Nezasa recommends building them as Exclude rules. The "extra layer of refinement" Include Only needs is specific: an Include Only rule that names one or more sources in Content Source automatically stops the system from even searching every other, unnamed source for that DC — before any search runs, not just hiding results afterward. If you only meant that restriction to apply in one country or area, you must add that location as a Pre-Condition (step 4.f) — otherwise the source restriction applies everywhere, silently locking out unnamed suppliers globally, not just where you intended. Exclude rules don't have this hidden side effect, which is why they're the safer default for anything beyond a single simple condition.
4. Consolidation Checklist
Before migrating, it's worth auditing your current rule set — the new UI is built to reduce duplication:
Duplicate-per-DC rules: identify sets of rules that are identical except for the Distribution Channel — these can become a single rule with multiple DCs selected.
Split rules expressing one intent: identify separate rules that exist only because the old UI couldn't combine two conditions (e.g. one rule for "exclude Ratehawk", one for "exclude below 3 stars", both meant to apply together in Lisbon) — these can become one AND-combined rule.
Single-supplier rules: no change needed structurally, but re-check the source selector, since "Inventory" is now labelled "Nezasa".
Rules that mixed per-condition Include/Exclude: if an old rule set some conditions to Include and others to Exclude within the same rule, that can't be expressed in one Extended rule anymore — split it into a separate Include Only rule and a separate Exclude rule instead.
5. Worked Examples
Business need | Extended rule configuration |
Don't offer low-rated hotels (below 3 stars) from Ratehawk in Lisbon | Action: Exclude Use Case: All User Type: All DC: All Source: Ratehawk & Nezasa (Inventory) Details: Hotel stars (1–2) AND Area = Lisbon |
Suppress Expedia offers in DC A & B only, keep them elsewhere | Action: Exclude Use Case: All User Type: All DC: A & B Source: Expedia Details: Supplier Filter |
Give a set of hotels exclusively to Peakwork | Action: Exclude Source: all suppliers except Peakwork Details: Hotel filter A, B, C, D |
Block non-refundable offers from Ratehawk & TBO everywhere | Action: Exclude Source: Ratehawk & TBO Details: Cancellation filter (Non-Refundable) |
Exclude non-refundable rates only in specific sun & sea areas | Action: Exclude Source: All Details: Cancellation filter (Non-Refundable) AND Area = Málaga, Palma de Mallorca, Gran Canaria |
Protect own contracts in Lima by excluding HotelBeds | Action: Exclude Source: HotelBeds Details: Area = Lima AND Supplier Filter |
Only allow Hotelbeds hotels in Spain — leave every other country's supplier mix untouched everywhere else | Action: Include Only Source: HotelBeds Pre-Condition: Country = Spain Details: Supplier Filter
Without the Pre-Condition, this same rule would lock out every non-Hotelbeds supplier worldwide, not just in Spain. |
6. FAQ
Can I run old and new rules at the same time?
No. Once you flip the "Switch to V2" toggle, it uses the new UI for rule creation and every old rule is deactivated immediately — that's what step 6 (disable/delete old duplicates) is there to help you clean up, to prevent conflicting logic once you've rebuilt everything. Old and new rules can't run side by side, even temporarily.
What happens if we switch the "Switch to V2" toggle back off after building Extended rules?
It's safe at the data level — nothing is deleted. All your old rules reactivate immediately and all your Extended rules go inactive immediately. It is not behaviour-safe, though: whatever old rules you'd stopped maintaining resume exactly as they were (possibly stale), and all the Extended rule work is set aside, not merged. Treat switching back off as a full revert, not a quick undo.
What is the Pre-Condition field I only see on Include Only rules?
It restricts where an Include Only rule is active, by country or area. Outside the chosen location, the rule — including any supplier restriction it carries — is switched off entirely for that offer, as if the rule didn't exist. It is not available on Exclude rules. See #3 step 4.f and the worked example in #5.
What happened to "Inventory" as a source?
It's the same source, renamed Nezasa in the new content source selector.
Do I need to contact Nezasa to start using Extended Content Rules?
No. Extended Content Rules will be enabled for your company — you can switch over yourself, whenever you're ready, using the "Switch to V2" toggle.