---
title: Nested If-else and Merge is now available
slug: nested-if-else-and-merge-is-now-available
docTags: 2PhNMll2pynOxQSFeuETM,PwOvfiFKzjFaUXg5rDcTy
createdAt: 2026-05-20T08:00:34.263Z
---

You can now build multi-level decision logic inside one scenario with Nested If-else & Merge. Keep related conditions in one visual flow, so teams can review changes faster and follow how each branch connects.

![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/mk3vZASqEHtorK2Z9Uuui_image.png)

### What's new

- **Nested decision paths**: Place an If-else module inside a branch of another If-else, so you can model detailed business rules without spreading logic across separate Router chains.
- **Cleaner scenario reviews**: Keep related branches together in one flow. Your teammates can now see the whole scenario at one glance to trace decisions, check changes, and understand what the scenario does.
- **Clear merge points**: Give each nested If-else its own Merge module, so every decision level closes in the right place and the scenario stays easier to maintain as rules change.

### When to use it

- A condition inside one branch depends on evaluating a second, related condition.
- You want to keep logically related rules together rather than splitting them across separate Router chains.
- You need teammates to be able to trace and review decision logic in a single flow.

For more information, see the [Nested If-else and Merge](docId:5F6OZVB5VL2gvDsA7EoRP) documentation.