Online stores

Stores we have built

We have built stores in a range of niches — computer hardware, car parts, mobile phones, cosmetics. Some examples:

• ITsector.bg, an OpenCart store with TBI Bank instalment purchasing built in.
• DND-Parts.com, a car-parts store, covering design, development and project management.
• FlexiCasa.es, on WordPress, with Stripe payments and REST API links to outside systems.
• Fitmama.bg, a WooCommerce store we designed and developed.
• Lorieta beauty, a cosmetics store with online payments.
• Gago GSM and Masis.BG, both on OpenCart.

WooCommerce or OpenCart

WooCommerce runs on WordPress and is a good fit when the store sits alongside a lot of content: a blog, articles, guides, brand pages. Many people already know how to edit it, and its plugins cover almost every need. OpenCart is tidier and built purely for selling. It copes well with large catalogues full of variants and filters, such as car parts, electronics and spares.

We do not recommend either out of habit. The choice depends on the size of the catalogue, how much content there will be beyond products, which systems the store has to talk to, and who will look after it. If neither platform fits — for example, when the store is just a shop window onto a large warehouse or B2B system — we build a custom solution tied directly into it.

Speed matters too. A store with thousands of products and a dozen plugins easily turns sluggish, and every second of waiting on a phone loses buyers. So we watch how many requests each page makes, cache the catalogue and never add a plugin without checking what it costs in speed.

Payments, instalments, couriers, stock

This is where most of the real work lies. We connect the store to:

• Card payments, through Stripe or your bank's payment module, with proper handling of failed and refunded payments.
• Instalment buying and leasing, such as TBI Bank, so customers can apply straight from the basket.
• Couriers: a shipping label created from the order, delivery cost shown in the basket, tracking for the customer.
• Warehouse and ERP: stock and prices that update automatically, and orders that go straight into processing.
• Accounting and invoicing: an invoice or receipt with no retyping.

How the build runs

We start with the catalogue and the process, not the design. How many items you carry, what variants they come in — size, colour, pack size — where the descriptions and photos come from, and how an order is handled from payment to delivery. Then we work out the category structure and filters, because that is how customers find products.

We show the design as a prototype on a phone, since that is where most orders come from. The basket and checkout matter most: the fewer steps and fields, the fewer abandoned baskets. Before launch we run test orders with every payment and delivery method, including a refunded payment and a cancelled order, to be sure everything ends up where it should.

There are also legal must-haves that often get forgotten: terms and conditions, a privacy policy, information on the 14-day right of withdrawal, cookie consent and the trader's details in plain view. The legal wording itself should be checked by a lawyer, but we make sure each item appears where the law requires and that customers accept it at the right point in checkout.

If you have an existing store, we migrate the products, customers and order history, and redirect old product URLs to the new ones so you keep your search rankings.

After launch

A store needs more care than an ordinary website. The platform and plugins update often, payment providers and couriers change their APIs, and the holiday season puts the server under load. Support covers updates, backups, monitoring of payments and orders, speed checks and fixes. When the store is your main sales channel, support runs 24/7. We also train your team on adding products, handling orders, running promotions and reading the reports.