B2B commerce · Physical-digital product
A virtual showroom built around how wholesale buyers actually order
- Role
- Product Manager, Obsess
- Employer
- Obsess
- Client
- Marimekko
In one minute
I interviewed and observed wholesale buyers who planned large purchases across multiple visits. That research made save-and-return Lists central to Marimekko's showroom. The B2B work led the client to extend its engagement with Obsess for one year.
What I owned
As Product Manager at Obsess, I personally interviewed and observed wholesale buyers, translated their behavior into requirements, and worked across design, technology, content, and the client team. Launch approval was shared with the wider team.
What held up
The product tied immersive discovery to the actual work of wholesale ordering. Marimekko renewed Obsess for another year because of the B2B work.
Choice + alternatives
The consequential choice
We made Lists core product infrastructure, not a convenience feature. Without them, buyers would have had a beautiful but temporary browsing experience, then had to recreate their work somewhere else.
We kept the existing ordering flow intact. The showroom became a useful layer on top of the commerce system, rather than a disconnected destination competing with it.
Stakes
What was at stake
The showroom had to do more than make the collection feel immersive. Wholesale buyers use a visit to plan large orders, so they needed a way to save their selections as well as discover products.
Constraint
The hidden constraint
Research showed that saveable Lists were essential to the buyer's process. The experience also had to work with Marimekko's legacy Magento / Adobe Commerce catalog and ordering system. Commerce did not begin inside the new interface.
Delivery
What we built
A virtual B2B showroom connected to the existing product catalog.
Saveable Lists that let buyers build and return to a wholesale order plan.
Add-to-cart and a handoff into the continuing Magento / Adobe Commerce ordering flow.
Supporting material
Inspect the work
- Catalog-to-order system map
View artifact · System map
A simplified, non-client-confidential map rendered on this page from the verified integration path.
What this proves I can do for you
I turn buyer research into product requirements, integration decisions, and a launch that supports how customers actually order.
Relevant problem?