Rules Engine

Automate the busywork

Five rule engines, 24 action types, 20 operators, and 55+ condition fields — all no-code. Rules can target any field in your order metadata. First rule to claim a field wins.

5
Rule Engines
independent pipelines
24
Action Types
no-code automation
20
Operators
string, numeric, date
55+
Condition Fields
extractor registry

Five engines, one pipeline

Every order passes through five independent rule systems — each handles a different concern. They execute in sequence with zero interference.

1
Territory RulesGate

Block orders from disallowed shipping regions. Country + state/province validation.

2
Automation Rules24 actions

24 action types: route, tag, hold, release, set carrier, expedite, flag, cancel. Priority-based — first rule to claim a field wins.

3
Hold RulesTime + inventory

Time-based holds with business hours awareness. Inventory watch holds until SKU is back in stock. Auto-release scheduler.

4
Pre-Order RulesSKU holds

Hold orders containing specific SKUs until a release date. Split-or-hold mode for mixed pre-order orders.

5
Routing RulesDestination

Assign shipping destination based on conditions. First match wins. Stamps route_destination on the order before dispatch.

No-Code Builder

IF this, THEN that

Build rules visually — pick conditions from 55+ extracted fields, set operators, chain actions. Recursive AND/OR logic for complex conditions. Rules can target any field in your order metadata, including custom fields.

Drag-and-drop condition builder with AND/OR nesting
Field mapper targets any data point — order, customer, shipping, line items, computed
Walter AI creates rules from natural language ("hold orders over $500 from California")
Priority ordering with field ownership — prevents conflicting rules
Every evaluation logged — see exactly why a rule did or didn't match
Expedited Shipping RuleActive
Conditions (AND)
tagscontains"ExpeditedShipping"
totalgreater_than50.00
Actions
set_shipping_methodUSPS Priority Mail
add_tag"Priority-Processed"
set_priorityhigh
Field ownership: shipping_method claimed — lower-priority rules cannot overwrite

20 operators

String, numeric, date, list, and pattern matching — every comparison you need.

Comparison

6 operators
equalsnot_equalsgreater_thanless_thangtelte

String

4 operators
containsnot_containsstarts_withends_with

List

2 operators
in_listnot_in_list

Date / Time

4 operators
beforeafterolder_than_daysnewer_than_days

Range

1 operator
between

Pattern & Existence

3 operators
regex_matchis_emptyis_not_empty

24 actions

Route, tag, hold, notify, flag, cancel — every action fires in priority order.

Routing & Fulfillment

Control where orders go and how they ship.

Set Warehouse
Route Destination
Set Shipping
Assign Carrier
Allocation Node
Set Route
Route Warehouse

Order Lifecycle

Hold, release, expedite, cancel — full lifecycle control.

Hold Order
Release Hold
Expedite
Cancel
Skip Order
Set Status
Set Priority
Ship Date

Metadata & Tags

Annotate orders with tags, notes, flags, and custom fields.

Add Tag
Remove Tag
Add Note
Flag Order
Custom Field

Communication & Advanced

Alerts, logging, exceptions, and custom scripts.

Notify
Log Message
Create Exception
Custom Script
Order
17 fields
sourcesource_idstatusexternal_idtotaltags+11 more
Customer
3 fields
customer_emailcustomer_namecustomer_phone
Shipping
7 fields
shipping_stateshipping_countryshipping_cityshipping_zipshipping_methodtotal_weight+1 more
Line Items
5 fields
skusskusku_listline_item_countitem_quantities
Computed
13 fields
order_hourtotal_quantityavg_item_priceunique_sku_countis_high_valueis_international+7 more
Aliases
11 fields
shipping.stateshipping.countryshipping.cityshipping.zipshipping.methodline_items.sku+5 more
Extractor Registry

55+ fields, any order format

The extractor registry is a centralized field extraction system that pulls structured, type-safe values from any order — Shopify, Amazon, Acumatica, SPS Commerce, email CSV, or any other source. Same fields, same operators, regardless of where the order came from.

Single source of truth for field extraction across all 5 rule engines
Type-safe: STRING, NUMBER, BOOLEAN, LIST — operators auto-filter by type
Custom metadata fields supported — rules can target any JSON path
Aliases for backward compatibility (shipping_state → shipping.state)

Rules that write themselves

Tell Walter what you need in plain English. It builds the rule, shows you a preview, and saves it — no coding, no guessing.