IMtech

Service

Online stores

We build online stores and online ordering around your range and process: a catalogue you manage yourself, a cart and payment, order statuses, documents for delivery and data exchange with your accounting. There is no separate online-store case study on the site yet — the same parts (a catalogue, orders, online payment with payment verification, delivery documents) are in the corporate catering case study.

Animation: products move from the shelves into a cart one by one, the cart turns into an order, and a “paid” mark appears on it.

When you need it

Situations that bring people to us for this service.

  • Orders arrive in a messenger

    A customer writes in a chat, a manager copies the order into a spreadsheet — and some get lost on the way.

  • Templates can't hold your rules

    The price depends on several conditions, there are limits, company-paid orders or an order cut-off — a ready-made platform can't do it.

  • Payments are reconciled by hand

    Who has paid and who hasn't is worked out from the bank statement rather than seen in the order.

  • The warehouse and delivery find out last

    After an order, someone manually puts together lists for the warehouse, the kitchen or the courier.

What's included

  1. Catalogue and prices

    You manage categories, products, photos, hidden items and prices in the panel, and the store takes them from there.

  2. Cart and checkout

    A cart, a delivery address or point, a comment and a clear summary before payment.

  3. Online payment

    A payment service connected, with the system itself checking that the payment really went through.

  4. Prices by your rules

    Prices built from several conditions, limits and the “who pays” rule are calculated by the system, not a manager.

  5. Orders with statuses

    Every order is stored in the system with a status and a history; managers search and filter them in the panel.

  6. Customer account

    Customers see their orders, and companies can have separate accounts with their own rules.

  7. Documents for fulfilment

    The system prepares spreadsheets for the warehouse or kitchen, labels and delivery lists itself — on a schedule if needed.

  8. Data exchange with accounting

    Products, prices and orders pass between the store and your accounting system without double entry.

What you get

  • A catalogue structure and an ordering scenario
  • A store with a panel for managing the catalogue and prices
  • Online payment, connected
  • Orders with statuses and a customer account
  • Automatic documents for the warehouse and delivery
  • A technical foundation for search

The project path

From the first conversation to daily use

Every step ends with a decision: go on or stop. We don't start the next one until the previous one has given its answer.

  1. 01

    Getting to know the task

    You describe the process and what gets in the way. We reply by email with questions and arrange a call.

  2. 02

    Discovery

    We study the process with the people who work in it and write down what the system must change and how we will check it.

  3. 03

    Prototype

    We build a working prototype of the key scenario to test the idea on real data rather than on polished screens.

  4. 04

    Pilot

    We run the system in your real environment with agreed outcome criteria and a deadline. After the pilot we decide together whether to go further.

  5. 05

    Launch and growth

    We bring it to daily use: reliability, access rights, links to other software, documentation, support. Then we develop it based on user feedback.

Systems where we have already done this kind of work.

Technology in these case studies

  • Strapi
  • PostgreSQL
  • Next.js
  • LiqPay
  • Puppeteer
  • Django
  • Django REST Framework
  • Telegram

Questions about this service

Why not use a ready-made store platform?

If your process fits its template, use it. We are needed when you have your own rules: prices built from several conditions, an order cut-off, company accounts, a link to accounting.

Which online payment can you connect?

In the corporate catering case study it is LiqPay, with a check that the payment really went through. We choose another payment service to fit your task.

Can the store be linked to our accounting system?

Yes — exchanging data with what already works is one of our principles. What to pass across — products, prices, stock levels, orders — we decide during discovery.

Is there an online store among your case studies?

There is no separate online-store case study on the site yet. The corporate catering case study shows a catalogue, ordering and online payment with payment verification.

Have a project with no ready-made solution?

Describe it in a few sentences: how things work today and what gets in the way. We reply by email with questions on the next business day.

Get in touch