# About

The problem we think is worth solving, who already runs this, and how it is built.

## Where things stand

- 30+ live merchants, brands running it in production today.
- 400+ live locations, warehouses, stores and partner sites routed across.
- Rated 5.0 on the Shopify App Store, across every review merchants have left (https://apps.shopify.com/charlie-1/reviews).

## Who already runs this

- Luxe: Khaite
- Fashion: Kujten, Lafaurie, Serge Blanco, From Future, Pied de Biche, The Bradery
- Maison: Maison Sarah Lavoine
- Health: Nordleaf
- Beauty: Groupe Eleganza
- Sport: Pyörävarikko

## What we think is true

### A decision you cannot explain is a decision you cannot improve

Every routing outcome records the options it weighed, the rule that won, and the stock it had at the time. You can replay it a month later and see exactly why an order went where it went. Most systems in this category cannot answer that question at all.

### Routing and inventory are the operation, not an edge case

Merchants outgrow the defaults the moment they open a second location. Orders land in the wrong place, stock reads as available in one view and gone in another, and the rules that decide it end up in a spreadsheet or in somebody's head. That is not a small problem to be patched around the side.

### Your data is yours

We are the system of record for how you fulfill, and all of it exports in a format anyone can read. Nothing is held in a shape only we can open, and nothing about the checkout your customer sees changes, which is why this uninstalls as easily as it installs.

### Meet people where they already work

It runs inside Shopify and inside Shopify point of sale, so the office uses the admin it already has and the store floor uses the till it already has. Anything a person can see, an agent can see; anything a person can do, an agent can do.

## How it is built

The routing engine is one Rust crate compiled to WebAssembly. It runs at checkout inside a Shopify Function and again when you preview a rule, which is what makes those two answers the same answer rather than two implementations that agree most of the time.

Everything else runs on Cloudflare's edge, with no long-lived servers to keep patched. Business layers we would be reinventing badly, carriers and returns portals and ERP sync, stay with the people who do them well.

It is a small team building one thing carefully, in the open where we can be. If you want to know how a specific piece works, the feature sections of the home page say, and the documentation goes further than most people want to read.

Customers, with every review in full: https://usecharlie.ai/customers