Storefront Error Radar
Spot live storefront breakage before your revenue path stays broken too long.
A privacy-first OpenCart extension that captures anonymous storefront failures, keeps only a short-lived local incident buffer, and surfaces the result inside an owner-facing admin console without any external telemetry service.
Features
Built for operators who need actionable incident visibility without a heavyweight monitoring stack.
Live Incident Snapshot
See the current active incident window directly inside the module page, including counts for recent signals, resource failures, critical path failures, and burst alerts.
Revenue-Path Monitoring
Prioritize checkout and add-to-cart failures instead of treating every browser error as equally important operational noise.
Privacy-First Storage
No cookies, no IP storage, no checkout field capture, and no third-party telemetry pipeline. Payloads are sanitized before they are written locally.
No Extra Infrastructure
Runs entirely inside your existing OpenCart stack with no Redis requirement, no Node.js collector, and no separate incident database.
Preview Mode
Demonstrate the dashboard with synthetic incidents when you need screenshots, demos, or UI validation without waiting for real storefront failures.
OpenCart Native Admin UI
Built to sit naturally inside the OpenCart 4 admin experience using a Bootstrap-based module settings page instead of a separate application shell.
How it works
Five steps from storefront failure to admin-side incident visibility.
- 01
Storefront collector loads
A lightweight collector is injected on the storefront footer through the normal OpenCart application flow.
- 02
Anonymous failure is captured
JavaScript errors, promise rejections, resource failures, and critical request failures are normalized into a small payload.
- 03
Payload is sanitized
Sensitive values are stripped before storage so the incident window remains operationally useful without turning into a customer data archive.
- 04
Incident buffer is updated
Events are written to a short-lived JSON buffer inside DIR_STORAGE and summarized into operator-facing rollups.
- 05
Admin dashboard refreshes
The module page polls the snapshot endpoint and updates the current live window without leaving OpenCart admin.
Privacy by design
Storefront Error Radar is designed to help operators diagnose storefront reliability problems without building a permanent customer event archive.
- No IP addresses are intentionally stored.
- No cookies are intentionally stored by the extension.
- No customer-entered checkout values are intentionally stored.
- Incident retention is deliberately short-lived rather than historical.
- All captured storefront payloads are sanitized before storage.
- No third-party telemetry backend or external monitoring service is required.
Requirements
| OpenCart | 4.0 or higher |
| Tested on | 4.1.0.3 |
| PHP | 8.3 or higher |
| Storage | Writable DIR_STORAGE path |
| Database | No extra custom extension tables required |
| Infrastructure | No Redis or Node.js collector required |
Installation
- 01 Download the .ocmod.zip package for Storefront Error Radar.
- 02 In OpenCart admin, go to Extensions → Installer and upload the package.
- 03 Open Extensions → Extensions and choose the Modules type filter.
- 04 Install Storefront Error Radar.
- 05 Open the module settings page and enable monitoring.
- 06 Review the live snapshot, preview mode, retention, and sampling settings.
Frequently asked questions
Does this extension add anything visible to the storefront?
No. The storefront side is only a silent collector for anonymous incident signals. The operator console lives entirely in OpenCart admin.
Does it keep historical analytics forever?
No. The extension is intentionally built around a short-lived local incident buffer rather than a permanent observability archive.
What kinds of failures can it detect?
It captures JavaScript runtime failures, unhandled promise rejections, asset load failures, failed cart or API requests, slow critical-path requests, and derived burst alerts.
Do I need Redis, Node.js, or an external dashboard service?
No. Storefront Error Radar runs entirely inside a normal OpenCart deployment and stores its short-lived incident window locally.
What is preview mode for?
Preview mode injects synthetic incidents so you can demo the dashboard state, validate the UI, and prepare screenshots without waiting for real production issues.
Need a lighter way to watch storefront reliability?
Storefront Error Radar is built for OpenCart operators who want immediate signal, not another infrastructure project.
MIT · Developed by Devlin Duldulao