Inventory Management on cPanel: A Practical Setup Guide

You can run real inventory management on cPanel, and for a lot of small warehouses and online sellers it's the cheapest path to a working system. Shared hosting has hard limits (PHP timeouts, memory caps, a shared MySQL server, coarse cron intervals), and inventory software tends to be write-heavy at exactly the moments those limits bite. Below: the setup steps, a sizing example, and the point where you should move to a VPS.
Why cPanel is a reasonable place to start
Most self-hosted inventory apps are a PHP plus MySQL stack, which is precisely what cPanel is built for. You get a few things for free that would otherwise cost you a weekend:
- Hosting you probably already pay for.
- One-click database creation, phpMyAdmin, and a File Manager.
- AutoSSL for free HTTPS certificates.
- Managed backups and PHP version switching through MultiPHP Manager.
The trade-offs are just as real. Shared plans throttle CPU and memory, cap the number of concurrent "entry processes" (often around 20), enforce a max_execution_time, and give you no long-running background daemons. None of that is fatal. You just have to design around it.
What you actually need
Confirm your plan meets these before you install anything. If your host hides these settings, open a ticket and ask.
| Requirement | Minimum | Notes |
|---|---|---|
| PHP | 8.4.1 or newer (8.4 and 8.5) | With pdo_mysql, mbstring, bcmath, gd or Imagick, zip, fileinfo, curl, xml, openssl, tokenizer, ctype and sodium |
| Database | MySQL 8.0+ | One DB and one user is enough. PostgreSQL 13+ also works if your host offers it |
| Disk | 512 MB free | For the application files |
| Cron jobs | 1-minute interval | Runs the scheduler, which also works through the queue |
| SSH / Terminal | Recommended | For migrations and the storage link |
If your host offers a "Terminal" in cPanel, that counts as SSH access. Composer is not needed: the cPanel release zip ships its dependencies and pre-built frontend assets. Without a terminal you would have to run the migrations and storage link some other way, so ask your host for Terminal access.
How to set up inventory management on cPanel
- Set the PHP version. In MultiPHP Manager, pick PHP 8.4 (8.4.1 or newer) for your domain, then confirm the required extensions are enabled in the PHP selector.
- Download the cPanel release. Get
inventoros-cpanel-X.X.X.zipfrom the GitHub releases page. It has two folders:inventoros/(the application) andpublic_html/(the web-accessible files), plusINSTALL.md. - Create the database. Use MySQL Databases to make a database and a user, grant all privileges, and write down the exact names. cPanel prefixes them with your account name.
- Upload the files. Upload the
inventorosfolder to your home directory (/home/username/inventoros/) and the contents ofpublic_htmlto your web root. The application stays above the web root, so your.envis never exposed. For a subdomain or addon domain, upload the public files to that domain's folder and adjust the path inindex.php. - Set permissions. Make
storageandbootstrap/cachewritable (775). - Configure the environment. Copy
.env.exampleto.env, set your database credentials andAPP_URL, and runphp artisan key:generate. You can run the web installer at/installinstead of editing the database lines by hand. - Migrate and cache. From Terminal, run
php artisan migrate, create the storage symlink by hand (the standardstorage:linkdoes not work with the split layout), then run the config, route and view cache commands. - Wire up cron. Add a cron entry that runs
php artisan schedule:runevery minute. - Turn on AutoSSL. Issue a certificate for the domain and keep
SESSION_SECURE_COOKIE=true.
How background jobs run
Shared hosting has no supervisor and no persistent worker process, so you cannot leave a queue:work daemon running. Inventoros does not need one there. The single one-minute cron entry runs the scheduler, which decides what is due and also works through the database queue. Keep QUEUE_CONNECTION=database in .env. Stock adjustments, low-stock alerts, and webhook deliveries then flush within roughly a minute. That latency is fine for a small operation and unacceptable for a high-volume storefront, which is one of the clearest signs you have outgrown cPanel.
A worked example: will your plan handle it?
The number people worry about is database size. It's almost never the real constraint. Here's a quick way to size it.
Stock movements per year = orders/day x average lines per order x 365, plus receiving and adjustments (add roughly 30%).
Say you ship 150 orders a day at 3 lines each:
- 150 x 3 x 365 = 164,250 movement rows/year
- Add ~30% for receipts and manual adjustments = ~213,000 rows/year
At a few hundred bytes per row plus indexes, that's roughly 60 to 120 MB of movement data per year. A typical 5 GB shared plan holds years of history before disk becomes an issue, and MySQL handles millions of rows without breaking a sweat. What fills disk first is product images, not transactions.
The real ceiling is concurrency. If three warehouse staff are scanning while a storefront syncs over the API, you're comfortably inside a 20-process cap. Put 20 pickers hammering the API simultaneously during a sale and you'll start seeing throttling. Size for peak concurrent writes, not total records.
cPanel vs VPS vs Docker
| cPanel (shared) | VPS | Docker | |
|---|---|---|---|
| Cost/month | $5-15 | $6-40 | Host-dependent |
| Setup effort | Low | Medium | Medium |
| Concurrency | Limited (~20) | Good | Good |
| Background jobs | Cron only | Real workers | Real workers |
| Redis / search | Rare | Yes | Yes |
| Best for | Starting out, low volume | Growing ops | Reproducible deploys |
Where cPanel stops being enough
Move up when you see any of these:
- Queue backlog builds because a one-minute cron can't keep pace with orders.
- Large exports or reports throw 500s from the host's memory limit.
- API partners need webhooks delivered in seconds, not up to a minute.
- You need Redis, full-text search, or a genuine queue daemon.
- Multi-location, near-real-time stock sync at volume.
None of these mean cPanel was a mistake. The business grew.
Where Inventoros fits
Inventoros installs on cPanel, a VPS, or Docker from the same codebase. It is free, open source under AGPL-3.0, and fully self-hosted. You get multi-location stock, a REST and GraphQL API, webhooks, and an MCP server. The cPanel release is a zip with prebuilt assets, so no Composer is needed. Moving from cPanel to a VPS or Docker later means exporting the database and files and moving your .env; the Docker image uses PostgreSQL by default while cPanel installs usually run MySQL, so the database has to be dumped and imported, not just repointed. The full install steps for each environment are in the documentation.
FAQ
Can I run inventory management on cPanel with a shared hosting plan? Yes, for small to mid-size operations. As long as you have PHP 8.4.1 or newer, MySQL 8, and cron, a shared plan runs a full inventory system fine. The limits you'll meet first are concurrent processes and background-job latency, not database size.
Do I need SSH access?
It's recommended. SSH (or the cPanel Terminal) lets you run database migrations and php artisan commands. The install uses a release zip, so Composer is not needed, and the admin panel has an in-app update manager for cPanel installs. Without a terminal you lose easy command-line troubleshooting.
How do background jobs and queues work without a daemon? Through cron. Shared hosting won't keep a worker process alive, so you schedule a one-minute cron job that runs the scheduler, which also works through the queue. Alerts, syncs, and webhook deliveries then flush within about a minute. If you need sub-second delivery, that's your cue to move to a VPS with a real worker.
Will it handle barcode scanning and multiple users? Yes, up to a point. A handful of staff scanning over HTTPS sits comfortably within shared-hosting limits. Once you have many concurrent users or heavy API traffic during peaks, the entry-process cap becomes the bottleneck and a VPS is the right next step.