Try it in two minutes
- Choose a kitchen, search or filter the menu, and place a fictional collection order.
- Open Kitchen from the confirmation or navigation and accept the order.
- Move it through preparing, ready and completed, then return to Orders and refresh.
- Open API lab from the navigation and run the live API checks. Expand the log to see requests and actual responses.
Interface
The customer-first interface pairs a licensed cooking illustration with twelve illustrated African dishes across two kitchens, search and dietary filters, separate kitchen baskets, and draft recovery. Menu images are AI-generated and disclosed in the credits. A confirmation leads to order tracking. An uncertain response retains its request key across refresh for a safe retry. The vendor desk turns explicit order stages into clear actions. The frontend uses semantic HTML, responsive CSS and a small vanilla JavaScript interface without a framework build.
API rules
- Price integrity: meal prices and totals come from the server catalogue; client-supplied prices are ignored.
- Request replay: a unique workspace/request-key constraint returns the original order for an identical submission and rejects a changed payload under the same key.
- Restaurant scope: vendor list, detail and update queries include the session workspace and restaurant. Another restaurant's order ID returns 404.
- Safe transitions: each stage requires the current revision. An atomic conditional update rejects a stale revision or skipped stage.
- Audit history: each successful status and its event are committed in the same database transaction.
Verification
The 14 November 2026 menu expansion passed 28 Django API tests and 15 DOM integration checks against the actual local Django API. Checks cover server pricing for six-dish baskets, kitchen isolation, all menu-image endpoints, generated-image disclosure, filtering, search recovery, focus retention, separate kitchen baskets, draft recovery, confirmation, vendor updates, order history, navigation state and safe replay after an accepted request loses its response.
The preceding layout release was rendered and inspected at 1440, 1280, 390 and 320 CSS pixels, including phone basket, confirmation, order progress, kitchen queue and API lab. Fresh screenshot review of the expanded menu remains pending. This is targeted verification, not a complete accessibility audit. No load or PostgreSQL concurrency guarantee is claimed.
Scope choices
The role selector is intentionally a demo device, not production authentication. Browser sessions isolate fictional workspaces. SQLite keeps deployment small; data on the free service filesystem can reset. Real tenant memberships, durable database hosting, payment processing, notifications and delivery integrations are outside this slice.
The concept demonstrates contribution to an existing product workflow. It does not imply that FufuPlanet lacks these capabilities.