Maintenance Center is the operational toolkit for keeping Stockra stable over time. It provides controlled deployments (updates via ZIP package), system and database backups, restore/import of backups, cache management, and a clear snapshot of the current environment and health.
Where you find it
Administration → System → Maintenance Center
What you see on this page
System snapshot (left panel)
Current version: installed application version.
PHP version: current runtime version on the server.
Laravel version: core framework version used by the app.
System health: overall health indicator (green = OK).
Upload deployment package (left panel)
Drag & drop deployment ZIP: upload a deployment/update package (ZIP), with a maximum size (example shown: max 200 MB).
Deployment button: starts the deployment process (enabled when a package is selected/validated).
Deployment timeline: opens the deployment history/timeline for auditing and review.
Backups (main area)
System backups
Backup system files: creates a backup of application/system files.
Recent backups: shows the latest created backups (empty state if none exist yet).
Database backups
Backup database: creates a database dump/backup for recovery.
Recent backups: shows database backup history.
Managing deployments (main area)
Deployment list/card includes:
Deployment identifier
Date/time of deployment
Version tag (e.g., 1.0.0)
Files count and uncompressed size
“Current” label for the active deployment
This area supports safe tracking and (where available) rollback to a previous deployment.
Top actions
Clear caches: clears application caches to apply configuration changes and resolve stale UI/data issues.
Import backup: import/restore from a backup package (dropdown implies multiple import options).
Typical workflows
A) Deploy an update (ZIP)
Create a system backup and database backup first (recommended).
Drag & drop the deployment ZIP into Upload deployment package.
Click Deployment to apply the update.
Use Clear caches after deployment if the UI or data appears stale.
Verify version and system health in System snapshot.
B) Take backups before risky changes
Click Backup system files to snapshot the application files.
Click Backup database to snapshot operational data.
Confirm backups appear under Recent backups.
C) Restore from a backup
Click Import backup.
Select the backup file/package.
Follow prompts to restore system files and/or database (based on what was imported).
Clear caches and verify system health.
Notes & best practices
Always back up before deployments, large imports, or configuration changes.
Prefer testing updates in a staging environment first for production systems.
Use Clear caches after changing configuration (languages, branding, performance settings) or after updates.
Keep deployment ZIP packages from trusted sources only.
System Performance (Caching, Queue, Limits)
System Performance controls background processing behavior, caching intervals, and safety limits designed to keep Stockra responsive under heavy workloads. This is especially important for large imports/exports, frequent scanning, and high-volume movement documents.
Where you find it
Administration → System → System performance (or System settings → performance, depending on your navigation)
What you see on this page
Caching
Dashboard cache (seconds): controls how frequently dashboard data is refreshed (example: 60 seconds).
Application timezone: sets the system timezone for timestamps across the app (example: UTC).
Queue & reliability
Queue connection: defines how background jobs run (example: Sync (no queue worker)).
DB transaction retries: number of retries for database operations in case of transient failures (example: 3).
Warning (shown): Sync queue may block requests
Meaning: when running “sync”, exports/imports run during web requests. Large jobs may slow down the app or time out. Using an asynchronous queue driver with a worker is recommended where possible.
Search & scanning limits
Item search rate (/min): throttles item search requests per minute (example: 60).
Barcode lookup rate (/min): throttles barcode lookup requests per minute (example: 120).
Inbound/Outbound limits
Max movement lines: limits the maximum number of line items in a single movement document (example: 200) to protect performance.
PDF max rows: limits the maximum number of rows rendered in PDF exports (example: 1000) to avoid memory/timeouts.
Action
Save settings: applies changes system-wide.
Typical workflows
A) Improve performance for large exports/imports
Change Queue connection from Sync to an async queue driver (when supported in your environment).
Keep DB transaction retries at a conservative value (e.g., 3).
Save settings.
Test export generation and confirm it completes without slowing normal usage.
B) Tune dashboard responsiveness
Increase Dashboard cache (seconds) to reduce server load (e.g., from 60 to 120) if many users are active.
Decrease it for more real-time dashboards if your server can handle it.
Save settings.
C) Protect the system from heavy documents
Keep Max movement lines and PDF max rows within safe limits.
Increase only if you have adequate server resources and tested results.
Save settings.
Notes & best practices
On shared hosting, Sync mode may be acceptable for small data volumes; for larger operations, use a queue worker if your hosting supports it.
If users scan frequently (POS/warehouse), keep barcode lookup limits high enough to avoid throttling normal operations.
Timezone should match your business location to keep printed documents and audits consistent.