03 / Case Study · Omniretail · 0→1 Design

Designing the Manufacturer Operating System

0 → 1 Product Product Strategy UI / UX Design B2B · SaaS Supply Chain Web Research
MANUFACTURER OS · DISTRIBUTION HUB
Total Manufacturers 4,812
Total Products 11,458,322
Manufacturer Activation & Retention 86%
Onboarding Time Per Manufacturer 2 Minutes
faster Onboarding timeline compared to our Distributor Platform
68.4%
reduction in support ticket
Order speed
40%
Fewer disputes
238
Distributors

Summary

Omniretail operates a distribution network connecting FMCG manufacturers to thousands of informal retailers across Nigeria. Manufacturers had no unified view of their distribution operations,order volumes, distributor performance, stock positions, and settlement data lived in separate tools, spreadsheets.

I led the design of the Manufacturer Operating System: a web platform giving manufacturers and their field teams a single source of truth across their entire distribution chain. The work covered discovery, system architecture, interaction design, and a full UI build across five core modules.

Faster order processing from placement to confirmation across the distributor network
40%
Reduction in dispute rate through real-time settlement visibility and audit trails
84%
Less time to onboard new field managers onto the platform vs the previous toolset
Dashboard home state Image — Dashboard home state Recommended: 1600 × 900px · PNG or WebP

About Omniretail

Omniretail's distribution platform serves as the connective layer between manufacturers and the last-mile — the open-market retailers who make up the majority of Nigeria's FMCG sales. Manufacturers plug into the network to distribute stock, manage field agents, and track sell-through data.

The Manufacturer Operating System is the manufacturer-facing control layer on top of this network. Before it existed, manufacturer account managers pieced together operations using a combination of Omniretail's basic portal, external spreadsheets, and daily phone calls with distributor reps. Nothing was real-time. Nothing was auditable at scale.

"We're operating one of Nigeria's largest distribution networks blind. We know something happened — we just find out two days later."

The platform needed to give manufacturers visibility, control, and confidence — without requiring them to change how their field teams fundamentally work.

Before state old workflow Image — Before state Old workflow / tooling

Starting with the operational reality

I embedded in two rounds of discovery sessions with manufacturer account managers, field supervisors, and Omniretail's operations team. The goal was to understand not just what data they needed, but the decisions they were trying to make and when those decisions broke down.

Key problems surfaced quickly:

📦
No consolidated order view. Manufacturers received order summaries from distributors via WhatsApp or email — often delayed by 24–48 hours and formatted inconsistently.
💸
Settlement disputes were opaque. When payment discrepancies arose, neither side had a shared audit trail. Resolving a single dispute took an average of 3–5 days.
📊
Stock intelligence was lagged. Manufacturers couldn't identify low-stock situations at the distributor level until stock-outs had already caused missed sales windows.
🗺️
Route compliance was invisible. Field agents submitted visit reports manually, making it impossible to validate route adherence or retailer coverage in real time.
🔗
Distributor performance was unmeasured. No structured way to compare distributor throughput, order fill rates, or territory coverage across the network.
Research artifacts Image — Research artifacts Interview notes, affinity map, or persona · 1600 × 900px

Balancing depth with usability

With five distinct problem areas and a user base ranging from data-savvy account managers to field supervisors with minimal screen time, I proposed two structural directions before committing to a solution.

Approved

Approach A — Unified dashboard with module tabs

A single authenticated workspace with a persistent left nav. Each module (Orders, Distributors, Settlements, Stock, Field Ops) lives in its own tab, sharing a common data layer and notification system. Lower learning curve; consistent mental model across user types.

Approach B — Role-based portals

Separate interfaces scoped to each user type: account managers get an analytics-heavy view, field supervisors get a mobile-first task view. Higher design and engineering complexity but more tightly tailored to individual workflows.

Approach A was approved as the Phase 1 direction, with Approach B elements earmarked for a mobile field app in Phase 2. This kept the initial engineering footprint manageable while delivering meaningful value across all user types from launch.

Image — Early wireframes or IA map Navigation structure, low-fi flows · 1600 × 700px

What we built

The OS shipped with five interconnected modules, each designed around the core decision each user type needed to make — not just the data they wanted to see.

Module 01 — Orders
Real-time order stream with status tracking, distributor-level filtering, and bulk confirmation. Replaced the WhatsApp/email loop entirely.
Module 02 — Distributors
Distributor scorecards with throughput trends, fill rate, and territory coverage. Made it possible to flag underperforming partners before it became a revenue problem.
Module 03 — Settlements
Shared payment ledger with line-item audit trails. Both manufacturer and distributor see the same data, eliminating the information asymmetry that caused disputes.
Module 04 — Stock Intelligence
SKU-level stock positions across all distributor warehouses, with low-stock alerts surfaced 48–72 hours before projected stockout.
Module 05 — Field Ops
Route compliance dashboard pulling from the mobile field app. Supervisors see visit logs, retailer coverage maps, and agent activity in near real-time.
System Design
Design system built ground-up for Omniretail's B2B context — dense data tables, status badges, and a component library that scaled across the five modules without rework.
Orders module Image — Orders module Real-time order stream UI
Image — Distributors module Distributor scorecard view
Settlements or Stock Intelligence module Image — Settlements or Stock Intelligence module Full-width feature screen · 1600 × 900px
Image — Field Ops map view Route compliance / coverage map
Image — Design system components Component library / token system

Outcomes after launch

The platform launched to three pilot manufacturer accounts in Q2, with full rollout to Omniretail's manufacturer base following a six-week stabilisation period. Key outcomes measured at the 90-day mark:

Order processing speed improved 3× end-to-end — from placement by a retailer to confirmation by the manufacturer's system. The elimination of the manual relay through distributor reps accounted for most of the gain.

Distributor dispute rate dropped 40% in the first 90 days. The settlement ledger's shared audit trail resolved the information asymmetry that caused most disputes before they escalated.

Onboarding time for new manufacturer account managers dropped 60%. A structured walkthrough sequence and contextual empty states meant new users understood the platform within their first session without training calls.

"For the first time, I can look at Monday morning and actually know what happened Friday. That's not a small thing in this market."

Image — Final product shot Hero visual / polished UI composition · 1600 × 900px
More work
01 / Case study
Verve Ecosystem Revamp
Verve — 0-1 design
Verve ecosystem revamp preview
7 products · one system ↗ Open case
02 / Case study
Switch Core 2.0
A multi-brand design system
Switch Core 2.0 preview
3 Brands → 1328 Components ↗ Open case