V2.0.0-rc Open protocol

The universal language
of food service

Open Delivery defines how ordering platforms, management systems, and logistics operations communicate — from the order to the dining room — on one standard, without point-to-point integrations.

Start integrating Migrate from V1 What changed in V2
01 Guide Concepts and paths 02 Protocol Concepts and flows 03 API API Spec
Release Candidate V2 is in an ecosystem validation period: company review and implementation pilots. A stable release will be published only after that phase. V1 remains active during the transition. Learn more

How the documentation is organized

Open Delivery is an interoperability protocol with an API Spec. Documentation separates onboarding, domain, and implementation.

1

Guide

Concepts, roles, getting started, and migration. Understand the ecosystem before you code.

 2

Protocol

Domain: flows, status, events, and responsibilities per capability — in human language.

 3

API reference

API Spec (REST/HTTP): endpoints, schemas, and examples.

Where do you want to start?

Pick the path that best matches what you need right now.

New here

I do not know the project yet

Understand what Open Delivery is, how the ecosystem works, and which problems the protocol solves before implementing.

I want to implement

I know the project and will implement protocol V2

You already know Open Delivery — or knew V1 — and want to start or deepen your V2 implementation.

Migrating from V1

I have a V1 implementation and want to migrate to V2

You already implemented V1 and need to understand what changed, what breaks, and how to plan migration.

Who are you in the ecosystem?

Implementation paths by role — Open Delivery does not require every capability at once.

Originator

App, marketplace, totem

Creates orders, consumes the menu, and follows the lifecycle.

Orders · Merchant · Discovery PDV / Software

Restaurant management

Confirms orders, publishes the catalog, and is the authority for the dine-in account.

Orders · Merchant · Indoor Logística

Delivery and tracking

Quotes, dispatch, and delivery events without redefining order status.

Logistics · Orders CRM software

Customer data, reviews, loyalty

Customer capability — relationship and intelligence, without changing kitchen operational flow.

Customer · Reviews · Loyalty

See full role paths →

Protocol capabilities

Capabilities are the functional areas of the protocol. They are independent: each participant implements only what makes sense for their role.

Orders
Indoor New
Merchant
Store data
Menus
Logistics
Customer New
Reviews New
Loyalty New

What changed in V2

Main Release Candidate changes. Details and tables in the changelog.

Auth by application Merchant ID from originator Menu with CRUD Customer Indoor Mandatory Discovery Full changelog →
Ecosystem links: GitHub Changelog Roadmap Report an issue