Automation rules v2: nested conditions and simulation

The rules engine at Admin → Automation → Rules now supports nested condition groups, so you can write logic like "(weight > 5lb AND zone ≥ 5) OR (has_battery AND destination = CA)" without splitting it into multiple rules. You also get 11 new condition fields: custom_field_1, custom_field_2, custom_field_3, customer_lifetime_value, customer_order_count, postal_code_pattern, has_dangerous_goods, has_battery, store_tag, order_age_hours, and shipping_method_requested.

Beyond the original "set carrier" and "set warehouse," v2 adds: add_insurance, require_signature, hold_for_review, assign_tag, send_notification, set_package_preset, set_priority, route_to_3pl, and add_packing_note. Actions stack—a single matched rule can require signature, add $500 of insurance, and route to your CA warehouse all at once.

Drag conditions into groups. Each group has its own AND/OR operator, and groups can be nested up to 5 levels deep. The rule editor renders the structure as a tree so you can see at a glance what's being evaluated. A flattened "all conditions AND" rule still works the same as before—just don't use groups if you don't need them.

Hit the Simulate button and ShipWave evaluates your draft rule against your last 100 orders. You see exactly which orders would match, what actions would have fired, and which conditions failed for the non-matches. This is the single biggest fix in v2—you can finally tune a rule without saving, watching production traffic, and rolling it back.

Rules execute in priority order, low to high. The first rule that matches wins (unless you mark a rule as continue, which lets later rules layer on top). Every rule can be set to dry-run, which logs what it would have done without actually doing it. We recommend running every new rule in dry-run for 24-48 hours before flipping it live.