Online store on OpenCart

Will pull out. The largest catalog we measured was 115,456 product items. Another measured store holds 54,302 products and 635 categories and gives the first server response in 413.8ms. Another thing is how to fill this volume. It won't work because of the admin, it will crash after a timeout: you need a console import in batches, revised MySQL indexes and a cache of categories. This is already a separate volume of work and a separate page.

We do not keep a public price - it would almost always be false in stores. The amount is driven by three things: the volume of the catalog, the number of integrations, and the state of the content you give away. A catalog of up to a thousand items with a ready-made theme, payment and Nova Poshta and a catalog of several thousand items with its own design, feed to the marketplace and exchange with the accounting system are different works, and it is impossible to call them one number. Reset the price download and the list of integrations: after a free audit, you will receive an estimate with a breakdown by stages.

25–45 working days from the approval of the TK. These are seven stages: brief and TOR 3-5 days, prototype 3-5, design 5-9, build 7-11, catalog import 3-7, integrations 2-4, testing and transfer 2-4. The accelerated queue with an additional payment of 25% shortens the deadline by about a third, but only if the content is ready at the start, and approvals are invested in one working day.

By default, we set 4.x: this is the branch that is being developed, and it is on it that the store will live in the coming years. We mention the nuance in the brief, and not at the stage of integrations: the four rewrote the event system, and some of the Ukrainian modules — individual Nova Poshta assemblies, price aggregators, uploading to sites — still only work under 3.x. 13 of the 24 stores we measured have the kernel fixed as 3.x because of this. Therefore, before starting, we go through your list of integrations item by item: everything we need has an assembly under 4.x — we install 4.x; some critical module exists only for three - we tell about it right away and decide together whether to install 3.x or change the module to an analog one. The version is fixed in the TOR before the start of work.

Yes, via CSV or XML import. We map your fields to OpenCart fields: item, price, balance, category, attributes. The update is then scheduled — daily or hourly, depending on how fast the balances are moving. This is a one-way import, it is included in the work. Two-way exchange with 1C or BAS is a separate job, about ten working days.

Yes. The catalog is uploaded to an XML feed that the site reads, prices and availability are pulled from the same source as on the site. It works in both garden equipment stores from our sample, and in one of them Rozetka Delivery is also connected as a delivery method. Feed - about three working days.

Depends on page weight, not platform. On the same OpenCart, we measured 103.2 KB of HTML in a medical store and 751.2 KB in a wholesale lingerie catalog: the difference is huge, and it lies in the theme and the number of connected modules. Therefore, at the start, we turn off everything that does not work for sale, and measure TTFB before starting, and not after complaints.

Your manager is through admin or automatic import from the price list. OpenCart admin is arranged simply: product, category, attribute, order. On the transfer, we go through it on a live order, from adding the product to printing the TTN. If your person is not there, we provide filling and support as a separate service.

No one guarantees a position, and we will not. We close the technical part: CNC without index.php, canonical, unique title, site map without duplicates, JSON-LD. The hole is most often right here. For the cosmetics store, we found 271 sitemap entries for 116 unique addresses, for the spice store, we found 3,971 entries for 590 addresses, and all 590 led to only one of the two language versions.

Advance payment of 50% at the start, the rest — after acceptance before the start. Two rounds of edits at the design stage are included in the cost if the edits are within the approved TOR. Thirty calendar days after acceptance, we correct errors free of charge on our part (warranty period according to the contract) - this does not cover new additions and consequences of independent changes in the code by third parties.