Skip to main content

Availability Rules

Learn how to configure Availability Rules in Claimlane to hide, block, or label products in self-service flows based on attributes such as SKU, EAN, tags, request type, or mapped fields.

Written by Support team

What Availability Rules are used for

Use Availability Rules when you need to:

  • Hide products from product search in a self-service flow (so end-users never see them).

  • Hide products from orders in a self-service flow.

  • Mark products as unselectable (visible, but blocked) with a custom label explaining why.

Common examples:

  • Exclude final sale items from certain flows.

  • Show only warranty-eligible items.

  • Restrict a flow to a small list of SKUs/EANs for a campaign, pilot, or partner setup.

How it works (conceptually)

An Availability Rule has three parts:

  1. Scope (optional): which request type / flow context the rule applies to

  2. Conditions: which products it matches (e.g., SKU, EAN, tags, mapped fields)

  3. Effect: what happens to matching products (hidden / blocked / labeled)

Setup guide (step-by-step)

  1. Open the product datasource that your flow uses.

  2. Go to Availability Rules (in the datasource settings).
    ​

  3. Click Add rule.

  4. Configure the rule:
    ​

    1. Name: use a clear purpose-driven name (e.g., "BD flow – only allowed SKUs") (Optional)

    2. Request type scope: choose the request type(s) this should affect (recommended when the same datasource is used across multiple flows)

    3. Conditions: define how to match products (for example SKU/EAN)

    4. Effect: choose one:

      • Hide from product search

      • Hide from orders

      • Mark as unselectable + set a label (e.g., "Not eligible for this flow")

  5. Save the rule.

  6. Test the flow:

    1. Search for an allowed product (should appear and be selectable)

    2. Search for a blocked product (should be hidden or blocked, depending on the effect)

When you might need a new datasource instead

Create a new datasource only if:

  • The flow needs a different underlying product catalog, or

  • The flow requires different product attributes/mappings that can’t exist in the shared datasource.

In most cases where it’s “same datasource, different subset of products,” Availability Rules are the intended solution.

Did this answer your question?