Examples of rules that connect modules

Four examples of rules that connect modules. The trigger and action names in your panel may read slightly differently and new ones keep arriving — treat this as a way of thinking and check the specifics on the list when creating the rule. Remember the only principle: you create the rule where the action should run.

1. The last item sells → the offer disappears from other channels

Where: OmniChannel → Automated actions
When: Offer purchased
Do: End the offer on the remaining accounts (or Reduce stock on the remaining accounts)

2. An order lands in OMS → the warehouse plans a route

Where: WMS → Automated actions
When: Order downloaded from OMS
Do: Plan picking routes

Routes then appear on their own instead of waiting for someone to click "Plan a route".

3. A picker reports a shortage → a reaction on the sales side

Where: WMS → Automated actions
When: Missing product reported during picking
Do: Change order status (to one of your own that stands out) and fire a custom trigger

This is exactly the case where warehouse information has to reach sales immediately, not at the end of the day.

4. A new product in PIM → an update in the warehouse

Where: WMS → Automated actions
When: Product created in PIM (or edited, price changed, VAT rate changed)
Do: Fetch product information from PIM

A rule can perform several actions in sequence and can be narrowed with conditions — only for a chosen order source, or only for paid orders. It is worth assigning every rule to an action group, because beyond a dozen rules you will lose track without it.