Orbital Cart CMS
B2B purchasing workflow with built-in approvals to reduce back-and-forth before checkout
Designed a shared cart where teams can review, comment, and approve items before purchase, improving clarity across roles.
Role: Product Designer
Scope: System concept, user flows, interaction states, low-fidelity wireframes
Tools: Figma
Timeline: ~2 weeks
Scope: System concept, user flows, interaction states, low-fidelity wireframes
Tools: Figma
Timeline: ~2 weeks
These screens show the core workflow, from adding items to reviewing and finalizing purchases.
Buyer Experience
Buyers add items and track approval status while waiting for decisions
The Problem
Most ecommerce carts are built for a single user, while real-world purchasing involves multiple stakeholders.
The Idea
A shared cart where teams can review, discuss, and approve items before checkout.
Core Workflow
Items move through three states:
• Proposed – Added and awaiting review
• Approved – Cleared for purchase
• Rejected – Needs revision
• Proposed – Added and awaiting review
• Approved – Cleared for purchase
• Rejected – Needs revision
Checkout is locked until required approvals are complete.
Checkout becomes available once all items are approved
Item Review Interaction
Approvers can expand an item to review details, discuss, and approve or reject directly in the cart.
Decisions stay tied to the item instead of getting lost in email or chat.
Decisions stay tied to the item instead of getting lost in email or chat.
Purchase approvers review proposed items and make final approval or rejection decisions
Roles and Permissions
Supports role-based permissions that reflect real purchasing workflows.
• Buyers add items and participate in discussions
• Budget owners review item purchases
• Purchase approvers authorize final checkout
• Budget owners review item purchases
• Purchase approvers authorize final checkout
Defines roles and permissions that control who can propose, review, and approve items
Reflection
Explored how a shopping cart could support team-based purchasing instead of a single buyer.
Focused on keeping the workflow simple while clearly showing who proposed, discussed, and approved each item.
Focused on keeping the workflow simple while clearly showing who proposed, discussed, and approved each item.