> For the complete documentation index, see [llms.txt](https://docs.homescriptone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.homescriptone.com/wordpress-plugins/doko-bundle-builder-the-ultimate-dynamic-bundle-builder-for-woocommerce/configuration/how-to-configure-dynamic-rules-for-each-steps-in-doko-builder-pro.md).

# How to configure dynamic rules for each steps in Doko Builder (PRO) ?

In order to create a new bundle, access your WordPress dashboard and head to the **Bundle Rules** menu.

<figure><img src="https://3823528938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3z3RATm3FlzqlvbHrX9%2Fuploads%2FaBEffGpwiAbloz0z5jMh%2Fimage.png?alt=media&amp;token=5617fefb-60c0-47a3-bb6a-b6e8d1437788" alt=""><figcaption><p>submenu doko bundle rule</p></figcaption></figure>

Then clicks **New Bundle Rule** and you will be redirected to this this page :&#x20;

<figure><img src="https://3823528938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3z3RATm3FlzqlvbHrX9%2Fuploads%2FbcxhyDIdhzLzNcceh3Qt%2Fimage.png?alt=media&amp;token=d5f7a363-8923-4311-9d09-57bc67111303" alt=""><figcaption><p>new bundle rule creation</p></figcaption></figure>

The page shows many fields that must be filled so the rules be applied smoothly : &#x20;

* **Bundle Rule Name :** Give the bundle rule you're creating a name that only you will see.
* **Bundle where this rule will apply :** Specify the bundle to which this rule applies, you can only apply it to one bundle at a time.&#x20;

Once you have selected the bundle,  click **Add Rule** to specify the rules you want for this bundle.

<figure><img src="https://3823528938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3z3RATm3FlzqlvbHrX9%2Fuploads%2FIsCwycZMRu3WrrHhRv15%2Fimage.png?alt=media&amp;token=d900de30-36df-4781-b2ae-ecd72836da87" alt=""><figcaption><p>define-rule</p></figcaption></figure>

Once the rule is added, customize-it the way you would like by filling the various field or options present there :&#x20;

* **Step Name :** Choose the step where this rule must be applied,
* **Rules :** Specify the trigger of the rules, you can say if a specific product or a group of products are the ones that trigger these rules.<br>

  <figure><img src="https://3823528938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3z3RATm3FlzqlvbHrX9%2Fuploads%2Fvb0taKjySHeBhv2fgeSa%2Fimage.png?alt=media&amp;token=858fb178-0dad-458a-aa00-7e2d51c855ab" alt=""><figcaption><p>rules-for-bundle-rules</p></figcaption></figure>
* **Action :** Specify the action to execute once the rule has been triggered. The available action are listed below :<br>

  <figure><img src="https://3823528938-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg3z3RATm3FlzqlvbHrX9%2Fuploads%2FGKLtCgy27cpvTDVNiysm%2Fimage.png?alt=media&amp;token=6db0090e-b7a0-4f47-8551-a264e1f2ce59" alt=""><figcaption></figcaption></figure>

  &#x20;

  * **Limit product in next step :** This restrict the numbers of products users will be able to add to their bundle in the next step,
  * **Limit product in current step :** This restrict the numbers of products users will be able to add to their bundle in the current step,
  * **Limit amount in current step :** This restrict the product amount users should be able to add to their bundle in the current step,
  * **Limit amount in next step :** This restrict the product amount users should be able to add to their bundle in the next step,
  * **Go to step :** This redirect the user to the step defined if the rule is triggered.

Find below, a tutorial video showing how to configure the dynamic rules for each steps in Doko Builder plugin :

{% embed url="<https://youtu.be/zZJ4flUC04g>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.homescriptone.com/wordpress-plugins/doko-bundle-builder-the-ultimate-dynamic-bundle-builder-for-woocommerce/configuration/how-to-configure-dynamic-rules-for-each-steps-in-doko-builder-pro.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
