Skip to content
v1.0.0 OpenCart 4.x PHP 8.3+ MIT

Checkout Geo Flash

Owner-only OpenCart dashboard for recent checkout and paid-order activity.

A standalone OpenCart 4 extension that captures privacy-safe order events, keeps only short-lived recent activity, and renders the experience exclusively in the admin dashboard without extra services.

Features

Recent order visibility for operators without adding infrastructure sprawl.

📍

Live Activity Feed

Show recent checkout-created and paid-order moments in an owner dashboard that stays inside the normal OpenCart admin experience.

🧪

Preview Mode

Use the built-in fake-data preview to demo, validate, and capture screenshots without waiting for real customer orders.

🔒

Privacy-Safe Payloads

The browser-visible feed excludes names, emails, raw IPs, order totals, and order IDs while still giving operators useful visibility.

🗂️

Short Retention

Recent events are pruned aggressively so the module remains lightweight and avoids turning into a long-lived analytics archive.

🧩

OpenCart Native Admin UI

Built as an OpenCart module page for store owners, not as a separate app shell or storefront widget.

⚙️

No Extra Infrastructure

Runs entirely inside OpenCart using the existing database and native event hooks, with no Redis, Node.js, workers, or external service.

How it works

Five steps from OpenCart order event to owner dashboard activity.

  1. 01

    OpenCart event hook fires

    Native OpenCart order hooks capture checkout-created and paid-order moments at the application layer instead of relying on external collectors.

  2. 02

    The order is sanitized

    The catalog model keeps only the fields needed for owner visibility: event type, first product name, coarse location label, and timestamp.

  3. 03

    A recent event row is stored

    The extension writes short-lived activity rows into the store's existing OpenCart database and deduplicates repeated order-phase emissions.

  4. 04

    The admin feed is polled

    The owner dashboard requests only events newer than its last cursor so the UI stays responsive without heavy refresh logic.

  5. 05

    The dashboard renders owner insight

    OpenCart admin shows the recent activity cards or fake preview data while keeping the storefront free of public monitoring UI.

🛡️

Privacy model

Checkout Geo Flash is intentionally narrow in scope: recent owner activity only, with customer-sensitive data kept out of the browser payload.

  • No raw IP retention.
  • No shopper names or emails in owner feed payloads.
  • No order totals or order IDs exposed in the browser.
  • No public storefront rendering or shopper-facing widget.
  • Recent events are retained only for a short window.
  • No Redis, Node.js service, or external telemetry platform is required.

Requirements

OpenCart 4.x
PHP 8.3 or higher
Database Existing MySQL or MariaDB store database
Runtime Standalone OpenCart extension
Composer Local testing and linting only
External services None required

Installation

  1. 01 Build or download the .ocmod.zip package for Checkout Geo Flash.
  2. 02 In OpenCart admin, go to Extensions -> Installer and upload the package.
  3. 03 Open Extensions -> Extensions -> Modules and install Checkout Geo Flash.
  4. 04 Grant admin access and modify permissions for extension/module/checkout_geo_flash if needed.
  5. 05 Open the module page, enable it, and save the settings.
  6. 06 Use the dashboard feed or preview mode to validate the owner experience.

Frequently asked questions

Does this show anything on the storefront?
No. Checkout Geo Flash is designed for the business owner. The activity experience lives in OpenCart admin only.
What event types does it capture?
It captures checkout-created and paid-order events through OpenCart's native order hooks.
What data is stored?
The module stores only product name, coarse location, event type, and timestamp for recent owner visibility.
Do I need Redis, Node.js, or a worker queue?
No. The extension is intentionally standalone and runs inside a standard OpenCart deployment using the existing database.
Why include preview mode?
Preview mode makes demos, onboarding, QA, and screenshots possible before live orders arrive and without exposing real customer data.