Inventory Refactoring
Platinumlist
2026
Role
Product Designer
Product Design, B2B, SaaS, Redesign
Platinumlist's inventory management was split across two separate platforms, creating a fragmented experience for both organisers and the internal operations team. Organisers lacked the tools to configure their events independently, leaving ops to handle a significant portion of setup manually. Existing system was poorly handling repetative setups as well, such as setting up weekend and weekday shows, custom packages availablity and custom settings per show for venue and ticket office.

Challenge

Managing inventory across two separate platforms created friction for both organisers and the internal operations team. Organisers mostly rely on ops team since existing toolset lacked the tools to configure their events independently, while ops handled a significant portion of setup manually: copy-pasting entities and filling gaps the interface simply couldn't support.

Goal

To consolidate two legacy inventory platforms into a single unified tool, reduce manual workload for the operations team, and give organisers enough control to manage their setups independently – without relying on internal support for routine tasks.

Discovery

We ran a series of interviews with organisers alongside dedicated sessions with the operations team across several domains. Two distinct problem layers emerged. On the ops side, the interface didn't support inline repetative scenarios – same packages had to be set up separately for identical shows. On the organiser side, the available setup types didn't match how they actually worked — organisers were repurposing features like Multi-show configurations to handle attraction-type events because the right tools simply didn't exist. The core insight was that the product was missing self-service infrastructure, and the ops team had quietly become the workaround.

Together with anayltics team we also done a competitor analysis of organiser tools across different ticketing platforms and highlighted nice-to-have features and better workaround for the same features that we've had on our platform.

Guided introduction

One of key insights from interviews was that users are getting lost in features. Solution to this problem was found in helping cards and highlighting the most essential parts of toolset.

Inline edits

To speed up the process I've also added inline edit, where possible. This way we also reduce human mistake factor by having an ability to compare parameters in the same context.

Ticket office setup

Exceptions handling

Popup edits

For creating more complex entities we're sticking to popups. They keep the user in context, which is visible enough to understand what they're editing, without losing sight of the broader inventory view.

AI Implentation

For this project we tested the designs by vibe-coding them into an interactive prototype using Claude Code. This allowed us to observe how the operations team tackles complex edge cases in real conditions and gather feedback rapidly before committing to the final implementation.

Interviews

After designing majority of screens I've created an interactive mockup using Claude Code. It helped us together with analytics team measure the coverage of potential scenarios and to understand how users interact with each feature

Results

The clearest measure of success was behavioural: organisers stopped copy-pasting existing events as a workaround and began creating from scratch. The majority of routine cases are now executed by organisers directly. Usage of legacy platform features has significantly reduced for new events.
Let's get connected
RésuméEmailLinkedIn
© Kornilov Dmitrii, 2026