PaymentsSeptember 14, 2026by
Empoorio Apps
Empoorio Apps

Empoorio Manager: The Merchant Side of the Network

A delivery network is only as real as its merchant tooling. Empoorio Manager (com.gnoosis.empooriorestaurant, in production on Google Play at version 3.3.26) is where a restaurant or shop becomes a node in the Empoorio commerce network. This is what it does, from the August 2026 screen-by-screen inventory.

Onboarding a merchant

  • Authentication: email, phone verification, re-authentication for sensitive changes, password reset — all against a live identity backend.
  • Register a restaurant with name, category, description and media.
  • Location: pick the address on a map with real geocoding, or edit an existing location.
  • Opening hours per day.
  • Bank details: enter and view payout details — this is where a merchant is paid today, in fiat.
  • Multi-location: a merchant can create secondary accounts for additional restaurants and switch between them.
  • Language selection, persisted to the account.

The inventory found 64 of 76 Manager features connected to a real backend. The remaining twelve are named: onboarding slides (static by design), an informational bottom sheet (static), and a handful of dead code paths from an abandoned wallet-connect tutorial that are never navigated to. Nothing in the merchant's daily path is a mock.

Orders and dispatch

When a customer orders through Empoorio Eats, the merchant sees it in Manager, prepares it, and confirms. Confirmation writes a dispatch to a connected rider — the same mechanism the Riders app, the Warehouse app and the external Partner API all use. To the rider's app, an order from a restaurant, from a warehouse, or from a third-party company through the API is indistinguishable.

Where DMS enters

Today the merchant is paid in fiat through the bank details above. The designed path to on-chain settlement is:

  1. Link an Eoonia account to the merchant profile (the challenge–response linking already live in Empoorio Warehouse).
  2. Price in DUSD, the ecosystem's stable unit; the customer pays from Eoonia via a deep-link payment request.
  3. Settle through pallet-escrow so funds release on delivery confirmation, with pallet-logistics recording the handoff.
  4. Sponsor the merchant's first transactions through pallet-paymaster, so onboarding does not require buying DMS for gas.

Each step exists as a pallet in the live runtime or as a shipped feature in another Empoorio app. None is switched on for Manager yet, and this post will be updated when the first restaurant is paid on chain.

A note on the Play listings

The production listings for Eats, Manager and Riders were audited in September 2026 and found to point at a support URL and a contact email that did not resolve. Those are being corrected, and updates to the four apps are paused until the store's health and financial-feature declarations are filed — a policy step, not a code problem.

Based on FEATURE_INVENTORY_4APPS.md (2026-08-07) and the Play Developer API (2026-09-08).

Share this article