Developers

Fits your stack. Doesn’t replace it.

Ollie connects to the platform, payment providers, ERP and data tools you already run. Your team keeps ownership of the store; Ollie adds personalization on top.

Architecture

Where Ollie runs, and what it touches.

Ollie runs between your storefront and your systems. It reads catalog and profile data, applies your rules and risk filters, and hands the order and the payment to the providers you already use.

ERPLoyaltyCRMInventoryE-commerceplatformData and BIBrand rulesCatalogEventsExperienceOllieShopperat checkoutPSPPixAnti-fraudyour providers,after your risk filtersRisk filtersdata and rules, through Olliepayment, after your risk filtersERPLoyaltyCRMInventoryBrand rulesE-commerceplatformData and BIOllieExperienceShopperat checkoutRisk filtersPSPPixAnti-fraudyour providers, after your risk filters
Concepts

How a checkout is organized.

Each store has versions. Each version has its own template, components and functions, so you change one part without rebuilding the rest.

Read the docs →
Rules as code

One rule, in the Admin or in code.

Your business team edits rules in the Admin. Your engineers can write the same rule as code, keep it in your repo and review it like any other change.

  • Same rule, two editors
  • Reviewed in a pull request
  • Tested with a split before it reaches every shopper
Ollie · RulesPublished · no deploy

Reorder for returning shoppers

WhenProfile is returning
AndLast order under 30 days
ShowBuy again, last basket
WhereCart
Test50% split against your checkout
Events and data

Every step becomes an event.

Each checkout step, rule and filter is sent to the data tools you already use, so your team measures Ollie with its own numbers.

payload
Docs

Start with the docs.

Guides, API reference and examples for connecting your platform, writing rules and receiving events.

Read the docsTalk to an engineer