# Exceptions & Fallback

Even with well-defined rules, there are always cases where the expected product set cannot be fully generated. To ensure stability and consistency of your strategies, **exceptions** and **fallbacks** are built into the rule engine.

### **Exceptions**

* Allow you to *exclude specific cases* or define special treatments.
* Example: *If the current product belongs to “outlet” category, exclude it from recommendations.*
* Practical use: avoid showing restricted categories, duplicate products, or unwanted items in a given context.

### **Fallbacks**

* Define what happens if a rule does not return enough products (e.g., fewer than the required 12).
* Examples:
  * Fill remaining slots with *global top sellers*.
  * Show a *default curated list*.
  * Hide the block entirely (last-resort option).
* This ensures **no empty space** in your templates and guarantees a **predictable user experience**.

{% hint style="info" %}
Exceptions & fallback rules provide **resilience**. They prevent broken layouts, ensure continuity of engagement, and avoid showing irrelevant or empty recommendations
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.abtasty.com/recommendations-and-merchandising/concepts/strategies/rules/exceptions-and-fallback.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.