Predictive E-commerce for Smaller Webshops

Predictive E-commerce on Aito

Turn Your Commerce Platform into a Predictive Application

A predictive application is an operational SaaS where the data layer doesn't just store transactions — it predicts the next one. Predictive e-commerce means search results that re-rank for the customer in front of you, recommendations that learn from every click and purchase, demand forecasts that drive replenishment, inventory reorders that come with revenue-at-risk-in-€, markdowns that pick the discount that clears in three months at the highest recoverable margin, and churn risk surfaced before a customer goes silent.

Aito is the predictive database underneath. Every prediction comes back with a probability, top-3 alternatives, and a $why factor decomposition. No retraining, no MLOps, no separate ML pipeline alongside your storefront or merchandising tables.


Live Reference: ecommerce.aito.ai

ecommerce.aito.ai is our open-source reference implementation of a predictive e-commerce platform — the shop, the owner's views and back-office tools, built on _predict, _relate, _search, _recommend, _estimate, and _evaluate. PetNord is a synthetic Nordic-flavoured pet-store dataset generated deterministically from data/generate_fixtures.py (seed 42) to drive the demo: 658 SKUs, 3,000 customers, 10,594 orders, 36,357 order lines, 5,202 reviews, 5,626 recorded shop actions, a 27,003-row customer-month panel for churn modelling, and 15,157 SKU-month rows for demand forecasting. The data has planted effects, so the numbers cited from PetNord below show how Aito works and that it recovers those effects, not how much it would lift a real shop. They are reproducible against the live demo.

The PetNord Shop as a shopper with a guinea pig: Buy again, Next for their kit and Picked for you, with the query behind them

Explore the Use Cases →  ·  Try the Live Demo →  ·  Source on GitHub →

Read more: Every screen a decision, the tour of the whole shop and its routines.


What's Inside the Predictive E-commerce Reference

The demo is arranged by who is asking, and every view reads from a single Aito database and shows the query behind it.

Shop (what a shopper sees)

  • 🛍 The Shop — One view per intent: Buy again, Next for their kit and Picked for you, from what the shopper told the shop, the month and the cart. The ? on each card opens the $why behind its percentage. A search ranks products by their words and by what this shopper is likely to buy.

