> For the complete documentation index, see [llms.txt](https://adrasis.gitbook.io/console/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://adrasis.gitbook.io/console/sales-and-distribution/pricing-rules.md). # Pricing rules A rate plan's commercial model says what its source amount means. A **NET\_RATE** plan is quoted net and may receive a distribution markup or discount; a **COMMISSIONABLE** plan is already quoted at the guest-facing selling price and the supplier pays commission out of it. Pricing rules scope the permitted adjustment by market, agency or product, while a minimum selling rate keeps the resolved price from going too low. *** ## Net rate or commissionable The model belongs to the rate plan, not to the search request and not to a partner-facing response field. Different plans in one partnership may use different models.
ModelSource amountPlatform treatment
NET_RATEThe supplier quote is net.The distribution layer may apply its matching markup or discount. The plan carries no supplier commission.
COMMISSIONABLEThe supplier quote is the guest-facing selling price.The distribution-markup step is skipped. The supplier commission is calculated from the plan's commission rate and resolved commission base.
These two earnings paths are mutually exclusive for the same rate plan. An enrolled agency may separately add its **own retail markup** to the amount it owes under either model. That downstream markup belongs to the agency and is never folded into the provider's commercial breakdown. *** ## Layering Rules stack from general to specific, so you set a baseline once and override only the exceptions. * **Market default** — applies to everything a market sells. *"CIS market +12%."* * **Per-agency override** — adjusts one partner against the market baseline. *"Macedonia agency −10%."* * **Product-specific** — pins a rule to a property, room or rate plan. *** ## Which rule wins When more than one rule could apply, the winner is decided in a fixed order: {% stepper %} {% step %} ### Priority The priority you set on the rule comes first. A higher priority always wins. {% endstep %} {% step %} ### Specificity On equal priority, the rule pinned to more dimensions wins — a rule tied to a specific agency and product beats a broad market default. {% endstep %} {% step %} ### Target narrowness On a remaining tie, the narrowest target wins — product over destination over market. This is the last resort and rarely reached. {% endstep %} {% endstepper %} Across organizations in a chain, each organization may apply its own permitted retail markup to the amount it received. Each response retains the information provided by that operation. *** ## The price floor A minimum selling rate is a floor on the resolved selling price. If a promotion or distribution discount would push the price below it, Adrasis raises it back to the floor — it never rejects the sale. Commission does not reduce the commissionable plan's guest-facing selling price; it is settled out of that price. {% hint style="warning" %} **The floor clamps, it does not block.** An over-discounted price is lifted to the minimum and the booking proceeds. You never lose a sale to a too-low rule. {% endhint %} *** ## Plan currency and partner access A partnership can expose independently authored EUR and TRY contract plans from the same property. Existing access and market rules determine which plan the partner can sell; choosing EUR or TRY as a quote currency grants no additional access. Scope a fixed provider markup or floor price to the matching plan and use that plan's currency. Apply a property-wide fixed term only to plans in the property currency. The partner agency's own retail markup is applied to the converted quote in the quote's currency. *For Hotel Sunrise's TRY plan, enter a plan-specific TRY 400 markup. An EUR 10 property-wide markup is not interpreted as TRY 10.* *** ## What stays private * **Search and booking responses present the partner’s payable total.** Their existing price projection omits upstream commercial composition. Availability checks retain their diagnostic trace and optional nightly price details, including the applicable floor and adjustment. * **The partner's retail markup never reaches the provider.** What the agency charges its own customer is its business; only the agency can see its own retail layer. ## Where to next * **Scope the markets a rule applies to** → [Markets](/console/sales-and-distribution/markets.md) * **How prices are built from rate plans** → [Pricing engine](/console/pricing-and-availability/pricing-engine.md) * **Choose which products a partner sees** → [Access](/console/sales-and-distribution/access.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://adrasis.gitbook.io/console/sales-and-distribution/pricing-rules.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.