Birmingham and the wider Midlands are full of businesses that make or distribute physical products. The catalogues often grew over decades, with several people editing the same records.
We don't have a Birmingham office. We don't have a Birmingham case study either. The part we can describe properly is the catalogue, because that decides whether a Shopify build holds.
What the catalogue usually needs
Titles written three different ways. Options that should have been variants, or variants that should have been separate products. Pack sizes buried in a description. Prices that differ by customer. A checkout that still behaves like a retail shop.
Clean enough means one naming pattern, a unique SKU for every sellable item, and a decision about which system owns each field. The trade product data guide is the sequence we use before design starts. The choice between variants and separate listings is in this guide.
Account pricing is the next job, once the range is trustworthy. Fáilte Foods is a Glasgow wholesaler, and every trade customer there needed their own terms. Read it as the pricing pattern, if your prices work the same way.
If the catalogue is the bottleneck, send us the store.
Questions we hear
Do you have a Birmingham office?
No. We're based in Belgium and work with Midlands businesses on a call. We have not published a Birmingham case study.
Should we clean product data before a Shopify build?
Yes, on a trade catalogue. Agree one structure for products, variants and pack sizes, decide which system owns each field, then build. A design can't fix data it doesn't understand.
Can Shopify handle prices that differ by customer?
Yes. Account pricing is a normal part of a wholesale build. The catalogue still has to be clean first, or every customer sees a messy range at their own price.