The problem
A curtain is not a product with size options. It has a width and a drop, both supplied by the customer in centimetres, and the price is calculated from them together with the fabric and the heading style. Expressed as platform variants that is an unbounded set, which is why made-to-measure retailers so often end up with a catalogue that says "call for a price".
Calling for a price is exactly what an online customer will not do. The retailer loses the order to whichever competitor showed a number, and never learns it happened.
What I built
A catalogue where configurable products carry a pricing rule rather than a fixed price, so a customer enters their measurements and sees the cost update before they commit to anything.
Category and product pages structured around how people actually shop this market — by room, by fabric type and by function such as blackout or thermal — because those are the searches, and a single flat catalogue answers none of them.
Standard e-commerce plumbing around it: cart, checkout, order notification email, and an admin area where the retailer manages fabrics and pricing rules without needing me.
Decisions worth explaining
Pricing lives as data, not as code. Fabric prices change and the retailer has to be able to change them without a developer, so the rule is stored and edited rather than compiled in.
Measurement guidance sits next to the input fields rather than on a separate help page. In made-to-measure, a customer who is unsure how to measure abandons — and one who measures wrongly generates a return that costs more than the sale.
Want something like this?
If you are looking at this because you need the same thing built, send me the brief. You will get a reply within one business day and a fixed-scope quote before anything starts.