Security
New releases fix bugs and vulnerabilities. The longer a store stays on an old version, the harder it becomes to manage security risks.
CS-Cart update without losing data or control over customizations
We update CS-Cart and Multi-Vendor on a test copy, check how the store works after moving to the new version, and identify add-ons or customizations that need separate adaptation.
Why update
An old version gradually becomes a technical risk
Compatibility
An update helps prepare the project for current PHP and library versions, payment providers, delivery services, and external APIs.
Performance
A newer release uses the latest platform improvements and can significantly improve system performance.
Process
Test copy first, live store second
First, we assess the project, create a copy, and test the update in a controlled environment.
Initial assessment
We review the current CS-Cart version, server environment, theme, add-ons, integrations, and non-standard code changes.
Test copy and backup
We back up the files and database. The update is tested on a store copy so live sales are not disrupted.
Update and verification
After moving to the target version, we check the catalog, cart, checkout, customer account, admin panel, payments, shipping, and integrations.
Deployment and follow-up
Once approved, the result moves to the live store. We document any issues found and separate adaptation tasks.
Important condition
Third-party add-ons are checked, but adapted separately
All add-ons, including third-party ones, are checked after the update. If a add-on is incompatible with the new CS-Cart version, its adaptation is estimated and billed separately.
- Post-update errors and the conditions needed to reproduce them are documented.
- Core, theme, integration, and add-on issues are identified separately.
- Customization tasks are listed in priority order.
Price from $175
An exact estimate follows the initial project assessment.
What affects the price
- The number of versions the upgrade must pass through.
- The set of add-ons, the theme, and non-standard customizations.
- Core modifications and conflicts with the new CS-Cart version.
- The scope of integration checks: payments, shipping, CRM, 1C, feeds, and APIs.
- Whether third-party add-ons or custom functionality need adaptation.
FAQ
Frequently asked questions
The key points to understand before updating CS-Cart or Multi-Vendor.
Can the live store be updated directly?
Technically yes, but it is a poor choice for a store with orders and integrations. Testing on a copy first reveals conflicts before they can interrupt sales.
What does a CS-Cart update include?
The update covers moving to the latest system version, checking add-on compatibility, preserving data and customizations, and testing the store afterward.
What happens to third-party add-ons?
All add-ons are checked after the update. If a third-party add-on is incompatible, adaptation is a separate task or is handed to that add-on’s developer.
How long does an update take?
It depends on the gap between versions, the number of add-ons, and the amount of custom work. A small project may move faster; a store with a custom theme and integrations needs an individual estimate.
Why update CS-Cart?
Updates matter for security, stability, and compatibility with new add-ons and payment systems.
Need to update your store smoothly?
Send the current and target versions, a add-on list, and a brief description of your customizations. We will review the project and suggest the safest update path.
Result guarantee
Fixed price before work starts
A contract for every project