Skip to content

In developmentTested end to end · Not in production · Updated November 2026

One API betweenyour POS and whereyou sell and deliver.

OneAggrgtr is built to connect POS systems to marketplaces such as Uber Eats and delivery networks such as Uber Direct, through one shared order model. A POS integrates once; OneAggrgtr owns each provider connection.

Simulated marketplace eventsimulated:test-marketplace wire event
// A fictional wire shape, used by the test suite
{
  "eventId": "evt_5519",
  "orderRef": "tm_7281",
  "storeRef": "harbor-market-east",
  "lines": [
    {
      "skuRef": "milk_12",
      "qty": 2,
      "unitPriceCents": 549
    }
  ]
}
Canonical records
// Ingested once
Order { id: "c41e…7b3d", state: "RECEIVED" }

Find your path

The problem

Every new channel multiplies the integration work.

Connect each sales channel to each system directly and the work is channels times systems. Through one shared layer, it is channels plus systems.

Shared layerSales channelsSystems

16

direct integrations to build and maintain

8

connections through a shared layer

Sales channels
4
Systems
4

4 channels × 4 systems = 16 direct connections, or 4 + 4 = 8 through a shared layer. Illustrative arithmetic only.

Try your own numbers

Sales channels

Marketplaces, your own site or app

4

Operational systems

POS, delivery providers, inventory

3

Connect each one directly

4 × 3 = 12

Through one shared layer

4 + 3 = 7

5 fewer integrations to build, test, and keep working.

What it does

Less integration work. Fewer surprises after an order arrives.

OneAggrgtr is designed to sit between a POS and the places a business sells and delivers.

  • One connection for the POS

    A POS connects to OneAggrgtr once. OneAggrgtr owns the connection to each marketplace and delivery provider it supports. Today those are Uber Eats and Uber Direct, tested in Uber's test environments.

  • Every order in one shape

    Orders reach the POS through one order feed, in one format. Adding a sales channel is designed to need no change on the POS side.

  • Catalog and stock sent once

    The POS sends its catalog and stock levels to OneAggrgtr, through one API.

  • Nothing guessed

    A duplicated event has one effect. If a provider cannot confirm what happened, a reconciliation record stays open until someone resolves it, instead of the outcome being assumed.

Built for multiple industries

One model for a produce stand and a kitchen pass.

Business type is an attribute, not an architectural boundary. Pick an industry to see the same order carry what it needs.

Same order model

Sold by weight: the line carries the measured quantity and its unit.

Field names are from the partner API (v1) order. Values are illustrative.

{
  "name": "Gala apples",
  "quantity": 1,
  "measuredQuantity": "2.40",
  "unitOfMeasure": "LB",
  "unitPrice": "2.49",
  "isRegulated": false,
  "verificationRequired": false
}

Also modeled: convenience, hybrid retail and food.

All industries

Where things stand

Plain about what is built and what is not.

Built and tested end to end with simulated providers. The Uber Eats and Uber Direct connections have been tested in Uber's test environments. POS partners can try the partner API on a hosted sandbox by invitation; its orders are simulated, and no marketplace or delivery provider is connected to it. Nothing is in production yet.

Production connections
None yet
Provider test environments
Uber Eats and Uber Direct
Partner API (v1)
Built; not publicly published
Partner sandbox access
By invitation

Status as of November 3, 2026. “Tested end to end” means run against simulated providers and injected failures in our own environments. A provider test environment is not production, and no partnership or certification is implied. Full ecosystem status

Built for developers

Integrate against one surface, not one per provider.

POS partners connect to OneAggrgtr's partner API (v1): an order feed, order actions, and catalog and inventory intake. Documentation and a hosted sandbox with simulated orders are available to invited partners.

Talk to us about integration or partnership.

POS teams, marketplace and delivery providers, and merchants: we will be exact about what exists, what would need building, and what connecting would take.