Aeion Commerce Architecture

9 AI agents, 23 payment-provider adapters via the billing module, and native Bridge POS hardware integration — all sharing one schema with the rest of your business data. End-to-end request flow from cart → tokenized charge → async fraud scoring → automatic rollback on payment failure.

Module Inventory

AI Agents (9)

Loss Prevention, Conversion (cart recovery), Retention (churn prediction), Merchandiser (product copy), Pricing, Supply Chain (inventory prediction), Cross-Sell, Customer Success (review sentiment), Loyalty

Collections (30)

carts, abandoned carts, orders, products, product categories, tags, brands & bundles, inventory (locations + levels), price lists, promotions, gift cards, subscription plans & subscriptions, companies, customers, product reviews, wishlists, upsell rules, stores, loyalty (members / rewards / transactions), commerce pages, plus 5 always-on collaboration collections (product discussions, order notes, inventory alerts, presence, activity). Refunds are handled as an order status + action, not a separate collection.

Payment provider adapters (23)

Stripe, PayPal, Square, Adyen, Klarna, Razorpay, Coinbase, Braintree, Authorize.net, Affirm, Afterpay, Sezzle, Mercado Pago, Mollie, Paystack, Paytm, Clover, Helcim, 2Checkout, CyberSource, Flutterwave, GoCardless, Manual

Bridge integration

receipt printers, cash drawers, card readers (mag-stripe + chip via USB HID), barcode scanners, customer displays (pole displays), label printers

Background processing

async job queue handles fraud scoring, fulfillment routing, and inventory updates without blocking checkout

How the Engine Is Organized

Commerce is organized around four responsibility areas, each composed of collections + business logic + (where relevant) an AI agent.

End-to-End Order Flow

What happens between "user clicks Pay" and "order fulfilled."

The 9 AI Agents — How They Compose

Each agent is a focused, single-purpose worker that reacts to real commerce events (or runs on a schedule) and never blocks the customer-facing flow it's watching.

Bridge POS Hardware Integration

Native POS hardware support ships through the Aeion Bridge daemon — a lightweight local companion app that talks to physical devices.

Multi-Store + Multi-Currency

A single Aeion deployment can run multiple storefronts — each with its own domain, branding, currency, and payment providers, while optionally sharing (or scoping) the underlying catalog.

Commerce architecture built to scale with you.