Working with OCStudio: FAQ

Allow approximately 14–21 working days for Start and 30–45 working days for Business. Complex projects receive a custom schedule. Timing starts once the brief is agreed and materials are received.

Yes. Agree wireframes, designs and mobile workflows, with design and frontend work included in the agreed estimate.

Yes. The OpenCart admin lets you update products, prices and content within configured features. Package training covers these tasks; code and complex integration changes require a developer.

Start begins at UAH 23,500, Business at UAH 43,900 and Premium at UAH 120,000. The final quote follows a requirements review; automation and custom workflows are priced by scope.

The package comparison lists catalogue, mobile layout and store features. Specific integrations, licences, content entry and extras are recorded in the estimate before work begins.

These are itemised separately so you can see both implementation costs and recurring expenses. Check licences and subscriptions before approving the solution.

Yes. Review exports, structure and integrations, then run a trial migration. URL mapping, 301 redirects, metadata and indexing checks reduce organic traffic risk; unchanged rankings cannot be guaranteed.

Categories, products, images, attributes and metadata depend on available exports. Customers, orders, passwords and extension data require separate checks; confirm scope after testing.

Unchanged rankings cannot be guaranteed. URL mapping, individual 301 redirects, metadata migration and indexing checks reduce risk.

It depends on data volume, export quality, integrations and design changes. After a trial migration, agree the estimate, final synchronisation and launch window.

Yes. Agree data ownership, directions and update frequency for products, stock and orders. Implementation depends on system versions, APIs and available extensions.

Agree participating warehouses, stock aggregation and reservation deductions. Test examples: physical stock is not always the quantity available to sell.

No. Check the OpenCart version, 1C configuration and a real exchange file. An extension may cover basic exchange without supporting your variants, price types or customisations.

Link external IDs and check previous delivery before retrying. Test lost responses and repeated events; implementation depends on the CRM API.

Yes, provide examples and mapping rules for methods, statuses and additional fields. An OpenCart field does not automatically have an identical KeyCRM representation.

Yes. For OpenCart stores, you can integrate a dedicated search engine for much faster, relevant catalog exploration with live autocomplete, typo tolerance, and zero MySQL strain. Learn more about smart search integration →

Yes, following an initial code and access review. Define scope, dependencies and risks, then agree working terms before changing the site.

Yes. Define the change and test the related payment, delivery and order creation flows. Estimate the specific feature without requiring a full redesign.

Yes. Arrange ongoing maintenance after any support included in the development package. Hours, schedules, priorities and SLA are agreed separately.

Updates are scoped separately. Check theme, extension and PHP compatibility on a copy before changing versions. A major version upgrade may require a separate project.

No. Monitoring detects an event; the agreement defines working hours, priority and response time. Response means starting work on the request. Resolution time depends on the cause and complexity.

Agree backup contents, frequency, location and retention. Verification includes test restores on an agreed schedule. Having an archive alone does not establish that the store can be recovered.

No. Agree deliverables and measurement: technical fixes, structure, metadata and indexing checks. Rankings, traffic and sales also depend on competition, demand and other factors.

Compare the same pages before and after under consistent test conditions. Check mobile workflows, images, server response and third-party scripts. A single PageSpeed score does not describe the entire customer experience.

The platform, theme, extensions or hosting may change. Measure the production domain after launch against the baseline. Moving to OpenCart alone does not guarantee faster loading.

First check the live page, canonical, crawl access and sitemap. Then inspect the URL in Search Console and request recrawling where appropriate. Updating server files does not instantly update the search copy.

The agreement records the transfer of access and rights to the client. Third-party extensions, fonts and other licences retain separately documented terms.

Record milestones, payments and deliverables before starting. When requirements or scope change, agree cost and schedule impact before performing the extra work.

Agreed access, implemented changes and instructions within scope. The contract defines ownership transfer; third-party licences retain their terms. Ongoing support is agreed separately.