when it doesn’t
When another platform fits better
If the store lives alongside a blog and landing pages, compare it with WooCommerce. If every client has their own price and a manager approves orders, look at Laravel.
All store formatsShoppers narrow the catalog with attribute filters, and wholesale buyers see their own prices once they log in. If you run an older OpenCart, we first check what is worth keeping.
// when it fits
You have hundreds or thousands of products with specifications, both retail and wholesale buyers, and ready-made modules cover payment, delivery and accounting.
when it doesn’t
If the store lives alongside a blog and landing pages, compare it with WooCommerce. If every client has their own price and a manager approves orders, look at Laravel.
All store formatsBefore design starts, we agree which attributes shoppers use to find your products and who on your team manages prices. The filters, product page and admin panel are built around those answers.
// The module list goes into the estimate before development starts.
01
from $2,499
When you sell on the Prom marketplace or on social media and need a store of your own.
02
quoted separately
For a store on OpenCart 1.5 or 2.x that you're afraid to update.
03
quoted separately
When the store works but lacks a filter, a module or a sync with your accounting system.
// The $2,499 base covers the catalog, product page, cart, checkout, admin panel, one payment provider and one delivery service. It assumes one language and photos and descriptions you already have. Version upgrades and extensions are quoted after a store audit.
Open the projects and compare how each one handles the catalog, product page and checkout.
// prepayment when work starts, then handover and payment in stages. Proportions are indicative: the exact schedule is in the spec.
01
We go through your range, customer groups and price sources, then decide what goes into the first version.
// deliverable a brief and an outline of the estimate
02
We load part of your products and agree on filters, product page, cart and checkout.
// deliverable prototypes and a tested import template
03
We design the layouts and build the store on a staging server with approved modules only.
// deliverable a store you can click through from catalog to cart
04
We connect payment, delivery and accounting, then place test orders as a retail buyer and as a wholesaler.
// deliverable orders that have passed through every status
05
We move the store to the live server, hand over access and show your team how to manage products.
// deliverable a store that takes orders
Usually not. Templates and the module format changed between versions, so moving an old store to a new version works the same way as moving it to a new platform. First we take stock of what the store is built from: theme, modules, modifications and edits to core files. That shows what will carry over and what has to be replaced. You can describe your starting point in the brief.
We keep the URLs that bring traffic or point them to the new pages with 301 redirects. Before the move we collect old category and product URLs, metadata and indexed pages, and after launch we spot-check the redirects. This work is part of the migration, while ongoing SEO is priced separately.
Yes, as long as attributes, filters and imports are designed for that volume and the hosting can handle the load. Before the estimate we take a sample of your products and agree how fast a filtered category should open and how fast the price list should update. Ballpark prices are on the pricing page.
Yes, if your accounting system or CRM has an API or can exchange files. OpenCart has ready-made sync modules for BAS, 1C and popular CRMs, and for anything else we build the integration from its documentation. To estimate it, we need a field description, test access and a sample export. You can add all of this to the brief.
Ready-made modules, if they exist for your OpenCart version and your provider. The base store gets one payment module and one delivery module, such as LiqPay and Nova Poshta. Your own shipping rates, several carriers or installment payments are priced separately. You can send us a list of the providers you already work with through the contacts page.
From $2,499 for a base store with a catalog, cart, payment and delivery. We give the exact price and launch date in the estimate once we've seen the catalog, modules, migration and integrations. Ballpark figures for other formats are in the price table. A turnkey store with custom design, catalog population and integrations starts at $4,500.
Yes. We meet online, you open the staging store in your browser, and you accept the work against an agreed list of scenarios. Our offices are in Kharkiv and Kyiv, and we build OpenCart stores for businesses all over Ukraine.
The base includes the catalog, product page, cart, checkout, admin panel, and one payment module and one delivery module. Product upload, migration from an old version, ERP or CRM sync, a second provider and custom modules are priced separately. If you also need a blog and landing pages next to the catalog, take a look at WooCommerce as well.
Out of the box, OpenCart focuses on the catalog and a sales-oriented admin, while WooCommerce adds a store to a WordPress site with a blog and pages. For a large catalog we compare product variants, filters, imports and whether the modules you need are still updated. The number of products alone doesn't decide it. Describe your catalog in the brief and we'll recommend a platform.
Leave your name and phone number or Telegram username. We'll get in touch during business hours, ask about your catalog, current store and accounting, and after the call tell you what will go into the estimate.
By pressing the button, you agree to the privacy policy
Kharkiv · Kyiv
// In depth
OpenCart ecommerce development starts with a spreadsheet of your products. Out of the box the platform has categories, attributes, manufacturers, options and customer groups, but how your range fits into them is something we decide together. If values are entered carelessly, the filter shows "Black" and "black" as two separate options, and the shopper messages a manager instead of buying. That's why we agree on the catalog structure using a real sample of products before we draw any layouts.
We consider a turnkey OpenCart website done when a test order has gone all the way from the cart to payment and a shipping label from the delivery service. The $2,499 base covers the catalog, product page, cart, checkout, admin panel, one payment provider and one delivery service, such as LiqPay and Nova Poshta. The price assumes one language and photos and descriptions you already have. A turnkey store with custom design, catalog population and integrations starts at $4,500.
Product upload, accounting sync, a second language, upgrading an old version and migration are priced separately. You can compare formats on the pricing page.
A filter helps when it shows only the values that products in the category actually have. We take them from a single reference list, so each size or color appears in the filter once. The test import contains a simple product, a product with options and a product listed in several categories. We use it to check the filter, page URLs and that a repeat import doesn't create duplicates.
Sometimes a product is sitting in the warehouse and the site search still can't find it. Often the cause is in the product data.
OpenCart splits buyers into customer groups. A retail shopper sees regular prices, while a wholesale buyer who logs in sees their group's prices and quantity discounts. A manager approves new wholesale buyers by hand. The platform does all of this itself, so you don't need a second site for wholesale.
It's a different story when every client has their own negotiated price list, credit limit and payment terms, and a manager signs off on large orders. Customer groups can't express that, and it's fairer to look at a Laravel store, where these rules are written around your process.
Templates and the format of modules and modifications changed between versions 1.5, 2.x, 3.x and 4.x, so an old store rarely updates with one click. First we make a list: theme, modules, OCMOD and vQmod modifications, edits made directly in core files. Those edits often carry an important rule, such as a discount for regular customers or a special delivery option, and they don't show up in the module list.
After that review you can see what moves over as is, what needs replacing and what can be left behind. The new version can be built alongside the old one, so the store keeps selling while we move the data.
We collect the old category and product URLs in advance and decide where each one should lead. Pages that bring traffic get a 301 redirect to their new address, so a shopper coming from search doesn't hit a 404 error. Old filter URLs aren't carried over mechanically if the new catalog structure is different.
Customers, orders and loyalty points are migrated separately, because passwords and history don't move the way products do. Before switching the domain, we check the priority URLs by hand. For promotion after launch, see SEO for online stores.
OpenCart has ready-made modules for LiqPay and Nova Poshta, for exports to the Prom and Rozetka marketplaces and for sync with BAS or 1C. Before the estimate we check whether a module supports your version, who wrote it and whether it still gets updates. Two modules that both change checkout can conflict, so each job gets one module. If a closed-source module carries your sales, we flag it in the estimate along with its developer's name.
We estimate the accounting sync once we've seen the documentation and have test access. We agree where prices come from, how often stock updates and what happens when a sync fails. Large price-list updates are split into batches and run when they won't get in shoppers' way.
We hand the store over with access details and a list of versions, licenses and custom changes. Core and module updates are tested first on a copy of the store, payment and delivery included. That work falls under support, which is ordered separately.
If you're still choosing a platform, the online stores page lists every format, from ready-made platforms to development from scratch.
Leave your contact details in the form above, or fill in the brief if you'd rather answer in writing. After the call we'll tell you whether OpenCart suits you and prepare an estimate with a list of open questions.