PrimeOS
Every channel.
One operating view.
A shared workspace for commerce teams to connect performance signals with the work that needs attention.
The project
The daily work of commerce,
in one shared context.
I designed and prototyped an internal product that brings orders, stock, products, channels and customer information into a consistent operating workspace.
- Role
- Product Design + Front-end
- Deliverable
- Interactive front-end prototype
- Platform
- Responsive web application
- Stack
- React, TypeScript, Vite
Product structure, information architecture, interface design and AI-assisted front-end implementation. Working screens made it possible to explore navigation, density and responsive behaviour together.
The challenge
A signal in one place.
The next action somewhere else.
The product brief centres on fragmented commerce work. A team can see revenue in one tool while the order, stock issue or customer context sits in another. My design goal was to reduce that separation.
What needs attention now?
Surface pending orders, delivery exceptions and low-stock items before a team has to search for them.
Which channel is affected?
Connect store health and channel performance with the underlying operational records.
Where does the work continue?
Use consistent navigation and statuses so a signal leads into a recognisable workspace.
These questions express the design problem; they are not quotations from user interviews.
A platform first.
A collection of screens second.
The solution concept connects demand, CRM, commerce, service, integrations, dashboards and AI. It provided a product map for deciding how the different areas should relate.
The available evidence consists of the solution concept, product introduction video, light interface explorations and dark desktop/mobile prototype screens. It supports a design rationale and visual comparison. Interview records, original wireframes, dated test feedback and production results were not provided.
Group the work.
Keep the operating loop connected.
I organised the interface around the work a commerce team returns to: understanding performance, managing operations, supporting growth and maintaining the workspace.
Overview & analytics
Operating queues
Channel performance
Revenue context
Commerce work
Orders & fulfillment
Products & warehouses
Connected channels
Customer context
Customers & segments
Marketing
Promotions
Workspace settings
Configuration
Plan & billing
Help & support
A retrospective map of the product structure and intended operating loop.
Make hierarchy visible
before adding visual detail.
Three layout studies explain the structure behind the final interfaces: a prioritised overview, a filterable work queue and a focused record detail.
Low-fidelity reconstructions created for this case study from the documented interfaces, not original project wireframes.
Design decisions
From a conceptual loop
to the everyday operating view.
The archive contains two interface directions. The light Decision Hub makes the signal-to-action model explicit. The dark home screen foregrounds operational queues and channel revenue.
A comparison of documented directions. Dates and feedback are not available to establish a tested before-and-after iteration.
The working interface
Open the day
with a clear set of priorities.
The home view separates readiness, operations and performance. Orders, fulfillment, inventory and CRM become visible queues, while the revenue strip keeps each commerce channel in context.
ReadinessKeep setup work visible.
OperationsExpose exceptions and pending tasks.
PerformanceRetain the cross-channel picture.
A shared picture
of business performance.
Unified Analytics brings channel contribution, regional revenue and customer segments into the same workspace. The visual hierarchy moves from comparison to key totals and then into detail.
High-density work.
A recognisable way through it.
Orders and warehouses need detailed lists. I kept the surrounding structure consistent so that filters, status summaries and record actions remain easy to locate.
The product and the customer
stay part of the same story.
Product records support commerce work; customer records preserve the relationship behind an order. Shared search, filters and table patterns give these workspaces a familiar structure.
Connected channels.
Visible connection health.
Each channel carries its own store, listing and synchronisation state. The connected-channels view keeps those signals together so operators can identify where attention is needed.
AI inside the workspace,
with the operator in control.
The Prime AI concept sits within the existing navigation and working area. Suggested requests offer an entry point while the product context remains visible around the assistant.
Responsive system
Less room.
The same order of importance.
Mobile layouts replace horizontal breadth with a focused reading order. I carried the dark interface, section hierarchy and working context across analytics, customers and billing.
A consistent language
for a complex product.
The prototype repeats a dark workspace shell, violet primary actions, quiet borders and compact information groups. Semantic status colours help distinguish operational states.
Scan the overview.
Act on the detail.
- Shared navigation and page headers
- Consistent filters, tables and status patterns
- Responsive reading order
#0C0C11#191822#6B5CFF#F3F2F7A visual summary of the existing interface direction and case-study palette, not an exported design-token specification.
Even the plan screen
belongs to the same product.
Plan and Billing uses the same shell and information hierarchy. Tier differences remain visible inside the workspace instead of introducing a separate visual language.
Outcome & reflection
A working product direction.
A foundation for validation.
The deliverable is an interactive front-end prototype for a client internal product. It connects product thinking with responsive screens and reusable working patterns.
What I delivered
A shared operating structure, desktop/mobile interface design and AI-assisted React implementation across the core commerce workspaces.
Building alongside design made the practical trade-offs visible: how much information fits, where actions belong and how the hierarchy changes on mobile.
What comes next
Validate whether operators can identify the highest-priority exception, find the relevant record and complete the next action with fewer context switches.
No verified usability results, public release or business-impact metrics are available. Revenue, counts and percentages in the screens illustrate the prototype.
A useful operating workspace connects an overview to the next task. Consistency matters most at the handoff between them.