Automations

Automations overview

Automations are if/then rules that run against orders as they land in EcomFlux — typically right after a channel sync brings in new or updated rows. They let ops teams enforce policy without babysitting every SKU: route by country, flag risky orders, or prep payloads for downstream systems.

Where to configure them

Open Dashboard → Automations (or the automation hub path shown in your workspace navigation). The in-app editor is the source of truth for triggers, conditions, and actions available on your plan.

Common building blocks

  • Triggers: Order created or updated from sync; some workspaces also expose status transitions (e.g. paid → ready to ship) depending on feature flags.
  • Conditions: Filters on shipping country, order total, SKU patterns, channel, tags already present, weight bands, or custom fields your team uses.
  • Actions: Add or remove tags, move orders to a hold queue, assign a default courier preference, notify a webhook, or enqueue work for integrations — match what you see in the Visual Automation Engine.

Example recipes

  • International prep: If destination is outside your domestic region, add tag INTL-DOC and require manual review before label purchase.
  • High-value gate: If order total exceeds a threshold, hold until a supervisor releases — reduces fraud exposure on new channels.
  • Channel-specific routing: If source is Amazon FBA vs merchant-fulfilled, branch tags so fulfillment SOPs differ in the Orders views your team uses.

Best practices

  • Start narrow: Ship one automation, watch audit or order logs, then expand.
  • Avoid loops: Rules that re-trigger on their own writes can churn; test with staging data when available.
  • Pair with channels: Reliable automations depend on clean channel mapping — see Sales channels overview.

Related