Real commerce systems generate constant events. Automation must coordinate actions across systems, not just react once. Tanqory treats automation as a first-class orchestration layer that reduces manual work without losing human control.
Part of Tanqory Commerce Core
Automation reacts to real operational events. When orders change state, inventory hits thresholds, customers are created or tagged, or carts are abandoned—automation responds deterministically.
Order created, paid, fulfilled, shipped, returned, canceled. Each state transition can trigger workflows: send notifications, update inventory, initiate fulfillment, alert teams.
Stock falls below reorder point, item goes out of stock, item restocked. Send supplier notifications, alert purchasing, or notify waitlisted customers automatically.
Order paid, canceled, or refunded. Trigger order processing, customer follow-ups, accounting webhooks, and review workflows based on the order's payment outcome.
Order fulfilled. Trigger customer notifications, tracking updates, and downstream webhooks. Order state transitions drive fulfillment-stage workflows.
Product created or updated, custom webhook received, scheduled time reached, or a workflow triggered manually. Connect external systems and time-based jobs into the same orchestration layer.
Subscription activated, renewed, upgraded, downgraded, paused, canceled. Planned trigger category to drive billing, access control, and retention workflows.
Event-driven, not polling. Deterministic behavior. Predictable outcomes.
Automation that survives edge cases—not breaks on them
Define conditions based on order value, customer type, product category, location, inventory levels. Rules execute only when all conditions match.
→ Precise control over when automation runs
Chain multiple actions together. Order paid → Reserve inventory → Route to fulfillment → Send confirmation → Update analytics. Each step either completes or fails cleanly with a clear recovery path.
→ Complex operations automated reliably
Actions execute in sequence as an ordered chain. Failed executions retry automatically with exponential backoff. Schedule-based and event-based triggers fire workflows when conditions are met.
→ Predictable ordering with automatic retry
Planned: pause workflows for approval before sensitive steps. Currently, a triggered workflow runs its action chain without these approval pauses.
→ Planned controls
Workflows tied to explicit system states. Execution guaranteed to run once, or not at all. Every action traceable and auditable.
Workflows trigger on state transitions, not arbitrary events. Order moves from 'paid' to 'fulfilled'—automation runs exactly once for that transition.
Actions are designed to avoid duplicate effects—a tag is added only if not already present, executions are tracked per run, and retries use backoff rather than blindly repeating.
Every workflow run logged with timestamp, trigger event, actions taken, outcomes. Finance and ops teams trace exactly what automation did and why.
When steps fail, workflows halt cleanly. No partial executions that corrupt data. Retry logic built in. Manual intervention paths clear.
Idempotent execution. Failures surface clearly. Full execution history.
Automation accelerates teams—it does not replace judgment
Notify store admins by email or Slack so people can review important events. Notifications do not pause a running workflow for approval.
→ Admin notifications
Enable or disable a workflow and review it before use. Disabling prevents new executions; it does not mean stopping an execution already in progress.
→ Control new executions
When an action fails, the execution is marked failed with the error captured, retried with backoff, and reported to error monitoring. Failures are visible in execution history, not swallowed.
→ Failures are traceable and recoverable
Planned: manual approval pauses and hard refund or bulk-operation limits. Use conditional rules and admin notifications for sensitive steps today.
→ Planned controls
Automation connects operations, fulfillment, finance, customer success, and marketing. Workflows drive coordinated responses across the business.
High-value order placed → Notify ops team. Inventory below threshold → Alert purchasing. Order refunded → Notify finance. Notifications go out by email or Slack with priority levels.
→ Teams informed in real-time
High-value order placed → Notify ops for review. Order refunded → Alert the finance team. Order matching a risk condition → Escalate to admins via email or Slack before it ships.
→ Problems escalated automatically
Order paid → Notify the warehouse or post to a fulfillment system via webhook. Inventory restocked → Alert the team to release backorders. Use webhooks to hand off to WMS and ERP systems.
→ Ops-to-fulfillment handoff via notifications and webhooks
Cart abandoned → Send a recovery email and generate a discount code. New customer created → Send a welcome email and tag the customer. Product restocked → Alert customers who were waiting.
→ Revenue recovery automated
Operational outcomes. Reduced response time. Fewer manual handoffs.
A planned layer to support better decisions—surfacing patterns for review, never acting autonomously without human sign-off
System identifies recurring operational patterns. Frequent customer service issues, inventory restocking cycles, payment failure trends. Patterns surface for review.
Based on observed patterns, system suggests automation rules. 'Orders over $500 frequently need fraud review' → Suggest automatic review workflow.
Track automation effectiveness. How often do workflows complete successfully? Where do manual overrides happen? Use data to refine rules.
Pattern-based recommendations never execute automatically. Ops teams review, approve, and configure before new automation goes live.
Data-informed automation improvement with human control.
Teams get full visibility into what automation ran, when it ran, why it ran, and what changed as a result.
Every workflow run recorded. See trigger event, conditions evaluated, actions executed, success or failure status, execution time.
Workflows record creation and last-updated timestamps and the template they originated from. Enabled state is explicit, so teams can see what is live and what is paused.
See what each run did. Emails and SMS sent, tags applied, discounts created, admins notified, webhooks called—each action's result is recorded in the execution output. Trace automation's operational footprint.
When workflows don't behave as expected, logs provide exact execution details. Identify failed conditions, retry attempts, timeout issues quickly.
Critical for enterprise trust. Essential for debugging and compliance.
Automation rules managed in Admin. Events and actions API-accessible. Integrate external systems without breaking orchestration.
Ops teams create, configure, and deploy automation workflows through Admin. Start from prebuilt templates, define triggers, conditions and action chains, and monitor execution history and success rates.
Trigger workflows via API. Subscribe to events programmatically. Build custom automation logic on top of core orchestration engine.
Automation events published via webhooks. Integrate with Slack, email systems, ERP, CRM, analytics platforms. Extend automation beyond Commerce Core.
Custom automation logic runs within operational constraints. State validation, idempotency guarantees, audit logging maintained even for custom workflows.
Control with extensibility. Compliance maintained.
Automation operations for businesses scaling beyond manual processes
Teams handling hundreds of orders daily. Automating routine tasks like order routing, inventory updates, customer notifications while maintaining control over exceptions.
D2C brands, marketplaces, omnichannel retailers processing thousands of transactions. Automation handles scale while ops teams focus on growth and optimization.
Businesses that run customer lifecycle workflows—welcome series, win-back, post-purchase follow-ups, and segment tagging—triggered by order and customer events. Subscription-specific triggers are on the roadmap.
Businesses integrating commerce with ERP, WMS, CRM, accounting. Automation orchestrates data flow and operational handoffs across systems reliably.