Skip to main content

Service

Online store development

An online store is not a page with a pay button - it is the connection between what the customer sees and what the business does.

The order is only the beginning. The questions that decide whether a store works are what happens after it: how the kitchen knows what to make, how stock comes down, who updates a price and where. We built a bilingual store for a six-branch chain - picker screens, kitchen displays, two-way ERP sync - with automated tests running the ordering path on every update, because in commerce the difference between a bug and a lost day of sales is no difference at all.

Let's Talk

Prefer to write? Send an enquiry through the form

What it gives you

  • Orders that reach fulfilment directly - no phone read-outs, no manual handoffs
  • Stock and prices in one source of truth - what the customer sees is what is true
  • Secure checkout, and a bilingual interface where the audience needs one
  • The ordering path is covered by automated tests - a code change cannot break checkout

Who this is for

  • A business whose orders arrive by phone and WhatsApp, with somebody reading them out to the kitchen or the warehouse.
  • A business selling online where the order lands in an inbox somebody has to remember to check.
  • A business with several branches or collection points, where an order has to reach the right one.
  • A business whose stock and prices live in another system that the store has to agree with.

How the work runs, stage by stage

  1. Scoping the order path

    Not the product page - what happens after payment. Who receives the order, on which screen, and what they do with it. That is what decides whether the store works.

  2. Catalogue, stock and prices

    The catalogue structure and the variants, and which system is the source of truth for stock and price. What the customer sees has to be what is true, and that is an architectural decision rather than a setting.

  3. Checkout and tests

    The payment connection, and the handling of failures and refunds. The ordering path is covered by automated tests that run on every update, because in commerce a checkout bug is a lost day of sales.

  4. Operational screens

    A picker screen in the warehouse or the branch, a kitchen display that receives the order directly. We built both for a six-branch chain, and without them the order goes back to being a printed sheet.

  5. Sync and launch

    A two-way connection to whatever manages stock and prices, so an update in one place reaches the other. And after launch, the first month of fixes is included.

What setting up an online store costs

There is no single number, and anyone who gives one over the phone before seeing the business is guessing. The cost of an online store is built out of layers, and the difference between a cheap store and an expensive one is almost always in the operational layer - what happens after the order comes in - rather than in the design of the product page. These are the components every store pays for, in any quote you receive and from any supplier:

  • The catalogue: how many products, how many variants each, and who enters them the first time.
  • Checkout: the payment connection, and the handling of failures, refunds and an order that stalls halfway.
  • Stock and prices: one source of truth, and who updates it. This is the component that surfaces late when it is not handled up front.
  • Delivery or collection: areas, prices, and a courier connection where there is one.
  • Order operations: where it goes after payment. A picker screen, a kitchen display or an ERP sync are the real work, and they are what separates a store that works from one that looks good.
  • Integration with an existing system: a documented API is days of work, its absence is weeks.
  • Two languages, where the audience needs them. That is a doubled structure rather than a translation.
  • Automated tests on the ordering path. That is a cost up front in place of a lost day of sales later.

What we built

A kosher restaurant chain - six branches in Thailand, two languages, and a kitchen that receives the order directly.

Common questions

How much does it cost to set up an online store?

It depends almost entirely on the operational layer rather than the design: a simple catalogue with a payment connection is one project, and a store wired to stock, a kitchen display and an ERP is a different one. The range comes in a written proposal after a scoping call that maps what happens once an order arrives. The section above lists every cost component, so you can compare quotes on the same criteria.

Which cost component surprises people most?

The source of truth for stock and price. As long as there is one place they are managed, it is configuration. Once there are two - the store and the system the business runs on - somebody has to decide which one wins and build the sync, and that is work no price list mentions.

Can the store be connected to the system we already use?

Yes. We built a two-way ODOO sync for a six-branch chain, so stock and prices stayed one source of truth. If your system has a documented API it is days of work; if not, we look at what is possible.

Why not Shopify or WordPress with WooCommerce?

For a simple catalogue store they are usually the right choice, and we will say so. The gap opens once an order has to reach operations - a picker screen, a kitchen display, the correct branch, a two-way sync - at which point plugins accumulate, each with an annual licence and a failure point, and the store becomes something it is hard to change safely.

What if orders land at the wrong branch?

It happens, and it is not a display bug - it is a meal that left the wrong kitchen. The answer is for the server to be the sole authority on branch identity, with no default values in the code guessing when that identity is lost. We solved this on the J-Cafe store and its case study sets out how.