Integrations
One read layer, on top of what you already run.
ORIGIN does not replace your POS, your delivery-platform portals, or your reporting. It sits on top of them, ties the numbers together, and gives your team one place to look.
A read layer, not a rip-and-replace
Your POS stays your POS. Your Instacart, DoorDash, Uber Eats, and Shipt portals stay exactly where they are. ORIGIN reads what those systems already produce, files and reports your team already pulls or exports, and turns them into one reconciled picture. Nothing to rip out, nothing to migrate. Your team keeps its existing tools and adds one governed number on top.
The data workflow, automated
From the partner API pull to one governed answer, five steps, no human in the middle.
Authenticated API pulls from each channel partner: Instacart, DoorDash, Uber Eats, Shipt, Amazon. File upload stays as the fallback route.
RoadmapPartner API access. The connector framework and the Instacart adapter are built and tested; every partner credential is still being granted, so upload and archive drop are the routes carrying data today.
The weekly operating workflow, your team
What actually happens Monday through Monday, once the data workflow above is running.
One screen opens the meeting. Everyone sees the same numbers before anyone starts talking.
API software, on a database you own
Data goes in through one governed path, comes back out over an authenticated API, and sits in your Postgres, not ours.
- Data in
Authenticated API pulls are the default path: ORIGIN holds its own credential against each platform and fetches daily, so nobody exports anything. The same adapter mapping, canonical validation, and row-level quarantine run on every arrival, and any batch already seen is recognized rather than double counted.
Instacart, DoorDash, Uber Eats, Uber Eats Market, Shipt, Amazon, Storefront Pro sites, in-store POS
- Data out
Authenticated JSON endpoints sit behind the same role checks and per-user rate limits as the portal, with Excel export on the same permissions. The same endpoints back the ORIGIN iPhone client, in internal testing today, so anything it shows, your systems can pull.
Role-scoped JSON API, rate limited, Excel export
- Where it lives
Point ORIGIN at your own Postgres and every ingest snapshot persists there, with Bronze, Silver, and Gold tables built on top. Data quality runs as tests on each build, not as a promise.
Postgres or Supabase, medallion build, dbt and Great Expectations checks
- Who gets in
OIDC single sign-on maps your existing groups to portal roles, so access is granted and revoked where you already manage it. Sessions can be revoked centrally.
OIDC SSO, group to role mapping, session revocation
See it on your own systems.
Bring your POS exports and delivery-platform reports to a 30-minute walkthrough. We will show your own banners reconciled into one read, built for operations and technology leaders who need the number to hold up in the room.