Improving the clarity, discoverability, and usability of essential workflows across a B2B marketplace and procurement platform.
OutcomeImproved critical Lot Management workflows through customer feedback and cross-functional collaboration. Following a feature-flagged rollout and public release, the customer-facing team reported fewer lot-editing support requests.
Requis is a B2B platform supporting marketplace, procurement, inventory, and customer relationship management workflows.
As a Product Designer, I worked across multiple areas of the platform with product, engineering, and customer-facing teams. This case study focuses on three Lot Management improvements: clearer toolbar actions, easier filtering, and consolidated lot editing, with Procurement and CRM work shown as supporting examples.
Recurring support requests revealed friction across critical workflows.
Recurring support tickets highlighted problems with lot editing and adding assets.
Customer-facing, product, engineering, and design teams examined where requests were concentrated.
Important actions already existed but were difficult to recognize because of unlabeled icons.
Focus on issues preventing customers from preparing and listing marketplace assets.
Rather than treating every usability issue as equally urgent, we addressed the friction preventing users from completing important workflows before tackling less urgent improvements.
The feedback shaped three design principles that guided each change:
Make important functionality understandable without guesswork.
Preserve established interaction patterns where possible.
Bring related actions and navigation together to simplify workflows.
In Requis, a lot is a collection of assets prepared for listing on the marketplace. Lot Management allows users to organize these assets, manage listing information, and prepare them for sale through options such as Buy Now, Make Offer, Auction, or Inquire.
Recurring support tickets showed customers struggling to identify important actions on the Lot Listing Preview page, particularly attaching documents and adding assets. The actions existed, but they were represented by small, unlabeled icons, so customers sometimes needed help finding functionality that was already there.
My design decisionI added visible text labels to the existing toolbar actions and kept the toolbar in its established location on the page.
Clearer actions, familiar placement. I introduced visible labels while preserving the toolbar's existing location to improve discoverability without requiring returning users to relearn the interface.
Managing a large number of lots meant narrowing the list by attributes such as sale method and status, but the filters were hidden inside the settings menu, behind the gear icon. Feedback from the internal customer-facing team, who manage large numbers of lots, showed they needed a quicker way to filter.
My design decisionI moved filtering out of the settings menu into a dedicated filter panel, opened directly from the list toolbar, so the lot list stays visible while users refine results. Active filters appear as removable chips above the table, with a Clear All option.
Filters where people already look. Bringing filters out of settings and into the list toolbar, and keeping active filters visible above the table, made it quick to narrow a long list and always clear which filters were shaping the results.
The Edit Lot page contained many sections of information, but its structure wasn't visible from the editing view. Section navigation was available through Lot Preview, but it wasn't consolidated on the Lot Edit page, so users had little indication of what information was available or where to find it while editing.
My design decisionI brought section navigation into the Lot Edit page itself, covering Info, Description, Seller Terms, Finance, Questions, Inspection, Shipping/Pickup, and Images, with a clear path back to Lot Preview.
One place for every editing task. Consolidating editing navigation within the Lot Edit page gave users one place to access and move between related editing tasks.
The redesigned workflows were first introduced to a small group of customers through a feature-flagged release. Feedback from customers and the internal team helped validate the improvements before wider availability.
Invited customers successfully edited and published their lots during the feature-flagged release.
The customer-facing team reported fewer lot-editing support tickets during the feature-flagged release and after the changes became publicly available.
The internal customer-facing team reported that the updated filtering and Lot Edit experiences made their work easier.
Reported, qualitative outcomes. Several improvements were released together, so they reflect the combined changes rather than any single one.
Beyond Lot Management, I also designed across Procurement and CRM.
Designed and refined responsive interfaces and interactions across complex procurement workflows, including the mobile experience of a procurement project, from the workspace overview to requests, suppliers, and commercial questions.
Requis was building its own CRM so customers could manage their relationships inside the platform instead of relying on a separate tool such as Salesforce.
A new feature I designed: from a CRM account, users find the matching company in the Requis network, verify it's the right one, and create the connection, and when the company isn't in the network yet, they can invite it directly from the same flow.
Working across Lot Management, Procurement, and CRM, I reused the same building blocks so moving between areas felt like one product, while adapting them to each workflow's needs.
Used familiar interactions and components that could work across multiple features.
Created consistent treatment of primary information, actions, and supporting content.
Considered how layouts and interactions adapted across different screen sizes.
One Lot Detail experience, adapted across desktop, tablet, and mobile. Desktop uses a multi-column layout with a separate actions panel, tablet reorganizes the content within a narrower layout, and mobile prioritizes a readable, vertically stacked presentation. Click any screen to enlarge it.
I worked closely with product managers, engineers, and customer-facing teams to translate feedback and product requirements into practical design improvements.
Our discussions helped us prioritize issues affecting essential workflows and understand technical constraints. I explored interface solutions, refined designs through feedback, and collaborated with engineers to support implementation.
Working on an established platform also meant considering how changes would affect existing users, not just how an individual screen could be improved.
Working on Requis reinforced that improving a complex product doesn't always mean redesigning it.
The Lot Preview improvements were a good example. The functionality already existed, but users struggled to recognize it. Adding clear labels while preserving familiar controls helped address the problem without disrupting established workflows.
The experience strengthened how I approach product design: understand the friction first, then make changes that solve the problem without introducing unnecessary complexity.