Empoorio Eats (com.gnoosis.empoorioeats) is where a customer meets the network: browse restaurants and shops, order, pay, track the courier. It is in production on Google Play at version 13.3.23, one of five Empoorio apps in production and the one with the longest release history. This post follows an order through the system.
The order path
- Customer orders in Eats. Menu, basket, address, payment. Payment is in fiat through the app's payment rails.
- Merchant sees it in Empoorio Manager, prepares, confirms.
- Confirmation dispatches to a courier: the system writes the order to a connected rider's record. The rider's app — Empoorio Riders — picks it up, shows the route, and the courier delivers.
- Customer tracks in Eats and confirms receipt.
The same dispatch write is what the Warehouse app and the external Partner API use, which is why a courier's day can mix restaurant orders, warehouse shipments and third-party deliveries without the app knowing the difference.
What is verified
The four logistics apps were inventoried screen by screen in August 2026. Across them, 232 of 279 features are connected to a real backend. For Eats the customer path — authentication, browsing, ordering, tracking — is real. Where the earlier codebase had aspirational features (a Web3 checkout, for one), they were parked rather than left as dead buttons; the compile fix that took the app from 445 build errors to a clean release in August 2026 removed them explicitly.
Where the chain comes in
Eats does not pay in DMS today. The designed path is the same as for merchants: link an Eoonia account, receive a payment request by deep link at checkout, pay in DUSD, and let pallet-escrow hold the funds until delivery is confirmed. For the customer the visible change would be one extra payment option; for the network it would be the moment the order path settles on the ledger it was built for.
What has to be true first, in order: on-chain checkout tested with a real merchant on the live testnet; Eoonia's payment-request deep link exercised from Eats; and the Play policy declarations that currently pause updates to the four apps filed. None of these is a research problem. All of them are steps that have not happened yet, and the app will not claim them until they do.
Distribution
Eats and its sibling apps are distributed in Spain. A review in August 2026 tightened country availability for the ecosystem's apps, and production for this family is Spain-only by decision. That is deliberate: the network is local before it is global.
Based on FEATURE_INVENTORY_4APPS.md, the Play Developer API (2026-09-08) and the August 2026 release notes.