Catalogue and variants
Sizes, colours, bundles, options and per-customer pricing, structured the way your products actually exist.
Country and language
Other markets: these available language versions show the same page.
eCommerce
Online stores wired to the stock you actually hold, the way you ship and the software you already run. Built in Paris, with the source code delivered to you.
The problem
Selling online breaks on the parts customers never see. Stock that says four when the shelf holds none. An order retyped by hand into the accounting software. A carrier label printed twice. A click and collect that nobody in the store is told about. The storefront is the easy half, and the plumbing behind it decides whether the operation survives December.
We build stores around the way you already work. The catalogue follows your real product structure, with sizes, variants, bundles and per-customer pricing, and each order flows straight into the tools that run the business: point of sale, stock, invoicing, accounting. Nothing is typed twice, and nobody has to remember to copy anything at the end of the day.
Payment, shipping and returns are set up with your own providers and your own rules rather than with defaults. Speed matters here more than anywhere else, so product and listing pages are built light: a slow catalogue costs you orders long before it costs you rankings. At launch you receive the source code and the data, and the store keeps running whoever maintains it next.
What you get
A catalogue is the visible part. These are the parts that decide whether it works.
Sizes, colours, bundles, options and per-customer pricing, structured the way your products actually exist.
One stock figure shared by the shop, the website and the warehouse. Nothing sells twice by accident.
Your own payment provider, your numbering, your VAT rules, and invoices that reach your accounting export.
Point of sale, ERP, accounting and carriers linked in both directions, so orders are never retyped.
Clean category URLs, product structured data, feeds for shopping channels, and search that tolerates typos.
Order history, quick reorder, price lists per customer, and quotes when a client buys on account.
How we work
Four stages, in this order. You sign off each one before the next starts.
We map the catalogue, the order flow and every system an order touches after checkout. Deliverable: a priced, prioritised scope.
1 to 2 weeksClickable listing, product page and checkout. Checkout is tested on a phone before a line of it is built.
2 weeksStore, integrations and catalogue import, delivered in testable batches every two weeks on a private address.
6 to 10 weeksPayment in live mode, carrier accounts, staff training, then close monitoring through the first campaigns.
OngoingIntegrations
An order should cross the business without being retyped. What we link most often:
Example project
The shop and the website counted stock separately, so oversold orders were cancelled by hand every week and the team had stopped trusting either figure. We connected the store to the point of sale and moved the catalogue to a single source.
Budget
The figure depends on the catalogue and on how many systems the order has to reach.
Indicative figure for a standard scope. Every quote is issued as a fixed price after the scoping phase, with no per-seat fee.
Plans
The fixed price is still available. The subscription spreads the cost of setting the store up: the store you get is the same one, and hosting, security, backups, payment monitoring and your changes are included in it.
24-month term
Choose this plan24-month term
Choose this plan24-month term
Choose this planPrices include VAT, with the VAT-exclusive amount shown below each price. No commission on your sales, on any plan. The source code is handed over to you on day one. Maintenance prices and terms are stated in the published maintenance offers. Advanced integrations — ERP, accounting, marketplaces, APIs, warehouse systems — are quoted separately.
After launch
For a store delivered at a fixed price, or at the end of a subscription.
FAQ
Ten to sixteen weeks for a first store, from scoping to the first real order. Catalogue quality is usually the critical path: photographs, descriptions and clean product data take longer than the build. We import a sample early so problems in the data surface in week two rather than week twelve.
Yes, and it is the request we get most often. If your systems expose an API or a scheduled export, we synchronise products, stock, orders and invoices in both directions. We check exactly what is possible during scoping, before you commit to anything, because that answer changes the budget.
Yes. Price lists per customer or per group, quantity breaks, prices excluding VAT, quotes turned into orders, and payment on account with a credit limit. Many of our stores serve retail and trade customers from the same catalogue, with two different sets of rules behind the login.
You use your own payment provider, so card data never sits on your server. Legal and data protection requirements that apply to your sector are discussed during scoping and built into the specification, and we tell you plainly where you need advice we are not qualified to give.
See also
Let's talk
Bring your catalogue and your order flow. Thirty minutes is enough for an honest range and a clear view of the integrations.