FLAGSHIP — PRODUCTION ERP & FULFILMENT OS · RUNS SUPA & LIVE DARK STORES
From any sales channel, through human packing on the store floor, to courier handover — plus batch-level inventory, expiry-driven pricing, supplier replenishment and loss prevention. Built and battle-tested inside Smart Kitchen Co's live operation.
What an operator sees: every order, surface and courier as one living system. demo stream — the shapes are real, the numbers are illustrative
Mngr is a production ERP and fulfilment operating system for dark stores and quick commerce. It runs SUPA — the Yango-Tech-backed marketplace — and merchant storefronts, every day. Every number below is architecture, not marketing.
Orders arrive from seven channel types through three mechanisms — signed webhooks (Uber Eats, Mr D Food, Deeliver), durable pollers with reconcile sweeps (Yango / SUPA), and first-party APIs (the embeddable Merchant POS and the Supa customer app).
Every source gets its own validator and payment strategy — gateway-paid, aggregator-settled or confirmation-gated. Dead orders are dropped before stock is touched. Combos sold as a single virtual SKU are exploded back into components, each holding real batch stock atomically.
Auto-acceptance within each platform's SLA with verified retry logic — a transient API blip never kills an order; a truly dead one is failed fast so no packer wastes time on it. Then fairness-based auto-assignment: least-recently-assigned, driver-aware grouping. No manual claiming.
Barcode-driven packing on web terminals, Android handhelds and a native packer app on FCM. Split grocery / kitchen flows with a kitchen display and order parking. Substitutions, removals and reductions happen with the customer involved live — refund amounts included.
One semantic event per order moment fans out simultaneously to five surfaces — store terminal, kitchen display, staff feed, packer's phone, and the buyer. Meanwhile the Envoyer pushes state to each marketplace through protocol adapters that declare what their platform truly supports.
Aggregator couriers, Uber Direct dispatch, Bob Go shipments — courier events are first-class. A courier bailing does not cancel the order. Cancellations flow store→platform, platform→store and customer→store, each exactly once, with refunds and stock release per payment model.
One moment, every screen, no doubles.
One semantic event per order moment — created, assigned, packing, ready, delivering, completed, canceled, denied, timed-out, courier events, item changes. A failing surface never starves the others; new screens and apps subscribe to moments, they don't get hand-wired into flows. Merchant-iframe customers see live item changes with refund amounts and substitute pricing, and can accept or decline. Supa app customers get push and webhooks.
A protocol adapter per marketplace translates Mngr's lifecycle into each platform's native vocabulary — real accept calls where the platform wants them, state-machine updates where it doesn't, queued with retries, escalating backoff, and explicit desync alerts when a platform refuses. Capability contracts mean a platform without a cancel API is never pretended at: unsupported actions are skipped explicitly.
Expiration dates, per-batch holds, atomic operations, oversell-aware reconciliation, an Inventory Health Index dashboard — and a reconstructable lifecycle timeline for every item.
Stock nearing expiry is automatically discounted — 50%, then 75% on the last day — and pushed to every channel via its native mechanism, from the Uber promotions API to price overrides. Shrink becomes revenue.
Par-based stock orders, supplier purchase orders with buyer approval workflows, DC barcode receiving, and packer-verified intake with expirations captured at the door.
Enforcement-gated, signal-weighted, deliberately unpredictable cycle counts — ABC plus opportunistic. Loss prevention through randomness, with per-store kill switches and full mobile / terminal parity.
Paystack, Flutterwave, Ozow, PayFast behind one gateway layer. Payment-aware order gating and automatic refunds on every cancel path — store-, platform- or customer-initiated.
AI agents inside the product answer sales and analytics questions in natural language. This is the one place we'll say "AI-powered" — because here, it is.
This is what's actually running — one shared core behind admin, merchant, pack, food, parcel and api portals, with tenant-style separate deployments per brand.
Quality gates, not promises: PHPUnit, PHPStan at zero errors, Pint, and adversarial parity audits on every architectural migration.
The same team and the same architecture discipline, pointed at your business. Book a free consultation — no jargon, just a conversation about your goals.
Start the conversation→