The Elo Cloud family
EloERP Cloud
Start Free Trial
The compliance differentiator

FBR, ZATCA, MyInvois & UAE e-invoicing — built into every invoice, not a bolt-on. Sell compliantly from day one.

Compliance hub
Ecommerce › Automation & rules

Rules that protect margin while you sleep

An event-driven rule engine that watches every order and acts on the same data your ledger uses — real order values, real risk tiers. Hold the risky ones, auto-verify the safe ones, require prepay where it counts, then auto-book the rest. Every action is logged, every rule can be tested first, and automation can never block an import.

Rule engine

Event, condition, action — evaluated in the order you choose

Every rule is built from three parts. A trigger decides when the rule is considered, a set of conditions decides whether it applies to this specific order, and one or more actions decide what happens next. Rules run in priority order, and a matched rule can stop the chain so lower-priority rules never override a decision that’s already been made.

  • Triggers fire on order created, verified, confirmed, or a delivery-failed event
  • Conditions match on value range, payment type, channel, city list, tag, risk tier, or a duplicate window
  • Actions hold, require verification, require prepay, cancel, add tags, assign an agent, or auto-book
  • Priority-ordered with a stop-on-match option that breaks the chain when a decisive rule fires
  • A live fire count and a last-fired timestamp on every rule, so you can see what’s actually working
rule #7 · high-value COD guard
When
order created
If
value > 15,000 and payment = COD and risk = high
Then
require prepay · add tag “screen” · stop
priority 20 · stop-on-matchfired 341× · last 2m ago
The rule vocabulary

Three building blocks, one predictable engine

Combine any trigger with any set of conditions and any list of actions. The vocabulary is small on purpose — so a non-developer can read a rule and know exactly what it does.

Triggers

The lifecycle event that puts a rule up for evaluation.

  • Order created
  • Order verified
  • Order confirmed
  • Delivery failed

Conditions

All must match for the rule to apply to an order.

  • Value range & payment type
  • Channel & city list
  • Tag & risk tier
  • Duplicate window

Actions

One or more effects applied when the rule fires.

  • Hold & require verification
  • Require prepay & cancel
  • Add tags & assign agent
  • Auto-book the shipment

Because conditions read the same fields your order desk and ledger use, a rule that says risk = high is acting on the exact risk tier an agent sees — not a separate, drifting copy.

dry-run · order #EL-51902
Auto-verify low value would fire
High-value COD guard skipped — value below range
Auto-book verified would fire
No changes committed — this is a preview. Apply to run for real.
Dry-run & audit

Test a rule on a real order before it ever touches one

Automation should be predictable. A dry-run shows exactly which rules would fire for a real order — and which would be skipped, and why — without committing a single change. Once rules are live, every action they take is written to a full audit trail.

  • Dry-run preview against a live order, showing every rule’s match decision
  • A full audit trail — every action logged with rule name, outcome and detail
  • Skipped and failed actions are logged too, so debugging is never guesswork
  • Fail-safe by design: an automation failure never prevents an order import
Built to switch on cleanly

Self-healing schema, and one log for every sync

Turning automation on shouldn’t mean a migration window or a support ticket. The module provisions what it needs on demand, degrades gracefully when it doesn’t, and records every sync — manual, webhook or service — in one filterable place.

Tables created on first access, per tenant

The schema is self-healing — the tables a tenant needs are created the first time the module is used. There’s no separate migration step to activate automation, and each tenant is isolated.

Graceful degradation, never a hard failure

When an optional table doesn’t exist yet, the module degrades gracefully instead of erroring — the rest of the order flow keeps running while the missing piece heals itself into place.

One unified sync log

Manual UI syncs, webhook events and service calls all land in a single view. Filter by platform, sync type, status or date range to trace exactly what moved and when.

Conflict resolution & payload retention

Choose local-wins or remote-wins when a record diverges, and keep webhook payloads on hand for debugging — so a disputed sync can be replayed and understood instead of guessed at.

The same fail-safe principle runs through the module: automation and sync are additive layers over the order desk — they can heal, degrade or retry without ever stopping an order from being imported.

Explore the suite

Automation acts on the same data the whole module shares

← Back to the Ecommerce overview

Automation that never blocks an import

Let the rules do the routine — and prove every move

Hold, verify, require prepay and auto-book on your terms — dry-run first, audited always, acting on your real books. Start free for 14 days.

Start 14-Day Free Trial Book a demo
Schedule a demo