OpenCart
OpenCart, built and kept running properly
Development, migration, support and hosting for OpenCart 3 shops. One practice accountable for the whole stack, from theme to server.
Questions? Write to us vlad@uask.pro
What we do
Everything a shop needs, in one practice
New shops and themes
New stores on OpenCart 3.0.x with Evolution, our own theme (PHP 7.4–8.5), or on a theme you already own. The theme’s own settings first, custom code only where there is no setting.
Migration
Moving a shop to another server, version or fork: OpenCart, ocStore, LiveStore. Data, URLs and redirects are checked before the switch, so customers and search engines find the same shop.
Upgrades and PHP
First an honest answer on whether a shop can be upgraded. Then a current PHP: extension compatibility, MyISAM to InnoDB, caches. A backup and a way back for every step.
Integrations
eBay listings and orders through the Webkul eBay Connector, exchange with 1C, price feeds and marketplace exports. Delivery rates that match what you quote elsewhere.
Multilingual catalogues
Translation of products, categories and pages with a glossary, automatic checks, a report per group and a rollback. Correct hreflang, so every language ranks on its own.
Support and hosting
Updates, security fixes, monitoring and a quick response when something breaks. Managed hosting on our own CloudLinux servers. A backup before every change.
How a shop job runs
Evidence before theatre, step by step
Audit
Read-only. Versions, PHP, database engine, extensions, code compatibility. You get what we found, in writing.
Plan
What we do, what we do not, and how you will accept it. Scope and acceptance criteria before any work starts.
Backup and staging
Nothing touches the live shop without a restorable backup. Risky steps are rehearsed on a copy first.
Release
Acceptance checklist against the live shop, clean error logs, a rollback ready. Then the job is closed with a record of what changed.
The audit
What we look at before we quote
Most surprises in an OpenCart job live in the same few places: the PHP version, the database engine, old modifications and the cache. We look at them first, without changing anything, so the estimate rests on facts about your shop.
Send the address of the shop and, if you know them, the OpenCart and PHP versions. That is enough to start.
audit.read-only
- OpenCart or fork version, PHP version
- database engine and charset (MyISAM, utf8mb4)
- extensions and modifications (ocmod, vqmod)
- code compatibility with the target PHP
- cache, cron, PHP error log
- hreflang, canonical, sitemap, redirects
One email. A real reply.