Automation Rules

Create visual workflows to automate warehouse operations and business processes with triggers, conditions, actions, variable handling, and execution history in one system.

5,678 executions

Rule Builder

5,678 executions

When

Order status = Paid

AND

Weight > 5 lbs

Then

Assign carrier: FedEx Ground

Build rules visually, not in code

Automation rules use event-driven triggers with condition matching to decide what happens. Conditions evaluate against live warehouse data so ops teams can configure logic without engineering involvement.

  • Event triggers: orders/created, shops/updated, inventory changes
  • 20+ condition operators including equals, greater than, contains, starts with, regex, and more
  • Variable interpolation in action configs for dynamic values
Last run: 2 min ago

Active Rules

RuleStatusExecutionsTags

FedEx Ground > 5 lbs

Enabled

1,234

shipping
carrier

Same-day SLA priority

Enabled

3,891

sla
priority

Hazmat hold for review

Disabled

553

compliance

Visible, auditable execution

Every rule fire is logged with the trigger event, matched conditions, and actions that ran. When a step fails, the execution record shows exactly which action broke and why.

  • Filter executions by status: Pending, Processing, Completed, Failed, Cancelled
  • Tags for grouping rules by merchant, workflow area, or priority
  • Validation rules catch misconfigured automations at setup time

Rule engine

Visible, auditable automation that ops teams can own

Draft and publish workflow

Rules are edited in draft state with a full configuration UI. Publish when ready, disable when not needed, and re-enable without rebuilding. Every rule tracks its enabled state independently.

Step-by-step execution

Each rule execution logs every step with its own status, start time, completion time, and error message. When a step fails, the execution record shows exactly which action broke and why.

Execution audit trail

Every rule fire is logged with the trigger event type, context ID, processing status, and timing data. Teams can filter executions by status (Pending, Processing, Completed, Failed, Cancelled) to diagnose issues.

Make operational logic enforceable

Give ops teams a visible automation layer with event-driven triggers, condition matching, step-level execution logs, and configurable actions they can manage without engineering.

Schedule a Demo