For grocery
Built for grocers running several banners and every marketplace.
ORIGIN is the omnichannel operating system for grocery. It starts from the grocer's own data model, banner, store, channel, SKU and pricing zone, and ties every register and marketplace to one number per question.
Every delivery channel, unified on one read
Where the data breaks
Every banner, marketplace and pricing zone reports a different number.
Every banner exports differently
Banners acquired at different times run different POS schemas, and the fields drift further apart every year.
ORIGINNormalized to one schema on connect, so an executive view compares like for like.
Instacart's numbers don't match yours
Different basket definitions, different fees, different timezones.
ORIGINReconciled against your weekly close, so net revenue means net revenue.
Marketplace fees move silently
Instacart, DoorDash, Uber Eats and Shipt change fees and rules without notice.
ORIGINFee drift shows on the next scheduled export, not at quarter close.
Shrink hides in fresh categories
Produce and meat shrink is a slow leak that no single banner report shows.
ORIGINAnomaly detection flags banner-by-banner variance against forecast.
Out-of-stocks misroute orders
Found-rate variance across banners turns into substitutions, refunds and cancelled baskets.
ORIGINLow-fill SKUs surface by store, beside the refunds they cause.
Reconciliation eats analyst time
Tying banners, channels and pricing zones together is a weekly copy-paste job that runs before anyone reads a number.
ORIGINORIGIN runs that reconciliation, so the week starts on the number.
How you start
Live on day one. On API in weeks.
We act as your data agent. We schedule the exports from every platform ourselves from day one, then move each one to API, vendor by vendor, in 1 to 8 weeks. Your team never downloads a file, and the number doesn't change when the pipe does.
Order and timing vary by vendor. Illustrative.
A database you own
Your Postgres. Bronze, Silver and Gold tables, checked with dbt and Great Expectations.
An API your systems can read
Role-scoped JSON and Excel export, with the same permissions as the portal.
Your sign-in
OIDC SSO. Your groups, your revocation.
How operators use it
The standup, the quarter close and the new banner read one number.
Every Monday
Operator standup
Last week's GMV, basket and search conversion are trued up against one control total before the meeting. The team starts on agreement, not on reconciliation.
Quarter close
Finance review
Lineage on every metric down to the source row. Auditors and finance see the same number through the same chain.
Onboarding
A new banner joins
The new banner goes through the same adapter mapping and canonical validation as the rest, without rebuilding dashboards.
When a rule changes
Marketplace response
When an Instacart rule change moves basket conversion, the next export shows it by banner, and Origin AI answers what moved.
The shape it runs at
The footprint the portal is modelled on.
- banners on one read
- banners on one read
- stores
- stores
- channels reconciled
- channels reconciled
See ORIGIN on your banners.
A 30-minute walkthrough with an Instacart and POS reconciliation on your own data.