Custom ecommerce development

When the catalogue breaks

None of these situations is exotic: they're the ones we hear most often, and they have something in common. The platform doesn't fail because it's bad; it fails because it's being asked to do a job it wasn't designed for.

• A genuinely configurable product: the customer picks between options that condition each other, and the price recalculates with every choice.
• The store has to talk to the rest of the business: real stock, production, invoicing, the management system.
• Sales processes that aren't "add to cart and pay": quotes, made-to-order, approvals.
• The pile of extensions holding all of the above together steps on itself and breaks with every update.

We cover the first case in detail, with a real project, in WooCommerce and configurable products: where the limit is (in Spanish).

And an honest read: if you recognise yourself in just one of these situations, a well-chosen extension might be enough. In two or more, cheap starts getting expensive, because every new piece leans on the previous ones and maintenance eats what you saved. It's the pattern from cheap build, expensive maintenance (in Spanish), store edition.

Store and management, together

Most stores that grow end up the same way: the website on one side and the management on the other, usually in Excel. The order comes in through the store and someone retypes it to invoice it. The real stock lives in a sheet that doesn't match the website's. And the same customer exists twice, with different data in each place.

A custom store is designed with the other half in mind: orders that reach invoicing or production without anyone retyping them, stock that is the same everywhere, customers that exist only once. It's the same logic we lay out in custom ERP and management software: very often the store is the visible face of that system, not a separate piece.

The sign that a store has reached that point is usually a hire: someone whose actual job, even if the contract doesn't say so, is moving data between the website, the spreadsheets and the invoicing. Growing shouldn't mean that.

How we work

The same way we build everything: deliveries every two weeks that you can actually use, and no fixed project price, because no two stores are alike. For stores that need it we add profiles (development, UX, QA) at the same rate, and the code and repository are in your name from day one.

The first delivery arrives two weeks after starting and it's real: the architecture decided and documented, the environments deployed and a first piece working. From there, every delivery adds up. And you can scale down or pause whenever you need to: no lock-in periods.

Frequently asked questions