Stores that survive the catalogue and the audit
A shop with thousands of items breaks in two places: when the catalogue grows, and when somebody actually reads the terms. We build for both.
The catalogue decides the platform
Three hundred products and fifteen thousand are different problems. We measure the volume and the process before choosing what to build on.
- Item count, variants, and how often prices move
- Where stock comes from - warehouse, ERP, supplier feed
- Who adds products today, and how long it takes them
- Shipping and payment methods, and who handles them
Built to stay fast past the thousandth product
Most stores slow down at the filters and the search, not the design. That is where a year from now is decided.
- Filtering and search that stay fast across tens of thousands of items
- Carrier integrations for labels, rates and tracking
- A link to the warehouse or accounting, so nothing is typed in twice
- An admin panel your team runs without calling us
The compliance most stores get wrong
Not legal advice - a list of checkable things. We run it on every store, because most fail at least one.
- The link to the European ODR platform: it closed on 20 July 2025 and now leads nowhere
- The withdrawal form, which is the item most often missing entirely
- priceCurrency in the structured data, which goes stale quietly and never shows on screen
- Trader details reachable directly - a contact form alone does not satisfy the requirement
After launch the store has to sell
A launched store is not a finished store. We look at where people stop and what keeps them from paying.
- Product feeds to Google and marketplaces, in the right currency
- Tracking that reports orders, not just visits
- An AI assistant that answers from your actual catalogue
- Support on stated response times, peak season included
Who this is for
We work best where the catalogue is large and the processes are real.
- Stores with thousands of items that crawl when filtering
- Merchants whose stock arrives from a supplier and is keyed in by hand
- Shops on an ageing platform that is now costing them orders
- Businesses selling across borders who need more than one language done properly
Frequently asked questions
What does an online store cost?
It depends on the catalogue and the integrations, which is why we publish no price list - it would mislead both sides. A store with standard shipping and payment is one thing; a store wired to a warehouse, three supplier feeds and two languages is another. After the first conversation you get a quote in 3 working days, broken down by stage.
How long does it take?
Usually two to four months depending on scope. The longest part is rarely the store itself - it is the integrations and the state of the product data. If the catalogue arrives from a supplier in poor shape, that is its own stage and we say so up front.
My store is slow. Fix it or rebuild?
We check it first and tell you honestly. Sometimes it is a handful of database queries and takes days. Sometimes the foundation will not survive another year and patching only delays the conversation. Either way you hear which one it is.
Will a new store cost me my Google rankings?
Not if the migration is done properly - redirects from every old product URL, structure preserved, verification in Search Console afterwards. This is exactly where rankings are lost through carelessness, so it is a separate stage with its own check.
Where is the store hosted?
Wherever fits - your hosting, ours, or a data centre in the EU when data residency matters. We run our own infrastructure, so this is a real choice rather than whatever the platform allows.
Tell us what you sell
Send us the catalogue and where it breaks today. We answer with scope and a quote in 3 working days.