Run the Shop (the owner's decisions)

  • 🏷️ Product — The funnel from showings to clicks, purchases and profit, beside the month as it was counted. Change the offer, list price, stars, pictures, description or advertising and the funnel moves.
  • 💶 Pricing — An editable list price, the demand range and the profit at each price, only within the prices the product has sold at.
  • 📦 Supply — What to reorder now and what is stuck on the shelf, from next month's forecast per product, with the euros that follow. Markdowns for overstock are tested at 5–20 % off over a quarter.
  • ↩️ Retention — Who is about to leave and why, ranked by the spend at stake. For each customer the shop's actions (an email, a discount, a voucher, a personalised ad, an apology) are ranked against doing nothing, after what each costs. An ad is only offered to customers who consented to tracking.
  • 🔗 Patterns — What goes in the same basket, what goes with a purchase and who buys what, each lift with its interval.

Operate (back-office tools)

  • ⚡ Product Filling — Five catalogue fields (pet type, category, weight, dietary, tax class) predicted from a product's name and brand, each with its $why.
  • 💬 Review Triage — Category, sentiment and owner predicted from a review's text in one round-trip.

Evidence (how well; accuracy numbers live only here)

  • 📊 Business Reorders (real data) — On UCI Online Retail II, for buyers with 1–2 earlier orders, Aito's top suggestion was in their next orders 31 % of the time, against 15 % for the strongest of five classical baselines.
  • 🧪 Model Checks (synthetic) — Held-out _evaluate runs on PetNord, including the ones that fail.

E-commerce Use Cases, One Page Each

Each use case below runs in the demo and has its own page with the query, the numbers and the honest limits.

For the shopper

  • For You: tiles ranked per shopper from their history, pets, month and cart
  • Smart Search: the same query ranked differently for different shoppers
  • Bought Together: cross-sell ranked by co-purchase lift
  • Cart Completion: what this shopper is likely to add, given the basket

For the owner: supply and pricing

For the owner: customers

Running on their own


What the Demo Shows, in Numbers

Each number below is computed on the generated PetNord data (release 3b). Its effects are planted, so these show that the queries recover them, not an uplift in a real shop. The one real-data result is the UCI reorder figure above.

ViewWhat it showsNumber
PatternsDog dry food and dental treats in the same basket3.17× more often than chance, interval 2.75–3.66 (2,044 of 10,594 orders); dog dry food with cat foods about half as often as chance
RetentionNext best action, against the generator's own best actionAito's top action is the best one for 81 % of 300 customers; mean regret €0.45 per customer, against €9.36 for always emailing and €10.72 for never acting
RetentionSigns before churn, for customers who had just orderedAn NPS answer of 0–3 comes with 1.93× the churn within three months, a 1–2 star review 1.23×, a late or damaged delivery 1.17×; an NPS of 9–10 0.71×. The generator caps these contrasts
SupplyThe reorder queue for May 2026Reorder 83 products (833 units, €12,620 at cost): if May sells like the last three months, about €14,400 of sales can't be served without them; €27,691 tied up in 79 overstocked products
Model ChecksHeld-out _evaluatePet type from the name 90.0 % against 40.0 % for the most common value; dietary 66.7 % against 26.2 %; churn +14.7 pp (interval +11.4 to +18.0)
Model ChecksThe honest failureReturn risk 99.0 % against 99.0 %: +0.0 pp, flagged FAIL. About 3 % of lines come back, and nothing in the data predicts which. Demand ties the naive forecast

How Much Can You Automate? (The Honest Answer)

Two things are true at once.

The verifiable facts. Aito has shipped predictive infrastructure in production since 2018; on the operational side, Nordic enterprise AP deployments have run at 95%+ accuracy on thousands of invoices per month — same _predict, same $why decomposition. On the commerce side, the structural regularity of consumer purchase data (catalog taxonomies, segment behaviour, seasonality, replenishment cycles) makes _recommend and _relate produce statistically meaningful results on a few hundred impressions per segment, and _predict produce calibrated forecasts on a panel of SKU-month rows.

The conditional answer. All commerce transactions are super-regular at their core. Catalog taxonomies are stable across years, suppliers map to categories, customer segments behave predictably, and seasonality repeats on calendar cycles. What differs between commerce tenants is how much of your incoming volume matches prior patterns with sufficient history vs. arrives as a first-time pattern. Predictive e-commerce is a conditional-probability engine that works the same way on each transaction; how many of your transactions benefit from it depends on the volume mix.

Why commerce data is statistically usable to begin with

Consumer purchase data has more structure than typical ML training data. Catalog taxonomies are durable: product categories, brands, attributes, and tax classes are stable across years. Repeat customers behave consistently: someone who bought cat litter and lactose-free cat treats this month will likely behave the same way next month. Seasonality repeats: Q4 gifting, summer outdoor goods, back-to-school. Segment effects compound: similar customers do similar things, so a few hundred orders per segment carries real predictive signal.

This is why on regular commerce data a stable pattern becomes predictable after a handful of observations; how many depends on how consistent the pattern is, so measure it on your own history with _evaluate rather than assume a fixed count. The top confidence bucket carries near-zero realized error in production — Aito's confidence is calibrated, so when it says >95%, the realized rate matches.

Three pattern-repetition profiles, three different ranges

Underneath all three, the engine is the same: same _recommend / _predict / _relate / _estimate shapes, same calibrated confidence. What changes between deployments is the volume mix.

ProfileExamplesVolume mixRange we typically see
Mostly-recurringGrocery, pet supplies, replenishment commerce, subscription boxes, household staples, pharmacy, baby goodsStable repeat customers, calendar-driven baskets, narrow tailCross-sell at 1.5-3× lift on common pairs; demand forecast accuracy strong on top SKUs; churn modelable with a 3-month panel; near-zero-touch reorder on staples
MixedMulti-channel general retail, apparel, home goods, electronics, beauty, sporting goodsCombination of repeat-pattern carts and one-offs; meaningful share of trend-driven novelty each seasonPersona-conditioned re-ranking visibly outperforms popularity; demand forecast accurate on the core, weak on newness; markdown decisions reliable for stable categories
Mostly-snowflakeGifting, made-to-order, art and collectibles, project-driven B2B commerce, gallery/curated commerce, antiquesMost incoming orders are first-time patterns. Cross-sell signal sparse at the SKU level; demand forecasting drops to category-levelCross-sell shifts to the category band rather than SKU; demand forecast useful at the brand/category level; predictive search still works via Text tokenisation on name + description

The conditional-probability machinery is the same across all three profiles. What differs is how much of your incoming volume matches patterns already seen many times vs. arrives as a snowflake.

Find your profile in 15 minutes: run _evaluate on a held-out slice of your real data. Per-target accuracy and per-confidence-bucket calibration tell you which range your tenants sit in.

What production actually looks like

A predictive e-commerce stack splits naturally into three layers, and the volume mix above determines how much each layer carries:

  • Consumer-facing (the Shop: search, Buy again, Next for their kit, Picked for you). Works on segment-level signal, so meaningful results emerge on tens of thousands of impressions per segment. Mostly-recurring and mixed tenants get strong persona-conditioned re-ranking; mostly-snowflake tenants get category-band recommendations rather than SKU-level.
  • Merchandiser-facing (Product, Pricing, Supply). Needs at least 6-12 months of SKU-month history. Mostly-recurring tenants get high-confidence forecasts on the top 80% of SKUs by revenue; the long-tail SKUs surface as low-confidence and route to manual judgement with $why rendered.
  • Retention-facing (Retention, Review Triage). Needs a customer-month panel for churn (12+ months ideal). Works across all three profiles because the panel always has structure — what varies is which drivers carry the signal (recency / category mix / review sentiment).

A predictive e-commerce product covering tenants with a heavier snowflake share will see lower headline accuracy at the SKU level — that's the data, not the model. Both numbers are correct, and both are useful, as long as your UI is field-level confidence-aware.


The Override → Learn Loop

Merchandiser bumps the recommended reorder qty from 12 to 18 at 14:00:23. The next request for a similar SKU — different SKU, same category, similar velocity — reflects the new pattern in its conditional probability. No retrain queue. No model deploy. No A/B holdout.

In a typical ML pipelineIn a predictive database
User correction → label storeUser correction → INSERT
Nightly retraining job(none)
Model artifact + deploy(none)
Canary, holdout, regression monitoring(none)
24-72 hours from correction → live<1 second

Same loop covers a merchant tagging a recommended cross-sell as "no thanks", a buyer overriding the markdown level for an SKU, a CRM lead overriding the recommended retention action, an analyst correcting a category prediction during catalog enrichment. Every override trains the next prediction.

This is why predictive e-commerce scales differently than rule-based personalisation engines. Rules rot; predictions improve with every override.


The End-to-End Workflow Loop

The signature interaction in predictive e-commerce is one loop that crosses the consumer-facing / merchandiser-facing boundary without ever crossing a model boundary:

  1. 🔍 A shopper searches — the Shop ranks products by their words and by what this shopper is likely to buy, via _recommend.
  2. 🛍 The Shop's cards — Buy again, Next for their kit and Picked for you follow the shopper, the month and the cart.
  3. 🛒 The cart fills — each addition changes the suggestions, with the lifts in each card's $why.
  4. 📦 The order ships — Supply's forecast and reorder queue move, with revenue at risk in €.
  5. 📉 If the customer goes quiet, Retention ranks them by the spend at stake, with the $why behind the risk.
  6. ↩️ The next best action is the one of the shop's actions worth more than doing nothing, after its cost.

Every override trains the next prediction. Same operators across the whole loop. Same Aito DB. No model boundary between the consumer-facing and merchandiser-facing surfaces.


Try Live E-commerce Predictions

Run the same predictions used by ecommerce.aito.ai directly from this page. These queries hit our hosted PetNord database — no signup, no setup.

Interactive Predictive E-commerce Queries

Run live queries against ecommerce.aito.ai's PetNord (Nordic pet store) database

Bought Together (Cross-Sell Lift)

Which categories go in the same basket as dog dry food. Dental treats lead at about 3.2× chance; cat foods come in at about half.

Aito Query
{
  "from": "orders",
  "where": {
    "line_categories": {
      "$match": "dog_dryfood"
    }
  },
  "relate": "line_categories",
  "limit": 8
}

Multi-Tenant SaaS Pattern

If you're building a predictive e-commerce product for multiple merchants, the same Aito table serves every tenant. merchant_id (or shop_id / customer_id) in the where clause scopes the conditional probability to that merchant's history. accounting.aito.ai runs 255 tenants this way on one shared Aito DB, sub-100 ms predictions, no per-tenant model or retraining schedule.

{
  "from": "order_lines",
  "where": { "merchant_id": "SHOP-0123", "customer_pet_size": "large" },
  "recommend": "product_sku",
  "goal": { "customer_segment": "dog_owner" },
  "limit": 12
}

Same query shape, different merchant_id returns a different ranking — because the conditional probability is computed only over that merchant's rows. No per-tenant index, no per-tenant model, no per-tenant retraining schedule.


Three Signature Interaction Patterns

Three small, reusable components carry the predictive-application UX. Anyone porting this pattern keeps them.

PredictionExplanation — the $why renderer

Pure component that turns Aito's $why factor tree into:

  1. Prediction value + confidence bar
  2. Base rate (baseP)
  3. Top 3-5 pattern matches with token-level highlighting — the words in the product name, the categories on the cart, or the phrases in the review that contributed
  4. The multiplicative chain baseP × lift₁ × lift₂ × … = finalP
  5. Top 2-3 alternatives, clickable to override

LiftHint / ConfidenceBar — the calibrated annotation

A small badge anchored to a recommended SKU, a cross-sell, or a forecast value. Renders the lift or confidence as a coloured pill: green for strong (lift ≥ 1.5, confidence ≥ 85%), grey for neutral, faint red for the protective band (lift < 0.7). Merchant tooling — and savvy consumers, via a "why am I seeing this?" tooltip — gets a calibrated signal instead of a black box.

SmartField — three-state input

Single DOM input that's the same field whether the value came from a prediction or the user. Three visual states: empty / predicted (gold-italic with a 🤖 badge) / user (normal). Tab promotes, Esc rejects, typing replaces. Used in Product Filling (catalog enrichment) and any merchandiser form where Aito has a credible guess.

These match the patterns in the smart form fill use case and the $why explanations in the API docs.


Predictive E-commerce vs. Rule-Based Personalisation

Traditional commerce personalisation means: write a segmentation rule, write a recommendation rule, write a cross-sell rule, write a markdown rule. Maintain them. Watch them rot. Hire vendors to fill the gaps.

A predictive e-commerce stack flips it: load your orders and impressions, query for predictions, promote patterns to merchant-visible rules with governance. No retraining, no MLOps, no feature engineering. The data is the model.

ApproachWhat it covers
Rules-only personalisation engineStatic segmentation, hand-tuned cross-sell, popularity ranking — ceilings at top-of-funnel, no operational coverage
Bolted-on commerce search & rec vendorSearch and recs only; demand forecast, markdown, churn, win-back stay separate vendors
Predictive e-commerce on AitoOne substrate covers consumer-facing AND operational — search, recs, demand, inventory, markdown, churn, win-back, catalog enrichment, anomaly detection

Prove It on Your Data in 15 Minutes

The fastest way to disqualify Aito for your e-commerce use case is to run _evaluate on a slice of your real data.

  1. Export 10K orders + impressions (or product views) from your store as CSV — customer, product, segment, category, timestamp, anything else you'd predict on.
  2. Upload to a free Aito sandbox.
  3. Run _evaluate on a held-out slice for top-k recommendation accuracy, demand forecast accuracy, churn AUC, or whatever target matters for your roadmap.
  4. Compare to always-recommend-bestseller, always-predict-popular, and whatever you have today.

If the lift over baseline is convincing, schedule a technical review. If not, you've spent an afternoon.

_evaluate is the same operator that powers the Model Checks view on ecommerce.aito.ai. Same code path you'd use in production to monitor accuracy per merchant.


Build vs. Buy: The Honest Math

For a 5-15 person product team building a predictive e-commerce SaaS:

Build it yourself. A working prediction loop with multi-tenancy, retraining, evaluation, and override capture takes ~6 months and ~1.5 FTEs (one ML engineer, ~0.5 backend for plumbing). At €100-130K loaded ML salary plus infrastructure: year-1 TCO €200-400K, year-2 €120-200K maintenance. Plus you're operating retraining infrastructure in production while shipping new features.

Drop in Aito. API key and SQL-like queries, 1-2 weeks to a working prediction loop. Multi-tenancy is merchant_id (or shop_id) in the where clause. Aito plans start at €0 (sandbox), €75/mo (small production), €350/mo (growth) — see pricing. You give up some control over model internals; you gain ~5 months of engineering and the right to delete user data without a model-retraining ticket.

The breakeven question. Time to first paying merchant matters more than build-vs-buy purity. Six months later means six months less revenue and a smaller dataset to learn from when you do ship.


How This Compares: Algolia, Klevu, Shopify Magic, Klaviyo, GPT-4 + a Vector DB

The honest alternatives we hear:

vs. Algolia AI Recommendations / Klevu / NoSto / Searchspring / Boost (commerce search & rec vendors). These bolt on as services with their own data ingestion, taxonomy, and UI patterns. They work, but: (a) they own your prediction layer and the taxonomy decisions inside it; (b) they cover search and recs but stop at the storefront, leaving demand forecast, markdown, churn, and win-back for separate vendors; (c) the same pixel reports to several SaaS products rather than one substrate. Aito is the database underneath your own features, so the predictions are yours, the taxonomy is yours, and a single substrate covers consumer-facing AND operational.

vs. Shopify Magic / Magento Live Search / BigCommerce native AI. Great if you're a merchant on that platform. Useless if you're a platform vendor building a competing or complementary product. Aito is the substrate for the team building the platform feature.

vs. Klaviyo / Recharge / Bloomreach (retention and personalization vendors). These ship CRM + email + retention workflows. They own segmentation and campaign delivery. Aito does the predictive scoring underneath: which customer to win back, which product to offer, how to price the offer. Most predictive e-commerce roadmaps end up running one of these and Aito — the CRM for the workflow, Aito for the score.

vs. GPT-4 + a vector database for product reasoning. LLMs reason well over unstructured input but cost ~1-3 sec per call, are opaque (no $why), and don't learn from corrections. For volumetric commerce work — thousands of impressions/day per merchant — the unit economics break. Use LLMs for free-form customer-message classification or product-description generation, Aito for the structured prediction.

vs. building it on scikit-learn / Vertex AI / SageMaker. You can. You'll spend the 6 months above. The thing you build is a worse predictive database with retraining infrastructure you operate.


Where Predictive E-commerce Fits

For commerce SaaS platform vendors. Shopify-class, headless commerce, niche vertical platforms, marketplace platforms. Bake predictions into your product. Personalised search and recommendations, demand forecast, markdown, churn and retention actions become default features instead of premium add-ons or third-party integrations. Multi-tenancy is merchant_id in where — same pattern accounting.aito.ai runs across 255 tenants on a single Aito DB.

For e-commerce agencies and integrators. Shopify Plus shops, headless commerce agencies, BigCommerce / Magento / WooCommerce dev shops, freelancers running multi-client retainers. Aito is forkable (Apache 2.0), the PetNord demo doubles as a client pitch deck, and one Aito plan can drive predictions across a portfolio of small clients. See the Partner page for the agency programme.

For ERP vendors with a commerce module. Oscar Software, ERPly, Visma, Lemonsoft, NetSuite — if your product spans accounting + commerce + inventory, the same Aito instance running AP coding and PO routing also runs demand forecast, markdown, churn, and win-back for the commerce side. One substrate, three product surfaces.


Throughput & Sizing Per Plan

Latency is per-prediction in the 20-50 ms range, sub-200 ms P95 at scale. Throughput is what you provision for:

PlanCostAPI calls / monthStorageRight for
Sandbox€05,000100 MBEvaluation, PoC, _evaluate on sample data
Dev€75500,000500 MBOne small production merchant or pilot
Prod€350Unlimited1 GB (extendable)Single-instance production at SME scale
EnterpriseContactCustomCustomMulti-tenant SaaS, multi-region, dedicated infra

Worked example. A predictive commerce SaaS with 200 merchants averaging 500 product impressions + 50 cart events per merchant per day = ~110K events/day. Each impression triggers ~2 predictions (re-rank + cross-sell), each cart event triggers ~1 (completion suggestion) = ~210K predictions/day. Comfortable on Prod (€350/mo, unlimited). Storage at ~10K rows per merchant fits 1 GB; extends as you grow.

For multi-tenant SaaS beyond ~500 merchants or multi-region deployments, contact us — Enterprise pricing is per-instance with dedicated infrastructure.


Security, Compliance & Data Residency

  • EU data residency by default. Hosted in AWS Frankfurt (eu-central-1). US deployment on request.
  • Encryption. TLS 1.2+ in transit; AES-256 at rest.
  • Tenant isolation. Per-customer Aito instances by default; shared multi-tenant pattern is opt-in.
  • DPA. GDPR-aligned Data Processing Agreement on request.
  • Audit logging. Every API call logged with timestamp, key ID, query, and response time.
  • Right to be forgotten. No model artifact derived from user data — DELETE the rows and predictions reflect it from the next query forward. Important for GDPR Article 17 in consumer-facing e-commerce.
  • PII handling. PetNord uses anonymous customer_id (CUST-NNNNN). The recommended pattern: keep PII in your own DB, send Aito the segment / behaviour / event signals scoped per customer_id.

We do not currently hold a SOC 2 Type II attestation; we share our security posture and pen-test results under NDA. For procurement that requires SOC 2 today, contact us.


Platform Stability & Long-Term Commitment

E-commerce platforms ship for 10+ years. Before you bet a product roadmap on Aito:

  • API stability. The core query API (_predict, _relate, _search, _recommend, _estimate, _evaluate, _match) dates from the public v1 release in 2019. We version at the API level, and behavior changes are listed in the changelog.
  • Deprecation policy. Minimum 12 months notice before any deprecation. Migration guides published with each.
  • Operating history. Aito has run in production since 2018 across multiple corporate owners — Nordic enterprise AP deployments processing thousands of invoices per month at 95%+ accuracy. See About for the current corporate posture.
  • Source of truth, not lock-in. Your data goes in via standard JSON. It comes out via _search. There is no proprietary format you can't export. Worst case migration: read your rows, write them somewhere else.
  • Open-source reference implementations. The accounting, ERP, and e-commerce reference apps are Apache 2.0. If our company posture changes, the patterns we taught remain yours to operate.

For company posture, funding, and team — see About or contact us for current details under NDA. Multi-year procurement reviews welcome.


Get Started

Ready to ship a predictive commerce product — or add predictive features to one you already operate?

Try ecommerce.aito.ai → — the shop, the owner's views and the evidence, live.

Read the source on GitHub → — Apache 2.0, with a use-case guide per view and the architecture decision records.

Schedule a Technical Review → — walk through your specific commerce automation use cases with our team.

Start Free Trial — point Aito at your own order and impression data in our sandbox environment.


Why we built all of these on one substrate

Predictive Accounting, Predictive ERP, and Predictive E-commerce are not three separate products. They are three instances of the same pattern: a SaaS application designed around the premise that the user should never make a decision the data has already made for them. The substrate is a predictive database. Prediction becomes a query rather than a project.

For the full architectural argument, see The Predictive Application. The canonical explanation of why per-prediction cost determines what gets built, and what changes when that cost collapses.