Opencart User Manual Archives - Knowband Blog

OpenCart SEO Audit Manager User Manual

1. Introduction

Having an OpenCart website requires much more than just adding your products and completing orders. Search engines need to know what is on the web page, customers require faster-loading pages, and there are also broken links that have to be detected before they start bringing losses to you. An OpenCart SEO Audit Manager developed by Knowband provides all these functions from one dashboard instead of using different add-ons, Excel sheets, and manual checks. An OpenCart SEO Audit Extension indeed does all these things at once.

The fundamental principle behind the operation of the OpenCart SEO Audit Extension is to rate products, product categories, informational pages, manufacturers, and blogs that are compatible with OpenCart. Every single page will get its own quality rating, taking into account such aspects as meta tags, readability, keyword inclusion, linking, and more. For those store owners who do not know much about SEO, this is a good checklist.

Apart from scoring, the Extension includes functionalities such as OpenCart Google Analytics 4 Analysis, OpenCart Google Search Console, and OpenCart PageSpeed Insights for traffic analysis, search analysis, and page speed information to be found in one dashboard. In addition, it takes care of redirect management using the OpenCart URL Redirect Extension. This extension also identifies any 404 URL that might ruin users’ experience and detects duplicate SEO URLs.

This module acts as an OpenCart Technical SEO plugin, which allows you to edit your robots.txt file using OpenCart Robots.txt Editor and creates XML and HTML sitemaps using OpenCart Sitemap Generator. With the optional OpenCart AI Content Generator based on ChatGPT, it drafts such important elements as meta titles, meta descriptions, product descriptions, and social media tags.

This manual describes the functionality of the Knowband OpenCart SEO Audit Extension on the basis of its actual navigation, features, and performance. This document does not give any guarantees concerning the ranking of the page in search results, since no on-page service can control the search engine ranking of a page. It gives an explanation of each feature’s function, usage, and relevance. The manual is written for those OpenCart store owners who have the knowledge of OpenCart but do not know how to perform an OpenCart SEO audit.

2. Key Features of OpenCart SEO Audit Manager

OpenCart SEO Audit Manager, a complete OpenCart SEO audit extension for OpenCart stores, combines several distinct capabilities under one module. Together, they cover most of the recurring SEO maintenance tasks an OpenCart store needs:

SEO and readability scoring for products, categories, information pages, manufacturers, and supported blog content
Score history with trend charts, snapshots, and comparisons over time
Issues grouped by rule, so administrators can fix one problem across many pages at once
OpenCart Google Analytics 4 integration with sessions, users, eCommerce, and behavior reporting
OpenCart Google Search Console integration covering performance, sitemap submission, and URL indexing checks
PageSpeed Insights integration with mobile and desktop testing, plus historical trend tracking
An OpenCart Redirect Manager supporting OpenCart 301 Redirects plus 302 and 303 redirect types, including bulk CSV import
404 URL detection that records missing storefront requests for review
Duplicate URL checking, effectively an OpenCart SEO Checker for SEO keywords assigned to more than one page
XML and HTML sitemap generation through the module’s OpenCart Sitemap Generator, along with RSS feed support
robots.txt management via the built-in Robots.txt Editor, directly from the admin panel
An OpenCart AI Content Generator (ChatGPT-assisted) for meta titles, descriptions, product copy, and social metadata
Import/export for bulk SEO data backup, restore, and AI-assisted enhancement
Social Cards for Open Graph and X (Twitter) card metadata, plus structured data support

Each of these areas is documented in detail in the sections that follow, using the exact tab names and fields found in the OpenCart SEO Audit Module.

3. Installation of the Extension

Step 1: Download the module. Download the OpenCart SEO Audit Manager, an OpenCart SEO plugin developed and extract it on your local machine.

Step 2: Copy the files to your server. Upload the contents of the files’ upload (admin, system, catalogue) directory into your store, keeping the existing folder structure intact.

Step 3: Install or refresh the OCMOD modification. The module includes an OCMOD modification that adds the Knowband SEO group to the admin sidebar. In OpenCart, go to Extensions > Modifications and refresh the modification list so the OpenCart SEO Extension appears correctly. If the sidebar entry does not appear immediately, the extension also includes an event-based fallback that adds the menu automatically once the extension is installed.

Step 4: Install the extension. Open the OpenCart administration panel, go to Extensions, locate Knowband SEO, and install it.

Step 5: Confirm user permissions. Installation grants the installing user group access and modification permission for the module’s routes. If other administrator groups also need to use the module, add their access and modify permissions manually under System > Users > User Groups.

4. Admin Overview of OpenCart SEO Audit Extension

The OpenCart SEO Audit Extension organises its tools under a dedicated admin menu. The navigation includes Dashboard, Analytics (includes GA, GSC & PageSpeed Insight dashboards), Score History, URL Optimisation, Sitemap XML, and HTML. This extension also includes updating products in bulk using import/export settings. Also allow you to edit sitemap.xml, sitemap.html, and robots.txt.

4.1 Dashboard

The dashboard is the summary view of your store’s overall SEO condition. It is usually the first place to check when reviewing how your catalog is performing from a content and metadata POV.

You can view the current and previous overall SEO scores, review several breakdown charts, run a bulk analysis of pages that have not yet been scored, and jump straight into Score History.

Current website score / Previous score: The overall SEO score of the store as of its latest audit, presented in relation to the previous period’s score to track if there was an improvement or decline.
Trend of the overall SEO score: A graph showing the performance of your website over time that will help understand whether the improvements made had any lasting impact or just an initial positive response.
Index/Follow ratio: The ratio of pages marked for indexing and following versus those marked noindex and nofollow, will allow to detect the pages that were mistakenly blocked from search engines’ crawling.
Pages by scores distribution: A chart reflecting the number of pages with strong, moderate, and poor SEO scores.
Readability: a chart summarizing readability scores across analyzed content, separate from the SEO score.
Meta settings completed: a chart showing how many pages have complete metadata (title, description, and similar fields) versus how many are missing it.
SEO checklist: a list of store-wide technical items, including SEO URLs enabled, SSL enabled, XML sitemap enabled, robots.txt existence, maintenance mode status, webmaster verification, URL redirects, RSS, and blog detection where relevant. Each row shows whether the item is in place and may include an edit or external link to fix it directly.
Score History (header action): a shortcut that opens the Score History tab without using the main menu.
Analyze missing pages (header action): opens the bulk analysis tool described below, used to score pages that have not yet been analyzed.

4.2 Analytics

Analytics contains the tabs, including Analytic Dashboard, Settings, GA4 Analytics, Search Console, and PageSpeed.

4.2.1 Analytics Dashboard of the OpenCart SEO Audit Manager

This is a customizable widget dashboard that pulls together GA4, Search Console, and PageSpeed data in one place, so you do not need to open each integration separately for a quick check. These widgets are included from Google Analytics 4, Google Search Console and PageSpee

Period selector: The Store owner can set the reporting window for every widget on the page, with choices of Last 7 days, Last 28 days, Last 30 days, or Last 90 days.
Sessions: Select GA4 sessions recorded in the selected period.
Users: total Unique users recorded in the selected period.
Page views: Total page views recorded in the selected period.
Realtime users: The number of users currently active on the storefront, updated close to live.
Sessions trend / Users trend: Line charts showing how sessions and users changed day by day across the selected period.
Sessions by country: A breakdown of sessions by visitor country.
Sessions by device: A breakdown of sessions by device category, such as desktop, mobile, or tablet.
Top traffic sources: The channels or sources sending the most sessions to the store.
Clicks: total Search Console clicks in the selected period.
Impressions: total times your pages appeared in Google search results.
CTR: click-through rate, calculated as clicks divided by impressions.
Avg position: the average ranking position of your pages in Google search results for the period.
Clicks vs Impressions: a combined chart plotting clicks and impressions together so you can see how they move relative to each other.
Top search queries: the search terms generating the most clicks or impressions.
Top landing pages: the pages receiving the most traffic from search.
PageSpeed performance: a widget summarizing your most recent PageSpeed test scores.
Refresh: reloads the data for all currently displayed widgets.
Customize: opens the widget library so you can add, remove, or reorder widgets.
Save layout: stores your current widget selection and arrangement for this store.
Cancel: closes the customization view without saving changes.
Reset layout: restores the default widget selection and order.

4.2.2 Settings of GA4, GSC and PageSpeed

This includes holds every configuration value the Analytics area needs, organized into General, Credentials, Properties, Access, PageSpeed Cron, and Notifications sections.

General

Analytics Status: turns Analytics data collection and dashboards on or off for this store.
Default Period (days): the reporting window used by dashboard widgets when no other period has been chosen.
API Cache TTL (minutes): how long API responses are cached before the Extensionrequests fresh data from Google, which reduces API usage but delays how quickly new data appears.
Search Console Data Lag (days): the number of most recent days excluded from Search Console reporting, since Google typically finalizes that data a few days after it occurs.
History Retention (days): how long PageSpeed test history is kept before older records are removed.

Credentials

PageSpeed API Key: your Google PageSpeed Insights API key, required to run performance tests.
Google OAuth Client ID: the Client ID from the Web application OAuth client you created in Google Cloud.
Google OAuth Client Secret: the matching Client Secret; leaving this field blank when editing keeps the value already stored.
Connect with Google: starts the OAuth authorization flow using the Client ID and Secret above.
Disconnect Google: removes the stored Google connection for this store.
Refresh: reloads the list of available Google properties after a successful connection.

Properties

Search Console Property: the specific Search Console property this store’s data should be pulled from.
GA4 Property: the specific GA4 property ID this store’s data should be pulled from.
PageSpeed Test URL: the default URL used when running a PageSpeed test without specifying a custom one.
Custom Test URL: an optional alternate URL available when a custom PageSpeed target is selected instead of the default.

PageSpeed Cron

Enable Scheduled Checks: turns on automatic, recurring PageSpeed tests.
Pages To Test: which page targets are included in the scheduled checks.
Cron URL: the unique URL your server scheduler should call to trigger scheduled PageSpeed checks.
Last Run: the date and time the scheduled check last executed.
Regenerate: creates a new security token for the Cron URL; any existing scheduled job still using the old URL will stop working until it is updated.
Run now: triggers a scheduled check manually, without waiting for the next scheduled time.

Notifications

Enable Email Alerts: turns on email notifications for score or performance changes.
Alert Recipient: the email address that receives alerts.
Alert Threshold (points): the score-change amount that triggers an alert.
Also Notify On Recovery: sends an additional alert when a score that previously dropped recovers.
Notify When Core Web Vitals Fail: sends an alert specifically when Core Web Vitals metrics fail their thresholds.
Send test email: sends a sample alert to the configured recipient so you can confirm delivery is working.

Steps to Create Google Client ID & Secret ID

Enable the required APIs. Inside that project, turn on the Google Analytics Admin API, Google Search Console API, and PageSpeed Insights API.
Configure the OAuth consent screen. Google requires this before it will let your project request access to Analytics and Search Console data.
Create an OAuth 2.0 Client ID. Choose “Web application” as the type.
Add the redirect URI. Copy the exact redirect URI shown by the module and paste it into the OAuth Client’s settings.
Save the Client ID and Client Secret. Copy both values from Google Cloud and paste them into the matching fields here.
Click Connect with Google. This starts the authorization process using the credentials you just saved.
Click Refresh. This loads the list of Google properties available to your account.
Select the correct properties. Choose the right Search Console property and GA4 property for this store.
Create a PageSpeed Insights API key. Generate this in the same Google Cloud project.
Paste the key into the PageSpeed API Key field. This connects PageSpeed testing to the module.

4.2.3 GA4 Analytics

This is inclusive of visualization of your Google Analytics 4 metrics including traffic, engagement, and eCommerce activities.
Period Selector: Last 2 days, Last 7 days, Last 28 days, Last 30 days, or Custom that shows Date start, Date end, and an Apply button for a particular period.
Compare to previous period: this will add a second line to your charts and cards in order to indicate the corresponding period SEO score of fStore, this way you can tell whether there has been an improvement.
Overall SEO score trend: This is a graph of website score trend overtime, and it will help in knowing whether the changes that you have made recently are working or not.
Index/Follow ratio: This will show the number of pages that are marked as index and followed against the number of pages that are noindexed and nofollowed. This way you can know the pages hidden from the search engines
Page audit: a chart showing how many pages fall into strong, fair, and weak score bands, giving a quick sense of catalog-wide health.
Total users: everyone who visited the store in the period.
Active users: users counted by GA4 as actively engaged during the period.
New users: first-time visitors in the period.
Sessions: total sessions recorded in the period.
Engaged sessions: sessions that met GA4’s engagement criteria, such as lasting a minimum duration or including a conversion event.
Views: total page or screen views.
Views per session: average number of views per session.
Avg. session duration: average length of a session.
Engagement rate: the share of sessions that were engaged sessions.
Bounce rate: the share of sessions that were not engaged.
Events: total events recorded, such as clicks or scroll triggers configured in GA4.
Realtime panel: shows active users from the last 30 minutes, broken down by country, device, or page.
Traffic over time: a chart of sessions, users, and views across the selected period, with a previous-period comparison line when enabled.
Sessions by hour of day: a chart showing which hours typically bring the most sessions.
Revenue: total eCommerce revenue recorded by GA4.
Purchases: total completed purchase events.
Transactions: total recorded transactions.
Average order value: revenue divided by the number of orders.
Items purchased: total quantity of items sold.
Purchase funnel: a step-by-step view of Add to cart, Begin checkout, and Purchase, plus the conversion rates between them (Cart to checkout, Checkout to purchase, and Cart to purchase).
Top items: the best-selling products by revenue or quantity in the period.

4.2.4 Search Console

This Google Search Console Integrations in OpenCart includes performance and sitemap & URL check options. Together they show how your store appears in Google search results and whether Google has indexed your pages correctly.

Available Options

Clicks: how many times a search result led to a click on your site.
Impressions: how many times your pages appeared in search results, whether clicked or not.
CTR: click-through rate, clicks divided by impressions.
Average position: the average ranking position of your pages for the queries measured.
Comparison toggle: adds a previous-period series alongside the current data.
Period / date range selector: sets the reporting window for the Performance data.
Search type filters: narrows results to Web, Image, Video, or News search.
Queries table: search terms, with Clicks, Impressions, CTR, Position, Previous, and Change columns.
Pages table: individual URLs, with the same metric columns as Queries.
Countries table: performance broken down by visitor country.
Devices table: performance broken down by device type.
Search appearance table: performance broken down by the type of search result shown (for example, a normal listing versus a rich result).
Clicks vs impressions chart: plots both metrics together over time so you can see whether visibility and clicks are moving in the same direction.

Sitemaps & URL Check

Sitemap: the submitted sitemap’s URL.
Last submitted / Last downloaded: when the sitemap was last submitted to Google and when Google last downloaded it.
Status: Google’s current processing status for the sitemap.
Warnings / Errors: counts of issues Google found while processing the sitemap.
Submitted URLs: how many URLs the sitemap contains.
Submit/Delete sitemap: actions to add a new sitemap to Search Console or remove one that is no longer needed.
Google Index Checker: URL filter: enter a specific URL to check its indexing status.
Google Index Checker: Indexed filter: narrows results to indexed or not-indexed URLs.
Details: opens the full inspection result for a checked URL, which can show Indexed by Google, Not indexed, Listed in a submitted sitemap, or Not found in any submitted sitemap.
Check new URL: runs a fresh indexing check on a URL and stores the result in history for future reference.
Open in Search Console to request indexing: opens Google’s own URL Inspection tool, since Google does not provide an API for requesting indexing of ordinary pages.

Submit your XML sitemap here after configuring the Sitemap tab, and revisit the Sitemaps table periodically to check for warnings or errors rather than assuming a one-time submission is enough.

4.2.5 PageSpeed

PageSpeed brings Google PageSpeed Insights testing into the admin, with Run Test, Results, and History areas.

Run Test

Home page: runs the test against the storefront’s home page.
Category page: runs the test against a selected category page.
Product page: runs the test against a selected product page.
Custom URL: runs the test against any URL you specify.
Mobile / Desktop: every test runs on both device types, since performance often differs between them; a full test can take up to 90 seconds.

Results

Field data: real-world performance measured from actual Chrome users, when enough data exists in the Chrome User Experience Report.
Lab data: performance measured in a controlled, simulated test environment, useful when field data is unavailable.
Lighthouse scores: the overall category scores Google’s Lighthouse tool assigns.
Metrics: individual timing measurements such as load and rendering speed.
Insights: guidance describing what is affecting performance.
Diagnostics: additional technical detail about performance issues.
Passed audits: checks the page already satisfies.
Failed audits: checks the page does not satisfy, each with an explanation of the issue.

History

Target: filters history by which page type was tested (Home page, Category page, Product page, Custom URL).
Device: filters history by Mobile or Desktop.
From / To: date range filters for the history list.
Date: the date a specific test was run.
URL: the exact URL that was tested.
LCP: Largest Contentful Paint, a Core Web Vitals loading metric.
INP: Interaction to Next Paint, a Core Web Vitals responsiveness metric.
CLS: Cumulative Layout Shift, a Core Web Vitals visual stability metric.
Source: whether the test was run Manually or by a Scheduled check.
Export CSV: downloads the filtered history as a CSV file.

4.3 Score History

Score History in OpenCart SEO Audit Extension tracks how your store’s overall SEO score, and individual entity scores, change over time. This is where you confirm whether your SEO efforts are actually moving the needle..

Use Create snapshot to capture the store’s current state manually, for example before a large content update. To compare two points in time, select one snapshot as Snapshot A and another as Snapshot B, then click Compare snapshots; the two selections must be different from each other.

Best practice is to enable automatic snapshots and configure a retention policy in General Setting so that history builds up on its own, rather than depending on manual snapshots that are easy to forget.

4.5 URL Optimisation in Prestashop

This OpenCart SEO Audit Extension includes features like a redirection feature, 404 URL fixing and Duplicate URL detection.

A 301 redirect signals a permanent move and is generally the right choice when a page has been renamed or merged and the old URL should never be used again, this is the most common use case for OpenCart 301 Redirects. A 302 redirect signals a temporary move, useful for short-term changes such as a seasonal category being swapped out and back. A 303 redirect is typically used to point a request elsewhere after an action, such as a form submission, and is less commonly needed for straightforward catalogue URL changes.

Import CSV: this includes adding a bunch of URLs directly at once from a sheet.

Add Redirect: Type in a redirect’s name, its source URL, or its target URL, and click Filter to narrow the list down, handy once you’ve got more than a handful of redirects saved.

Redirect entry type: Individual for a single redirect, or Bulk for a CSV upload; Bulk mode is available only when adding, not editing.

Redirect name: an optional label to help you identify the redirect later, such as “mens-tshirts.”

Source URL: the old address to redirect from; this can be an SEO path (for example, old-category/old-product), an OpenCart route such as information/contact, or a path without the domain. This field is required.

Target URL: the destination address, entered as a relative path or a full http(s) URL. This field is required, and unsafe schemes such as javascript: or data: are rejected.

Redirect type: 301, 302, 303, or 404; new individual forms default to 301.

Active: Enabled or Disabled; new individual forms default to Enabled.

Save: stores the redirect and returns to the list with a success message.

The file must stay under 2 MB and 2,000 rows. Invalid rows are skipped, and the import result reports how many rows were imported and how many were skipped.

Editing and managing redirects. Use Search redirects to locate an entry by name, source, or target, then use Edit or Delete from the row actions. Bulk mode is available only when adding redirects, not when editing an existing one.

Avoiding mistakes. Redirects do not run on the storefront unless both the module’s master Status and Enable URL redirects are turned on in General Setting. Base redirect decisions on an actual URL change, such as a renamed product or a restructured category, rather than redirecting pages speculatively. A chain of redirects pointing to other redirects should generally be avoided; point each source directly to its final destination where possible.

Example. If a product URL changes from /product/old-name to /product/new-name after a rename, add a 301 redirect from the old path to the new one so that existing links and bookmarks continue to work.

10. 404 URL Detection

A 404 URL is a storefront request for a page that no longer exists or never existed at that address. Left unaddressed, these broken links frustrate visitors and waste any traffic or link value the old page had earned.

This module detects the 404 URLs and allow the store owners to redirect the 404 URL by following redirect feature.

4.6 Robots.TXT

Robots.txt is a plain text file at your store’s root address that tells well-behaved search engine crawlers which parts of the site they should avoid crawling.

A misconfigured robots.txt file can accidentally block important pages from being crawled, while a well-configured one keeps crawlers away from admin and system directories that offer no value in search results.

The OpenCart Robots.txt Editor includes:

File path: the server location of the robots.txt file, for reference.
Exists: shows Enabled when a robots.txt file is already present, or Disabled when it is not.
robots.txt content: an editable text area containing the file’s directives. If no file exists yet, this area is pre-filled with a starting version that disallows the /admin/ and /system/ directories.
Save: writes the edited content to the file.

4.7. XML Sitemap

An XML sitemap is a structured list of your store’s URLs that helps search engines discover and prioritize pages for crawling.

The module’s OpenCart XML Sitemap tool, part of its broader OpenCart Sitemap Generator, allows you to configure the following under Sitemap > XML Sitemap:

Enable XML sitemap: turns on the public XML sitemap endpoint.
Sitemap page URL: displays the public URL once the sitemap is enabled.
Per-language sitemap URLs: shown for each enabled storefront language, since each language can have its own sitemap address.
Enable RSS: turns on the RSS feed endpoint alongside the sitemap.
Include in sitemap: checkboxes for Product, Category, Information, and Manufacturer, controlling which content types are listed in the sitemap.
Product limit: the maximum number of products included; the Extension recommends a positive value of 5,000 or lower, and treats zero or a blank value as a safe maximum.
Priority (per content type): a value from 1.0 down to 0.0 indicating relative importance within your own site; saved values are clamped to this range.
Change frequency (per content type): Always, Hourly, Daily, Weekly, Monthly, Yearly, or Never, describing how often that page type typically changes; invalid values are normalized to Weekly.
Save: stores the configuration.

The HTML Sitemap sub-tab works alongside the XML version, publishing a customer-facing sitemap page instead of a machine-readable file. Its fields are:

