Omnichannel operating system for grocery

One operating system
for every banner.

In-store POS and every delivery marketplace, reconciled into one live picture across every banner and store. The way Walmart runs omnichannel.

$47.9MGMV reconciled
116stores
8channels unified

The product

The dashboard your team actually opens at 8 AM Monday.

One operating picture across every banner, every channel, every POS. Click a number and the chart follows it. Ask a question in plain English and get the answer with its chart.

The ORIGIN portal executive summary

Consulted with people from

Andreessen Horowitz logoHandshake logo

It's an Innovative Product and can really help the Grocery Sector

Co-Founder and CEO of Handshake

Reconciled across

Instacart logoDoorDash logoUber Eats logoShipt logoAmazon Fresh logo

The axis

Planned by department, the way grocery works.

ORIGIN groups product by grocery department, not a generic product collection. That is the axis merchandising teams already plan against. Pick one and see what the portal reads in it.

Produce department
ProduceSubstitutions
01 / 08

What the picker swapped, per store and per marketplace, against what the shopper had ordered.

How it works

Built around the exports you already receive.

Nothing to rebuild first, no marketplace passwords handed over, no eighteen month rollout. What it plugs into is the section below.

One filter bar, every page

Banner, region, channel and period re-cut every tile, chart and table on the page at once. A page only offers the controls that can actually move it, so nothing sits in the bar pretending to work, and the assistant cannot narrate a cut the page is not showing.

The ORIGIN filter bar above the executive summary KPI grid

Connect the platforms, not the files

Instacart, DoorDash, Uber Eats, Uber Eats Market, Shipt, Amazon and the in-store POS. ORIGIN authenticates directly against each platform's reporting API and pulls on a schedule, so the data arrives without anyone sending it.

Reconcile to one control total

Every upload ties out to the cent, per banner and per channel. Each card carries a dot saying whether that number came from a real feed or is still seeded, so nobody presents a placeholder by accident.

Ask it in plain English

Origin AI reads the same governed numbers the page reads and answers with the chart that proves it. It can set the filters or open the page it is talking about, and it says the scope it answered under.

Origin AI summarising year to date GMV in the portal, with the scope it used

Integration

An API on top of the stack you already run.

ORIGIN is software your systems can talk to, not a dashboard your team retypes numbers into. Data lands through one governed path, comes back out over an authenticated API, and sits in a database you own.

RoadmapScheduled connector pulls and email-inbox ingestion run as jobs today, not as an always-on hosted service.

Eight panes of glass scattered at different angles in a dark studio.

01 / 04

01

Land the data

Upload the exports, drop a whole quarter as an archive, or point ORIGIN at an authenticated HTTP feed. Every route runs the same adapter mapping, canonical validation and row-level quarantine, so a file and an API call produce the same governed rows.

Instacart · DoorDash · Uber Eats · Uber Eats Market · Shipt · Amazon · Storefront Pro sites · in-store POS

02

Read it back over the API

Authenticated JSON endpoints sit behind the same role checks and per-user rate limits as the portal itself, with Excel export on the same permissions. The ORIGIN iPhone app is built on them, so anything it shows, your systems can pull.

Session or SSO auth · role-scoped · rate limited · Excel export

03

Run it on your database

Point ORIGIN at your own Postgres and it persists every ingest snapshot there, then builds Bronze, Silver and Gold tables on top. Data quality runs as tests, not as a promise: dbt plus Great Expectations on each build.

Postgres · Supabase · medallion build · dbt and Great Expectations checks

04

Sign in with your identity provider

OIDC single sign-on maps your existing groups to portal roles, so access is granted and revoked where you already manage it. No second user directory to keep in step.

OIDC · role mapping · session revocation

Who opens it

One portal, three ways in.

The same governed dataset, scoped to what each team opens first on Monday morning.

Aisle 01

Merchandising

Plan departments, promotions and the weekly ad against one shared number instead of five exports from five platforms.

  • Departments and collections
  • Campaigns and promotions
  • Weekly ad flyers
Aisle 02

Operations

Watch fulfillment, substitutions and refunds across every banner and channel from one screen instead of four logins.

  • Fulfillment
  • Substitutions
  • Refunds and cancellations
Aisle 03

Marketing

See retail media and ad spend next to the sales they actually drove, banner by banner, channel by channel.

  • Retail media
  • Ads
  • Media executive summary

Six logins and a spreadsheet is not an operating picture.

Today

Monday, 8 AM

  • Instacart Insightsone export
  • DoorDash merchant portalone export
  • Uber Eats and Uber Eats Markettwo exports
  • Shipt and Amazontwo exports
  • In-store POSa separate report per banner
Total6 exportsplus POS per banner

Then someone reconciles them by hand, and the number the executive team reads on Wednesday describes a week that already closed.

ORIGIN

Monday, 8 AM

One reconciled book
Every channel and every banner on one control total, tied to the cent
One filter bar
Banner, region, channel and period re-cut every number on the page together
One question box
Ask in plain English, get the answer and the chart that proves it

The ask

Run your whole omnichannel from one place.

In-store, every delivery marketplace and your own storefront, reconciled into one operating picture across every banner and store. See it on your own data in a 30 minute walkthrough.