euroboxx
A parts catalogue built in WordPress and Elementor where search, filtering and checkout stay out of the buyer’s way — and stay fast as the catalogue grows.
The brief
Nobody browses a parts catalogue for pleasure. They have a machine that has stopped working and a specific component in mind, and every extra click between them and that component is a chance to leave for a competitor.
So the brief was unglamorous and clear: fast search, filters that behave, product pages that state the facts, and a checkout that does not ask for anything it does not need. Then keep it quick with hundreds of products in the database.
The problem
Finding things
Search and filters are where catalogue sites live or die. They have to return the right part in one attempt, and keep working when the visitor spells it differently.
Scale
A store that is quick with twenty products and slow with four hundred was never built properly. Query load and image handling had to be planned for the full catalogue.
Checkout friction
Every optional field, surprise shipping cost and forced account creation loses a percentage of buyers who had already decided to pay you.
How I built it
01 · Set the system before the pages
Global colours, global type, container presets and a spacing scale taken straight from the Figma file — so every page after the first one inherited the design rather than re-implementing it.
02 · Build to the design, ask before improvising
Every section checked against the file at desktop, tablet and phone. Where the design didn't specify a breakpoint I proposed one and got it signed off instead of guessing quietly.
03 · Keep it fast with the whole catalogue loaded
Efficient product queries, sensible caching, image sizes generated per context, and filtering that does not reload the world every time someone ticks a box.
04 · Hand it over properly
Named containers, a short recorded walkthrough of the sections they'd actually edit, and two weeks of cover afterwards for anything that came up.
Catalogue filtering and repeating product layouts are exactly where stock builder controls run out, and where a small piece of custom Elementor widget development replaces a stack of nested containers. The wider build followed the usual Figma to Elementor process.