New store development
Catalog structure, implementation of your design and frontend, theme development, product pages, cart, customer accounts and administration. Launch preparation and continued development.
OpenCart and ocStore
OpenCart development and custom features
I build OpenCart and ocStore stores from the ground up and extend existing ones. My work covers catalog structure, bespoke themes, checkout, integrations and the technical demands of a live store.
What I can help with
Complex catalogs
Variants, bundles, compatibility and product relationships, warehouse stock, pricing and availability rules. Custom OCFilter behaviour, search and navigation for technical or extensive catalogs.
Orders, payments and shipping
Checkout tailored to your operation, extra order fields, statuses, shipping calculations and payment flows. Notification, cancellation and refund handling within the provider’s capabilities.
ERP and CRM integrations
Bidirectional product, price, stock, customer and order exchange with systems such as 1C and MoySklad. Custom APIs, connector enhancements and data consistency across platforms.
Extensions and migration
Custom modules and resolution of OCMOD or third-party extension conflicts. Catalog and order migration with mappings for legacy identifiers, images and page URLs.
Performance and maintenance
Investigation of expensive queries, filters, cache behaviour, PHP failures and database issues. Controlled changes to live stores, staged upgrades and moves to new hosting environments.
Relevant experience
Complete store builds
Industriehof was built from scratch on OpenCart and connected to 1C through a custom API. A surveying equipment store required a bespoke theme, product relationships and grouping, and a redesigned option system.
Continued development of live stores
Work on Suborbia covered MoySklad synchronisation, variant and bundle stock, cart recovery and checkout. Later work added recovery of CloudPayments orders after database failures and corrected paid-payment synchronisation with RetailCRM.
Catalogs and operations
Planar involved EKDB/CSV import, data mapping and OCFilter improvements. Bezelstore required stabilisation of filter traffic and file caching.
Selected work in this area
Industriehof: custom API and 1C integrations
Bidirectional exchange of categories, products, prices, warehouses, customers and orders with GUID-based mapping.
View project details
Suborbia: MoySklad, inventory and cart recovery
Catalog and orders, variant-level inventory, bundles, OCFilter, recoverable carts and production caching.
View project details
Planar: technical catalog import and OCFilter
EKDB and CSV imports, preservation of legacy mappings, active-category filtering and targeted 301 redirects.
View project detailsHow the work is delivered
Assessment and scope
We define the process, source data and expected result. For an existing project, I review the affected code. We then agree scope, cost and milestones.
Development and verification
I implement the agreed workflows and check the result and its dependencies. Changes to live systems account for data integrity and neighbouring functionality.
Release and continued support
I prepare the deployment and rollback procedure and verify the result after release. I hand over the changes and we agree further support where needed.
What you receive
- A working store or the agreed functionality within your existing project.
- Verified catalog, cart, order and integration workflows affected by the work.
- Source code, implementation notes and a release procedure with a rollback path.
Before we start
Can you build the whole store?
Yes. The scope can include requirements, structure, implementation of the design, catalog, purchasing, external services and launch. If the design is not ready, we agree its scope and delivery format before development starts.
Do you work with inherited code and older versions?
Yes. I first review the theme, extensions, modifications and data. Then I identify changes that can be made locally and areas that need a staged upgrade. A complete rebuild is not a prerequisite.
How do you make changes to a live store?
We agree the affected workflows, backup, test environment and release sequence. I verify the change and related processes before deployment. Any cutover that requires downtime is planned separately.
Can a migration preserve data and existing URLs?
Yes. Products, categories, customers, orders, images, mappings and redirects can all be included in the migration plan. The exact scope depends on the source database and available exports.
Let’s discuss a new store or the next stage of your existing one.
Tell me about your project
No passwords or access credentials are needed for an initial assessment. Send a project link, briefly describe the current and expected behavior, and include a timeframe or budget if already defined.