OQID · OpenQloud ID
OQIDs identify restaurants, brands, locations, users, orders and ecosystem relationships across every connected system, so everyone talks about the same thing.
§01Anatomy of an OQID
rst_01kmj9fw7q
Entity type
Unique identifier
- Restaurant
rst_01kmj9fw7q - Brand
brd_01kmi7dc74 - Location
loc_01kmj8xvz5 - Order
ord_01kmjb3n2k - User
usr_01kmja2p8d - Marketplace
mkt_01kmj5rz4c
§02Resolution
Your ids stay. OpenQloud connects them.
A POS, a marketplace and a website each know the same restaurant by a different id. OpenQloud resolves all of them to one OQID and keeps both references on every event.
- POS
#4412 - Marketplace
store-88 - Website
aco-burger
OQID
rst_01kmj9fw7q
The same restaurant, recognized everywhere.
- 01
Shared identity
The same restaurant, brand, location or order has the same OQID in every connected system, whoever created it.
- 02
Cross-platform routing
Because every event carries OQIDs, OpenQloud knows who it belongs to and which systems must receive it.
- 03
Stable references
An OQID does not change when a restaurant changes POS, marketplace or middleware. History and connections stay attached to it.
What does OQID stand for?
OQID stands for OpenQloud ID: the shared identifier OpenQloud assigns to restaurants, brands, locations, products, orders, users and ecosystem relationships.
Do I have to replace my own ids?
No. Every system keeps its own internal ids and stores the OQID next to them. OpenQloud resolves one to the other, so both references always travel together.
What does an OQID look like?
A short prefix that tells you the type of entity, such as rst for a restaurant or ord for an order, followed by an underscore and a unique identifier.