Multilingual storefront
RU, EN, SV, DE, FR and AR, including right-to-left layout for Arabic.
CASE 02 / RESTAURANT COMMERCE
MERAKKI GLOBAL.
A premium restaurant storefront — from a multilingual menu to a resilient cart and carefully bounded operations logic.
Live checkout and payments are disabled. This is a storefront demo; no real order is submitted.
06LocalesRU · EN · SV · DE · FR · AR
PWAOffline shellManifest · service worker
01CartNormalize · recover · sync
OPSOperationsOrders · refunds · reporting
01 / EXPERIENCE
A clear path from selection to an understandable order.
The interface focuses on choosing a dish, configuring extras and keeping cart contents transparent. The prototype does not simulate a completed payment or claim an order was submitted.
Resilient cart
Data normalization, quantity bounds, state recovery and cross-tab synchronization.
PWA readiness
Manifest, service worker, static offline shell and versioned cache.
02 / OPERATIONS
Behind the interface: explicit operational logic.
The source project contains a separate dashboard and API boundaries for orders and financial events; live integrations require a separate verification gate before activation.
Order queue
Cursor pagination with deterministic created_at and UUID ordering; PostgreSQL timestamp precision is preserved.
Refunds and revenue
Partial refunds are tracked separately from captured amounts; currencies are not mixed into one headline KPI.
Safer export
CSV omits personal contact fields and neutralizes values that resemble spreadsheet formulas.
03 / DELIVERY STATUS
A clear boundary between demo and production.
We distinguish implemented scope from unverified integrations — without a fictional “ready to take payments” status.
Public demo
The restaurant storefront demo is available. No real orders are submitted.
Source scope
The project includes dashboard, order API logic and refund tracking; the public storefront does not expose the admin panel.
Before production
A production build, browser E2E and staging database/payment checks remain. Payment processing is currently disabled.
04 / START A PROJECT
Building a digital product like this?
Let’s define the goal, agree on scope and choose a realistic next step before development starts.
Scope, timing and outcomes are agreed before work begins.OSGARD / DEVELOPMENT / CASE 02
From an elegant storefront to a dependable system.
Explore the public storefront. Order and payment integrations are not described as production-ready before staging verification.