Delivery marketplaces
Shape live catalog, availability, checkout, and order operations around one portable capability contract.
Partners & network integrations
One contract for the commerce network.
Onsell is developing a portable way for authorized agents, delivery marketplaces, and commerce systems to exchange catalog and checkout intent without replacing the systems that already hold the truth.
No live network connections or third-party partnerships are advertised on this page.
Who it’s forEvery side of the network
Built for the systems and teams connecting GCC commerce.
Use the same capability language across consumer channels, merchant systems, and the teams responsible for connecting them.
Super-apps
Add local discovery and checkout while the merchant or provider remains authoritative for price and availability.
POS & channel platforms
Map merchant data once, then advertise the profiles and capabilities each connected system supports.
Integration teams
Start with catalog, checkout, or order placement and validate safety semantics before expanding coverage.
Agent commerce standardDraft 0.1
Adopt the contract in layers.
Platforms advertise the profiles they support instead of making an all-or-nothing compatibility claim. Checkout is the active reference beta; catalog portability remains draft, and order support is limited to placement inside Onsell.
1Draft contract
Catalog profile
Discover businesses, locations, offerings, prices, availability, service areas, and supported fulfillment modes.
2Reference beta
Checkout profile
Create, read, update, or cancel a persisted checkout while the provider remains authoritative for every total.
3Reference beta · placement only
Order profile
Bind consent to an exact checkout revision and create a durable Onsell order reference; payment and external handoff are not included.
Capability statusCurrent reference
Clear about what is—and is not—available.
A draft is useful only when its limits are visible. These statuses describe Onsell’s current reference implementation, not third-party compatibility.
Discovery document
Reference betaA public ACP-shaped document advertises the current checkout capability, transport, QAR currency, and Qatar locales.
Portable catalog reads
Draft contractOnsell has structured merchant and catalog APIs, but the cross-platform catalog profile and MCP binding are not finalized.
Checkout sessions
Reference betaFive persisted MCP tools support create, read, update, complete, and cancel with provider-authoritative repricing.
Consent & retry safety
Reference betaCompletion requires explicit confirmation of the current revision; mutations use idempotency keys for safe retries.
Order placement
Onsell beta onlyA confirmed checkout can create an Onsell order reference. External provider handoff and lifecycle sync are not included.
Partner authentication
Controlled betaAccess is configured manually. Public OAuth client registration and granular partner scopes are not self-serve yet.
Payments & reconciliation
Not availablePayment processing, 3DS, capture, refunds, settlement, and reconciliation remain outside the current reference beta.
Provider webhooks & status sync
Not availableSigned provider events, external status mapping, deduplication, and delivery outboxes are not implemented yet.
Reference flowFive portable steps
From capability discovery to a durable order reference.
Discover
Advertise versions, capabilities, locales, currencies, and transports.
Read
Resolve authoritative catalog, availability, and fulfillment data.
Prepare
Create a server-priced checkout with an expiring revision.
Confirm
Show the current revision and collect explicit customer approval.
Complete
Re-price, complete idempotently, and return an order reference.
Platform adoption targetsNot connected
Designed for the systems already serving GCC commerce.
These platforms help shape the draft’s requirements. They are not announced partners, certified implementations, or live connectors.
Delivery marketplace
6 design targets
Uber Eats
Design targetNot connected
Future menu, availability, and order-handoff interoperability.
talabat
Design targetNot connected
Future catalog and order-workflow interoperability.
Snoonu
Design targetNot connected
Future menu, availability, and order-handoff interoperability.
Deliveroo
Design targetNot connected
Future catalog and order-workflow interoperability.
Careem
Design targetNot connected
Future menu, availability, and order-handoff interoperability.
Keeta
Design targetNot connected
Future catalog and order-workflow interoperability.
Commerce infrastructure
2 design targets
Foodics
Design targetNot connected
Future POS catalog and order-workflow interoperability.
Deliverect
Design targetNot connected
Future channel-management and menu-sync interoperability.
These logos identify interoperability design targets only. Onsell does not claim a live integration, partnership, endorsement, or access to these companies or their systems.
Target onboarding pathNot self-serve yet
A deliberate path from fit to pilot.
Live exchange requires more than matching JSON. Credentials, operational ownership, security, brand approval, and commercial terms must all be agreed before a platform is represented as connected.
- 01
Choose profiles
Agree on the catalog, checkout, and order-placement capabilities in scope. Selecting a profile is not a compatibility claim.
- 02
Map the contract
Map stable identities, locations, offerings, options, availability, money, fulfillment, and order states into the draft model.
- 03
Configure controlled access
Bind the contract to the agreed transport and authentication model; public partner enrollment is not self-serve yet.
- 04
Validate safety behavior
Exercise authoritative repricing, stale revisions, idempotent retries, expiry, cancellation, and failure recovery.
- 05
Approve a pilot
Complete security, brand, operational, and commercial review before any pilot or live exchange is represented publicly.
What the platform owns
- Merchant and customer agreements
- Authentication, scopes, and credential custody
- Payments, fulfillment, support, and local compliance
- Operational readiness and incident ownership
What the standard coordinates
- Capability and profile discovery
- Canonical catalog and checkout semantics
- Revision, confirmation, and idempotency rules
- Structured errors, references, and safe retries
Status FAQ
Clear about the network from day one.
Are the companies shown here Onsell partners?
No. They are interoperability design targets. Their inclusion does not represent a partnership, endorsement, connection, certification, or data exchange.
What is available today?
Onsell provides the checkout reference beta and placement-only order semantics. Portable catalog interoperability remains a draft contract.
Must a platform adopt every profile?
No. A platform can adopt one profile at a time and advertise only the capabilities it actually supports.
Who controls prices and availability?
The provider remains authoritative. Checkout is re-priced before completion, and a changed revision requires fresh customer confirmation.
Shape a commerce contract your platform can trust.
Partner enrollment is not self-serve yet. Start with the profile that fits your system and review the current developer beta before planning a pilot.