Custom web store development — when your process does not fit the template
The honest part first: when is an off-the-shelf system better?
If you sell a standard product through a standard process — fixed prices, per-piece ordering, home delivery — then a well-configured Shopify, WooCommerce or other hosted platform will be cheaper and faster. I say that in the first conversation, and I do not take on a project just because it is takeable. I walk through the choice with a decision table here: Shopify, WooCommerce or a custom web store.
You need custom development if you have already said to a developer, at least once: "yes, but that is not how it works for us". Wholesale price lists per customer group. Minimum order quantity per product. Variants that change the price non-linearly. Pre-orders with production lead time. Order intake that also schedules production.
For these you go looking for a plugin in an off-the-shelf system, then another plugin for that plugin, and two years later patching the exceptions costs more than the custom system would have.
What do you get in a custom web store?
- A custom product data model. Your product goes into the system the way it exists in reality: with dimensions, variants, minimum quantities, per-customer pricing — not crammed into three standard fields.
- Your own cart and ordering logic. The ordering flow follows how you work, including what happens after the order: confirmation, release to production, shipping notification.
- Payment and invoicing connected. Card payment and your invoicing system (Stripe, QuickBooks, Xero or a local provider) wired together — an order becomes an invoice without a human hand touching it. The quote names the specific payment provider.
- An admin interface you will actually use. Not the thousand menu items of a general-purpose engine, but your five daily operations, five clicks away. For bulk operations you also get a command-line tool — this is what that looks like in practice at the honeyzsu.hu store.
- Product structured data. Your products can appear with price and stock information in Google results and in AI answers.
- Measurable handover. Speed and indexing measured, with a report, so you can see what you got.
What does it cost, and what makes up the price?
The starting price is $1,400 (net). Scope moves it upward: the complexity of the product data model, the number of integrations (payment, invoicing, inventory, shipping), the depth of the admin interface. Every item appears separately in the quote, and the price is fixed, not an hourly estimate. Details and typical project sizes: pricing.
What happens after the order?
A web store does not end at the pay button. The path after the order — confirmation, release to production, stock movement, invoice, shipping notification — is exactly the stretch where off-the-shelf systems get stuck, and where most of the manual work is created. I build that part as process automation, often within the same project.
Frequently asked questions
Can you take over an existing store?
Yes — first I review the code and tell you whether it is worth fixing or rewriting. You get an honest answer even if the answer is to stay with your current system.
What if traffic grows?
A custom system runs on your own server and scales the way your traffic requires — no forced plan upgrades and no transaction commission.
Who owns the code and the data?
You do. Full source code, database, access credentials — handed over and documented. No vendor lock-in: any developer can continue it.
What is the lead time?
Typically one or two weeks, if all the material is available; the quote states a fixed date. The most common reason for delay is missing product data — you get a checklist for that at the start.
Why is my current WooCommerce store slow?
Usually there is not a single cause but the amount of code loaded by plugins and the number of database queries. How far it can be sped up and where a rebuild starts: why WordPress stores are slow.