About ORIGIN
Built by operators and data obsessives, for the grocery aisle.
The omnichannel operating system for grocery, built by 4 co-founders from grocery e-commerce, payments and data engineering.
Who we are
Modelled on grocery from the first commit.
- 01
Grocery-first
Banner, store, channel, SKU and pricing zone were in the schema from the first commit.
- 02
One filter bar
Banner, region, channel and period re-cut every tile, chart and table on a page at once.
- 03
Exports, then API
Scheduled exports from day one. Each vendor moves to API in 1 to 8 weeks.
- 04
Published pricing
Every tier and what it includes is on the pricing page.
Why we build it
A grocer should not have to reconcile six exports to find out how Saturday went.
Mission
Give multi-banner grocers one governed number per question. Every channel, every store, tied to a control total, with the lineage in the box rather than sold as a second product.
Vision
The Monday operating review starts on agreement. No one opens a marketplace portal to check the number, and nobody presents a figure that closed a week ago.
Origin AI
Type the question. Get the number and its chart.
Origin AI reads the same governed dataset the portal pages read. It returns the chart the answer came from and can set the filter bar to match.
If the data cannot support a number, it says so instead of writing one.
Portal, Origin AI
Morning. Four feeds landed overnight and the book ties out.
Where did we grow most WoW?
Back comes the banner, the channel and the week that moved, with the trend it was read off and a filter bar already set to that cut.
Also on open
- Top 3 banners by sales
- Focus on Instacart, year to date
- Open the operations page
That is the portal assistant, behind the login. The Origin AI tab on this page is the public one: it answers questions about ORIGIN and books you a walkthrough. It holds no customer data.
Our sector
Generic BI assumes one store and one channel.
Grocers run several banners and five marketplaces. ORIGIN starts from that data model.
Gap 01
Banners drift apart
Each banner's POS exports slightly different fields. ORIGIN normalizes them on connect, so one executive view means the same thing in every store.
Gap 02
Marketplaces disagree
Instacart, DoorDash, Uber Eats and Shipt each ship a different file and a different basket definition. ORIGIN reconciles them, so net revenue means net revenue.
Gap 03
Reconciliation eats the week
ORIGIN ties every load to a control total and shows the lineage behind each figure, so nobody reconciles by hand before the meeting.
What we hold
Every figure traces back to the till.
- Data integrity first
- Every record is validated, normalized and auditable. Lineage is in the box, not a separate product.
- Built from the operator's chair
- Multi-banner, multi-channel grocery as it actually runs, not a textbook schema.
- Roadmap says roadmap
- Anything not yet built carries a Roadmap tag. No page claims more than the code does.
Work with us
See it on your own exports.
Founding customer pricing off published list is open to a small number of operators.