Choose OpenCart hosting around the work your store actually performs: serving catalogue pages, processing checkout, importing products and running background jobs. A label saying “OpenCart supported” does not describe how a plan handles your extensions or peak workload. Two stores with similar traffic can behave differently when one synchronises several sales channels.
Build a store inventory first
Record the exact OpenCart or ocStore version, theme, critical extensions and PHP version. Add product and image counts, languages, import size and synchronisation frequency. Timing matters too: ten jobs starting together produce a different peak from the same jobs distributed across an hour.
Check every extension’s requirements. Encoded modules may need a compatible ionCube Loader. A PHP version appearing in the hosting control panel does not prove that every installed extension supports it. Keep a compatibility list before changing the runtime or moving providers.
Ask about limits beyond disk space
- CPU allowance, memory, concurrent PHP workers and storage throughput limits.
- Web request deadlines and separate CLI or scheduled-task limits.
- Access to PHP logs, resource history and slow-query diagnostics.
- MySQL or MariaDB version, connection limits and database capacity.
- File-count limits, backup retention and the actual restoration procedure.
There is no single memory allowance suitable for every OpenCart installation. Request a trial and measure your own catalogue. More disk space will not fix a process that repeatedly hits its CPU or execution-time limit.
Check web PHP and cron separately
The website and task scheduler may use different PHP executables and configuration files. Verify the version, extensions and limits in both environments. Use the cron entry point documented by the installed extension; an arbitrary admin route is not automatically a supported background command.
Agree on the server timezone, schedule and where execution results are recorded. Import jobs should track progress and prevent overlapping runs. Keep secret cron tokens out of screenshots, public issue reports and example URLs.
Run a small acceptance test before moving
- Prepare an access-controlled staging copy. Disable live payments, outgoing customer emails and external order submission.
- Measure a category, product, search and admin page several times, including a warmed-up request.
- Run an agreed small import and record duration, resource use and any errors.
- Restore a backup in an isolated environment to verify that recovery works.
Measure a representative workflow rather than the empty homepage alone. An import that finishes successfully can still overlap the next scheduled run, so compare its duration with the proposed interval. Also confirm who investigates resource restrictions when a problem occurs.
Browse ShopX OpenCart extensions with this checklist in mind and compare each product’s requirements with your hosting environment. Keep your current service available until the new store, scheduled jobs and recovery process pass acceptance checks.
Technical reference: PHP command-line documentation.
