Multi-channel orders, multi-courier logistics, live tracking and COD & gateway reconciliation — every online sale posted to your real books.
Explore the Ecommerce moduleFrom auto spare parts to optical stores to cloud kitchens — find the configuration made for you.
Browse all industriesFBR, ZATCA, MyInvois & UAE e-invoicing — built into every invoice, not a bolt-on. Sell compliantly from day one.
Compliance hubBook a free 30-minute demo on your own kind of business — no slides, just the product.
Book a demoAn 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.
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.
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.
The lifecycle event that puts a rule up for evaluation.
All must match for the rule to apply to an order.
One or more effects applied when the rule fires.
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.
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.
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.
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.
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.
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.
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.
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.