A rule in Order Daemon has three parts. The trigger (WHEN) defines the order event that starts evaluation, for example when an order status changes to Processing. The conditions (IF) are optional filters that must all pass before anything happens, for example if every item in the order is a virtual product. The action (THEN) is what fires when the trigger occurs and all conditions pass, for example automatically set the order status to Completed.

How rules evaluate

When a trigger event fires, Order Daemon evaluates every active rule that uses that trigger. Conditions are evaluated in order, and all of them must pass. If any condition fails, the rule stops there and the action does not run. Actions fire once per trigger event, not repeatedly. Rules are independent, so a later rule does not know whether an earlier rule ran or failed.

A worked example

Consider a store selling a mix of physical and digital products. You want digital-only orders to complete automatically without manual review.

• WHEN order status changes to Processing
• IF all items in the order are virtual
• THEN set order status to Completed

The trigger fires every time any order reaches Processing. The condition checks the item types and blocks the action for mixed or physical orders. Only pure digital orders move forward and get completed automatically. The customer receives the standard WooCommerce order completion email, and your fulfillment queue stays clean.

This is one of the most common automations Order Daemon handles, and it requires only the free plugin.

Free and Pro components

The free plugin covers the most common automation patterns. Core triggers include order status changes, payment events, and order creation. Core conditions cover item properties, order totals, and product categories. Core actions include status changes, order notes, and email notifications.

Pro extends the available components in each category. Pro adds scheduled triggers, webhook triggers (fire a rule when an external service posts to your site), timing-based conditions, the webhook action for sending HTTP calls to external services, rule export/import, and the rule testing tool.

Child docs in this section

• How Rules Work explains the full evaluation model, including rule priority, error handling, and what happens when an action fails
• The Rule Builder walks through the UI step by step
• Triggers, Conditions & Actions is the full catalog of every built-in component with configuration options
• Testing Rules covers the Pro rule testing tool Pro
• Export & Import Rules covers moving rules between sites Pro