SYSTEM OUTPUT
PROJECT // READY
CASE STUDY / DIGITAL EXPERIENCE
Peter's Tools
From PDF catalog to operational ecommerce.
I transformed a digital presence built around PDF catalogs and manual enquiries into a specialized ecommerce experience designed to help automotive professionals discover, evaluate and buy technical tools online.
CLIENT
Peter’s Tools
ROLE
Digital Strategy, UX/UI Design, Ecommerce Architecture & WordPress / WooCommerce Implementation
YEAR
2026
duration
5 months
scope
UX Research · Information Architecture UX/UI · Ecommerce · Responsive Design WordPress · WooCommerce
status
Functional ecommerce / Launch preparation
Context
The products existed. The digital buying experience did not.
Peter’s Tools had years of commercial experience, technical product knowledge and close relationships with workshops.
Online, however, the business worked mainly as an informational presence supported by a PDF catalog.
Customers could discover that products existed, but they could not complete the full journey from finding the right tool to purchasing, managing an account and receiving support through the website.
Before
PDF CATALOG >> FIND PRODUCT >> PHONE / EMAIL / MESSAGE >> MANUAL ORDER MANAGEMENT
After
DISCOVER >> FILTER >> PRODUCT >> CART >> CHECKOUT >> ACCOUNT >> SUPPORT
THE SCALE OF THE CATALOG
186 products. 464 SKUs. One catalog that needed structure.
The goal was not to migrate the entire catalog indiscriminately.
The initial ecommerce selection focused on 24 products Peter wanted to prioritize, while the underlying structure was designed to support an evolving catalog over time.
186 PRODUCTS IN
THE ORIGINAL CATALOG
464 SKUs
INCLUDING VARIANTS
24 PRODUCTS SELECTED
FOR INITIAL LAUNCH
40+ SUBCATEGORIES
15+ BRANDS
RESEARCHING HOW PEOPLE SEARCH
Professionals do not all start from the same question.
The research showed that a purely category-based catalog would not reflect how different customers actually look for technical tools.
Some users know the exact reference.
Others know the type of tool.
Others only know the repair they need to perform, the result they want to achieve or the kind of workshop they operate.
“I KNOW THE REPAIR”
→ Repair
“I KNOW THE TOOL”
→ Tool family
“I KNOW WHAT I NEED TO ACHIEVE”
→ Professional goal
“I’M EQUIPPING MY BUSINESS”
→ Workshop type
INFORMATION ARCHITECTURE
A technical catalog cannot be navigated in only one way.
Instead of forcing the complete catalog into a single hierarchy, I designed several entry points around different user intentions.
The same product ecosystem could therefore be approached through technical knowledge, task, objective or professional context.
Backend catalog taxonomy
4 main categories · 40+ subcategories
///////
User-facing discovery architecture
4 ways to explore
01 — BY REPAIR
5 repair contexts
02 — BY TOOL FAMILY
8 tool families
03 — BY PROFESSIONAL GOAL
6 work objectives
04 — BY WORKSHOP TYPE
5 workshop profiles
THE USER JOURNEY
From uncertainty to a complete purchase.
The architecture was designed around more than product discovery.
The experience needed to continue through evaluation, purchase, payment, account management, order communication and post-sale support.
That meant solving an ecommerce system, not redesigning a homepage.
NEED / REPAIR >> CATEGORY / TOOL >> FILTER >> PRODUCT >> CART >> CHECKOUT >> ACCOUNT >> SUPPORT
VALUE PROPOSITION
Ecommerce without losing the value of human expertise.
Peter’s Tools did not differentiate itself only through product availability.
Part of its value came from helping professionals identify the right tool, responding quickly and offering technical support when compatibility or application was unclear.
The digital experience therefore needed to automate buying without removing access to human expertise.
PROFESSIONAL
SELECTION
CLOSE
SUPPORT
FAST
DELIVERY
SPECIALIZED
ADVICE
UX/UI SYSTEM
One interface across the full purchase journey.
I designed the main ecommerce touchpoints as one responsive component system:
home, store, categories, product pages, filters, search, cart, checkout, account, support and corporate content.
The objective was to keep a dense technical environment readable and consistent while making the most important actions easy to locate across desktop and mobile.
PRODUCT INFORMATION
Technical products need technical clarity.
Product content arrived in different levels of completeness.
Peter provided core references, product names and imagery, while I researched and structured additional categories, descriptions, attributes, brands and supporting imagery where required.
Each product page had to balance commercial information with specifications, applications and compatibility.
Product
name
REFERENCE
price
Application
TECHNICAL
ATTRIBUTES
compatibility
images
availability
add to cart
related
products
BUILDING THE ECOMMERCE
The design had to become an operational system.
The approved experience was implemented in WordPress and WooCommerce using Elementor, custom HTML/CSS and supporting plugins for filtering, privacy and ecommerce functionality.
The build covered the operational journey from catalog discovery to cart, checkout, account management, transactional communications and support.
CATALOG
MANAGEMENT
FILTERS &
SEARCH
CART &
CHECKOUT
User
account
ORDER
MANAGEMENT
support
email
communications
legal &
cookie system
responsive
experience
PAYMENTS & OPERATIONS
The platform was configured around the operational requirements of selling in Spain, including taxation and multiple payment options.
The ecommerce structure supports direct purchase while leaving room for personal assistance when a customer needs help.
PAYMENT METHODS
Bank Transfer
Stripe
PayPal
tax
Spanish ecommerce taxation
tested on
Desktop
Large display
Smartphone
TECHNICAL PROBLEMS & ITERATION
Real products are built through constraints and failures.
Implementation introduced a second layer of design problems.
Conflicts appeared between WooCommerce, Elementor, filtering plugins, login states, checkout templates, side cart behavior, caching, email templates and custom styles.
The work therefore became an iterative cycle of design, implementation, testing and technical correction.
ISSUE 01
Slow loading
→ cache / assets / configuration refinement
ISSUE 02
CSS overload and inconsistent rendering
→ style cleanup / optimization
KEEPING HUMAN SUPPORT
Automation should remove friction, not remove people.
I deliberately kept human support visible throughout the ecommerce.
Technical purchases can involve doubts about measurements, compatibility, performance or application. A cart does not remove those questions.
The final model therefore combines autonomous purchasing when users know what they need with direct assistance when they do not.
RESULTS
From an informational website to a complete ecommerce infrastructure.
The project resulted in a functional, responsive ecommerce infrastructure capable of supporting product discovery, technical information, direct purchasing, user accounts and post-sale support.
Peter’s Tools moved from relying on PDF catalogs and manual order handling towards a hybrid model: autonomous ecommerce when the customer knows what they need, and personal support when technical guidance is required.
THREE DECISIONS THAT SHAPED THE PRODUCT
01 — MULTIPLE ENTRY POINTS
I designed several ways to explore the catalog because technical knowledge cannot be assumed.
02 — HUMAN SUPPORT STAYS
I kept direct support visible because technical ecommerce does not eliminate questions about compatibility or use.
03 — BUILD THE FULL JOURNEY
I developed the complete WooCommerce experience because the business problem was operational, not only visual.
CLIENT
Petar Ivanov Mitev
catalog & product validation
Peter’s Tools
DIGITAL STRATEGY
INFORMATION ARCHITECTURE
UX/UI DESIGN
ECOMMERCE IMPLEMENTATION
Pablo Guijarro - Pabel Stonehenge
BACKEND & WOOCOMMERCE SUPPORT
Marcos Bohórquez
RESULTS
Peter’s Tools reinforced something I had learned in UX but had never experienced at this operational scale: a digital product is not finished when the interface is finished.
Catalog structure, product data, payments, accounts, legal requirements, plugins, performance, communication and support all shape the final experience.
The project strengthened my ability to translate a manual business into a digital system while balancing user needs, commercial priorities and technical constraints.
If I buld it again, I would define a more structured product database, analytics framework and technical launch plan from day one to reduce rework and measure impact from the first order.
IS YOUR CATALOG STILL DEPENDENT ON PDFs, CALLS AND MESSAGES?
Let’s turn it into an ecommerce experience that understands how your customers actually buy.
Start a Project
> Press ENTER tostart a project.
STATUS: PROJECT READY