Enable HTML sitemap: publishes the customer-facing sitemap page.
Sitemap page URL: shown only once the HTML sitemap is enabled.
Per-language HTML sitemap URLs: shown for each enabled storefront language.
Include in HTML sitemap: checkboxes for Home page, Product, Category, Information, Manufacturer, and Specials (Price Drop).
Custom URLs: an optional table of additional links, each with a Title and a URL (an absolute https:// address or a store path such as contact).
Add URL: adds a new blank row to the Custom URLs table.
Remove: deletes a row from the Custom URLs table.
Save: stores the configuration; the extension returns to the HTML tab if it was the active tab when you saved.

The HTML sitemap’s product list reuses the Product limit set on the XML Sitemap tab.

4.8 Settings

4.8.1 General Setting

General Setting is the module’s central configuration page, and Status here is the master switch that everything else depends on. This is also where the extension functions as an OpenCart Metadata Manager, letting you define default meta title and description templates for products and categories.

Master and analysis controls

Status: the master switch for the entire module; storefront metadata, redirects, panels, and score columns only work when this is enabled. Default: Disabled.
Enable Page audit: shows SEO score cards, the Page audit tab in catalog forms, and SEO Score columns in catalog lists. Default: Disabled.
Enable readability analysis: shows readability score cards and lists alongside the SEO scores. Default: Disabled.
Enable auto analysis on edit: reruns analysis automatically while a page is being edited; scores are also saved when the catalog form is saved. Default: Disabled.
Record 404 requests: records missing storefront URL requests for the 404 URLs report. Default: Disabled.
Enable URL redirects: applies active redirects on the storefront. Default: Enabled, though the master Status must also be enabled for redirects to actually run.
Enable XML sitemap: turns on XML sitemap functionality store-wide. Default: Disabled.
Enable RSS: turns on RSS functionality store-wide. Default: Disabled.

Search and metadata defaults

Title separator: the character or text used between parts of a generated title, such as -; referenced by the {title_separator} shortcode. Default: -.
Show products in search by default: whether new products appear in the storefront search index by default. Default: Enabled.
Show categories in search by default: whether new categories appear in the storefront search index by default. Default: Enabled.
Show manufacturers in search by default: whether new manufacturers appear in the storefront search index by default. Default: Enabled.
Show information pages in search by default: whether new information pages appear in the storefront search index by default. Default: Enabled.
Product meta title template: the default meta title pattern for products, using shortcodes. Default: {product_name} {title_separator} {shop_name}.
Product meta description template: the default meta description pattern for products. Default: blank.
Force product meta templates: when enabled, the template is applied even if a product already has its own meta title or description. Default: Disabled.
Category meta title template: the default meta title pattern for categories. Default: {category_name} {title_separator} {shop_name}.
Category meta description template: the default meta description pattern for categories. Default: blank.
Force category meta templates: when enabled, the template is applied even if a category already has its own meta title or description. Default: Disabled.

Supported shortcodes across these templates include {product_name}, {category_name}, {shop_name}, {title_separator}, {brand}, {og_meta_title}, and {og_meta_description}.

Cron and verification

Cron secure token: the secret value used in the module’s cron URL to authenticate scheduled requests; a token is generated by default.
Google verification code: the content value from Google Search Console’s HTML-tag verification method; it can be left blank if verification is already completed another way.
Bing verification code: the content value from Bing Webmaster Tools verification; it can also be left blank if verification is already completed another way.

Score History

Enable SEO score history: turns on score tracking and snapshots. Default: Enabled.
History retention: Keep all history (default), Delete older than X days, Keep only daily snapshots, or Keep only weekly snapshots.
Retain history for (days): the number of days to keep when the day-based retention option is selected. Default: 365.
Automatic snapshot schedule: Manual only, Daily (midnight) (default), Weekly, or Monthly; automatic snapshots also require a scheduled request to the module’s cron URL.

4.8.2 Social Cards

Social Cards controls the Open Graph and X (Twitter) card metadata added to storefront pages, along with basic structured data settings.

Enable Facebook Open Graph: turns Open Graph metadata on or off. Default: Enabled.
Enable X Card: turns X (Twitter) card metadata on or off. Default: Enabled.
X card type: summary or summary_large_image, controlling how a shared link’s preview card is laid out. Default: summary_large_image.
Site type: Organization, WebSite, or LocalBusiness, used in the structured data describing your store. Default: Organization.
Site name: the name used in site-level metadata.
Breadcrumbs: turns breadcrumb structured data on or off. Default: Enabled.
Facebook: your store’s Facebook profile URL.
Twitter: your store’s Twitter/X profile URL.
Instagram: your store’s Instagram profile URL.
LinkedIn: your store’s LinkedIn profile URL.
YouTube: your store’s YouTube channel URL.
Pinterest: your store’s Pinterest profile URL.
Save: stores the settings.

4.8.3 ChatGPT Content Generator

Knowband OpenCart SEO Audit Extension also includes the feature of an AI Content Generator as an additional tab inside product and category SEO panels, and as a bulk tool within Import/Export.

Enable ChatGPT: turns the assistant on or off across the module. Default: Disabled.
ChatGPT model: GPT-4o, GPT-4o mini, GPT-4 Turbo, GPT-4, or GPT-3.5 Turbo; the controller falls back to gpt-4o-mini and the installation default is gpt-3.5-turbo.
ChatGPT API token: your OpenAI secret key, which must begin with sk-.
Test API key: sends a live validation request to OpenAI to confirm the token works.

Single-page fields (SEO panel > ChatGPT tab).

Prompt templates: a set of ready-made prompts you can select instead of writing your own.
Your prompt: a free-text box for a custom prompt, supporting shortcodes such as {product_name}, {brand}, {category_name}, {meta_title}, and {meta_description}.
Generate: sends the prompt to ChatGPT and returns a draft.
Generated content: displays the draft returned by ChatGPT for review.
Apply: places the generated content into the relevant field (the catalog form must still be saved afterward for the change to take effect).
Apply to: chooses which field the generated content should be applied to.
Clear history: clears the recent generation history for this page.
Recent history: a list of previous prompts and results for this page.

Bulk fields (Import/Export > ChatGPT enhance).

Field checkboxes: choose which fields to generate, from Meta title, Meta description, Meta keywords, Social title, Social description, Product tags, SEO URL, Primary keyword, Supporting keywords, and Product description (readability).
Select all / Select none: quickly selects or clears every field checkbox.
Process all products: generates content for the entire catalog.
Max products: an alternative to Process all products, capping the run at a specific number, up to 5,000 distinct catalog products across all languages for each product.
Products per API call: how many products are sent together in a single request, from 1 to 5; the Extension forces this to 1 whenever Product description (readability) is selected.
Start / progress indicator: begins the enhancement run and shows live progress.
Maximise SEO & readability scores (download JSON): the action that runs the enhancement and produces a downloadable file; it does not save directly to the catalog.

That downloaded file must then be brought back in through the Import panel described below; the bulk ChatGPT tool never writes to the catalog on its own.

4.9. Import/Export

Import/Export handles product SEO data as a JSON file: meta title, description, keywords, and tags; the SEO URL, primary and supporting keywords, robots and canonical settings, social title, description, and image; SEO and readability scores and analysis data; and rating markup fields. This is used in updating multiple product in bulk.

Supported format. The exported file uses JSON format at version 1.2 and includes an export timestamp and field list along with the product data.

Export fields.

Export: the single action button that generates and downloads the current product SEO data as a JSON backup file, versioned 1.2 and including an export timestamp, field list, and product data. This same file can also serve as a baseline before running the ChatGPT enhancement tool described in Section 14.

Import fields.

Choose file: selects the .json file to import; the extension must be .json, the content must be valid JSON, it must contain a products array, and it must stay under 5 MB with no more than 5,000 rows.
Import: runs the import; product and language IDs in the file must be positive numbers matching the current store. Successful imports report the number of updated product and language rows.

Other Modules is a shared Knowband catalogue page reachable from the Knowband SEO menu. It lists other Knowband extensions available for OpenCart rather than SEO configuration options specific to this module.

5. SEO Audit and Scoring

The scoring system is the foundation of Knowband’s OpenCart SEO Audit Extension. Every product, category, information page, manufacturer page, and supported blog entity can receive an SEO score and a separate readability score once the relevant analysis settings are enabled in General Setting , the core of what makes this an effective OpenCart SEO Analyzer.

Supported page types. Scoring covers Products, Categories, Information pages, and Manufacturers by default. Blog posts, Blog categories, Blog tags, and Blog authors are included only when a supported Knowband Blog integration is connected to the store.

What the score measures. Running this OpenCart SEO Audit means the rule library evaluates content length, sentence and readability quality, heading structure, internal links, image alt attributes, title and description length, and the placement and density of your primary and supporting keywords in the page’s content and URL slug. Any rule that scores below 7 is logged as an issue and grouped under the Issues tab.

What the score means. A high score indicates that a page has covered the fundamentals: a reasonably descriptive title and description, readable content, sensible heading structure, and keyword usage that matches the page’s stated focus. A low score does not mean a page is invisible to search engines; it means specific, correctable gaps exist. Since the Extensioncannot see how Google actually ranks a page, the score should be read as a content quality checklist rather than a ranking prediction.

Why the score matters. Search engines reward pages that clearly answer a search intent with well-structured, readable content. A low score often points to the same weaknesses that make a page harder for a human shopper to read, so fixing them tends to help both audiences.

What to do about a low score. Open the page from the catalog list, review its Page audit panel, and check the specific rules it failed. Alternatively, open the Issues tab, filter by the relevant entity type, and work through rules that affect multiple pages at once. After making changes, save the page (or rely on Enable auto analysis on edit) so the score updates. This ongoing review is the heart of OpenCart SEO Optimization within the module.

How to improve a page. Set a clear primary keyword and, where relevant, supporting keywords that reflect what a shopper would actually search for. Write a meta title and description that describe the page honestly rather than stuffing keywords. Break long content into sections with headings, add descriptive alt text to images, and link to related products or categories where it makes sense for the shopper, not purely for the score.

Throughout this process, remember that an OpenCart SEO Audit is only useful when it leads to real edits. The module’s role is to surface what needs attention; the administrator’s role is to decide how to phrase and structure the fix, using the OpenCart SEO Audit Extensionas a guide rather than a final authority.

5. Frequently Asked Questions

I found several 404 URLs. How can I redirect them? Open URL Optimization > 404 URLs, review the list ordered by visit count, and click Redirect next to the entry you want to fix. This opens the redirect form with the old URL already filled in as the Source URL; enter the correct destination as the Target URL, choose the redirect type, and save. Only redirect to a page that is genuinely relevant to the original content.

How should I handle a URL that is no longer available? If a replacement page exists, add a 301 redirect from the old URL to the new one through URL Optimization > URL Redirects. If no relevant replacement exists, it is reasonable to leave the URL as a 404 rather than redirecting visitors somewhere unrelated.

How can I improve a page with a low SEO score? Open the page’s Page audit panel, or open Issues and filter by entity type, to see exactly which rules the page failed. Address specific gaps, such as a missing meta description, thin content, or missing image alt text, then save the page so the score updates. Score History will then show whether the change moved the page’s score in the right direction.

Can I use the Extensionto generate meta titles and descriptions? Yes. Enable and configure ChatGPT under Settings > ChatGPT, then use the ChatGPT tab inside a product or category’s SEO panel to generate a meta title or description from a prompt. Review the result, click Apply, and save the catalog form. For many products at once, use the bulk ChatGPT tool inside Import/Export instead.

How can I check duplicate URLs? Open URL Optimization > Duplicate URLs to see which SEO keywords are assigned to more than one page in the same store and language. Click Update on a conflicting row, edit each keyword so it becomes unique, and save.

How can I check my XML sitemap? Open Sitemap > XML Sitemap, confirm Enable XML sitemap is turned on, and open the displayed public sitemap URL to verify it loads. Submit that same URL under Analytics > Search Console > Sitemaps & URL Check to confirm Google has received it and to monitor for warnings or errors afterward.

Can I connect Google Search Console? Yes. Set up a Google Cloud project with the Search Console API enabled, configure OAuth credentials under Analytics > Settings, click Connect with Google, and select the correct Search Console property for the store. Once connected, the Search Console tab shows Performance data and lets you manage sitemap submissions and URL indexing checks.

Can I view Google Analytics data inside the module? Yes. After connecting Google and selecting the correct GA4 property in Analytics Settings, the GA4 Analytics tab displays sessions, users, engagement, eCommerce, and breakdown data directly in the admin panel, without needing to open Google Analytics separately.

How can I identify SEO issues on product or category pages? Use the Dashboard’s Page audit by type chart to see which content type has the most low-scoring pages, then open Issues and filter by entity type to review specific rules affecting those pages. Alternatively, open an individual product or category and review its Page audit panel directly.

Does the Extensionguarantee better search rankings? No. The OpenCart SEO Audit Manager measures on-page content quality, technical configuration, and available Google data, all of which support good SEO practice. It does not control, and cannot guarantee, how any search engine ranks a specific page.

Is a blog required to use the module? No. Blog-specific scoring, trends, and entity types appear only when a supported Knowband Blog integration is connected to the store. Every other feature works fully without a blog installed.

Do I need Google or OpenAI accounts to use the core module? No. Analytics, Search Console, PageSpeed, and ChatGPT are optional integrations that require their own external credentials. The scoring system, redirects, 404 detection, duplicate URL checking, sitemap generation, and robots.txt management all work independently of those connections.

OpenCart Backup and Restore Extension: Complete User Manual

Ask any OpenCart store owner when they last backed up their database, and most will hesitate before answering. It’s not that people don’t care about their data. It’s just that backups sit at the bottom of the to-do list, right under “get to it eventually.” Then one bad update, one failed plugin install, or one hosting glitch happens, and suddenly there’s no way back. That’s exactly the gap this OpenCart backup and restore Extension is built to close.

Instead of relying on you to remember, this backup extension by Knowband is one of the best OpenCart backup extensions that turns automatic store backup into something that just happens in the background, quietly, on a schedule, without you lifting a finger once it’s set up. Think of it as insurance for your catalogue, your orders, your customer records, and everything else sitting in your OpenCart database.

This isn’t just a database tool either. It works as a full OpenCart store backup Extension, meaning it can grab your files, your images, your database, or all of it together, depending on what you need at that moment. On top of that, it comes with a proper restore engine and a standalone restore script, so even if your admin panel becomes unreachable for some reason, you still have a way back in. That combination, backup plus a reliable restore path, is really what disaster recovery for eCommerce is supposed to look like.

The rest of this manual walks through every screen, every setting, and every button in Knowband’s OpenCart backup and restore Extension, so you can set it up correctly the first time and troubleshoot with confidence if something looks off later.

Quick tip before you start: Read the General Settings section first. The CRON token and the restore password you set up there are needed for every scheduled backup and every restore you’ll ever run through this OpenCart restore Extension. Skipping that step now just means backtracking later.

2. Getting Familiar with the Admin Panel of Backup and Restore Plugin

Once installed through Extensions in your OpenCart admin, the module adds its own dashboard and a handful of tabs. We’ll go through each one, starting with the Dashboard, since that’s the screen you’ll actually look at most often.

2.1 Dashboard

The Dashboard exists to answer one question the moment you open it: is my store’s data actually protected right now, or not? You shouldn’t have to dig through logs to find out, so everything important is summarized right here.

Last Backup: Tells you whether the most recent backup job succeeded, failed, or is still running, along with the date, time, and how long it took.

Last Restore: Same idea, but for restores. This matters more than people think. You want to know a restore genuinely completed before you trust it, not just assume it worked.

Storage Used: Shows how much space your stored backups are eating up across every connected storage platform. Useful when you’re deciding whether it’s time to clean up old archives.

Platform Health: A quick status check across whatever storage destinations you’ve connected, local folder, FTP or SFTP, S3-compatible storage, or an OAuth-based cloud service. Each one is flagged as healthy or unreachable so problems don’t sit hidden until backup day.

Backup Activity: A simple view of how many backups ran over a given period, day by day, along with any that failed. Handy for spotting a pattern, like backups quietly failing every Sunday because of a server maintenance window.

Storage by Platform: Breaks down exactly how much space each connected storage destination is using. If your local server storage is filling up faster than expected, this is where you’d notice.

Latest Backup Composition: Shows what’s actually inside your most recent archive, database, images, other files, and roughly how big each piece is.

Recent Jobs: Lists your latest backup runs with quick Restore or Retry buttons right there, so if something failed overnight, you can act on it immediately instead of hunting through menus.

Restoration History: A snapshot of recent restore attempts, their outcome, and timing, so you can confirm at a glance whether a restore genuinely finished properly.

Connection and Error Feed: Live status and error messages as they happen. This alone often saves you a trip to the Logs tab, since you get the exact cause of a failure right there on the dashboard.

3. General Settings of the OpenCart backup and restore Extension

This is really the control center of the whole OpenCart backup Plugin. It decides whether the module runs at all, how your standalone restore script is protected, and what CRON command your host (or an external scheduler) needs to trigger scheduled runs.

Enable Module: A simple on/off switch. Turn it off and scheduled CRON jobs stop firing, though you can still run manual backups and restores from inside the admin panel whenever you like.

Restore Password: This protects the standalone restore script from being used by anyone who shouldn’t have access to it. It’s stored as a hashed value, never in plain text, and you’ll need it any time you restore your shop outside the normal admin interface.

CRON Secure Token: A unique token baked into every scheduled backup URL and command line trigger. Here’s the thing though, if you regenerate this token, every existing CRON job tied to the old one stops working. So the moment you regenerate it, go update every scheduler entry that references it. Don’t put that off.

Standalone Restore Script: This gives you the direct URL and server file path for restoring your shop even when the OpenCart back office itself won’t load. As long as you know your restore password, you can restore your shop from this script alone, without needing to log into admin at all.

Scheduled Backup (CRON): Ready-made commands, web URL, PHP CLI, or shell script, that you copy straight into your hosting panel’s CRON manager or any external scheduler. One trigger runs every enabled backup profile in a single pass.

4. Backups Tab in Knowband’s OpenCart backup Manager

This is where you run a one-off backup outside your regular schedule, and where you review every archive the OpenCart database backup Extension has generated so far. Pick a profile from the dropdown, hit Run, and watch progress update live on the same screen, no page reload needed.

4.1 What You’ll See in the Backups Table

ID: An internal identifier used to link a restore action back to the exact archive it came from.

Filename: The actual file saved to disk, usually timestamped so backups never overwrite each other by accident (and it’ll carry a .crypt suffix if you’ve turned on encryption).

Type: Tells you whether it’s a database-only dump, a files-only backup, or a complete backup covering both, matching whatever the profile was set to do.

Size: The compressed size of the finished file.

Profile / Platform: Which saved profile created this backup, and which storage destination is currently holding it.

Encrypted: A simple Yes or No showing whether AES-256 encryption was applied before the archive was stored.

Locations: Shows the from and to file paths, which is genuinely useful for confirming a copy actually made it to your remote destination and isn’t just sitting in a local staging folder.

Date: When the backup finished, used for sorting and for whatever retention rules you’ve set on that storage platform.

5. Profiles

A profile is basically a saved recipe for how you want backups done. It stores what gets backed up, where it goes, and who gets notified when it’s done. You can build as many profiles as your store needs, one for a quick daily database snapshot, another for a full weekly files and database backup, whatever fits your workflow.

5.1 Setting Up a Profile

Profile Name: Whatever name helps you recognise this profile later, in the dashboard, the backups list, or the restore history.

Backup Type: Choose whether this profile grabs both database and files, database tables only, or just files and folders with no data at all.

Database Tables: You can back up every table in your OpenCart database, or pick specific ones if you only need, say, orders and customers, and don’t care about log tables cluttering the archive.

Files & Folders: Same idea. Back up everything, or select specific folders. There’s also an exclude list below for skipping things like cache directories or temp files that just add bulk without adding value.

Exclude These Files or Folders: List anything you want skipped, one entry per line, things like system/storage/cache/ or image/cache/. These get skipped even when “all files” is selected above.

File Extensions to Include: If you only want certain file types backed up (php, js, css, whatever), list them here. Leave it blank and every file type gets included.

Tick Budget (seconds): Big backups take time, so the process runs in short bursts called ticks. This setting controls how long each burst runs, somewhere between 5 and 300 seconds. Lower it on shared hosting that tends to time out scripts.

Status: Enable a profile so it runs automatically during CRON jobs, or disable it so it only runs when you manually trigger it. Either way, you can always start it by hand.

5.2 Destination

Pick a storage platform here. You will need to create the destination first under the Platforms tab before it shows up as an option in a profile.

5.3 Email Notifications

Email on Completion / Email on Error: Decide independently whether successful jobs, failed jobs, or both trigger a notification email.

Send To: A comma-separated list of recipients. Leave it blank and it defaults to your store’s admin email address automatically.

Attach Restore Script: Turn this on and the standalone restore.php file gets attached to the completion email. That way, even if your server disappears entirely, you’ve still got a copy of the restore script sitting safely in your inbox.

5.4 Advanced Settings

Backup Filename: Customize naming using placeholders like {date}, {time}, {datetime}, {type}, and {version}. Leave it blank for the default naming pattern. One thing worth noting: a fixed filename without {datetime} in it will overwrite the previous backup instead of creating a fresh one, so be careful there.

Compression: Choose Auto (it picks between bz2, gz, or none automatically) or lock it to a fixed format. This determines whether your final archive ends up as .tar.gz, .tar.bz2, or plain .tar.

Max Part Size (MB): Split large archives into smaller chunks of a set size. Set it to 0 and splitting is disabled entirely.

Product Images: Choose whether product and source images are included in the backup or left out.

Encrypt Archive: This is where the OpenCart cloud backup Extension really earns its keep. Turn this on and AES-256 encryption gets applied to the archive before it’s stored locally or shipped off to a remote platform.

Encryption Key: The key needed to decrypt and restore that specific backup. There’s genuinely no recovery option if you lose it, so store it somewhere safe, and definitely somewhere other than on the same server.

Build File Map: Records a per-file size breakdown, which powers a detailed file map view later, handy for auditing exactly what ended up in a given archive.

Dump Values Per Line: Controls how many rows get batched into each INSERT statement when the SQL dump is written.

Dump Rows Per Select: Sets the maximum number of rows pulled per SELECT during the dump, using cursor paging (default is 25000). Lower this on memory-constrained hosting if you’ve got some seriously large tables.

6. Platforms

Platforms decide where your finished backups actually land. Local storage is fine as a starting point, but the real value of this OpenCart cloud backup Extension shows up once you connect something off-server, FTP or SFTP, an S3-compatible service (MinIO, Wasabi, Backblaze, Scaleway, take your pick), Google Cloud Storage, or an OAuth cloud provider like Google Drive, Dropbox, OneDrive, or Yandex.

Here’s the honest truth: keeping a copy away from your origin server is the single change that turns “I have backups” into actual disaster recovery for eCommerce. A backup sitting on the same server that just went down doesn’t help you much.

Platform Name: A friendly label used everywhere this platform gets referenced, in profiles, the backups table, and the dashboard’s health card.

Storage Type: Local folder, FTP/SFTP, an S3-compatible service, Google Cloud Storage, or an OAuth-based cloud provider.

Remote / Local Directory: The destination path for stored archives. It defaults to something like system/storage/backup/ if you leave it blank. Note that this field locks once the platform is created, so if you need a different path down the line, just set up a new platform rather than trying to edit this one.

Keep Remote Copies: The maximum number of archives this platform will retain. Set it to 0 and it keeps everything forever, which is convenient, but keep an eye on your available storage if you go that route.

7. Restore History

Every restore attempt gets logged here, successful or not, which matters most in the exact moment you’re actually trying to restore your shop under pressure. You shouldn’t have to trust that a restore “probably went fine.” This tab gives you a timestamped, per-file record instead.

ID / Filename / Type: Identifies the restore record and the exact archive that was restored, along with its type (Complete, Database, or Files only).

Source: Where the restore was triggered from. Usually it’s from inside the module itself, though the standalone restore script logs its attempts here too.

Status: Complete or Failed, showing the outcome of that particular attempt.

Launched By: The admin user who kicked off the restore. Useful for accountability on stores where multiple people have back-office access.

Started / Finished: Timestamps marking the operation from start to end, so you can work out exactly how long it took.

Message: The exact system message tied to that attempt, a permissions error on a specific folder if it failed, or a plain confirmation if everything went through fine.

8. Logs

Whenever the Dashboard’s Connection and Error Feed doesn’t give you quite enough detail, this is the tab to check next. Every backup, every restore, and every connection test writes a row here, and you can filter by date, platform, type, and severity.

Date: The exact timestamp of the event.

Platform: Which storage platform this entry relates to, where applicable. It’ll be blank for events happening before a platform comes into play.

Type: The category of the underlying operation, local, ftp, or whatever connector type was involved.

Context: What action was actually being performed, backup, restore, or test_connection.

Level: Success or Error. Filtering by this alone clears out most of the noise when you’re scanning for a specific problem.

Message: The full, unfiltered system message, file paths, permission codes, network errors, whatever it is. Usually enough to figure out what went wrong without needing to escalate further.

9. Frequently Asked Questions

1. Does this replace my hosting provider’s backups?
Hosting-level backups are useful, but having your own Knowband’s OpenCart database backup Extension means you control the schedule, the retention, and where copies actually go, rather than relying entirely on your host’s policy.

2. Can I restore my shop if the admin panel won’t load?
In the OpenCart backup and Restore Extension as long as you have the restore password, you can restore your shop directly through restore.php without ever touching the admin panel.

3. What happens if I lose my encryption key?
There’s no way around it, unfortunately. If a backup was encrypted and the key is gone, that archive can’t be decrypted. Store the key somewhere separate from your server; a password manager works well.

4. How often should scheduled database backup run in OpenCart?
It really depends on how often your store changes. A high-order-volume store might want daily or even more frequent database backups, while a smaller catalogue-based store might be fine with weekly. The scheduling is flexible enough to handle either.

5. Is cloud storage necessary, or is local storage enough?
Local storage is better than nothing, but cloud backup for OpenCart gives you real protection if the server itself fails, gets hacked, or becomes inaccessible. For genuine OpenCart data protection, an off-server copy is worth setting up.

10. Conclusion

This manual has walked through every tab in Knowband’s OpenCart backup and restore Extension, from the Dashboard all the way through to Logs, and it’s worth bookmarking for whenever you’re setting up a new profile or troubleshooting a restore later on.

If you ever hit a scenario this manual doesn’t quite cover- an unusual storage provider, a permissions quirk specific to your host, or a restore that isn’t behaving the way you expect- checking the Logs tab first will usually get you most of the way to an answer before you need to reach out for further support.

In short, treat scheduled backups and off-server copies as routine maintenance, not an emergency scramble. Once that’s part of your normal workflow, OpenCart data protection stops being something you worry about and just becomes something that quietly runs in the background, exactly the way it should

OpenCart Advanced Security Manager Extension – Complete User Guide (Updated)

Most OpenCart store owners end up securing their site the hard way: one extension for two-step login verification, another for blocking spammy bots, a third for CAPTCHA, and maybe a support ticket to their host about a firewall. OpenCart Security Manager was developed to remove that patchwork. This module puts admin-side protection, storefront defense, and file-integrity monitoring into one settings screen inside your OpenCart admin panel.

Whether you’ve been searching for an OpenCart two-factor authentication extension, an OpenCart firewall extension, protection against login brute-forcing, or a way to disguise your admin directory without stacking five separate add-ons, this single extension is built to cover that ground.

The OpenCart Advanced Security Manager extension is organised into three sections, each broken into its own set of tabs:

Admin Protection: Two-Step Verification, Login Attempt Throttling, IP-Restricted Admin Access, Admin Directory Cloaking, Server-Level Login Prompt, and login activity tracking.

Storefront Protection: Web Application Firewall, Security Response Headers, Form Spam Filtering (CAPTCHA), Copy/Scrape Deterrents, and a storefront-wide access prompt.

File Integrity Monitoring: Scheduled scans, threat flagging, and a scan history log.

Each area is covered field-by-field later in this document, so you’ll always understand what a setting does before you switch it on.

Attackers targeting OpenCart stores tend to go after the same handful of weak points: guessable admin passwords, scripted login attempts, an admin directory sitting at its default path, unguarded contact/registration forms, and quietly altered core files. This extension is meant to close those specific doors without requiring a security consultant or a stack of unrelated add-ons.

Protection is applied in independent layers, and each layer covers a different surface – the admin login screen, storefront-facing forms, the headers your server sends back to browsers, and the files on disk.

The risk in plain terms: OpenCart, being widely used and open-source, is a routine target for automated scanning. Bots probe for default admin paths, hammer login forms with credential lists, and flood contact forms with spam. One compromised admin login can lead to stolen customer records, injected code, or a defaced storefront – outcomes that cost far more in cleanup and lost trust than the setup time this extension requires.

New Features Added to the OpenCart Advanced Security Manager Extension v1.0.1 ( Updated July 10, 2026)

Knowband’s OpenCart Security Extension has been upgraded with two major additions: a Security Dashboard and a frontend Honeypot Field under Spam Protection powered by Project Honeypot. Together, these give store owners a complete, real-time view of their store’s safety along with a stronger, hassle-free shield against automated attacks.

1. New Security Dashboard

A centralised Security Dashboard is now available, giving OpenCart admins a single-screen overview of their store’s overall security health.

Key details displayed include:

Security Score
Active Security Protections
Failed and Successful Login Attempts
Login Success Rate
Two-Factor Authentication Coverage
Active IP Bans
Spam Protection Statistics
Flagged IP Addresses
Bot Trapping Activity
Recent Project Honeypot Classifications
Top Attacking IP Addresses
Top Targeted Admin Accounts

With this dashboard, merchants can track security activity as it happens and catch potential threats before they escalate.

2. Honeypot Protection

The new Honeypot feature adds an invisible layer of bot defence by embedding a hidden field within key storefront forms. Genuine shoppers never see it, but bots that auto-fill every field are instantly flagged.

Protects Registration, Login, Contact, Newsletter, and Product Review forms
Requires no theme modifications
No dependency on third-party services
Completely invisible to real customers
Reduces spam submissions and fake account creation

For added protection against more sophisticated bots, this feature pairs effectively with the OpenCart Captcha Extension.

3. Project Honeypot Integration

This release also integrates the extension with Project Honeypot, a globally trusted service that identifies known spammers and malicious IP addresses. Rather than relying solely on form-based checks, this integration evaluates a visitor’s reputation before they even interact with your store’s forms.

Key highlights:

Real-time IP reputation lookups via the Http-bl service
Observer Mode to monitor suspicious visitors without blocking them
Action Mode to automatically block flagged IP addresses
Configurable ban duration
IP whitelisting for trusted users, internal networks, and CDN services
Detailed logs showing visitor reputation scores and the corresponding action taken

Key Features of OpenCart Security Manager Extension

Two-Step Verification (2FA)

Requires an admin to supply a rotating six-digit code from an authenticator app in addition to their password. This blocks account takeover even when a password has leaked, been guessed, or reused from another breach.

Example: A shop with three admin users might require 2FA for everyone except a contractor’s fixed office IP, which is exempted. Tip: whitelist your own reliable IP addresses before turning on sitewide enforcement, so you’re never prompted to enroll from a connection you can’t act from.

Login Attempt Throttling

Temporarily blocks an IP once it racks up too many failed admin logins inside a set window – no manual watching required.

Example: if a script fires 50 password guesses at the admin login in under a minute, the source IP gets banned automatically once the retry limit is hit. Tip: pair a moderate retry ceiling (5–10 tries) with a ban long enough to discourage a retry (15–30 minutes), and exempt your office or VPN IP so a typo doesn’t lock your own team out.

IP-Restricted Admin Access

Limits admin panel access to a defined list of addresses – anyone else is turned away before the login form even loads. This is the single strongest control against outside admin access, since the block happens before any credentials are checked.

Admin Directory Cloaking

This feature hides your real admin path behind a secret alternate URL; the genuine path returns a 404 to anyone who doesn’t know the alternate name. This takes your store out of the pool that bots find by scanning for common admin folder names.

Server-Level Login Prompt (HTTP Authentication)

Adds a browser-native username/password prompt in front of the admin panel, the storefront, or both – before OpenCart’s own login screen loads. This runs entirely outside the application, which is useful for staging sites, pre-launch stores, or an extra admin gate.

Web Application Firewall (WAF)

Screens incoming GET/POST data and cookies for known SQL injection, cross-site scripting, and path-traversal patterns, and blocks matches with an HTTP 403 before they reach OpenCart’s code.

Security Response Headers

Adds headers (HSTS, clickjacking protection, MIME-sniffing protection, referrer policy, permissions policy) that instruct browsers to enforce extra safeguards. This is a low-risk way to harden how browsers treat your site, and it’s frequently required on PCI and security-audit checklists.

Form Spam Filtering (CAPTCHA)

Adds CAPTCHA verification – Cloudflare Turnstile, Google reCAPTCHA, or hCaptcha – to the contact form and registration form, cutting spam submissions and fake sign-ups with no theme edits required.

Copy/Scrape Deterrents

Discourages casual content copying by disabling right-click, copy/paste, view-source, and DevTools shortcuts, raising the effort needed to casually scrape product text and images.

File Integrity Monitoring

Runs scheduled scans that compare your OpenCart installation against a known-good baseline, flagging new or altered files as possible threats – often surfacing a compromise before it shows up on the storefront.

Detailed Overview of the OpenCart Security Extension

Admin Protection – Covers your admin login and sessions: 2FA, login throttling, IP restriction, directory cloaking, server-level login prompt, and login monitoring (which includes a Users sub-view for managing individual 2FA enrollments).

Storefront Protection – covers customer-facing traffic: the firewall, response headers, spam filtering, cart-bot blocking, copy deterrents, and the storefront-wide login prompt.

File Integrity Monitoring – scan settings and history, including the cron URL used for scheduling and a searchable log of past scans.

At the top of every tab you’ll find the emergency recovery link – a permanent URL that switches off the extension’s restrictive features in one click if you ever get locked out. This is the single most important detail in this manual: find it now, before touching any other setting, and save it somewhere outside the admin panel. This is the important information that an admin owner should be aware of.

The Users view under Admin Protection lists every admin account (ID, name, email, current 2FA status) and lets you reset a lost or compromised authenticator enrollment so that person can register a new one on their next login.

Reporting lives in two places: the Login Attempt Log under Admin Protection (IP, timestamp, email, and result for every admin login attempt, once logging is turned on) and the Scan History table under File Integrity Monitoring (every scan run, manual or scheduled, with file counts, threat counts, duration, and a link to the full report).

How Each Feature Actually Works

Two-Step Verification

This uses the standard TOTP (Time-based One-Time Password) protocol – the same one behind Google Authenticator, Authy, and similar apps. When an admin turns on 2FA, or is required to via sitewide enforcement, they scan a QR code into their authenticator app, which then generates a new six-digit code every 30 seconds. That code is entered alongside the normal password at each login.

Login Attempt Throttling

Every failed admin login is logged against the IP it came from. Once failures from one IP cross the configured limit inside the configured window, that IP is blocked from further attempts until the ban period runs out.

IP-Restricted Admin Access

Once turned on, every request to the admin panel is checked against an allow-list before OpenCart’s routing runs at all. Anyone not on the list is blocked outright – they never reach the login form.

Admin Directory Cloaking

The extension intercepts requests to your real admin path and returns a 404 unless the visitor has already reached a secret alias URL, which sets a cookie and quietly forwards them to the real location.

Server-Level Login Prompt

This adds a separate, browser-native prompt – rendered by the browser itself rather than an OpenCart form – in front of the admin panel, the storefront, or both, enforced at the web-server level before any PHP logic runs.

Web Application Firewall

The WAF checks incoming query parameters, POST fields, and cookies against a library of known injection, XSS, and path-traversal patterns. A match triggers an immediate 403 before the request reaches OpenCart’s controllers.

Security Response Headers

Each toggle here adds one specific header telling the visitor’s browser to enforce a particular behavior – refusing to render the page in an iframe, refusing to guess file types, forcing HTTPS, and so on.

Form Spam Filtering

When enabled, the extension injects the chosen CAPTCHA widget into the storefront contact and registration forms automatically, with no theme editing, and verifies the response server-side before accepting a submission

Copy/Scrape Deterrents

A set of client-side restrictions – disabling copy/cut/paste, right-click, text selection, view-source, and DevTools shortcuts – applied across the storefront, with an IP whitelist for staff who need normal browser behavior.

File Integrity Monitoring

A scheduled job, triggered by your server’s cron scheduler hitting a unique, token-protected URL, scans every file in your installation, compares it to a maintained baseline of known-good OpenCart core and common extension files, and flags anything new, missing, or modified.

1.0.0 Admin Protection

Two-Step Verification

Enable 2FA – turns on 2FA support; admins are guided to set up an authenticator app at their next login.

Whitelist IPs – addresses that skip 2FA entirely, even when enforcement is on. Add your office or home network as a safety net before enforcing.

Force 2FA – requires every non-whitelisted admin to set up 2FA before proceeding. Only enable after whitelisting a trusted IP or confirming the recovery link works.

ID – identifies the admin account.

2FA Status – shows whether that account currently has 2FA enrolled. Worth reviewing periodically, especially after staff changes.

Actions – resets a lost 2FA enrollment so the user can register a new device. Use right away if someone loses their authenticator phone.

Rolling out 2FA as optional first, then switching to enforced once everyone’s enrolled, is the recommended path – it stops account takeover from a leaked, guessed, or reused password, since the password alone is no longer enough. Never enforce 2FA sitewide without first whitelisting at least one trusted IP or confirming the recovery link works, and keep that whitelist short and reviewed regularly, since those addresses bypass 2FA completely. Add “reset 2FA” to your offboarding checklist for departing staff.

Brute Force Protection

Enable throttling – Temporarily blocks an IP after too many failed admin logins. Recommended on any live store.

Max retries – Failed attempts allowed before a ban triggers. 5 is a reasonable default.

Time window (seconds) – The rolling window in which failures are counted. 300 seconds (5 minutes) works for most stores.

Ban time (seconds) – How long a banned IP stays blocked; it expires automatically.

Whitelist IPs – Addresses never counted toward the limit or banned.

Start with moderate values, check your login log after a week, and tighten if repeated attack patterns keep showing up from varied IPs. This works best paired with 2FA rather than alone – throttling slows attackers down, 2FA stops them outright even if a password is eventually guessed. Bans clear themselves once the timer runs out; there’s no need to manually unban anyone.

IP-Restricted Admin Access

Restrict Admin Access by IP: Limits admin panel access to a specific list of trusted addresses.
How It Works: Once enabled, only listed IPs can reach the admin panel; every other visitor is blocked, including anyone attempting to reach the login page. Your current IP is added automatically the moment you enable this option, so you won’t lock yourself out.
Allowed IPs (required): Only addresses entered here are permitted through.

Admin Directory Cloaking

Hide Admin Directory Name: Replaces your real back-office URL with a secret alias, removing your store from the pool of sites automated scanners find by guessing common admin paths.
How It Works: When enabled, the direct admin URL returns a 404 response, and the panel is only reachable through the alias configured below.
Alias Name: 3 to 32 letters, digits, hyphens, or underscores. Treat this as a secret, the same as a password.

Server-Level Login Prompt (Admin)

Part of the OpenCart password protection plugin functionality built into this extension, this feature adds a browser-native authentication layer in front of the admin panel itself.

Enable HTTP Auth for the Admin: Adds a username/password prompt before the admin login screen even loads.
Username / Password: Credentials for the prompt; the password is stored encrypted and never saved in plain text.
Whitelist IPs: Addresses that skip the prompt entirely.
Server Compatibility (PHP-FPM/FastCGI): Adds a directive needed on servers where the authentication header isn’t otherwise passed through correctly.

Login Monitoring

A core feature of this OpenCart login security plugin, this tab provides visibility into every admin login attempt made against your store.

Email on Successful Login: Sends a notification whenever an admin logs in successfully.
Notification Email: Where alerts are sent; defaults to your store’s email address if left blank.
Log Admin Login Attempts: Records the IP address, time, email, and outcome for every login attempt to a downloadable log.
Login Attempt Log: The log itself; download buttons activate once entries exist.

2.0.0 Storefront Protection

Storefront Protection covers everything a customer or a bot interacts with directly. This is where the firewall, CAPTCHA, and security-header functionality of this OpenCart security extension all work side by side, each addressing a different customer-facing threat.

Web Application Firewall

Functioning as a dedicated OpenCart firewall extension, this feature automatically blocks requests carrying known SQL injection, cross-site scripting, or path-traversal patterns before they reach the storefront’s own code. No configuration is required beyond enabling it.

Security Response Headers

These settings add small, invisible instructions telling browsers how to handle your store safely. Most are safe to switch on and leave alone.

XSS Protection: An older safeguard against a specific attack type. Modern browsers have better built-in protection, but leaving this on doesn’t hurt; think of it as a backup lock for older browsers.
Clickjack Protection: Stops other sites from secretly displaying your store inside a hidden frame, a trick sometimes used to fool visitors into clicking things they didn’t mean to.
Content Sniffing Protection: Tells browsers to trust the file type your store declares instead of guessing, closing a path attackers sometimes exploit.
HTTPS-Only Browsing (HSTS): Tells browsers to always use the secure, encrypted version of your site, never the unsecured one.
Include Subdomains / Preload: Extends that rule to any subdomains you use, and can optionally register your store on a global list browsers check automatically.
Referrer Policy: Limits how much information browsers share about where a visitor came from when they click a link away from your store.
Permissions Policy: Controls which device features (camera, microphone, etc.) your store’s pages can request in a visitor’s browser.

Form Spam Filtering

1.0 Captcha

As a built-in OpenCart spam protection extension and OpenCart captcha extension, this feature keeps bots and spammers from flooding your contact and registration forms with junk submissions. It works with providers including Cloudflare Turnstile, Google reCAPTCHA, and hCaptcha, each verifying that a real visitor, not a bot, is submitting your form.

Enable Spam Protection: Adds a CAPTCHA check to your contact and registration forms, verified server-side so it can’t be bypassed.
Provider: Choose Turnstile, reCAPTCHA, or hCaptcha; each works a little differently, but all block automated spam.
Site Key / Secret Key: Codes from your chosen provider that connect your store securely.
Widget Theme: Controls how the CAPTCHA box looks (Auto, Light, or Dark).

2. [New] Honeypot Field

The Honeypot Field feature strengthens frontend security by embedding hidden fields within selected storefront forms. These fields stay completely invisible to human visitors, but any bot that automatically fills out every field on a form gives itself away instantly and gets blocked. It’s a low-overhead way to cut down on spam submissions, fraudulent account creation, and bot-driven login attempts, without adding any friction to the checkout or browsing experience for real shoppers.

Enable Honeypot: Switches Honeypot protection on for your store. Once active, a concealed field is silently inserted into each form you’ve selected below. Any submission where that hidden field gets filled in is flagged as bot activity and rejected before it reaches your database.

Protected Forms: Select which storefront forms Honeypot should guard. Available options include:

Registration: Prevents bots from mass-creating fake customer accounts.
Login: huts down scripted login attempts and credential-stuffing attacks.
Contact: Keeps your inbox free of bot-generated spam inquiries.
Newsletter: Blocks fake or automated subscription attempts. Note: Availability depends on your newsletter setup and active theme. If the form can’t be detected on a page, this protection is simply bypassed for that page.
Product Reviews: Shields your review/comment forms from spam entries. Note: Requires the Product Review module to be present; if the form isn’t detected due to theme differences, protection is skipped automatically.

3.0 Project Honeypot

Enable Project Honeypot: The master switch for this entire module. Turning it on means every incoming visitor’s IP address gets checked against Http:BL — Project Honeypot’s DNS-based reputation database — the moment they land on a page. Unlike the form-based Honeypot field, which only triggers on submission, this check happens proactively, before the visitor interacts with anything.

Access Key: A 12-character lowercase code assigned by Project Honeypot that links your HTTP:BL queries back to your registered account. It isn’t a security credential in the traditional sense — it can’t be used to access anything, it functions more like an attribution token so the service knows which site is making the request.

Observer-Only Mode: Runs the IP lookups and logs every classification, but takes no blocking action. Use this mode first to collect data and understand your traffic patterns before enforcing anything.

Log Scope: Determines the volume of data written to the Classification Log.

Flagged IPs only – A leaner option that records just the visitors Http:BL flags as risky.
All visitors – Captures every classification, including “Safe” entries, giving you a fuller picture of your overall traffic reputation. Because this fills up faster, records are automatically cleared after 7 days.

Ban Duration (seconds): Applies once you switch to Action Mode. Determines how long a flagged IP remains blocked before it can attempt access again.

Whitelist IPs: Add specific IP addresses here to exempt them from blocking entirely, regardless of what Http:BL reports.

Classification Log: A record of each visitor’s IP, its assigned classification (Safe, Suspicious, Harvester, or Comment Spammer), and whether the action taken was observation only or an actual block. Reviewing this log during the Observer phase helps you catch any false positives before committing to Action Mode

Content Protection

Enable Content Protection: Master toggle. This works as a deterrent only; a determined visitor can still bypass it using their browser’s developer tools.
Disable Copy/Cut/Paste: Blocks the keyboard shortcuts visitors would use to copy or paste page content.
Disable View Source (Ctrl+U): Blocks the shortcut for viewing a page’s source code.
Disable Right-Click Menu: Removes the context menu visitors could use to save images or copy content.
Disable Text Selection: Prevents highlighting or selecting text on the page.
Disable DevTools/Inspect (F12): Blocks the F12, Ctrl+Shift+I, and Ctrl+Shift+J shortcuts. Does not stop someone from opening DevTools through the browser’s own menu.
Whitelist IPs (Staff): Addresses that bypass all content-protection restrictions.

Storefront-Wide Login Prompt

Another layer of this OpenCart password protection plugin, this feature gates the entire storefront behind a browser-level username/password prompt, separate from the admin-side prompt described in Section 6.

Enable HTTP Auth for the Storefront: Adds a password prompt before any storefront page can be viewed.
Username / Password: Storefront-specific credentials, stored encrypted.
Whitelist IPs: Addresses that skip the storefront prompt entirely.

This is meant to keep a pre-launch or staging store private from search engines and casual visitors. The friction here is intentional, unlike the admin-side prompt. If the prompt keeps looping even with correct credentials on a PHP-FPM/FastCGI server, enable the compatibility setting under Admin Protection to resolve it; that setting applies to both the admin and storefront prompts.

3.0.0 File Integrity Monitoring

Settings

Enable File Integrity Monitoring: Master toggle; when off, the scan endpoint returns immediately without scanning anything.
Email Alert on New Threats: Sends an alert to the admin email whenever a scan finds something new or modified. Repeat alerts for known false positives are automatically suppressed.
Exclude Paths: Relative paths, one per line, to skip during scanning, useful for suppressing known false positives such as vendor directories.
Cron URL: A unique, token-protected URL that triggers a scan whenever your scheduler requests it.

To configure this correctly: enable the feature, turn on email alerts, and add the cron URL to your hosting control panel’s scheduled tasks (or your own crontab), typically scheduled for off-peak hours such as 2 a.m. Alerts fire only for genuinely new or changed threats. Once a file has been seen and either excluded or acknowledged, repeat alerts for that item are suppressed.

Scan History

ID: Sequential identifier for each scan run.
Date: When the scan was executed.
Triggered By: Manual or scheduled (cron).
Files Scanned: Total files checked in that run.
Threats: Number of new or modified files flagged.
Duration: How long the scan took.
Status: Completion state.
View Report: Opens the detailed findings for that scan.

This tab is purely historical and filterable by date range. No configuration is needed. Review your reports after the first few scheduled scans to learn what’s “normal” for your store, since most sites see a handful of flagged files tied to routine theme or extension updates. Once that baseline is established, genuinely unusual findings will stand out more clearly. Investigate any scan where the threat count jumps well past your baseline, even if individual files don’t look obviously malicious at first glance. That’s often exactly what an early-stage compromise looks like

Conclusion

OpenCart Advanced Security Manager brings together the protections most stores end up needing piecemeal – two-step verification, login throttling, a firewall, CAPTCHA, and file-integrity scanning – into one centrally configured screen. Set up thoughtfully, starting with login monitoring and the emergency recovery link before layering on more restrictive controls, it meaningfully cuts down the most common attack paths against OpenCart stores without adding friction for real customers or your own team.

The OpenCart Advanced Security Manager is also available on the OpenCart Marketplace, and store owners can access it the module by clicking here

OpenCart WhatsApp CRM and Order Notification Extension – Complete User Guide

1.0 Introduction

Order confirmation emails have a deliverability problem that most store owners do not think about until a customer complains. WhatsApp messages achieve open rates of 95 to 98 percent against email’s 20 to 25 percent, a difference that shows up directly in how many customers actually see the updates you send them. An OpenCart WhatsApp CRM Extension takes the manual work out of it, and alerts go to the customer at the right moment without your team needing to do anything.

The Knowband OpenCart WhatsApp CRM and Order Notification Extension ties your store to the WhatsApp Business API. New order confirmations and status change alerts are sent automatically. Your support team can chat with customers in real time from within the OpenCart admin. Promotional messages can also be sent to a segmented contact list at whatever time you schedule. A chat icon on your storefront puts your agents within reach of any visitor.

This guide documents every tab and field in the extension. Every setting is described exactly as it appears in the admin panel, whether you are doing a fresh setup or working through a specific configuration.

1.1 Who Is This OpenCart WhatsApp CRM Extension For

This extension suits:

Store owners who want WhatsApp order alerts to be sent automatically without needing a developer to set it up.
Support staff who need an OpenCart WhatsApp Live Chat Extension so they can reply to customer messages from the OpenCart backend.
Merchants who want an OpenCart WhatsApp Integration Extension that covers both automated notifications and outbound marketing campaigns in one place.
Agencies that are building OpenCart stores for clients who have asked for a WhatsApp Business API connected to their shop.

2.0 Installation Guide of the OpenCart WhatsApp Live Chat Extension

Step 1: Download the Extension

After purchasing, download the videomate.ocmod.zip file, which contains the complete video plugin for OpenCart.

1. Unzip the downloaded file; this will contain the videomate.ocmod.zip and necessary folders.
2. Go to the upload folder and locate the admin and catalog files.

3. Copy these files into the root directory of your OpenCart store

Step 2: Upload via Extension Installer

Go to Extensions > Extension Installer in your OpenCart admin panel.
Upload the videomate.ocmod.zip file.
Once installed, go to Extensions > Modifications, and click Refresh to apply changes.

Step 3: Assign User Permissions

Navigate to System > Users > User Groups, then edit your group and enable permissions for extension/module/videomate.

Step 4: Enable the Module

Navigate to Extensions > Extension Installer in your OpenCart admin dashboard.

2.3 Common Installation Issues

Upload fails: Your host is probably blocking the file size. Have them increase upload_max_filesize and post_max_size in the PHP settings to at least 32 MB.

Emails not going out: Go to System, then Settings, then the Mail tab. The extension uses the store’s default mail configuration unless you have set a different one at the form level.

Page looks wrong: Do a browser cache clear. Then reset the OpenCart theme cache using the blue cog icon on the Dashboard refresh panel.

3.0 Admin Panel Overview

The OpenCart WhatsApp CRM Extension adds its own section to the OpenCart admin sidebar after installation. Each tab in that section has a specific job:

Module/API Settings: This is where your WhatsApp Business API credentials go, along with the webhook configuration.
Templates: Where you write and submit templates to WhatsApp for review.
Order Settings: Decides which order-based WhatsApp alerts are active and when they are sent.
Order Status Trigger: Links each order status to the template that gets sent for it.
CRM: The live chat panel for two-way conversations with customers.
Contacts: Your full contact database, with import and export built in.
Lists: Groups of contacts that promotions get sent to.
Promotions: Builds and schedules outbound campaigns to your contact lists.
Agents: The support agents your visitors see in the storefront chat pop-up.
Chatbox Settings: Settings that control the floating WhatsApp icon on your storefront.
Message Logs: A timestamped record of all messages sent and received through the extension.

4.0 Module/API Settings of the OpenCart WhatsApp CRM Module

Nothing in the OpenCart WhatsApp Business API Extension works until this tab is filled in. Four credentials are required, and all four must be correct before the extension can send or receive anything.

4.1 WhatsApp API Settings

Enable Extension: You can easily enable/disable the plugin with this toggle. Turn it off, and the extension stops sending messages, and the storefront chatbox is removed.

Facebook App ID: Pull this from the Meta Developer Console. It identifies which Meta app the API request is coming from.

Facebook Access Token: This needs to be a permanent token, not the short-lived one shown in the API Setup tab. Head to Meta Business Settings, add a System User, give it full control over your app and WABA, then generate a token. The three permissions you need are whatsapp_business_messaging, whatsapp_business_management, and business_management. That token goes here.

WhatsApp Business Account ID (WABA ID): Your WABA ID lives in the Meta Developer Console, inside the WhatsApp section of your app. Copy it from there.

Phone Number: The registered WhatsApp Business number you want all messages to come from. Pick it from the dropdown.

Save the form once all four fields are filled. Any field left empty or entered incorrectly shows a validation error right away. An expired access token does the same.

4.2 Webhook Setup

Below the credential fields, the Configuration Information section shows a Webhook URL and a Verify Token that are specific to your store. These go into the Meta Developer Console.

In your Meta app, go to WhatsApp, then Configuration, and paste the two values into the webhook setup fields. After that, the extension picks up incoming messages and template status updates on its own.

The webhook is not strictly required to get started. If it is not set up yet, you can click Sync Templates inside the Message Templates tab at any time to manually pull the latest approval status from WhatsApp.

5.0 Order Settings

The Order Settings tab is where you control when the OpenCart WhatsApp Order Notification Extension sends messages and which templates it uses for them.

5.1 WhatsApp Order Settings

Enable New Order Message: When this is on, a WhatsApp message goes out to the customer every time a new order lands in your store.

Enable Order Status Message: When this is on, customers get a WhatsApp update each time their order status changes. Turning this on also adds a WhatsApp number field to the customer address form so shoppers can put in the number where they want to receive those updates.

5.2 New Order Message Templates

This section lists your store languages. For each one, pick the approved Utility template that sends when a new order is placed. The dropdown only pulls in Utility templates that WhatsApp has already approved.

If the dropdown has nothing in it, your templates are either sitting in the queue waiting on WhatsApp review, or they were categorised as Marketing instead of Utility. Create a Utility template in the Message Templates tab, wait for approval, then come back here and save your selection.

6.0 Message Templates

Templates used anywhere in the OpenCart WhatsApp CRM Extension are created and submitted here. WhatsApp has to approve a template before it can be assigned to any message flow. Both submission and status checking happen inside this tab.

6.1 Templates List

Every template tied to your WhatsApp Business Account shows up in this table. The columns cover Template ID, Name, Use Case, Category, Language, Status, and the date the template was created. Status can be Pending, Approved, or Rejected.

The Sync Templates button pulls the latest status data from WhatsApp whenever you need it. Search fields at the top let you filter by template name, category, language, or a date range.

6.2 Creating a New Template

Name: Use lowercase letters and underscores only. Spaces and special characters are not accepted.

Use Case: Pick the use case that fits: For Orders, For Marketing, or For Customers.

Category: Utility or Marketing. Any template assigned to order notifications has to be in the Utility category. WhatsApp reviews the body text and may move a template to Marketing if it reads like a promotion.

Language: Choose the language the template is written in. If your store serves customers in multiple languages, you will need a separate template for each one.

Header Type: Not required. You can leave it as No Header or add a Text, Image, Video, or Document header if the message needs one.

Message Body: The message itself. Bold, italic, and strikethrough options are in the editor toolbar. Use Insert Variable to drop in things like the customer’s name, their order ID, or the order total. The Body Preview below the editor shows you how the finished message reads as you build it.

Footer: An optional line of smaller text that sits below the main body.

Enable CTA Button: Switch this on to attach a CTA button to the message. You will need to fill in the Button Text and the URL it points to.

Hit Save when the template is ready. WhatsApp gets it for review right away. Straightforward templates are usually clear in a few minutes. More complex ones can take a few hours. Once it is approved, it shows up in Order Settings, Order Status Templates, and the CRM template list.

7.0 Order Status Triggers

Each order status in OpenCart can be paired with a Utility template in this tab. When an order hits a status that has a template assigned, the extension sends that message to the customer as an automated WhatsApp update.

Every status your store uses is listed in the table: Awaiting check payment, Payment accepted, Processing in progress, Shipped, Delivered, Canceled, Refunded, and the rest. Each row shows whether notifications are on or off and which template is currently mapped to that status.

Hit Edit on any row to change it. Toggle Enable WhatsApp Notification on, pick a Utility template for each store language from the dropdown, and save. The row reflects the change straight away.

8.0 CRM: Live Two-Way Chat in Best WhatsApp CRM Extension

The CRM tab is the live chat section of this OpenCart WhatsApp Live Chat Extension. Your contact threads sit in a sidebar on the left. Click on any one of them to bring up the full conversation on the right.

Two tabs are at the bottom of the chat window: Message and Template. The message is for free-text replies, though this only works during the 24-hour window that opens when a customer sends you something first. After that window closes, swap to the Template tab. Approved Marketing templates can go out from there at any time.

Automated order alerts sent by the extension also show up inside the relevant contact thread. That way, your support team always has the full picture of what the customer received before they start a reply.

9.0 Promotions

The Promotions tab is for outbound WhatsApp campaigns. You pick the list of contacts, choose the template, set when it goes out, and the extension takes it from there.

9.1 Creating a Promotion

Name: An internal name so you can tell this campaign apart from others. It is not included in the message the customer receives.

Contact List: Choose which WhatsApp List this campaign targets. Every contact on that list will get the message.

Template: Pick an approved Marketing template from the dropdown. Marketing category templates are the only ones that appear here.

Schedule at: The date and time you want the campaign to go out. It has to be in the future. If you leave this blank, the campaign runs on the next CRON trigger instead.

Save it. The campaign will sit in the list with a scheduled status. The CRON command at the top of the Promotions page needs to be added to your server if you want campaigns to send automatically. It checks for pending campaigns every minute.

After a campaign runs, the Sent and Failed numbers fill in. The WhatsApp Business API bills you per message, so it is worth sending to a small group of 10 to 20 contacts first, just to see what the actual cost looks like before you go to the full list.

10.0 WhatsApp Contacts

Every phone number the extension can message is stored here. A contact needs a phone number and a name at a minimum. Linking to an OpenCart customer account is optional.

10.1 Adding a Contact Manually

Phone Number: Start with the country code, no leading zero, no spaces or dashes. An Indian number, for example, would be entered as 919310436362.

Name: Whatever name you want displayed for this contact in the extension.

Click Save when done.

10.2 Importing Contacts in Bulk

Click Download Template to get the CSV file in the right format. Add your contact data to it, come back to WhatsApp Contacts, and click Import Contacts to upload the file. Numbers that are already in the extension get their records updated. Numbers that are not in there yet get added as new contacts. Export to Excel and Export to CSV are both available if you need to pull the whole contact list out.

11.0 WhatsApp Lists

A WhatsApp List is just a named group of contacts. Promotions target one list at a time. To create one, click Add new list, type a name, and save it. If you mark a list as Default, new contacts get added to it automatically.

You assign contacts to lists from the WhatsApp Contacts tab. One contact can be in more than one list at the same time.

12.0 Chatbox Settings

This tab is for the floating WhatsApp icon on your storefront. When a visitor clicks it, a pop-up appears listing the agents you have set up. They tap Chat next to whoever they want to speak with, and it opens a WhatsApp conversation on their phone.

Enable Chatbox: Switch this on to show the icon on the storefront, or off to hide it.

Icon Position: Where the icon sits on the screen. Options include Bottom Right and Bottom Left.

Theme Color: The main color used for the icon background and the pop-up header. It defaults to WhatsApp green, which is #25D366.

Header Title: The text shown at the top of the chat pop-up. The placeholder example is “Chat with us”; enter whatever heading you want your visitors to see when the popup opens.

Sub Title: A short line shown below the header title. Use this to set response time expectations or any brief supporting text.

Greeting Message: The opening message displayed to visitors inside the chat pop-up before they select an agent. Accepts plain text. A WhatsApp emoji picker and formatting options are available in the bottom right of the text area.

Online Text: The label shown on agent cards when the agent is available. Defaults to “Online.”

Offline Text: The label shown on agent cards when the agent is not available. Defaults to “Offline.”

Hit Save Settings once you have made your changes.

13.0 WhatsApp Agents

Agents are the people your storefront visitors see in the chat pop-up. Each agent card has a name, a department or role, and a Chat button. When a visitor taps that button, it opens a WhatsApp conversation with that agent’s number on their device.

Active: Controls whether this agent is visible in the storefront popup.

Agent Name: The name shown on the agent card. Capped at 50 characters.

Contact Number: The agent’s WhatsApp number, country code included (for example, +919876543210). If you use the same number as the one in the API Settings, conversations from this agent also appear inside the CRM tab.

Department: The team name or role shown under the agent’s name. Up to 50 characters, and it can be set differently per language.

Display Order: A number that controls where this agent appears in the pop-up. The lower the number, the higher up the agent shows.

Avatar Type: Pick a Predefined Avatar from the available options, or upload an image of your own.

14.0 Message Logs

The Message Logs tab keeps a record of every message that has passed through the OpenCart WhatsApp Messaging Extension, both sent and received. Each row tells you the Direction, the phone number it involved, the template used if any, a preview of the message text, the WhatsApp Message ID, the delivery status, and the timestamp.

Order alerts, CRM replies, and campaign messages all end up in this list. A success status means the WhatsApp API received and accepted the message. The date range, phone number, and template filters make it easy to find a specific message. When something is not delivering the way it should, this tab is the right place to start looking.

15.0 Frequently Asked Questions

Q: What is the OpenCart WhatsApp CRM Extension, and what does it do?

The Knowband OpenCart WhatsApp CRM and Order Notification Extension connects your OpenCart store to the WhatsApp Business API. Order confirmations and status change alerts go to customers on WhatsApp automatically. Your team handles live customer conversations from inside the OpenCart admin through the CRM tab. You can run scheduled WhatsApp campaigns to contact lists through the Promotions tab. A storefront chatbox lets visitors tap through to your support agents on WhatsApp directly.

Q: Does the OpenCart WhatsApp Messaging Extension require a WhatsApp Business Account?

Yes, it does. The OpenCart WhatsApp CRM Extension needs a WhatsApp Business Account, a phone number registered as a WhatsApp Business number, and a Meta Developer App that has WhatsApp Business API access set up. All three are needed before the API Settings tab can be completed and before the extension can send anything.

Q: How does the OpenCart WhatsApp Order Notification Extension send alerts when a new order is placed?

When Enable New Order Message is switched on in Order Settings, the OpenCart WhatsApp Order Status Extension sends an approved Utility template to the customer each time an order goes through. For status updates, turn on Enable Order Status Message as well. That puts a WhatsApp number field on the customer address form. Once a customer fills it in and their order moves to a status that has a template mapped in Order Status Templates, the message goes out to that number straight away.

Q: Why are no templates showing in the Order Settings dropdown of the OpenCart WhatsApp CRM Extension?

Order Settings only lists Utility templates that have been approved by WhatsApp. An empty dropdown usually means templates are still in the review queue or sitting in the Marketing category by mistake. Head to Message Templates, build a Utility template, wait for the approval to land, then go back to Order Settings. The Sync Templates button is there if you want to pull the latest approval status without waiting for the webhook.

Q: How does the live chat work inside the OpenCart WhatsApp Live Chat Extension?

The CRM tab in the OpenCart WhatsApp Messaging Extension shows all contact threads on the left side. Click a contact to open the conversation. Use the Message tab to type a reply while the 24-hour window from the customer’s last message is still open. Once that closes, the Template tab is the way to reach them; any approved Marketing template can be sent from there, regardless of when the customer last wrote. Automated order alerts from the extension appear in the thread too, so your team always has context.

Q: Can I run WhatsApp marketing promotions through the OpenCart WhatsApp CRM Extension?

Yes, through the Promotions tab. Go there, click Add new promotion, give it a name, pick a Target List, choose a Marketing template, and set a time in the future for it to go out. The CRON command on the Promotions page needs to be on your server for campaigns to send automatically; it checks every minute for anything due. Before sending to your whole list, send it at a small group of 10 to 20 contacts first to see what the API costs look like.

Q: How does the OpenCart WhatsApp Business API Extension connect to WhatsApp?

The OpenCart WhatsApp Order Status Extension also available on Opencart Marketplace with Price $49.99, connects through four fields in the Module/API Settings tab: your Facebook App ID, a permanent Access Token, your WhatsApp Business Account ID (WABA ID), and your registered phone number. On top of that, you paste the Webhook URL and Verify Token shown in the Configuration Information panel into your Meta Developer Console. With those two steps done, the OpenCart WhatsApp Business API Extension handles message sending, template approval tracking, and incoming messages without any further manual input.

Q: Can I bring existing contacts into the OpenCart WhatsApp Order Status Extension from a spreadsheet?

Yes. Open the WhatsApp Contacts tab and click Download Template to get the CSV in the right layout. Put your contact data into it, then upload it using Import Contacts. If a phone number is already in the extension, that contact’s record gets updated. Anything new gets added. Once the contacts are in, you can assign them to WhatsApp Lists and target them in your next promotion.

Q: A template was rejected inside the OpenCart WhatsApp CRM Extension. What now?

Go to Message Templates and look at what the rejected template says. WhatsApp will reject templates that put sales or promotional language inside a Utility template, contain anything inaccurate, or go against its commerce policies. Delete the rejected one, fix whatever the issue was in the body text, and submit a fresh template. If the tone was the problem, write the body more like a factual update and less like a sales message.

Q: Which versions of OpenCart work with the Knowband WhatsApp CRM Extension?

The Knowband OpenCart WhatsApp CRM Extension runs on OpenCart 3.x. If you need compatibility details for versions released after this guide was written, the extension product page on the Knowband website will have the most current information. You can also contact the Knowband support team directly.

16.0 Conclusion

The Knowband OpenCart WhatsApp CRM Extension, also known as the OpenCart WhatsApp CRM and Order Notification Extension, is a full OpenCart WhatsApp Integration Extension. Order alerts go out on their own. Live support runs through the CRM tab. Campaigns reach targeted contact lists on a schedule you define.

The only thing that happens outside the extension is pulling your API credentials from the Meta Developer Console. After that, templates, order mappings, contact lists, agent profiles, and promotions are all handled from inside OpenCart.

For help getting set up or questions about any feature, the Knowband support team is at support@knowband.com. There are also documentation pages and setup videos on the Knowband website.

OpenCart SocialAI Pro Extension Complete User Manual

Running a busy OpenCart store usually means someone has to sit down, look at the catalogue, and write captions for Facebook, LinkedIn, and X every single time a product launches or comes back into stock. The Opencart AI Social Media Post Generator Extension, also known as the OpenCart SocialAI Pro Extension, removes that issue by linking your frontend catalogue straight to an AI writing engine and to your connected social accounts, so posts can be written and published without anyone typing a single line of copy.

Three tasks happen inside this one extension automatically: the AI writes the caption, a rule decides when that caption goes out and to which network, and a history log keeps a record of everything that was ever generated, whether it was published, held as a draft, or scheduled for later.

1. 0 Installation of the Opencart Social Media Automation Extension

The setup below installs the Opencart Social Media Automation Extension the same way as any other OpenCart module. From the OpenCart admin, go to Extensions and open the Installer screen. Upload the ocmod.zip file exactly as it was downloaded after purchase.

Open the FTP, copy the files under the upload folder to the site root file.

Go to the modification, refresh and clear the cache.

2.0 Admin Panel Overview

Once configuration opens for the first time, three tabs are visible across the top: General Settings, Rules, and Post History. Each one handles a different part of the workflow, and together they make up the entire Opencart AI Social Media Post Generator Extension experience.

General Settings is where the AI provider gets connected, where API keys live, and where each social account gets authorised through OAuth.

Rules are the automation layer; this is where a store owner decides which products qualify, what has to happen for a post to fire, which platforms receive it, and what tone the AI should write in.

Every post the extension has ever produced shows up here with its status, the platform it targeted, which AI engine wrote it, and whether a rule triggered it or a human did. A post can also be started from scratch directly inside this tab, without involving a rule at all.

3.0 General Setting of Opencart AI Social Media Post Generator

Enable Module: Enable or disable the functionality on the frontend using the toggle.

Choosing an AI Provider: Three engines are available from a single dropdown, and a store can only run one of them at a time:

OpenAI: The OpenAI ChatGPT choices include GPT-5, GPT-5 Mini, GPT-5 Nano, GPT-4.1, GPT-4.1 Mini, and GPT-4o.
Google Gemini: Gemini 3 Pro, Gemini 2.5 Pro, Gemini 3.5 Flash, and Gemini 2.5 Flash are all selectable for stores that would rather stay inside Google’s ecosystem.
Anthropic Claude: Claude Opus 4.8, Claude Sonnet 4.6, and Claude Haiku 4.5 are offered for anyone who already has Claude API access or simply prefers its writing style.

Switching providers takes effect on the very next post generated; it doesn’t touch anything already sitting in Post History from before the change.

Entering the API Key: Store admins must paste the key for whichever provider was chosen above into this field. It needs to be a real, currently active key with either prepaid credit or billing turned on. A key that’s expired or been revoked will only show its error the first time the extension actually tries to generate something. The key itself stays in your store’s own database and is sent directly from your server to the provider, with nothing routed through a third party.

Temperature Slider: Store administrators can use the Temperature Slider to control the creativity and variation of AI-generated social media content. Lower values generate more consistent and predictable marketing copy, while higher values produce more creative, engaging, and diverse social media posts.

Token Ceiling: This shows how many tokens a single generation request is allowed to use, somewhere between 100 and 2,000.

Handles for X: Two optional fields sit here: one for the store’s own X handle, one for whoever is credited as the content’s author. Neither has any bearing on whether a post actually goes out; leave both blank if there’s no X presence to reference.

Linking Each Social Account: All three networks get connected from this same General Settings tab, and the Opencart Auto Publish Facebook LinkedIn Extension functionality handles each one through its own dedicated authorization flow.

Facebook: Click the Facebook connect button and a popup opens asking for posting permission on a Page. If more than one Page is managed under that account, a picker shows up so the right one can be chosen. As soon as that’s confirmed, the settings screen updates to show which Page is now linked: this is the Opencart Facebook Auto Post Extension side of the setup, and it’s usually the fastest of the three to finish.

LinkedIn: Open the LinkedIn Developer Portal first and find the app that was registered there. The Auth tab on that app holds the Client ID and Client Secret: copy both into the matching fields here. Before clicking the Connect button on this end, take the redirect URL shown in the extension and add it to the authorised redirect list inside the LinkedIn app, save that, and only then come back and finish authorising. This is the piece marketed as the Opencart LinkedIn Product Post Extension capability, and it’s the one most likely to need a second look if posts aren’t appearing: a mismatched redirect URL is the usual culprit.

X (Twitter): Inside the X Developer Portal, open Keys and Tokens for the registered app and copy the Client ID and Client Secret across into the extension. The redirect URL needs to be added to that app’s callback list too, the same way it does for LinkedIn. One thing that trips people up: the X app must have write permission turned on, not just read, or the whole Opencart Twitter Auto Post Extension connection attempt will fail at the authorisation step.

Instagram: Instagram posting isn’t part of this release. An Opencart Instagram Auto Post Extension capability is on the roadmap for a future update, but for now the extension only authorises and publishes to Facebook, LinkedIn, and X.

3.0 How to Create Rules To Generate Social Media Posts

Rule Name
Store administrators can use this setting to assign a unique and descriptive rule name for easy identification and tracking within the OpenCart AI Social Media Automation Extension.

Products / Categories / Manufacturer
This feature allows merchants to define the product scope for automated social media content generation based on specific products, categories, or manufacturers.

Trigger
Store administrators can configure trigger events that automatically initiate AI-powered social media post generation and publishing workflows.

New Product
Automatically generates and publishes social media content when a new product is added to the OpenCart store.

Back in Stock
Automatically creates promotional social media posts when an out-of-stock product becomes available again.

Manual
Allows administrators to generate social media content manually without relying on automated trigger conditions.

Platforms
Merchants can select one or more connected social media platforms, including Facebook, LinkedIn, and X (Twitter), for content distribution.

Publish Mode
This feature allows administrators to define how and when generated social media content is published across selected platforms.

Immediate
Publishes AI-generated social media posts instantly after content generation without requiring manual review.

Manual (Draft)
Saves generated content as a draft, allowing administrators to review, edit, and approve posts before publication.

Scheduled
Automatically schedules social media posts within a defined time range to maintain consistent content distribution and engagement.

Scheduled Delay Window
Administrators can define a minimum and maximum publishing delay to automatically distribute social media content over a specified period.

Brand Name

This setting allows merchants to specify their brand name, enabling AI-generated content to maintain consistent brand messaging.

Industry

Store administrators can define their business industry to help the AI generate relevant and industry-specific social media content.

Tone of Voice

This feature enables merchants to customize the writing style of AI-generated posts to align with their brand communication strategy.

Emoji Usage

Administrators can control emoji usage within generated content to ensure consistency with brand and platform requirements.

Hashtag Groups

Merchants can define predefined hashtag groups to improve social media visibility, discoverability, and audience engagement.

Word Blacklist

This feature allows administrators to restrict specific words, phrases, competitor names, or sensitive terms from appearing in generated content.

Per-Platform CTA

Store owners can configure platform-specific call-to-action messages to improve engagement and conversion rates across social media channels.

Custom Instructions

Administrators can provide additional content-generation guidelines to ensure AI-generated posts align with specific marketing objectives.

Max Posts Per Cron Run / Per Day / Per Product Per Day

This feature enables merchants to control social media publishing frequency and prevent excessive or duplicate content generation.

Saving and Testing Rules

Save Rule

Store administrators can save automation rules to activate AI-driven social media content generation based on configured triggers and publishing conditions.

Generate / Run Now

This feature allows merchants to test and execute a rule instantly, generating social media content for all eligible products and selected platforms.

4.0 Post History Log in Opencart AI Social Media Post Generator Extension

Post History Overview

Store administrators can use the Post History Log to monitor, review, and manage all AI-generated social media content from a centralised dashboard.

What’s Recorded

The system records essential details including post ID, generation date, platform, product, publication status, AI provider, and associated automation rule.

Create Post

Merchants can manually generate AI-powered social media content for selected products without creating an automation rule.

Manual Post Generation

This feature enables administrators to create, review, edit, schedule, or publish custom social media content directly from the Post History section.

5.0 Steps to Generate the API Key for Opencart SocialAI Pro Plugin

For Claude API:

Visit Anthropic’s website, and click “Start Building”.
Create an account, access your Dashboard, generate an API key, and save it securely.

For Gemini API:

To access the API, visit the Google AI Studio website.
Click “Get API key,” accept the terms of service, create your key, and paste it into the module’s configuration settings.

For ChatGPT API:

Obtain an OpenAI API key and configure it within the module settings.
Click on your profile (top-right) → “View API keys” → “Create a new secret key”.
Copy the key immediately and store it safely.

Conclusion

The Opencart AI Social Media Post Generator Extension covers the entire path from product data to a published post without requiring anyone to write captions by hand. As a complete Opencart Social Media Automation Extension, it handles the writing through AI, the timing and platform targeting through rules, and the record-keeping through its history log, all from inside the same OpenCart admin panel store owners already use daily.

Whether it’s running as an Opencart Auto Publish Facebook LinkedIn Extension pushing posts out the moment they’re generated, or as an Opencart Social Media Auto Scheduler Extension spacing a large batch out naturally over several days, editorial control never leaves the store owner’s hands: drafts can always be checked, edited, or held back before anything goes public.

For anyone evaluating it specifically as an Opencart Social Media Marketing Automation Extension, the short version is this: one AI engine writes on-brand copy, one rules engine decides when and where it goes, and one history log keeps track of all of it, which together cover the bulk of a catalogue’s day-to-day social presence without ongoing manual effort.

Opencart SocialAI Pro Extension is also available on Opencart Marketplace – https://www.opencart.com/index.php?route=marketplace/extension/info&member_token=a82287f721dce288db62f253df7a972b&extension_id=48624

Support questions, setup help, or configuration requests can go to support@knowband.com. Release notes and further documentation are maintained on the Knowband website.

OpenCart Order, Customer & Address Import Export Extension User Manual

Every growing OpenCart store reaches a point where data management becomes its own full-time job. Order records pile up across multiple systems. Customer accounts live in one place while fulfilment teams need them somewhere else. A warehouse partner expects a structured file every morning, and right now someone on your team is logging in manually to make that happen.

The Knowband OpenCart Order, Customer & Address Import Export Extension , the most capable OpenCart import export extension for orders, customers, and addresses , is the opencart import export extension for order and customer data , is developed to remove that manual overhead entirely. It gives store administrators of this proven OpenCart import export extension a single, centralised control panel to move order records, registered customer profiles, and delivery address data in and out of OpenCart, in any direction, on any schedule, to any destination. No custom development. No third-party middleware. No spreadsheet gymnastics every time a partner changes their preferred file format.

What sets this OpenCart data migration module apart from generic data tools is its native understanding of OpenCart’s data structure. It does not simply read and write flat files. It resolves entity relationships across stores, validates every record before touching the database, and keeps a timestamped log of every operation so your team always knows exactly what moved, when, and whether it succeeded.

This user guide documents every feature of the Knowband OpenCart import/export extension in full detail. Admins can follow it from start to finish for initial setup, or jump to the relevant section whenever you need to configure a specific workflow.

1.0 Installation Steps

Log into your OpenCart administration panel. From the top navigation, go to Extensions and then select Extension Installer. On the installer page, click the Upload button and select the kborderimportexport.ocmod file. The installer processes the file without requiring any additional steps from you.

When the upload finishes, navigate to Extensions, select Extensions from the submenu, and choose Modules from the category dropdown. Find the Order, Customer & Address Import Export entry in the list and click Install. Once installation completes, click the Edit button to open the main configuration panel.

If the module does not appear in the list after installation, go to Extensions and click Modifications, then hit the Refresh button in the top right corner. Return to the modules list and search again.

2.0 Admin Panel Configuration

After installation, the OpenCart order import/export extension introduces four distinct areas to your OpenCart back office. Each handles a separate part of the data transfer workflow.

Settings Panel: The global configuration hub. This is where you set performance preferences, download starter template files, manage size limits, and retrieve the scheduled automation URLs needed for task-scheduler setup.

Export Profile: Build, manage, and run export profiles. A guided setup process walks you through every configuration choice, from which fields to include to where the finished file should be delivered. This is the core of OpenCart’s bulk import/export capability.

Import Profile: Build, manage, and run import profiles. Handles one-time manual imports from local files and recurring automated imports from remote servers, making it a complete OpenCart CSV import customers, orders, and OpenCart customer migration solution.

Activity Log : A permanent record of every import and export operation the extension has performed. Includes run status, record counts, file references, and detailed error information for any operation that did not complete cleanly

3.1 General Settings

The Settings Panel is divided into four sub-sections. Work through each one during initial setup before creating your first import or export profile.

Enable/Disable Extension: Disabling the extension immediately pauses all scheduled automation. Any import or export profiles with scheduling enabled stop firing until the extension is re-enabled. Manual operations initiated directly from the Export Center or Import Center are unaffected by this switch.

Column Display Limit: Define how many mapping columns are shown simultaneously on the import mapping screen. The range is 1 to 20 columns. Files with more columns than this limit are still fully supported; the mapping interface provides navigation controls to move through all available columns in pages.

Preview Row Limit: Set how many data rows from your import file appear in the live preview section of the mapping screen. Increase this number when you want a broader sample of your data visible before committing to the import. The range is 1 to 50 rows.

Batch Processing Size: Determine how many records are processed in each cycle during an import run. The range spans 10 to 500 records per batch. If you are on a shared hosting environment where PHP execution times are tightly capped, set this to 50 or below to avoid timeout errors during large OpenCart bulk import export operations. Dedicated server environments can use higher values to complete imports faster.

Save your changes before moving to the next sub-section.

3.2 Template File Library

Before preparing your first import file, download the relevant sample template from this sub-section. Templates are available for all three data entities and all four supported formats , making this the most versatile OpenCart import/export CSV XLSX JSON XML toolkit available:

Order templates: CSV, XLSX, JSON, XML
Customer templates: CSV, XLSX, JSON, XML
Address templates: CSV, XLSX, JSON, XML

Use the XLSX template if you plan to export OpenCart orders to Excel format for review and editing before importing. Use CSV templates when integrating with third-party logistics platforms, ERPs, or automated data pipelines that expect OpenCart export orders in CSV format. The OpenCart export orders to CSV capability supports comma, semicolon, and pipe delimiters.

3.3 File Size and Volume Limits

Records Per Export File controls how many records the OpenCart order export module includes in a single generated file. Adjust this based on your server’s available memory. The range is 100 to 50,000 records. For very large datasets, use the date range filter in your export configuration to split output across multiple files rather than raising this limit to its maximum.

Maximum Import File Size controls the largest file the import engine will accept. The range is 1 MB to 200 MB. Set this in line with what your server’s PHP configuration allows, or slightly below it.

Save your changes before continuing.

3.4 Automation and Scheduled Tasks in Opencart Customer Migration Extension

This sub-section is where you find the three scheduler-ready URLs that power the extension’s OpenCart automated data export and import capabilities. Each URL is unique to your installation and includes an authentication token. Copy them into your server’s task scheduler to activate automated operations.

Temporary File Cleanup URL: Runs a housekeeping routine that deletes old import files from the server. Use the adjacent setting to specify how many days to keep files before they are eligible for deletion (range: 1 to 30 days). A daily schedule at an off-peak hour like 2:00 AM is typical.

Export Automation URL: Triggers every export profile that has been configured with scheduling enabled. This is how you set up OpenCart scheduled export operations , call this URL as frequently as your business requires: every hour, every six hours, daily, or weekly. All enabled export profiles run in sequence each time the URL fires.

Import Automation URL: Triggers every import profile that uses a remote FTP or SFTP source and has scheduling enabled. Profiles configured to use a manually uploaded file are ignored when this URL runs. A daily early-morning schedule works well for most overnight data feed scenarios.

All three URLs reject any request that does not carry the correct authentication token, so they are safe to expose to a task scheduler without additional access controls.

4.0 Export Feature, Full Setup Guide

The Export Feature in Opencart Customer Migration Extension displays a table of all saved export profiles. Each row shows the profile name, the entity type, the file format, and the outcome of the most recent run. From this view, you can launch an immediate export on any profile, open an existing profile for editing, or create a new one using the setup wizard.

4.1 Step One: Basic Configuration and Delivery Options

Profile Name: Give this profile a name that will make sense to you and your team six months from now. Something like “Daily Fulfilled Orders to WMS” or “Weekly Customer Backup XLSX” communicates the purpose at a glance.

Output Filename: The base name used for the generated file. File extension is added automatically. You can include dynamic tokens in this field to make filenames descriptive and date-stamped.

Entity Type: Choose which category of data this profile exports: Orders, Customers, or Addresses. The OpenCart address import export system handles all three entity types through this single unified interface.

File Format: Four options are available. CSV and XLSX work directly with Excel, Google Sheets, and most data tools with no conversion needed. JSON and XML are better suited to API integrations, ERPs, and software systems that consume structured data feeds.

Store Scope: In multi-store OpenCart setups, use this field to restrict the export to a single storefront. Leave it on the all-stores default to pull records from every store in your installation.

Date Window: Optionally limit the export to records created within a specific date range. This is particularly useful for daily or weekly OpenCart scheduled export workflows where you only want records from the most recent period. Leave it blank when you need the full historical dataset.

Sort Preference: Controls the row order in your output file. Available sort keys include order ID, reference number, creation date, modification date, total order value, and order status. Choose an ascending or descending direction for each.

Column Block Controls: Three independent toggles let you expand or collapse entire sections of the output:

The invoice address toggle adds all billing address fields when enabled.

The delivery address toggle adds all shipping address fields when enabled.

The payment detail toggle adds payment amount, currency, method name, and transaction reference columns when enabled. When disabled, only the payment method name is exported.

Use these toggles to strip out data that the receiving system does not need, reducing file size and avoiding unnecessary transmission of financial data.

Scheduled Automation – Enable this toggle to include this profile in the automated OpenCart export orders run triggered by the Export Automation URL. When active, every time the URL fires, this profile generates its output file and either saves it locally or pushes it to the configured remote destination.

File Destination: Local storage saves the file to the server and makes it available for download from the Activity Log. Remote delivery via OpenCart FTP export orders or SFTP pushes the file to an external server after each run. When remote delivery is selected, a local backup copy is also retained.

Remote Server Configuration (visible when remote delivery is selected):

Select the transfer protocol based on your partner’s server requirements. OpenCart SFTP export using SSH key exchange is the most secure option and the recommended default for any production environment handling customer or payment data. FTPS provides encryption over the standard FTP protocol. Standard FTP should only be used in internal network scenarios where security is controlled at the network level.

The port field updates automatically when you change the protocol selection: 21 for FTP, 990 for FTPS, and 22 for SFTP.

Enter the server hostname or IP address, username, and password. Credentials are stored in encrypted form. Provide the full absolute path to the destination directory on the remote server.

Passive mode is enabled by default. Use the Test Connection button before saving the profile to confirm the directory is accessible.

Field Delimiter: For CSV output, select the character that separates field values. Comma is the standard for most English-locale applications. Semicolon is the correct choice for European Excel locales.

Multi-Value Separator: Some order fields contain multiple values in a single cell, such as product options or applied discount codes. Pipe is the most unambiguous choice.

Order Filtering Options: The export wizard provides five narrowing filters:

Order Status: Narrows the export to orders currently in one or more selected status states, ideal for teams that need to export OpenCart orders to Excel for reporting only completed or pending records.
Shipping Method: Filters by carrier name, enabling logistics-specific exports for individual fulfilment partners.
Currency: Filters by transaction currency code, useful for finance teams working with region-specific revenue data.
Payment Method: Filters by the payment module used at checkout.
Order Value Range: Sets a minimum and maximum on the total paid amount, allowing you to isolate high-value orders.

Click Next to move to field selection.

4.2 Step Two: Choosing Which Fields to Export

The field selection screen lists every available export column organised by data category. More than 155 individual fields are available, spanning order header information, full customer profile data, invoice and delivery address details, payment records, and product line item data , making this the most complete OpenCart bulk order management and export toolkit available.

Use the Select All control to include everything, Deselect All to start fresh, or Reset to Defaults to return to the standard recommended selection. A small number of identifier fields are mandatory and cannot be removed.

Drag any row to change the column sequence in the output file. An export file that contains only what the receiving system actually needs is faster to generate, smaller to transfer, and less likely to cause issues at the destination.

4.3 Step Three: Review and Generate

The final screen shows a complete summary of the profile configuration, including entity type, format, filename pattern, active filters, and the total number of fields selected for output.

Click Generate and Download to produce the file immediately. The OpenCart order export module creates the output and either initiates a browser download for local storage profiles or pushes the file to the configured remote server for FTP and SFTP profiles. The operation is recorded in the Activity Log.

Alternatively, save the profile without running it and let the next scheduled cycle trigger the first automated run.

5.0 Import Process, Full Setup Guide

The Import Feature lists all saved import profiles with their configuration summary and last run status. The three-step wizard guides you through source configuration, field mapping, and execution. This is where OpenCart customer import, export and ecommerce order data transfer workflows are configured for both one-time and recurring use.

5.1 Step One: Source and Format Settings

Profile Name: A clear, descriptive label. Include the data entity and source system in the name for easy identification when multiple profiles accumulate over time.

Entity Type: Select Orders, Customers, or Addresses. The behaviour differs by entity type in an important way. Customer and address records are matched against existing data during import. A match updates the existing record, while no match creates a new one. Order records always result in new entries; the extension does not support updating existing order records through import, by design, to preserve the integrity of the historical order log.

File Format: Must match the format of the file you intend to import. The OpenCart CSV import customers details workflow requires CSV format selected here; XLSX for spreadsheet-based imports; JSON or XML for system-generated feeds.

Delimiter and Separator Settings: These must exactly match the settings used when the source file was created. A mismatch here is the most common cause of field boundary errors during OpenCart customer import and export operations.

Store Assignment: Imported records are created under the store selected here. Double-check this before saving in multi-store environments.

File Source: Manual upload accepts a file from your local machine and is suitable for one-time imports. Remote source connects to an FTP or SFTP server for the OpenCart FTP export orders and import automation workflows, required for any profile that runs on a schedule.

Remote Server Settings: Protocol, host, port, credentials, remote file path, passive mode, and test connection. Configure and test these before saving.

Schedule: When enabled, this profile runs each time the Import Automation URL fires. The extension connects to the remote server, retrieves the file from the specified path, and processes the OpenCart data migration without any manual action.

Click Save Profile to store the configuration, or proceed to the next step to continue directly to field mapping.

5.2 Step Two: Field Mapping

The mapping screen is where the extension reads your file and connects its columns to the corresponding OpenCart data fields. The process is largely automatic; the extension recognises standard column header names and common naming conventions used by popular eCommerce platforms and ERP systems.

A live data preview shows the first rows of your file alongside the field mapping assignments, so you can visually confirm that the data appearing under each field label is what you expect. Required fields are indicated clearly. If any required field has not been auto-matched, you must assign it manually before proceeding.

The search box above the mapping table makes it easy to find specific fields in files with a large number of columns. Review every auto-matched assignment carefully, particularly for date, currency, numeric, and address fields. These are the categories most likely to have naming variations that the auto-matcher may have interpreted differently.

The assignment you set manually is saved with the profile, so it only needs to be done once per file structure.

5.3 Step Three: Import the File

With mapping confirmed, click Start Import to begin processing. The extension works through the file in sequential batches, with each batch size determined by the Batch Processing Size value set in the Settings Panel.

A live progress display updates after each batch completes, showing how many records have been processed and how many are remaining. This is especially useful for large OpenCart bulk import/export operations on servers with limited memory.

Before clicking Start Import, click Save Profile if you want the field mapping preserved for future runs. Saving the profile means the next time you run an import with the same file structure, all field assignments are already in place.

6.0 Activity Log, Understanding Your Transfer History

The Activity Log maintains a permanent record of every import and export the extension has performed. It is searchable and filterable, making it a practical audit tool for compliance reviews, dispute resolution, and operational troubleshooting.

Each log entry displays the following:

Run Number- a sequential identifier assigned to each operation.
Operation Type- whether the run was an import or an export.
Entity- which data type was involved (Orders- Customers- or Addresses).
Format – the file type used (CSV- XLSX- JSON- or XML).
Status – whether the run completed cleanly or encountered errors.
Record Count – how many records the run processed.
Filename – the output file name- with a download link for export runs.
Timestamp – when the run started.Use the filter controls at the top of the log to narrow the view by any combination of these fields, including a custom date range. Export files remain downloadable from the log indefinitely. For runs that produced errors, expanding the log entry reveals the complete row-level error detail from that operation.

7.0 Full OpenCart Store Migration Workflow

This section covers end-to-end OpenCart store migration using Knowband as the sole migration tool.

Install the Knowband extension on both the source and destination OpenCart stores. On the source store, create three separate export profiles: one for Orders, one for Customers, and one for Addresses. For each, select all available fields, apply no filters, choose XLSX (easiest for pre-import review), and generate the files.

This approach makes the extension the most efficient OpenCart store migration plugin for preserving complete order history, ideal for OpenCart customer data migration scenarios, including customer accounts and delivery address data across environments, without requiring custom scripts or third-party migration services.

On the destination store, create a corresponding import profile for each entity type. Upload the exported file for each entity: orders, customers, and addresses. Confirm the field mapping and run the imports in this sequence: Customers first, then Addresses, then Orders. Running in this order means customer and address records exist before the order import attempts to link to them, which reduces the number of records the cross-store resolution engine needs to create from scratch.

This complete e-commerce order data transfer approach makes the Knowband extension the most efficient single-tool solution for OpenCart data migration.

8.0 Frequently Asked Questions

Q1: Can I export orders from multiple Opencart in the same operation?

Each export profile targets one store at a time using the Store Scope setting using Opencart Order Migrations Extension by Knowband. To combine data from multiple storefronts, run a separate export for each and merge the resulting files in your spreadsheet application before delivering them onward.

Q2: My import file has custom column names that do not match OpenCart’s field names. Will the mapping fail?

The auto-matcher recognises a wide range of common naming variants. For any column it cannot resolve automatically, the mapping screen lets you make the assignment manually by selecting the correct OpenCart field from a dropdown. The assignment is saved with the profile, so it only needs to be done once.

Q3: Does importing customer records create duplicate accounts?

No. Customer records are matched by email address. If the email already exists in your OpenCart database, the existing account is updated. New accounts are only created when the email does not match any existing record. This is the same de-duplication logic used by leading OpenCart customer import/export extensions.

Q4: Is it safe to re-run an export profile that already delivered a file to a remote server?

Yes. Each run generates a new file and each run is logged separately. Re-running a profile does not delete or replace files from previous runs when filenames include date or datetime tokens. If you are using a static filename without tokens, the file on the remote server will be overwritten on each run.

Q5: What should I do if a scheduled import or export did not run?

Check the Activity Log first to confirm whether the run was attempted. If no entry exists for the expected time, the issue is with the automation URL not being called by your task scheduler. Verify the URL is correctly saved in your task scheduler and that the scheduled automation toggle is enabled on the relevant profile.

This user guide covers the complete feature set of the Knowband OpenCart Order, Customer & Address Import Export Extension, the leading OpenCart import export extension for orders, customers, and address data. For technical support, contact the support team directly via the extension’s support channel.

OpenCart AI Review Generator Extension – Complete User Guide

1.0 Introduction

Getting reviews on a new OpenCart store is one of the hardest parts of building credibility online. Customers rarely come back to leave feedback, and waiting for organic reviews can take months. In that time, your product pages sit without social proof, and potential buyers move on.

The Knowband OpenCart AI Review Generator Extension changes that. It connects your OpenCart store to an AI provider of your choice- OpenAI (ChatGPT), Anthropic (Claude), or Google (Gemini)- and generates product-specific reviews directly from your admin panel. You set the rules. The extension handles everything else.

Each generated review comes with a star rating, a title, a review body written in your chosen tone, and a guest reviewer profile with a randomised name. All reviews are published through OpenCart’s native review system and appear on product pages exactly the way a real customer review would.

This guide walks through every setting, tab, and option so you can get the OpenCart AI review generator configured and running from day one.

2.0 Installation Steps

Installing the Extension

Step 1: Download the extension ZIP file from your Knowband account.

Step 2: Log in to your OpenCart admin panel and go to Extensions, then Extension Installer.

Step 3: Upload the ocmod.zip file using the file upload option. OpenCart will handle unpacking automatically.

Step 4: Log in with FTP, copy all the folders from the Upload folders to your store, and select the Modules category. Locate the AI Review Generator in the list and click Install.

Step 5: After installation, click Edit to open the configuration panel.

Common Installation Problems

Upload fails: Your server’s file upload limit is likely too low. Ask your hosting provider to raise upload_max_filesize and post_max_size to at least 32 MB.

Extension not appearing in the list: Clear your OpenCart cache by going to Dashboard and clicking the blue cog icon, then Refresh. Run the search again.

3.0 Admin Panel Overview in OpenCart Product Review Generator Extension

After installing the extension, the Opencart AI Review Generator integrates three main sections to your opencart admin panel:

General Settings: Enable the extension, connect your AI provider, and copy the CRON URL for automated generation.
Review Rules: Create and manage rules that define how reviews are generated, which products they cover, and when they go live.
Reviews: View, approve, publish and manage every review generated by the extension.

4.0 General Settings

The General Settings tab holds your global configuration. Changes here affect how the entire extension operates.

4.1 Enable Extension

The main on/off switch. When enabled, the extension is active and ready to generate. When disabled, all generation stops, but every rule, review, and history entry stays saved exactly as it was.

4.2 AI Provider

Choose which AI service you want to use for generating reviews:

ChatGPT (OpenAI)
Claude (Anthropic)
Gemini (Google)

Only one provider runs at a time. Switching providers does not affect any rules you have already created or reviews that have already been generated.

4.3 API Key

Paste your API key for the selected provider here. Without a valid key, the extension cannot connect to the AI service, and generation will not run.

Getting your API key:

OpenAI: Visit platform.openai.com, go to API Keys under your account, and create a new key. Copy it immediately; it will not be shown again.
Anthropic: Visit console.anthropic.com, open API Keys, and generate a new one.
Google Gemini: Visit aistudio.google.com, click Get API Key, and create one under your project.

Use the Test Connection button to confirm the key is working before saving.

4.4 Model Selection

Select the specific AI model to use. Admins can see the available options depending on your requirements. These AI models include ChatGPT, Claude and Gemini models.

These AI Models in OpenCart product review generation through AI include these models:

OpenAI ChatGPT models: GPT-5.5, GPT-5.4, GPT-5.4 mini, GPT-5.4 nano, GPT-5, GPT-4.1, GPT-4.1 mini, GPT-4.1 nano, o3, o3-mini, o4-mini, GPT-4o, GPT-4o mini, GPT-4 Turbo, GPT-4, GPT-3.5 Turbo

Anthropic Claude models: Claude Opus 4.7, Claude Sonnet 4.6, Claude Opus 4.6, Claude Opus 4.5, Claude Sonnet 4.5, Claude Haiku 4.5, Claude Opus 4.1, Claude Sonnet 4, Claude Opus 4

Google Gemini models: Gemini 3.5 Flash, Gemini 3 Flash Preview, Gemini 3.1 Flash-Lite, Gemini 2.5 Flash-Lite, Gemini Flash Latest, Gemini Flash-Lite Latest

4.5 Max Tokens

Store admins can set the maximum amount of text the AI can write per review request in the OpenCart customer review generator. The range is 1 to 16,384, with a default of 4,000.

Higher values give the AI room to write longer, more detailed content but increase the API cost for each run. Additionally, it is recommended to keep lower values for reviews shorter and reduce cost. Admins can set this in line with the Max Words per Review value you configure in each rule.

4.6 Temperature

Merchants can also handle the creativity of the Opencart SEO Powered Reviews Generator by controlling the temperature values scale, which runs from 0.0 to 1.0. For ChatGPT‘s GPT 5.5, temperature is not supported in the module.

At 0.0, responses are predictable and stay close to a fixed pattern , good if you need every review to hold a consistent tone. Closer to 1.0, the output becomes more varied and less uniform. For reviews that read naturally, a value between 0.5 and 0.7 works well for most stores.

4.7 Check Existing Reviews

When set to Yes, the Knowband OpenCart AI-generated customer reviews check each product before running the generation. If a product already has reviews, it is skipped entirely. This prevents the same product from accumulating repeated batches and avoids wasting API tokens on products that do not need new content.

4.8 CRON URL in Opencart Product Reviews Generation

The General Settings tab provides a token-secured URL for automated review generation. Copy this URL and add it to your server as a cron job.

Running it every 15 minutes is the recommended frequency. Only requests carrying the correct token will trigger generation; the URL does nothing without it.

Click Save before leaving this tab.

5.0 Review Rules

Review Rules are where you control exactly how the OpenCart automated review generation process runs. Each rule targets a specific group of products or categories and defines all the parameters, publishing timing, generation limits, tone, language, and rating breakdown.

The Review Rules list shows every rule with its ID, name, publish mode, content type, daily limit, active status, and assigned store. Hit Generate Now on any row to run that rule immediately. Click Edit to change its settings.

5.1 Adding a New Review Rule

Store admins can add a rule to generate the reviews based on the configurations added in OpenCart automated product reviews.

Store: Select which store this rule applies to if you run a multi-store setup in Opencart

Enable Rule: Toggle on to make the rule active. Inactive rules are saved but will not run on CRON or when Generate Now is clicked.

Publish Mode:

Immediate– Reviews are published the moment they are generated. No delay, no approval step.
Scheduled– Reviews are generated and scheduled, then published at a random point within a day range you define. Store admins can add configuration in a range of 0 to 7 days, for example, releases each review at a random point across that window. This makes the accumulation pattern look natural rather than sudden.
Manual– Reviews are generated and held in the Reviews tab in the Opencart AI Review Generated Plugin. Nothing goes live until an admin opens each entry and approves it. Best when you want full control over what appears on the storefront.

Random Delay (days): Appears when Scheduled mode is selected. Set a minimum and maximum day range. Each generated review is published at a random point within that window.

Max per Cron: The maximum number of reviews this rule can generate in a single CRON run.

Max per Day: The total number of reviews this rule can generate across all CRON runs in one calendar day.

Max per Product per Day: Handles how many reviews a single product can receive from this rule in one day using Knowband eCommerce Review Generations. This keeps any one product from picking up an unnatural volume in a short period.

Max Words per Review: The word limit for each generated review body. Use 150 for standard reviews. Drop to 50 or below for short-form content. Raise it for long, detailed reviews.

Languages: Tick each language you want reviews generated in. Selecting both English and French means every review is generated in both. Only languages installed in your OpenCart store appear in this list.

Content Type: Choose whether the rule targets specific Products or entire Categories. Selecting Products lets you search and add individual items. Selecting Categories applies the rule to every product within that category.

Tone: Set the voice for generated reviews.

Professional
Casual
Technical
Persuasive

Generate using: Toggle which product data points the AI uses when writing each review. At least one must be active.

Product name
Product description
Product price
Product category

Enabling the description gives the AI more context for specific, accurate content. Enabling price means reviews may reference value for money. Disabling a data point means the AI will not factor it in.

Rating Distribution (%): Store admins can set the percentage split across 1 to 5 star ratings. The total must equal exactly 100. For example: 5 stars at 50%, 4 stars at 30%, 3 stars at 10%, 2 stars at 5%, 1 star at 5%. The extension follows this distribution when assigning ratings to each generated review, so the overall profile on a product page looks realistic rather than uniformly perfect.

Rule Name: A required field. Give each rule a name that makes its purpose clear , for example, Winter Range English or Homepage Categories Casual.

Custom Prompt: An optional field in given in the rule review configurations that replaces the default generation instruction for this rule. Write a plain instruction and use the supported variables to pull product data into the prompt.

Supported variables are: {product_name}, {product_description}, {price}, {category}, {shop_name}, {tone}, {max_words}

Click Save to create the rule. It will appear in the Review Rules list straight away.

5.2 Editing and Deleting Rules

Click Edit on any rule row to reopen the form and change any setting. Use the dropdown arrow beside Edit and select Delete to remove a rule permanently. Deleting a rule does not remove reviews that were already generated under it in the reviews tab in the OpenCart review creation Plugin.

5.3 Bulk Actions

The Bulk Actions dropdown at the bottom of the rules list lets you apply actions to multiple selected rules at once.

6.0 Reviews Tab

The Reviews tab shows every review the extension has generated. This is where you manage, approve, or remove reviews before or after they reach the product page.

6.1 Reviews List in Knowband OpenCart AI Review Generator Plugin

Each entry in reviews tab shows:

ID: Sequential review number
Product: Which product was the review generated for
Language: Which language was it written in
Preview: A shortened version of the review body
Reviewer: The generated name and email address for the guest profile
Rating: The star rating assigned based on the rule’s distribution settings
Status: Scheduled, Published, or Pending Approval
Created: When the review was generated
Published: When it went live on the storefront
Store: Which store the review belongs to

Use the filter controls above the list to sort by product, language, reviewer, rating, status, date range, or store.

6.2 Approving and Publishing Reviews

For rules set to Manual publish mode, reviews arrive in this tab with a Pending Approval status. Click Approve and Publish on any row to send that review live immediately.

Click the drop-down arrow beside Approve and Publish to access the View option. This opens the full review text so you can read it before making a decision.

6.3 Deleting Reviews

Click the drop-down arrow beside Approve and Publish and select Delete to remove a review permanently. Deleted reviews cannot be recovered.

7.0 Steps to Generate the API Key for Prestashop AI Content Generator and Translator Module Configurations?

For Claude API:

Visit Anthropic’s website, and click “Start Building”.
Create an account, access your Dashboard, generate an API key, and save it securely.

For Gemini API:

To access the API, visit the Google AI Studio website.
Click “Get API key,” accept the terms of service, create your key, and paste it into the module’s configuration settings.

For ChatGPT API:

Obtain an OpenAI API key and configure it within the module settings.
Click on your profile (top-right) → “View API keys” → “Create a new secret key”.
Copy the key immediately and store it safely.

7.0 Frequently Asked Questions

What does the OpenCart AI Review Generator extension do?

The OpenCart AI Review Generator connects to ChatGPT, Claude, or Gemini and generates product-specific reviews based on rules you set in the admin panel. Each review is written for the specific product in the tone and language the rule specifies, then published through OpenCart’s native review system.

Which AI providers are supported?

The extension supports three providers: OpenAI (ChatGPT), Anthropic (Claude), and Google (Gemini). You connect using your own API key. Only one provider is active at a time. You can switch providers from General Settings without affecting existing rules or reviews.

What are the three publish modes in review generation?

Immediate publishes a review the moment it is generated. Scheduled holds it and releases it at a random point within a day range you configure, which creates a natural-looking pattern over time. Manual holds it in the Reviews tab until an admin approves it.

How does the rating distribution work in the OpenCart product review extension?

Inside any review rule, assign a percentage to each star level from 1 through 5. The numbers must total exactly 100. The extension follows this split when assigning ratings, so the profile across a product page does not look artificially uniform.

How does the CRON automation work in the OpenCart AI Review Generator Plugin?

Copy the token-secured CRON URL from General Settings and add it to your server cron job. Running it every 15 minutes is recommended. The URL only triggers generation when the correct token is present.

Does the OpenCart AI review extension support multiple languages?

Yes. Inside each rule, select the languages you want reviews generated in. Every review is produced in each selected language. Only languages installed in your OpenCart store appear in the list.

What is the custom prompt field for?

OpenCart AI-generated reviews replace the default generation instruction for that specific rule. Use it when you need reviews to follow a particular format or focus on a specific product attribute. Drop in the supported variables to pull in product data dynamically.

What does Max Tokens control?

It caps how much text the AI generates per review request. Higher values allow longer content but cost more per run. Lower values reduce both length and cost. Keep it consistent with the Max Words per Review setting in your rules.

Can I stop duplicate reviews in OpenCart automated product reviews from being generated?

Yes. Turn on Check Existing Reviews in General Settings. The extension will check each product before generating and skip any that already have reviews.

What versions of OpenCart do OpenCart AI-generated reviews support?

The OpenCart review automation runs on OpenCart 3.x. Make sure the native review system is active before running generation.

8.0 Conclusion

The Knowband OpenCart AI Review Generator puts automated review generation inside your admin panel. Set up a rule, connect an API key, and the extension takes care of generation, scheduling, and publishing from there.

Rating distribution keeps the review mix looking genuine. Multilingual generation covers every market your store serves. Manual approval gives you full editorial control when you need it. Once the rules are live, the CRON automation runs everything on schedule without daily input. The Opencart Automated AI Review Generator is also available on OpenCart Marketplace.

For support, custom development, or OpenCart extension requirements, contact the Knowband team directly.

OpenCart Form Studio: All-in-One Feedback, Contact, and Survey Form Builder User Guide

1.0 Introduction

Collecting customer data without a reliable solution results in missed feedback, unanswered enquiries, and lead-generation opportunities that go nowhere. Whether you need a basic contact form, a product feedback form, or a post-purchase customer satisfaction survey, the OpenCart Form Builder extension handles it all from one place.

This OpenCart Form Builder extension lets store owners create unlimited forms without writing a single line of code. Contact forms, survey forms, registration forms, lead generation forms, every data collection need an eCommerce store has is covered. This OpenCart contact form plugin works equally well for both small and huge businesses.

Form creation, spam protection via Cloudflare Turnstile, email notifications to admins and customers, Mailchimp and Brevo integration, form submission management, and IP and email blacklisting. The Knowband OpenCart Survey Extension covers the full workflow, use it as your OpenCart contact form plugin, survey tool, or lead capture form, all from one extension, without needing separate solutions for each job.

2.0 Installation Guide

System Requirements

Before installing the extension, confirm your environment meets the following:

OpenCart version 3.x
A working email configuration in your OpenCart admin panel

Installing the Extension

Step 1: Download the ZIP file and log in to your OpenCart admin panel.

Step 2: Go to Extensions, then Installer. Click the Upload button, select the ZIP file, and confirm. OpenCart processes the upload automatically.

Step 3: Once the upload completes, go to Extensions. Select the extension category from the dropdown. Find OpenCart Form Studio in the list and click Install.

Step 4: After installation, click Edit to open the extension configuration panel.

Step 5: If the extension does not appear in the list, clear your OpenCart cache under Dashboard, then click the blue cog icon and select Refresh.

Common Installation Issues

Upload fails: The server is rejecting the file size. Ask your host to raise upload_max_filesize and post_max_size to at least 32 MB.

Emails not going out: Head to System, then Settings, then the Mail tab. The extension pulls from the store’s default mail setup unless you have set a form-level override.

The page looks broken: Run a browser cache clear and reset the OpenCart theme cache from the Dashboard refresh panel.

3.0 Admin Panel Overview

After installation, the extension adds four sections to the admin:

General Settings: Turn the extension on or off, set global mail templates, configure Cloudflare Turnstile, and handle the IP and email blocklist.
Forms: Build, update, and organise all forms. Each one has its own tab structure.
Form Submissions: One view for every submission across every form.
IP and Email Blacklist: Block addresses from reaching your forms entirely.

4.0 General Settings

The General Settings section has three sub-tabs: Global Settings, Email Templates, and Cloudflare Turnstile.

4.1 Global Settings

Module Enable/Disable: The main toggle for the OpenCart Survey Plugin. Set to Enabled to make all active forms live on the front end. Switching to Disabled hides every form from visitors without touching any saved data or configuration.

4.2 Email Templates

Enable Mail Template: Turns the global HTML email template system on or off. When enabled, all outgoing emails, admin notifications, auto-responder, and manual replies use the HTML wrapper templates defined in this section. Disable this to send plain-text emails with no styling. The {message_content} tag in the template is replaced with the per-form email body at send time.

Admin Mail Content: The notification your team gets on each submission. Write the subject and body in the rich text editor and click variable tags from the Template Variables panel to pull in field values from the submission automatically.

Auto Responder Content: Goes straight to the customer after they submit. Use it to confirm receipt, give them a timeframe, or point them to the next step.

Reply Email: Defines the layout for manual replies your team sends from the Form Submissions panel.

All three email templates support rich text formatting, including bold, italic, links, lists, and HTML, so the emails can match your store branding without any custom development.

4.3 Cloudflare Turnstile Spam Protection

Any public-facing form attracts bot submissions. This Cloudflare Turnstile OpenCart integration blocks automated submissions without showing customers any visual puzzle or CAPTCHA challenge. Real visitors go through without any extra friction.

Switch the Enable Cloudflare Turnstile dropdown to Enabled, then paste the Site Key and Secret Key from your Cloudflare account into the fields provided. The Widget Theme can be set to Auto, Light, or Dark to match your store.

Steps to get your Cloudflare Site Key and Secret Key:

Sign in to your Cloudflare account at dash.cloudflare.com.
From the left menu, go to Protect and Connect, then Application Security, then Turnstile.
Click Add Widget and fill in your domain details.
Select a widget mode and finish creating the widget.
Copy the Site Key and Secret Key that appear on the confirmation screen.
Paste both into the Cloudflare Turnstile fields in the extension and save.

Once configured globally, the Cloudflare Turnstile field can also be added directly inside individual forms by dragging it into the form layout from the field selector.

5.0 Creating and Managing Forms

5.1 Forms List

The Forms section shows every form created using the OpenCart Form Builder. Each row in the list displays the form ID, title, short code, form URL, view count, message count, active status, and action buttons for viewing, editing, or deleting the form.

The short code column shows the embed code for each form in the format [kbcf-form id=1]. Paste this shortcode into any CMS page or content area in your OpenCart store to embed the form directly at that location without using the Placements tab.

Click Add New to create a form. Each form opens with eight configuration tabs: Info, Form, Mail, Notifications, Thank You Page, Settings, Placements, and Synchronization.

5.2 Info Tab: Form Identity and SEO Settings

Enable Separate Form Page: When set to Yes, the OpenCart Form Creator generates a standalone page for this form with its own URL based on the slug you enter.

Form Title: The name displayed to customers above the form on the front end. Supports English and French language inputs.

Form Slug: The URL path for the standalone form page. For example, entering contact-us produces the URL yourstore.com/contact-us. Supports multiple languages.

Meta Title: The SEO title for the standalone form page. Supports multiple languages.

Meta Keywords: Meta keywords for the form page to support internal content categorisation. Supports multiple languages.

Meta Description: The search engine description for the standalone form page. Keep it under 160 characters.

5.3 Form Tab: Building the Form Layout

The Form tab starts empty with a prompt to add a row. Click Add Row to open the layout selector.

You can select any layout out of the 9 options available.

After adding a row, click Add Input Field inside any column to open the field selector.

Available field types:

Text: short written responses
Textarea: long written responses
Email: with format validation
Password: masked input field
Phone: phone number input with validation
URL: web address input with format validation
Number: numeric input with validation
Date: date selection with format validation
File: customer attachment uploads in formats you specify
Dropdown selections: single-select multiple choice
Checkboxes: multiple-choice
Radio buttons: single-select with visible options
HTML: embed custom markup or section headers inside the form
Cloudflare Turnstile: Place the spam protection widget at a specific position
Submit: trigger configured actions on form completion

5.4 Mail Tab: Per-Form Email Configuration

The Mail tab has two sub-tabs: Email to admin and Auto responder.

Email to admin handles the notification your team receives on each new submission. Configure:

To: Recipient name and email address. Add multiple recipients using the + To button.
BCC: Hidden recipients. Add using the + BCC button.
From Name and From Email: The sender identity shown in the notification.
Reply-To Name and Reply-To Email: Where customer replies are routed.
Subject: The email subject line. Supports English and French.
Message: The email body is using the rich text editor. Supports English and French. Use the Available Tags panel on the right to insert dynamic values from the submission.

Auto responder mirrors the same fields for the customer-facing confirmation email. Enable Auto Reply and configure the subject, message, and sender details. The auto-responder fires immediately after submission with no manual action needed.

5.5 Notifications Tab: Custom Validation Messages

The Notifications tab sets per-form, per-language messages shown to the visitor when specific events occur during form submission. Leave any field empty to use the extension-level defaults.

Each message supports English and French language inputs. The configurable messages are:

Success Message: shown when the form submits successfully (default: Message Sent Successfully)
Failed Submission Message: shown when submission fails (default: Unable To Send Message)
Spam Detection Message: shown when spam is detected (default: Spam Activity Detected)
Required Field Validation Error: shown when a required field is left empty (default: Required Field Missing)
Maximum Length Validation Error: shown when input exceeds the allowed length (default: Input Exceeds Allowed Length)
Unknown File Upload Error: shown on unidentified upload failures (default: Unknown Upload Failure)
Invalid File Type Error: shown when an unsupported file format is uploaded (default: Unsupported File Type)
File Size Limit Error: shown when an uploaded file exceeds the size limit (default: File Size Limit Exceeded)
PHP File Upload Error: shown on server-side upload errors (default: Server Upload Error)
Invalid Number Format Error: shown when a number field receives an invalid value (default: Invalid Number Format)
Minimum Number Validation Error: shown when a number is below the allowed minimum (default: Number Below Minimum Limit)
Maximum Number Validation Error: shown when a number exceeds the allowed maximum (default: Number Exceeds Maximum Limit)
Invalid Email Address Error: shown when an invalid email is entered (default: Invalid Email Address)
Invalid URL Error: shown when an invalid URL format is entered (default: Invalid URL Format)
Invalid Phone Number Error: shown when an invalid phone number is entered (default: Invalid Phone Number)
Blacklisted IP Address Error: shown when a blocked IP attempts to submit (default: IP Address Blocked)
Blacklisted Email Address Error: shown when a blocked email attempts to submit (default: Email Address Blocked)

5.6 Thank You Page Tab

Display Thank You Page: Set to Yes to activate a post-submission page for this form.

Type:

Default page: A built-in confirmation page configured inside the extension. No separate CMS page needed.
Custom URL: Redirects the customer to any URL you specify after submission.

Thank You Title: The heading shown on the default thank you page. Supports English and French.

Thank You Alias: The URL slug for the thank you page. Supports multiple languages.

Thank You Content: Body text of the thank you page, editable with the rich text editor. Supports English and French. Accepts bold, italic, links, images, tables, and raw HTML.

5.7 Settings Tab: Display and Behaviour Controls

Active: Turns this specific form on or off on the front end. Set to Yes to make it live. Everything configured stays saved when set to No.

Customer Groups: Controls which customer groups can see this form. Tick the Default checkbox to limit visibility to the default customer group. Leave empty to allow all customer groups, including guests. This maps directly to the customer groups configured in your OpenCart store, not a Visitor/Guest/Customer segmentation.

Open Form Button: Toggle to Yes to replace the inline embedded form with a button that opens the form as a pop-up when clicked. When enabled, the following styling options appear:

Button Label (multilingual)
Text Color
Background Color
Text Hover Color
Background Hover Color
Show Icon (Yes/No)
Custom Icon (file upload)

Floating Button: Toggle to Yes to fix the Open Form Button to the screen so it stays visible as the visitor scrolls. When enabled, the following options appear:

Floating Label (multilingual)
Position (default: middle_right)
Right Margin (px)
Top Margin (px)
Text Color
Background Color
Text Hover Color
Background Hover Color
Show Icon (Yes/No)
Custom Icon (file upload)

5.8 Placements Tab: Where the Form Appears

The Placements tab controls where each form is displayed across your store. Pick one or more page layouts and one or more positions within those layouts. The form renders at every selected layout and position combination. The visual style, inline form or open-button pop-up, is taken from the Open Form Button toggle in the Settings tab.

Layouts available:

Account
Affiliate
Category
Checkout
Compare
Contact
Default
Home
Information
Manufacturer
Product
Search
Sitemap

Use Ctrl or Cmd and click to select multiple layouts at once.

Positions available:

Content Top
Content Bottom
Column Left
Column Right
Header Position
Footer Position

Tick every position where the form should appear within the selected layouts. No theme edits or custom code are needed.

For example, picking Product under Layouts and ticking Content Bottom under Positions puts the form below the product description on every product page. Picking Home with Content Top puts it above the page content on the homepage.

5.9 Synchronisation Tab: Email Marketing Integration

The Synchronization tab connects the form to Mailchimp or Brevo so submitted email addresses are added to your marketing lists automatically. Map form fields to provider fields before saving. Only the Email field is required. For Mailchimp, address fields must be mapped all-or-none.

Mailchimp:

Enable Mailchimp: Set to Yes to activate the integration for this form.
Mailchimp API Key: Paste your Mailchimp API key. Click Check API key to verify it.
SETUP: Click to load your Mailchimp account data.
Audience: Select the Mailchimp audience list to add subscribers to.
Field Mapping: Map your form fields to the corresponding Mailchimp fields using the Title and Mailchimp columns.

Brevo:

Enable Brevo: Set to Yes to activate the integration for this form.
Brevo API Key: Paste your Brevo API key. Click Check API key to verify it.
SETUP: Click to load your Brevo account data.
List: Select the Brevo contact list to add subscribers to.
Field Mapping: Map your form fields to the corresponding Brevo fields using the Title and Brevo columns.

6.0 Form Submissions Management

Every form submission across your store appears in the Form Submissions panel, making form submission management in OpenCart straightforward for any team size. Filter submissions by Email Subject, Submission Data, Form Name, or Replied status using the filter bar at the top.

The panel shows the email subject from the admin notification, the full submission data with field labels and values, the form name the submission came from, whether a reply has been sent, and the submission date and time.

Click the view icon on any row to open the full submission and reply directly from the same screen. The reply form includes From, To, Reply-To, and Subject fields pre-filled from the original submission. Attach files in JPG, JPEG, PNG, GIF, ZIP, or PDF format up to 8 MB if needed.

7.0 IP and Email Blacklist

The IP and Email Blacklist section handles repeat spam submissions at the source level. Any entry added here is checked before a form submission is recorded or sent to anyone.

Blocked IP Addresses: Enter one IP address or pattern per line. Use a single address for an exact block or a wildcard to cover a range. For example, 69.89.31.* stops every address in that range. Using *.226 blocks any IP ending in those digits.

Blocked Email Addresses: Follows the same logic as IP blocking. One address per line. Entering *@mail.ru shuts out every address from that domain. *@qq.com does the same for that provider.

Spam Email Filter (Regex): Write regex patterns here that run against incoming email addresses. Any address matching a pattern gets blocked before the submission goes any further. Add one pattern per line. The extension includes ready-to-use example patterns covering the most common high-spam domains and address structures. Paste them in, and they apply immediately.

8.0 Frequently Asked Questions

Q: What is the OpenCart Form Builder extension, and what does it do?

The Knowband OpenCart Survey Extension is a form builder tool that lets OpenCart store owners create unlimited contact forms, surveys, feedback forms, lead generation forms, and registration forms without writing any code. It includes drag and drop form creation, Cloudflare Turnstile spam protection, per-form email setup, auto-responder, Mailchimp and Brevo sync, form submission tracking, and placement control through the Placements tab. Works with OpenCart 3.x.

Q: How do I create a survey in OpenCart using the OpenCart Survey Builder?

Open the extension and click Add New Form. Give the form a title and a slug. Inside the Form tab, add a row, then drop in radio button fields for ratings, dropdowns for categories, and textarea fields for written feedback. Head to the Mail tab to set up the auto-responder, go to the Thank You Page tab to configure the post-submission message, pick the placement in the Placements tab, and turn the form on. No developer needed at any point.

Q: How do I collect customer feedback in OpenCart without a developer?

The OpenCart Survey Builder Plugin, also available on OpenCart Marketplace, manages the full feedback collection process from the admin panel. Build the form, go to the Settings tab, and set the Customer Groups to limit visibility, then pick the layout in the Placements tab. Once enabled, all submissions show up in the Form Submissions panel ready for your team to read and respond to.

Q: How do I display forms on product pages in OpenCart?

Go to the Placements tab inside the form. From the Layouts list, pick Product. In the Positions section, tick Content Bottom or Content Top. The form shows up at that position on every product page without any changes to the theme.

Q: Does this OpenCart survey plugin support email notifications?

Yes. Every form carries its own email setup in the Mail tab under the Email to admin sub-tab. The admin notification goes to whichever address you configure and fires as soon as a customer submits. The Auto responder sub-tab handles the customer-facing confirmation. Subject line, body text, and reply-to address are all set per form in the OpenCart Survey Builder using multilingual rich text editors.

Q: How do I build unlimited forms in OpenCart with this OpenCart Survey Extension?

This OpenCart Survey Extension has no cap on forms, fields, or submissions. Add as many as your store needs, contact forms, product feedback form OpenCart, customer satisfaction survey OpenCart, lead generation forms, registration forms, and post-purchase surveys. Each one runs on its own settings with separate placement rules, email routing, and a dedicated submission log.

Q: What is the easiest way to create a survey in OpenCart?

Open the OpenCart Form Creator, click Add New Form, name it, and set the slug. Use the drag and drop form builder OpenCart interface to pull fields into the layout rows. Set up the email and placement settings, switch the form on, and it goes live. A first-time user with no technical background can go from opening the extension to a live survey in under 15 minutes.

Q: What is the best OpenCart form builder plugin in 2026?

The best OpenCart form builder plugin in 2026 covers form creation, placement, spam filtering, email automation, and submission management from one installation with no developer needed for any of it. This extension covers all of these: drag and drop builder, Cloudflare Turnstile, per-form email and auto-responder, Mailchimp and Brevo integration with field mapping, layout-based placement control, and a full submission management panel with direct reply capability.

Q: How does spam protection work in the OpenCart Form Studio?

Switch Cloudflare Turnstile to Enabled in the General Settings Cloudflare Turnstile tab by entering the Site Key and Secret Key from your Cloudflare account. Once active globally, drag the Cloudflare Turnstile field into any individual form layout. This spam protection form OpenCart approach, blocks bots silently before the submission is recorded. Real customers see no challenge or CAPTCHA. The IP and Email Blacklist adds a second layer for blocking known bad actors by address or domain.

Q: Is the OpenCart Form Builder extension compatible with the latest OpenCart version?

Yes. This responsive form builder OpenCart extension is compatible with OpenCart 3.x. Check the Knowband OpenCart Form Builder product page for the most current compatibility information and version support details.

9.0 Conclusion

The OpenCart Form Studio covers every form-related need an OpenCart store has from one admin panel. Unlimited forms, drag and drop form builder, OpenCart functionality, spam protection, per-form email configuration, email marketing sync, placement control through the Layouts and Positions system, and a complete submission management panel, all without writing a single line of code.

For support, custom requirements, or OpenCart extension development, contact the Knowband team directly.

OpenCart Smart AI Admin Assistant Extention User Manual

1.0 Introduction

Every OpenCart store generates data every hour, orders arriving, stock moving, customers registering, carts being left behind, and revenue numbers shifting. All of it sits in the database. Getting to any specific figure means navigating to the right admin section, picking a date range, loading the report, and repeating the whole thing the next day.

The Knowband OpenCart Smart AI Admin Assistant removes that entirely. It places an AI chat interface inside your OpenCart admin panel. Type any store question in plain English and get a direct answer pulled from your live database in seconds. No SQL. No report pages. No developer in the loop.

This guide walks through every tab and setting so you can connect your AI provider, configure the assistant, and start querying your store data from day one. Compatible with OpenCart 3.x.

[Updated July 2, 2026] Analytics Dashboard Integration
Get a real-time view of your store’s performance right from the admin panel, revenue, orders, customers, and stock, all in one screen using the dashboard. Store owners can track trends, forecast revenue, spot slow-moving stock, and catch at-risk customers before they leave, with 34 customizable widgets you can arrange however works best for you.

1.1 Who Should Use This OpenCart AI Admin Chatbot

This admin assistant is built for:

Store owners who run the same data checks every morning need a faster way to get there.
Operations staff who want live answers on orders, stock levels, and revenue without loading report pages.
Multi-admin stores where different team members need different levels of access to store data.
Any merchant who wants OpenCart back office analytics powered by AI without relying on a developer.

2.0 Installation Guide

System Requirements

Before installing, confirm your setup meets the following:

OpenCart 3.x
PHP 7.2 or higher
An active API key from OpenAI (ChatGPT), Anthropic (Claude), or Google (Gemini)

Installing the Extension

Step 1: Download the extension ZIP file from your account. Log in to your OpenCart admin panel.

Step 2: Go to Extensions, then Installer. Click the Upload button, select the ZIP file from your system, and click Open. OpenCart processes the upload and extraction on its own.

Step 3: Once the upload confirms, navigate to Extensions, then Extensions. Choose Modules from the category dropdown. Locate the module in the list and click the green Install button next to it.

Step 4: After installation completes, click the Edit button to open the configuration panel for the first time.

Step 5: If the extension does not show up in the list after installation, go to the Dashboard, click the blue cog icon at the top right, and select Refresh to rebuild the cache.

Common Installation Issues

Upload fails: File size exceeds the server limit. Ask your host to raise upload_max_filesize and post_max_size in PHP settings to at least 32 MB, then try uploading again.

Extension not visible after install: Head to the Dashboard and use the cog icon to clear the OpenCart cache. Then return to Extensions, then Modules and search again.

Configuration screen looks broken: Clear your browser cache with a hard reload and reset the OpenCart theme cache from the Dashboard cog menu.

3.0 Admin Panel Overview

The Knowband OpenCart Smart AI Admin Assistant has eight tabs across the top of the configuration screen:

Settings: Core preferences, SQL visibility toggles, voice input, language, log retention, schema cache.
AI Provider: Connect OpenAI ChatGPT, Anthropic Claude, or Google Gemini using your own API key.
Widget Layout: Adjust how the chat widget looks inside the admin with a live preview on the right.
Database Views: Choose which store data domains the AI is allowed to query.
Access Control: Decide which employee profiles can open and use the assistant.
Predefined Chips: One-tap question shortcuts for daily store data checks.
Query History: A running log of every question asked with employee name, response time, and status.
Sessions: Full conversation threads per employee, viewable any time.

4.0 Settings Tab

4.1 General Settings for the OpenCart Smart AI Admin Assistant

Enable Chatbot: The main on/off control for this back office assistant. Turning it off removes the chat widget from the admin panel completely without deleting any saved configuration or query history.

Enable Predefined Chips: Shows or hides the one-tap question buttons inside the chat widget. The chips appear as an expandable panel that any admin can open or close.

Chips Default State: Sets whether the chips panel is open or closed when the widget first loads. Collapsed keeps it tucked away until the admin opens it. Expanded shows the chips panel straight away.

Max Result Rows: The upper limit on how many data rows the AI returns for a single query. Range is 1 to 1000, default is 100. Push it higher for queries that need full datasets and keep it at 100 or below for quick daily checks.

Show SQL Query Toggle: Set to Yes, and the SQL query used to produce each answer appears in the chat below the result. Any admin can read exactly how the data was fetched without asking a developer.

Allow SQL Edit and Re-run: Set to Yes, and the SQL shown under an answer becomes editable in the chat. Change a date range, swap a product category, or shift a threshold and run it again without typing a new question from scratch.

Voice Input: Turns on the microphone icon in the chat input. Speak a question and the browser converts it to text via the Web Speech API. Functions best in Chrome on desktop.

4.2 Language Settings

Use Back-office Language: The assistant replies in whatever language the OpenCart admin panel is currently running. Switch the back office to French, and responses come back in French automatically.

Use Custom Language: Lock the response language to a specific choice regardless of what the admin panel is set to. Useful where staff work in a different language from the back office default.

4.3 Log and Cache Settings

Log Retention (days): The number of days query history stays in the system before old entries are deleted automatically. Default is 90 days. No manual cleanup is needed; the purge runs on its own.

Schema Cache TTL (minutes): The period the extension holds the cached database schema before refreshing it. Default is 1440 minutes. The schema is a map of the store database structure that the AI relies on to build accurate queries. The Settings page displays the last cached timestamp and the next expiry, so the status is always clear.

Refresh Schema Now: Rebuilds the schema cache on demand without waiting for the TTL cycle. Use this after adding a new extension, upgrading OpenCart, or making any structural change to the database.

Click Save Settings to apply all changes on this tab.

5.0 AI Provider Tab

5.1 Choosing Your Provider

The AI Provider tab connects to an external AI model using your chosen provider. OpenAI (ChatGPT), Anthropic Claude, and Google Gemini are all supported. You bring your own API key, and it connects directly, no third-party relay, no separate subscription needed.

Click any provider button to load its settings below: the API key input, the model selector, and the temperature control. One provider is active at a time. Switching providers does not affect existing query history or configuration.

5.2 How to Get Your API Key

OpenAI

Visit platform.openai.com and log in or register.
Open the API Keys section from the account icon menu.
Hit Create new secret key, give it a label, and save.
Copy the key before leaving the page. OpenAI does not show it again. Paste it into the OpenAI API Key field.

Anthropic Claude

Visit console.anthropic.com and log in or register.
Go to API Keys in the left navigation.
Click Create Key, name it, and copy it.
Paste into the Claude API Key field. A direct link to the Anthropic console is also available in the module.

Google Gemini

Visit aistudio.google.com and log in with a Google account.
Click Get API key from the top left.
Pick a project and generate the key.
Copy and paste it into the Gemini API Key field.

5.3 Model Selection for the OpenCart Back Office Analytics Extension

OpenAI:

GPT-4o Mini, quick turnaround, lower API cost, suited to routine daily admin questions.
GPT-4o, stronger reasoning for queries that span multiple joined tables.
GPT-5.5, the most capable tier for complex or layered analytical questions.

Anthropic Claude:

Claude Haiku 4.5, fast and low-cost, works well for morning store checks.
Claude Sonnet 4.6 is a useful middle point between speed and analytical depth.
Claude Opus 4.7 is the best option when queries involve multiple data sources.

Google Gemini:

Gemini 3.5 Flash, fast and capable, the standard starting choice for most stores.
Gemini 3.1 Flash-Lite, the cheapest per query, ideal when keeping API spend low matters.

5.4 Temperature Setting

Governs how consistent or varied the AI responses are. At 0, the answers are most precise. At 1, there is more phrasing variation. For store data queries, 0.3 is the practical starting point. Use 0.0 when strict factual precision is the priority.

Click Save Provider Settings to apply.

6.0 Widget Layout Tab

The Widget Layout tab controls the appearance of the chat widget inside the OpenCart admin. Every adjustment shows in the real-time preview panel on the right before anything is saved.

Position: The screen corner where the chat bubble appears. Bottom Right is the default.

Chatbot Name: The name in the widget header. Smart Admin Assistant by default.

Greeting Message: The first message shown when the widget opens. Default: Hello! Ask me anything about your store.

Bubble Icon: Swap out the default bubble image. Square PNG, 64×64 px, 2 MB limit.

Chatbot Avatar: The image shown beside each bot reply. Square PNG, 48×48 px, 2 MB limit.

Widget Width and Height: The size of the open chat panel in pixels. Default is 400 wide by 560 tall.

Colour Settings: Six colour controls, Header, Chat Bubble, User Message, Bot Message, Background, and Text. No CSS knowledge needed. Changes reflect in the preview immediately.

Click Save Layout to apply.

7.0 Database Views Tab

7.1 How Database Views Work in This OpenCart Admin AI Chatbot

A set of pre-built MySQL views was built for the OpenCart AI reporting extension that organises and simplifies the relevant data for each domain. Queries run against these views only; the AI has no path to raw tables, and all views are read-only. Store data cannot be changed, deleted, or written through the chat under any circumstances.

Unticking a view removes that domain from the assistant’s allowed query list. The view stays in the database intact and can be re-enabled at any point.

7.2 Available Database Views

Orders Overview: Orders joined with customer details, currency, status, and totals.
Order Line Items: Individual product lines per order with quantities and prices.
Customers: Full customer records with group, gender, and last visit date.
Products: Catalog data with name, stock, price, category, and image info.
Specific Prices / Product Discounts: Per-product and per-combination price overrides. Off by default.
Categories: Category names and their hierarchy.
Shopping Carts: Active and abandoned carts with customer and currency details.
Cart Rules / Coupons: Discount rules with usage data and free shipping flag.
Stock Availability: Stock levels per product and combination with readable names.
Employees: Admin accounts and their profile data.
Customer Addresses: Address records with country, state, and customer data resolved.
Carriers / Shipping Methods: Active carriers with delivery delay text. Off by default.
Manufacturers / Brands: Brand records with descriptions and product counts.
Product Combinations / Variants: Variant data with stock, reference, and attribute names.
Product Attributes and Values: Attribute groups like Colour and Size with their values.

Click Save and Create Views to apply. The Knowband extension builds the MySQL views for any domain switched on.

8.0 Access Control Tab

The Access Control tab sets which OpenCart admin staff can open the assistant.

Tick: Restrict the chatbot to specific employee profiles to switch role-based access on. When this is off, every logged-in admin can use the assistant without restriction.

When role-based access is active, a profile list appears below. SuperAdmin access is permanent and does not appear in the list. Tick any other profiles, Logistician, Salesman, Translator, or custom roles, that should have access. Profiles left unticked see no assistant when they log in. Leaving all profiles unticked while role-based access is on limits the assistant to SuperAdmin only.

Click Save Access Settings to apply.

9.0 Predefined Chips Tab

Predefined chips are question shortcuts built into the chat widget. Each chip sends a stored question to the AI the moment it is tapped, no typing, no navigation.

9.1 Default Chips in the OpenCart Order Insights Plugin

Ten chips come ready out of the box:

Orders Today: How many orders were placed today?
Revenue (30d): What is the total revenue in the last 30 days?
Cancelled Orders: How many orders were cancelled in the last 30 days?
Abandoned Carts: How many carts were abandoned in the last 30 days?
Active Customers: What is the current active customer count?
Out of Stock: Which products are at zero stock right now?
Low Stock (under 5): Which products have fewer than 5 units left?
No SKU Products: How many products are missing a SKU reference?
Free Shipping Coupons: Which active coupons offer free shipping today?
New Customers (This Month): How many customers registered this month so far?

9.2 Adding a Custom Chip

Click Add Chip to open the chip form.

Label: Short button text. Keep it under three words. For example: Weekly Revenue.

Question: The question the AI gets when this chip is tapped. Write it the same way you would type it into the chat directly. For example: What is the total revenue for the past 7 days?

Position: The chip’s position in the panel list. Lower numbers appear first.

Active: Yes displays the chip in the widget. No keeps it saved but hidden.

Click Save Chip to finish. Edit and Delete buttons appear on each row for future changes.

10.0 Query History Tab

The Query History tab records every question sent through this tool. Each log entry shows:

Date: The time the query was sent.
Employee: Which admin account ran it.
Question: The full text of what was asked.
Rows: Number of data rows the query returned.
Time (ms): How long the query took to run.
Provider: The AI service that handled it, shown as a labelled badge.
Status: Green for success, red for errors.
SQL: The query that ran, visible inline.

Filter by status and date range at the top. Export visible results to CSV or Excel using the buttons above the table. Click Purge Old Logs to remove entries older than the Log Retention setting immediately.

11.0 Sessions Tab

The Sessions tab holds the full conversation history per employee. Each row shows the employee name, session start time, and message count. Click View to open the complete thread, questions and responses in chronological order in a pop-up window. Useful for reviewing what data was accessed, checking how the assistant is being used, or continuing the thread from a previous session.

12.0 Analytics Dashboard

The Analytics Dashboard gives you a real-time overview of your store’s performance, including sales, orders, customers, and inventory, all from a single screen in your OpenCart admin panel. The dashboard is organised into three widget groups:

Key Metrics: KPI cards summarising revenue, orders, and customer activity
Charts & Trends: visual breakdowns of sales over time and by category
Lists & Tables: detailed rankings such as best sellers and low stock alerts

Every admin user can choose which widgets appear on their own dashboard and reorder them freely. Store-wide behavior, such as which order statuses count as revenue, is controlled centrally by an administrator in Settings → Analytics Dashboard Settings.

12.1 Analytics Dashboard Settings

Store owners can find the dashboard setting in Settings -> Analytics Dashboard Settings
This is the central OpenCart admin dashboard settings screen for Knowband Smart AI Admin Assistant. Every field here applies globally, to all admin users. Individual users can still personalise which widgets they see and how they’re arranged from the dashboard’s Customize panel. Use this section to configure how your OpenCart analytics dashboard calculates revenue, which time period it opens with, how it looks, and whether it replaces your OpenCart admin home page.

12.2 Dashboard Settings in Smart AI Admin Assistant

Revenue Order Statuses

Revenue Order Statuses: This field controls which OpenCart order statuses count as revenue across every sales widget on the dashboard, including Revenue, Orders, Average Order Value, Best Sellers, Top Customers, and Coupon Usage.

Default Period

The default period is the period in which you want your dashboard to show the analytical data. Options are included as Last 7 days, Last 30 days, Last 3 months, Last 6 months, Last 1 year

Colour Theme

The colour theme is the theme of the dashboard which shows the analytics data. This module includes the Options like Indigo (default), Ocean, Emerald, Rose, Dark, and Custom.

List Rows

This feature controls how many rows are displayed in every list and table-style widget on the dashboard, including Best Sellers, Top Customers, Slow Movers, Reorder Suggestions, Churn Risk, Low Stock Alerts, Coupon Usage, and Brand Performance.

Churn Window

This defines the number of days of customer inactivity after which a customer is flagged in the Churn Risk widget, one of the key OpenCart customer retention tools on the dashboard.

Low Stock Threshold

This feature sets the product quantity at or below which a product is treated as “low stock” across the Low Stock, Low Stock Alerts, and Reorder Suggestions widgets, forming the basis of the dashboard’s OpenCart inventory management alerts.

Replace Default Dashboard

Store owners can enable the same to control whether the Analytics Dashboard should replace your opencart default dashbpard.
The admin home page automatically opens the Analytics Dashboard instead of OpenCart’s default dashboard the moment any admin user logs in. When set to Disabled, OpenCart’s standard dashboard remains the default landing page, and the Analytics Dashboard is accessed separately from the admin menu whenever needed.

5. Customising Your Dashboard

Each admin user can personalise their own dashboard layout independently by clicking on customisation on the dashboard.

Click Customise (widget library icon) on the dashboard.
Move or reorder any widget within its group (Key Metrics, Charts & Trends, Lists & Tables).
Close the panel, and now you will see the customised dashboard. You can click on Restore default to restore it to the original dashboard.

12.2 Key Metrics (17 widgets)

Revenue
Total order value for the selected period and order status chosen from the dashboard setting, with a daily trend graph and percentage change versus the previous period. This feature works as an OpenCart revenue report on the dashboard.

Orders
Total number of orders placed in the selected period, with a daily trend graph and percentage change, forming the base of the dashboard’s OpenCart order analytics.

Avg. Order Value
These values show the avgerage value per order, calculated on the basic total revenue divided by the total number of orders. Average order value provides store owners with a real-time check at a single glance. Instead of digging through spreadsheets, Excel, owners can instantly see if their pricing and marketing strategies are actually working.

Items Sold
This KPI metric shows the total units sold across all orders in the period that store admins have selected, which is useful for tracking sales volume independent of revenue.

Items per Order
This item per order metrics shows the items per order, so that store owners can have a idea of how he is selling items like individually or in bulk with OpenCart Analytics & Reporting Extension.

Discounts Given
The discount given option in the OpenCart AI Sales Analytics Plugin give the total value of coupon, voucher, and reward discounts applied during the selected period with per cent change from the previous analytics

Taxes Collected
The OpenCart AI Reporting Extension give the figure of total tax collected from orders in the period, useful for reconciliation and reporting.

Shipping Revenue
This feature gives the total shipping charges collected from customers on the orders during the selected periods, also show the percentage changes compared with the previous data.

Refunded Value
The total amount that is refunded will be marked as refunded in the selected periods, giving visibility into returns and lost revenue.

New Customers
Shows the total number of customers who registered during the selected period, calculated directly from new account sign-ups. This OpenCart Customer Analytics metric helps store owners gauge the real-time impact of acquisition campaigns, rather than waiting on a manual account export.

Repeat Customers
Counts customers who placed two or more orders within the selected period. This figure feeds directly into the dashboard’s OpenCart Customer Retention Dashboard, giving store owners a quick read on loyalty without cross-referencing order history manually.

Returning Buyer Rate
Shows the percentage/rate of buyers in the period who ordered more than once, which is calculated as repeat customers divided by total unique purchasers. This AI Assistant acts as an OpenCart Customer Analytics indicator; it shows store owners whether their retention strategy, from email marketing to loyalty programs, is actually converting first-time buyers into repeat business.

Total Customers
Total customers display every customer registered in the store to date, independent of the period selector. As a Real-Time Store Analytics snapshot, it always reflects the current customers the moment the dashboard loads, giving store owners an accurate data to check growth.

Active Products
Shows the number of products currently enabled and available for purchase in the storefront. This snapshot gives store owners an instant read on active catalogue size, useful when auditing inventory as part of the dashboard’s broader OpenCart Inventory Management toolkit.

Out of Stock
Flags-enabled products are currently sitting at zero quantity. As part of the OpenCart Inventory Management alert system, this widget lets store owners catch stockouts immediately, rather than discovering them after a lost sale.

Low Stock
Counts enabled products at or below the low-stock threshold configured in Analytics Dashboard Settings. This real-time alert gives store owners an early warning system for reordering, well before a product actually runs out.

Units in Stock
Totals the quantity across every enabled product in the store, giving a single figure for overall inventory volume. Store owners can use this widget alongside Low Stock and Out of Stock for a complete OpenCart Inventory Management picture in one glance.

12.4 Charts & Trends (9 widgets)

Revenue Trend
Plots revenue over time as a line chart, daily for periods up to six months and monthly for a full year. As a visual extension of the dashboard’s OpenCart Sales Report data, it helps store owners quickly spot spikes, dips, or seasonal patterns that raw numbers alone can hide.

Revenue Forecast
Analyses the last 90 days of trading and projects likely revenue for the next 30 days, using recent trend data rather than the selected period. This OpenCart Revenue Forecast widget helps store owners plan cash flow, stock orders, and marketing spend ahead of time, based on real sales momentum rather than guesswork.

Orders Trend
Charts order count over time using the same daily or monthly logic as Revenue Trend. It gives store owners a volume-based counterpart to the revenue chart, feeding into the dashboard’s wider OpenCart Order Analytics view of how order activity is moving.

Payment Methods
This chart shows how revenue splits across the payment options customers actually chose at checkout. If one method is quietly outperforming the rest, it’s worth understanding why, and if another barely gets used, that’s often a sign it needs more visibility or trust-building on the checkout page.

Sales by Country
A simple bar chart of revenue by shipping destination, but a genuinely useful one. It’s usually the fastest way to see where a store’s real strength lies geographically, which matters a lot if you’re weighing up new shipping zones or where to put the next ad budget.

Order Status
One bar list, every active status, revenue and order count side by side. It’s the quickest way to answer “where are things sitting right now,” whether that’s orders still processing, ones stuck pending, or ones already through to completion.

Sales by Carrier
Breaks revenue down by shipping method so you can see which carriers your customers end up using most. Worth checking every so often, especially when it’s time to renegotiate rates or decide if a new carrier option is actually needed.

Sales by Day of Week
Takes the whole selected period, not just last week, and groups total revenue by weekday. Patterns tend to show up here that aren’t obvious day to day, like a Thursday that consistently outsells everything else, which is handy to know when planning promotions or staffing.

Sales by Hour
Once you can see exactly when customers are most likely to buy, timing things like flash sales, email sends, or live support becomes a lot less guesswork and a lot more strategy.

12.4 Lists & Tables (8 widgets)

Best Sellers
Ranks products by units sold, with reference, quantity, and revenue shown side by side. As a key part of any OpenCart Sales Report review, this widget tells store owners exactly which products are carrying the business.

Slow Movers
Lists active products with the fewest sales in the selected period, helping store owners spot stock that needs a promotional push, a price adjustment, or removal from the catalog altogether.

Top Customers
Ranks customers by total revenue, alongside their order count, giving store owners a clear view of who to prioritize for loyalty perks, personal outreach, or account management as part of a broader OpenCart Customer Analytics strategy.

Churn Risk
Flags high-value customers who haven’t placed an order beyond the configured Churn Window, along with their lifetime value and last order date. This is the core of the dashboard’s OpenCart Customer Retention Dashboard, helping store owners win customers back before they’re gone for good.

Low Stock Alerts
Lists every product currently at or below the configured stock threshold, or already out of stock, with reference and quantity. This is a core OpenCart Inventory Management tool that gives store owners an early warning before a bestseller disappears from the shelf.

Reorder Suggestions
Calculates suggested reorder quantities for products sold in the last 30 days, based on current stock, units sold per day, and days of stock cover remaining. Store owners can use this feature to restock exactly the right amount, avoiding both overstocking and stockouts.

Coupon Usage
This shows every coupon redeemed during the selected period, along with number of uses and total discount value, so store owners can measure which promotions are actually driving orders versus which ones are just cutting into margin.

Brand Performance
Ranks manufacturers by revenue and units sold, rounding out the dashboard’s OpenCart Business Intelligence view of what’s actually driving the store, down to the brand level.
Rights Reserved.

12.0 Frequently Asked Questions

Q: What is the Knowband OpenCart Smart AI Admin Assistant, and how does it work?

This is an OpenCart Admin AI Chatbot that lets store admins ask plain-language questions and get answers from live store data instantly. It connects to the store database through pre-built read-only MySQL views, sends each question to the chosen AI provider, OpenAI, Anthropic Claude, or Google Gemini, which builds and runs a SQL query, then delivers the result in natural language. Compatible with OpenCart 3.x.

Q: Which AI providers work with the OpenCart back office analytics tool?

The Knowband OpenCart Smart AI Admin Assistant supports OpenAI (GPT-4o Mini, GPT-4o, GPT-5.5), Anthropic Claude (Haiku 4.5, Sonnet 4.6, Opus 4.7), and Google Gemini (Gemini 3.5 Flash, Gemini 3.1 Flash-Lite). Each provider connects via your own API key with no extra subscription. You pay only for what the AI actually processes.

Q: Can the OpenCart Smart AI Admin Assistant change or delete any store data?

No. The OpenCart AI sales analytics tool reads data only through pre-built MySQL views. No query sent through the chat can update, delete, or write anything back to the database. Every response is a read-only retrieval from your live store.

Q: What data can I query using the OpenCart admin AI chatbot?

Orders, customers, revenue, stock, abandoned carts, discount coupons, product combinations, employee accounts, shipping carriers, brands, and categories are all queryable. The Database Views tab governs which domains are active. Switch a domain on to allow it, switch it off to restrict it.

Q: How do predefined chips work in the OpenCart Smart Store Analytics tool?

Chips are one-tap question buttons in the widget. Tap one, and the saved question goes to the AI straight away. The default chip set covers orders, revenue, abandoned carts, low stock, out-of-stock items, active customers, new customers, cancelled orders, free shipping coupons, and products without a SKU. New chips can be added, edited, or removed from the Predefined Chips tab.

Q: What does the SQL visibility feature do in the OpenCart back office analytics tool?

Enable Show SQL Query Toggle, and the SQL behind each answer appears in the chat below the result. Turn on Allow SQL Edit and Re-run as well, and that SQL becomes editable directly in the chat. Change a date, a filter, or a threshold and run it again without asking a new question. This OpenCart AI sales analytics tool makes this accessible to any admin, not just those with SQL knowledge.

Q: How does role-based access control work in the OpenCart AI admin chatbot?

Open the Access Control tab and tick Restrict the chatbot to specific employee profiles. SuperAdmin access cannot be removed. For every other profile, Logistician, Salesman, Translator, or any custom role, tick the ones that should have access. Any profile left unticked will not see the assistant after logging in.

Q: What is the schema cache in the OpenCart back office analytics tool?

The schema cache holds the structural map of the store database so the AI can build queries accurately without reading the full database on every request. The first chat session builds it automatically. It refreshes based on the Schema Cache TTL setting. After installing a new extension, upgrading OpenCart, or making any database change, use Refresh Schema Now to rebuild it on the spot.

Q: How do I connect an AI provider to the OpenCart Smart AI Admin Assistant?

Go to the AI Provider tab. Click the provider you want: OpenAI, Anthropic Claude, or Google Gemini. For OpenAI, sign in at platform.openai.com, go to API Keys, and generate a new secret key. For Anthropic, sign in at console.anthropic.com, open API Keys, and create one. For Gemini, sign in at aistudio.google.com, click Get API key, and generate one for your project. Paste the key into the relevant field and save.

Q: Is the OpenCart Smart AI Admin Assistant compatible with OpenCart 3.x?

Yes. The Knowband OpenCart Smart AI Admin Assistant works on OpenCart 3.x. Visit the product page for current compatibility details and version notes.

13.0 Conclusion

The Knowband OpenCart Smart AI Admin Assistant delivers AI-powered OpenCart back office analytics to any OpenCart store without needing SQL knowledge, developer support, or third-party reporting platforms. Ask in plain English, get answers from live data, view the SQL behind each result, and refine it on the fly.

The Opencart AI Assistant for Admin is now available on OpenCart Marketplace. Try the demo now.

For support, custom requirements, or OpenCart development work, contact the Knowband team directly.

Opencart Catalogue Import Export Extension User Manual

If you manage a growing OpenCart store, you already know how time-consuming manual product updates can be. The Knowband OpenCart Import Export Scheduler Pro is, therefore, purpose-built to eliminate that friction entirely. It handles bulk product and category transfers in CSV, XLSX, JSON, and XML formats all from within the OpenCart admin panel with no coding, no developer involvement, and no wasted hours.

Furthermore, what truly sets this OpenCart bulk product import/export extension apart from generic tools is its reusable profile system. Every import or export task is consequently saved as a named profile with its own file format, column mapping, FTP or SFTP destination, and optional cron schedule. As a result, store owners can move from one-off data dumps to fully automated, scheduled catalogue syncs in a matter of minutes.

Moreover, whether you are running a daily supplier feed via FTP, migrating products between two OpenCart stores, or pushing bulk price updates to a remote SFTP server, Knowband‘s OpenCart Catalogue import export extension covers every scenario out of the box. No custom code is required. The OpenCart catalogue Migration via Import Export Extension is now available on the OpenCart Marketplace

1.1 Key Capabilities of Opencart Import Export Extension

Four file formats are supported for OpenCart bulk product import/export: CSV, XLSX, JSON, XML
Reusable named profiles with saved mappings, format settings, and FTP/SFTP configuration
FTP, FTPS, and SFTP transfer with live connection testing before saving
Fully automated, unattended OpenCart cron import/export on any schedule
Column auto-matching with required-field validation that blocks incomplete imports
Full import export support for OpenCart product combinations and variants
Multilingual field handling export and import translated fields across all active languages
Transfer Logs with row-level error detail and re-download links for every run
Automatic file cleanup on a configurable retention schedule
Compatible with OpenCart 3. x.x | PHP 7.2+ | MySQL 5.6+

1.2 Who Is This Extension For?

This OpenCart CSV import export extension is specifically designed for:

Store owners managing catalogs of 100 to 50,000 SKUs who need repeatable bulk updates without manual effort
Agencies handling multiple OpenCart stores and requiring smooth catalogue migration between instances
International stores managing multilingual product data across several active languages
Businesses syncing supplier feeds on a daily or hourly schedule via FTP or SFTP
Administrators who want a reliable, log-backed history for every OpenCart bulk import/export run

2. Installation

Before proceeding, verify that your server meets the minimum requirements for Knowband‘s OpenCart scheduled import export extension: OpenCart 3.x.x, PHP 7.2 or higher, and MySQL 5.6 or higher.

Step 1: Upload via FTP

To begin with, extract the ZIP archive downloaded from the Knowband store. Connect to your server via an FTP client and copy all extracted files from the upload folder into the root directory of your OpenCart installation.

Step 2: Install in the Admin Panel

Next, log in to your OpenCart admin panel. Navigate to Extensions > Extensions, locate Knowband Import Export Plugin in the list, and click Install. The Plugin will thereafter be registered with your OpenCart instance.

Step 3: Configure

Finally, click Edit on the same row to open the extension configuration page. You will land on the General Settings tab, where all global preferences including cron URLs, file size limits, and cleanup schedules are managed.

3. Admin Panel Overview

Once installation is complete, the Knowband OpenCart Import Export Scheduler Pro adds four clearly organised tabs inside its configuration page. Understanding each tab’s purpose is, consequently, the fastest way to get productive with OpenCart bulk catalog management.

4. General Settings

The General Settings tab is the control centre for all global behaviours of the OpenCart import export extension. It is divided into four sub-sections. Configuring these settings correctly upfront will, in turn, ensure that all subsequent import and export operations run smoothly.

4.1 Preferences

Extension Enable / Disable turns the entire extension on or off. When disabled, all scheduled cron import and export tasks are paused immediately.

Maximum Visible Columns sets how many columns display at once in the OpenCart import mapping table. Range: 1–20. Default: 6. Use the pagination arrows to navigate remaining columns.

Maximum Visible Rows sets how many sample data rows appear in the mapping preview. For visual verification only does not restrict the actual import row count. Range: 1–50. Default: 10.

Import Batch Size controls how many rows are processed per AJAX request during OpenCart bulk product import. Lower values reduce timeout risk on shared hosting. Range: 10–500. Default: 100. On VPS or dedicated servers, increase to 300 or higher for faster large imports.

Click Save Settings to apply.

4.2 Template Files

This section provides ready-to-fill sample files for every supported entity and format combination an essential starting point for anyone setting up an OpenCart CSV import or XLSX-based bulk upload for the first time. Two entities are available: Products and Categories. Each has four format buttons: CSV, JSON, XML, and XLSX.

Simply click the relevant button to download the template. Each template includes every column the importer recognises, with safe placeholder data. Fill it with real product data and import it back.

Important: Your uploaded file must follow the column layout shown in the templates. Deviating from this layout will cause column auto-matching to fail and require manual remapping.

4.3 Limits and Speed

Max Records Per Download: Maximum number of records exported per file. Increase only if your server memory supports it. Range: 100–50,000. Default: 5,000.

Max Upload Size (MB) Maximum import file size the plugin accepts. Works alongside PHP’s server-level upload limit; whichever is lower takes effect. Range: 1–200 MB. Default: 50 MB.

Click Save Settings to apply.

4.4 Scheduled Cleanup and Cron URLs

This is where you configure the three cron job URLs that power the automated side of Knowband‘s OpenCart scheduled import/export system. Each URL has a dedicated Copy button; paste it directly into your server crontab or OpenCart’s built-in scheduled tasks.

Keep Files For (Days) Import and export files older than this number of days are deleted automatically by the cleanup cron. Range: 1–30 days. Default: 7 days.

Cleanup Cron URL Recommended: daily at 2 AM. Deletes old temporary files automatically.

Export Profiles Cron URL: Recommended: daily at 3 AM. Runs every export profile flagged as cron-enabled and stores the generated file in Transfer Logs.

Import Profiles Cron URL Recommended: daily at 4 AM. Fetches files via FTP/SFTP and runs every FTP-source import profile flagged as cron-enabled. Upload-source profiles are manual-only and are skipped automatically.

Click Save Settings to apply.

5. Export Profiles: Complete Walkthrough

The Export tab lists all saved export profiles. Knowband‘s profile-based approach means you set up the OpenCart bulk export once and reuse it indefinitely either manually with one click or automatically on a cron schedule. Each profile displays its ID, name, entity type, format, cron status, and date added.

Click Add Export Profile to create a new one. The wizard runs through three steps: Transfer Settings, Choose Fields, and Generate File.

5.1 Step 1 Transfer Settings

Profile Name: A unique label for this profile in the Export listing. Example: Weekly Product Feed.

Output File Label: Base name for the generated file. The plugin is added automatically. Use letters, digits, hyphens, and underscores only. Example: products-daily.

Data Type: Select Products or Categories.

File Format: Select CSV, XLSX, XML, or JSON.

Language(s) Select one or more store languages. Translated fields such as name and description are exported for each selected language. Select All Languages to include every active language, a key feature for multilingual OpenCart product import export workflows.

Date Range (optional) Filter records by creation date. Leave blank to export all records.

Record Order (optional) Controls row sequence in the output file. Leave on default for standard database order.

Export Product Combinations (Options/Variants). When enabled, each product row is followed by one row per combination. Adds the columns row_type, parent_reference, combination_reference, attributes, and impact_price. Enable this for a full OpenCart catalog export that includes all product variants.

Scheduled Run Enable Cron When on, the Export Profiles Cron URL runs this profile automatically and stores the generated file in Transfer Logs after each run.

Export Destination

The file system saves the file locally. Administrators download it directly from Transfer Logs.

FTP / SFTP pushes the file to a configured remote server after each run. A local copy is also retained in Transfer Logs as a fallback.

When FTP / SFTP is selected, the following additional fields appear, Username, Password, Hostname and Remote Folder which is basically a path name of the folder on which you will export.

Output Style (CSV Delimiter): Universal comma, Windows/Excel semicolon, or Tab-separated.

List Glue Separator for multi-value fields such as Tags and Category Names. Options: Pipe, Slash, or Comma.

Narrow by Category / Manufacturer / Supplier. Optional filters to scope the export to a specific product subset.

Price Window: Include only products within a specified minimum–maximum price range. Leave blank for no filter.

Click Next Step to proceed.

5.2 Step 2 Choose Fields

Every available product or category column appears as a selectable checklist. Required fields, marked with an asterisk, cannot be deselected. Additionally, you can reorder columns by dragging rows to control the exact sequence in the output file.

Three quick-action buttons are available:

Select All includes every available column in the export.
Deselect All Clears all optional selections, leaving only required fields active.
Reset to Defaults restores the recommended default column set.

Available product fields include: ID, Model (SKU), Name, Status, Product Type, Condition, Manufacturer, Supplier, Tags, Date Added, Short Description, Description, Weight, Dimensions, EAN, UPC, MPN, Meta Title, Meta Description, SEO URL, Cover Image URL, All Image URLs, Category IDs, Category Names, Price, Cost Price, Special Price, Minimum Quantity, Stock Quantity, Stock Status, and Out of Stock Behaviour making it one of the most comprehensive OpenCart bulk product export tools available.

Click Preview Data to see the first five rows based on your current selection. Click Save Profile to save without generating, or Next Step to proceed.

5.3 Step 3: Generate File in Opencart Catalogue Import Export Plugin

The final step presents a Download Summary confirming Data Type, File Format, File Label, and Fields Selected. Click Build and Download to generate the file immediately. The file downloads to your browser or is pushed to the configured FTP/SFTP destination, and the run is recorded automatically in Transfer Logs.

Note: Export files remain available for re-download in Transfer Logs until the scheduled cleanup cron removes them after the configured retention period.

6. Import Profiles Complete Walkthrough

The Import tab, similarly to the Export tab, lists all saved import profiles. Each profile shows its ID, name, entity type, format, source type (Upload or FTP), cron status, and date added. Click Add Import Profile to begin the three-step wizard: Source Settings, Map Columns, and Run Import.

6.1 Step 1 Source Settings

Profile Name: A unique label for this profile. Example: Daily Supplier Feed.

Data Type: Products or Categories.

File Format CSV, XLSX, JSON, or XML must match the actual file format.

Output Style: CSV delimiter matching the file being imported.

List Glue must match the glue used during the corresponding export. This setting directly affects multi-value fields like Tags, Categories, and Image URLs.

Language: Default language for rows that do not specify their own language within the file.

Import Options

Update existing records when ID or model matches. Standard setting for all regular OpenCart bulk product import runs. Updates an existing product when a matching ID or SKU is found instead of creating a duplicate.

Force IDs from the file. Use only when migrating between stores where preserving the exact original product ID is required. Not recommended for routine imports.

Source Selection

Upload File for one-time manual imports. Maximum file size: 50 MB. Accepted formats: CSV, XLSX, JSON, XML.

FTP / SFTP For pulling files from a remote server. Required for cron-driven automated OpenCart imports via scheduled FTP product sync.

When FTP or SFTP is selected as the source for an import profile in the Knowband OpenCart Import Export Scheduler Pro, a set of additional configuration fields appears on the screen. Each field plays a specific role in establishing the remote connection and controlling how the automated OpenCart scheduled import behaves.

The Transfer Protocol field is where you choose the connection method between FTP, FTPS, or SFTP. FTPS is generally recommended for production environments because it adds a layer of encryption over the standard FTP connection. The Server field takes the address of your remote FTP server, for example ftp.example.com. Right alongside it, the Port field auto-populates based on whichever protocol you select, which is 21 for FTP and 22 for SFTP, though you can override this if your server uses a non-standard port.

The Username and Password fields hold the login credentials for the remote server. Both are stored encrypted at rest, meaning they are never saved in plain text anywhere in the system. Once you have filled in the credentials, the Remote File Path field requires the absolute path to the source file on the remote server.

This path must be exact and the file must exist at that location every single time the OpenCart cron import export runs. A typical example would be something like /home/feed/products.xml.

Passive Mode is a toggle that is recommended for FTP and FTPS connections, as it helps avoid connection issues caused by firewalls blocking the data channel. When SFTP is selected as the protocol, this setting is simply ignored.

The Cron toggle, when enabled, instructs the Import Profiles Cron URL in General Settings to automatically fetch the file from the remote server and run the OpenCart bulk product import on the configured schedule, without any manual intervention.

Click Save Profile, then Next Step.

6.2 Step 2: Map Columns

The column mapping screen loads actual rows from your uploaded or fetched file. Each column from your file is matched to the correct OpenCart field. Knowband‘s auto-matching engine detects column names and maps them without manual intervention wherever possible.

A confirmation at the top of the screen shows how many columns were successfully matched for example: 47 of 47 columns auto-matched. Nevertheless, you should still review the mapping below to verify accuracy, particularly for custom or non-standard column names.

Each file column appears as a dropdown selector at the top of its respective data column. The rows below display real data values from the file, making it straightforward to verify that each column is mapped correctly. Use the search box to find a specific column, and navigate through remaining columns with the pagination arrows.

Important: If a required field is left unmapped, the extension blocks the import and displays a warning before allowing you to proceed. This OpenCart import mapping validation step ensures data integrity on every run.

Click Save Profile to save the mapping. Click Next Step to proceed.

6.3 Step 3: Run Import

Once the mapping is confirmed, two options are presented:

Save Profile saves the import profile for future use without running the import immediately.

Start Import runs the import in batches as configured in General Settings. When complete, Transfer Logs records the full result: total records processed, successful records, and any failures with row-level error detail.

For large catalogs, the batch processing approach used by Knowband‘s extension means the OpenCart bulk product import continues reliably even on shared hosting because each batch is a separate AJAX request; server timeouts cannot interrupt the overall process.

7. Transfer Logs

The Transfer Logs tab provides a comprehensive history of every import and export operation run through the extension. This is, consequently, the first place to check whenever an OpenCart bulk import export run produces unexpected results or an export does not appear in the expected destination.

Using Transfer Logs for Troubleshooting

Click the Log button on any row to open row-level error detail for failed records. This detail view shows precisely which rows failed and the specific error reason for each. As a result, you do not need to re-import the entire file; simply fix only the affected rows in your source file and re-import just those rows.

Export files remain available for re-download in the Logs tab until the scheduled cleanup cron removes them after the configured retention period (default: 7 days). This gives you ample time to verify, redistribute, or archive any generated OpenCart bulk export.

8. Frequently Asked Questions

Question1: What is the Knowband OpenCart Import Export Scheduler Pro?

Knowband‘s OpenCart Import Export Scheduler Pro is a professional-grade bulk data management extension for OpenCart 3.x.x. It handles product and category imports and exports in CSV, XLSX, JSON, and XML, and furthermore includes reusable profiles, column mapping with validation, FTP/SFTP file transfer, cron scheduling, email notifications, and full transfer logs all from the OpenCart admin panel without any developer involvement.

Question2: How do I bulk upload products in OpenCart using a CSV file? Go to the Import tab and click Add Import Profile. Set the data type to Products, select CSV as the format, upload your file under Pick Source, and click Next Step. The extension auto-matches columns and displays the first rows of the actual file for verification. Confirm the mapping and click Start Import. Sample CSV templates are available from General Settings > Template Files to ensure your file follows the correct column layout.

Question3: Can I import and export OpenCart product combinations and variants? Yes. Enable Export Product Combinations (Options/Variants) in the export profile settings. Each product row is consequently followed by one row per combination, with attributes presented in a readable format. On re-import, any missing attribute groups and values are created automatically in the destination store.

Question4: How do I automate OpenCart product imports using cron jobs? Create an import profile with FTP or SFTP as the source and enable Cron in the scheduling section. Next, copy the Import Profiles Cron URL from General Settings > Scheduled Cleanup. Add it to your server crontab or OpenCart’s scheduled tasks with the required interval. From that point on, Knowband‘s extension handles the entire fetch-and-import cycle automatically a complete solution for scheduled OpenCart import automation.

Question5: How do I migrate products from one OpenCart store to another? Export the full catalog from the source store using any supported format. Import the resulting file into the destination store using a new import profile. Categories, product combinations, and attribute values that do not exist in the target store are created automatically on import, making cross-store OpenCart catalog migration clean and complete.

Question6: What happens if a bulk import fails or has errors? Every run is logged in Transfer Logs with a full record count. Partial failures show the count as X / Y with failures highlighted. Click the Log button on any row to review row-level error detail. Fix only the affected rows in your source file and re-import just those rows there is no need to process the entire file again.

Question7: Which OpenCart versions does this extension support? Knowband‘s OpenCart Import Export Scheduler Pro is compatible with OpenCart 3.x.x, running on PHP 7.2 or higher and MySQL 5.6 or higher.

Question8: Can I schedule exports to be pushed automatically to an FTP server? Yes. In the export profile’s Transfer Settings, set the Export Destination to FTP / SFTP, configure the remote server credentials, and enable Cron. Thereafter, the Export Profiles Cron URL when added to your server crontab will automatically generate and push the export file to your FTP server on the schedule you define. Knowband‘s Opencart Import Export Extension additionally retains a local copy in Transfer Logs as a fallback for every automated run.

9. Tutorial

Admins can check the overall functionality through the tutorial video for the Opencart Import Export Extension