-
Posts
281 -
Joined
-
Last visited
On this page you can find all the add-ons and services from IHOR1989
The module is designed to automatically display a modal window with similar products if the selected product is out of stock.
When a customer opens a product page with the status “Out of stock”, the system displays a modal window after a specified delay, showing products that are in stock and selected according to the configured filters.
This allows you to
avoid losing customers; quickly offer alternative products; increase conversion rate and number of orders. Module features
The module settings include the following parameters:
number of products – defines the maximum number of products displayed in the modal window; modal display delay – allows you to set the time (in seconds) before the modal window opens automatically after the product page is loaded; category filter – allows displaying only products from the same category as the current product; manufacturer filter – allows displaying products from the same manufacturer as the viewed product. How it works
The customer opens a product page. If the product is out of stock, the module is activated. After the specified delay, a modal window opens. The window displays in-stock products selected according to the chosen filters. The customer can immediately switch to an alternative product. Compatibility
OpenCart 3.x Theme compatibility
The extension is compatible with the standard default theme. For other themes, adaptation may be required (adaptation is paid).
Installation
Install the module via the OpenCart administration panel Refresh the modifications Enable and configure the module. DEMO
Admin Page login/password: demo/demodemo Store Page License
The license is valid for one domain and its subdomain.
When a customer opens a product page with the status “Out of stock”, the system displays a modal window after a specified delay, showing products that are in stock and selected according to the configured filters.
This allows you to
avoid losing customers; quickly offer alternative products; increase conversion rate and number of orders. Module features
The module settings include the following parameters:
number of products – defines the maximum number of products displayed in the modal window; modal display delay – allows you to set the time (in seconds) before the modal window opens automatically after the product page is loaded; category filter – allows displaying only products from the same category as the current product; manufacturer filter – allows displaying products from the same manufacturer as the viewed product. How it works
The customer opens a product page. If the product is out of stock, the module is activated. After the specified delay, a modal window opens. The window displays in-stock products selected according to the chosen filters. The customer can immediately switch to an alternative product. Compatibility
OpenCart 3.x Theme compatibility
The extension is compatible with the standard default theme. For other themes, adaptation may be required (adaptation is paid).
Installation
Install the module via the OpenCart administration panel Refresh the modifications Enable and configure the module. DEMO
Admin Page login/password: demo/demodemo Store Page License
The license is valid for one domain and its subdomain.
Updated
Similar Products in modal popup
320 грн
1 3
Це доповнення дозволяє отримувати прайси українського постачальника ЮгКонтракт за допомогою API для подальшої обробки парсерами товарів, такими як АОП або SimplePars. Доповнення тестувалося на OcStore 3.0.2.0/3.0.3.7. Якщо додаток буде затребувано, буде адаптовано для OcStore 2.3.
Основні можливості:
Налаштування завантаження прайсу здійснюється на сторінці Вашого магазину. Вивантажується два типи прайсу методами GET-PRICE, GET-CONTENT-GOODS. Формат прайсів – XML. Категорії для вибору вивантажуються також за допомогою методу GET-CATEGORIES з сайту постачальника. Можливість завантаження прайсів за допомогою CRON-завдань.
Вимоги для коректної роботи модуля:
Дозвіл користування API із боку постачальника, тобто. IP-адреса сайту має бути додана з боку постачальника (можливо доведеться звернутися до Вашого менеджера). Наявність даних авторизації USER_KEY, SECRET (можливо доведеться звернутися до Вашого менеджера).
Кому підійде цей модуль:
Добре підійде тим магазинам, які не мають інтеграції з ПЗ складського обліку, тобто. отримують прайси безпосередньо на сайт і обробляють за допомогою АОП або SimplePars.
Інсталяція та оновлення:
Після придбання Ви отримаєте доступ до інсталяційного файлу модуля та README.TXT (містить інструкцію). Файли сайту не модифікуються та не замінюються, відбувається лише додавання.
Інформація про прайс GET-PRICE
Формат виведення – XML. Тип прайсу: Звичайний, безготівковий контроль РРЦ. Можливість вибрати один варіант. Стан товару: Новий, Дефект упаковки, Уцінка. Можливість вибрати кілька варіантів. Додаткові дані: Стан (опис уцінки), Артикул, Штрих-код, Гарантійний термін, Країна, Ціна без ПДВ, грн., Ставка ПДВ, Код ЗЕД, В упаковці шт., У коробці шт., У палеті шт., Вага кг., Об'єм м3, Серія, Короткий опис, Повний опис, Фото, Велике фото, Ексклюзив ЮгКонтракт. Можливість вибрати кілька варіантів. Вибір категорій товарів. Можливість вибрати кілька варіантів. Можливість вказати назву прайсу, що вивантажується, буде зберігатися в /admin/uploads/[назва_прайсу] Приклад:
Інформація про прайс GET-CONTENT-GOODS
Формат виводу – XML. Мова прайсу: Українська, Російська. Можливість вибрати кілька варіантів. Можливість вказати назву прайсу, що вивантажується, буде зберігатися в /admin/uploads/[назва_прайсу] Приклад:
Основні можливості:
Налаштування завантаження прайсу здійснюється на сторінці Вашого магазину. Вивантажується два типи прайсу методами GET-PRICE, GET-CONTENT-GOODS. Формат прайсів – XML. Категорії для вибору вивантажуються також за допомогою методу GET-CATEGORIES з сайту постачальника. Можливість завантаження прайсів за допомогою CRON-завдань.
Вимоги для коректної роботи модуля:
Дозвіл користування API із боку постачальника, тобто. IP-адреса сайту має бути додана з боку постачальника (можливо доведеться звернутися до Вашого менеджера). Наявність даних авторизації USER_KEY, SECRET (можливо доведеться звернутися до Вашого менеджера).
Кому підійде цей модуль:
Добре підійде тим магазинам, які не мають інтеграції з ПЗ складського обліку, тобто. отримують прайси безпосередньо на сайт і обробляють за допомогою АОП або SimplePars.
Інсталяція та оновлення:
Після придбання Ви отримаєте доступ до інсталяційного файлу модуля та README.TXT (містить інструкцію). Файли сайту не модифікуються та не замінюються, відбувається лише додавання.
Інформація про прайс GET-PRICE
Формат виведення – XML. Тип прайсу: Звичайний, безготівковий контроль РРЦ. Можливість вибрати один варіант. Стан товару: Новий, Дефект упаковки, Уцінка. Можливість вибрати кілька варіантів. Додаткові дані: Стан (опис уцінки), Артикул, Штрих-код, Гарантійний термін, Країна, Ціна без ПДВ, грн., Ставка ПДВ, Код ЗЕД, В упаковці шт., У коробці шт., У палеті шт., Вага кг., Об'єм м3, Серія, Короткий опис, Повний опис, Фото, Велике фото, Ексклюзив ЮгКонтракт. Можливість вибрати кілька варіантів. Вибір категорій товарів. Можливість вибрати кілька варіантів. Можливість вказати назву прайсу, що вивантажується, буде зберігатися в /admin/uploads/[назва_прайсу] Приклад:
Інформація про прайс GET-CONTENT-GOODS
Формат виводу – XML. Мова прайсу: Українська, Російська. Можливість вибрати кілька варіантів. Можливість вказати назву прайсу, що вивантажується, буде зберігатися в /admin/uploads/[назва_прайсу] Приклад:
Updated
Загрузка прайсов поставщика ЮгКонтракт с помощью API
Продаж призупинено
37
The modifier lets you add a product to the cart via a direct link like: https://yourshop.com/index.php?route=checkout/checkout&{key}=VALUE
Where {key} is a configurable field (supported: model, sku, upc, ean, jan, isbn, mpn). The quantity added is always 1. No options are requested: if the product has options, the shopper is automatically redirected to the product page. Why this matters
Google Merchant Center Next (GMC), works only USA, “Add a cart or checkout page URL.” With our module, you can supply a dedicated Checkout URL per product in GMC. As a result, your ads will show two buttons: Standard: “Go to product page” New: “Buy” — takes users straight to the cart with the product pre-added For details, see your GMC account: Settings → Business information → Payments.
Where is the module useful outside of GMC
E-mail/SMS/Viber/Telegram: "Buy Now" button with a link Social networks and influencers: links directly to the cart in posts/stories/video descriptions. Banners, landing pages, blog. Offline QR codes: scan → product in the cart (showroom, price tags, booklets). B2B price lists/commercial offers: clickable "Buy" in PDF/Excel. Support/chat bots: quick answers with an add to cart link. Retargeting (outside of GMC): ads with a direct link to the cart (with UTM). Key benefits
Instant add-to-cart via URL. Flexible matching: choose which field to use — model, sku, upc, ean, jan, isbn, mpn. Smart options handling: if the product has options (size/color, etc.), users are correctly redirected to the product page. Clean UX: after adding, the module redirects to /checkout/ without GET parameters (prevents duplicates on refresh). Fast GMC integration: use SKU/MPN/Model in links to easily match feed data. Cart compatibility
Default cart Simple cart @octemplates cart @29aleksey cart Platform compatibility
OpenCart 3.x / ocStore 3.x OpenCart 2.3 / ocStore 2.3 Google Merchant Center setup
Your feed already carries an identifier (e.g., model). In GMC, go to Settings → Business information → Payments and set “Add a cart or checkout page URL” using: Default cart: https://yourshop.com/index.php?route=checkout/checkout&model={id} Simple cart: https://yourshop.com/index.php?route=checkout/simplecheckout&model={id} @octemplates cart: https://yourshop.com/index.php?route=checkout/oct_smartcheckout&model={id} @29aleksey cart: https://yourshop.com/index.php?route=checkout/onepcheckout&model={id} If your checkout page uses SEO_URL, you can specify: https://yourshop.com/checkout?model={id} Users coming from ads can either open the product page or go straight to the cart with that item.
Link examples
Product with options:
https://demo.ocmodules.in.ua/checkout?model=SM-X910NZAA https://demo.ocmodules.in.ua/index.php?route=checkout/checkout&model=SM-X910NZAA Product without options:
https://demo.ocmodules.in.ua/checkout?model=SM-X826BZAREUC https://demo.ocmodules.in.ua/index.php?route=checkout/checkout&model=SM-X826BZAREUC Installation
Upload the modifier via the standard installer. Refresh the modifications cache. Go to System → Settings → Edit store settings → “Options” tab. Find “Product key for link generation” and choose the field that matches your GMC feed identifier. Save store settings. Test the links using the examples above. Questions?
Contact us before purchasing — we’ll help you assess whether the module fits your store.
License
Licensed for use on one online store.
Where {key} is a configurable field (supported: model, sku, upc, ean, jan, isbn, mpn). The quantity added is always 1. No options are requested: if the product has options, the shopper is automatically redirected to the product page. Why this matters
Google Merchant Center Next (GMC), works only USA, “Add a cart or checkout page URL.” With our module, you can supply a dedicated Checkout URL per product in GMC. As a result, your ads will show two buttons: Standard: “Go to product page” New: “Buy” — takes users straight to the cart with the product pre-added For details, see your GMC account: Settings → Business information → Payments.
Where is the module useful outside of GMC
E-mail/SMS/Viber/Telegram: "Buy Now" button with a link Social networks and influencers: links directly to the cart in posts/stories/video descriptions. Banners, landing pages, blog. Offline QR codes: scan → product in the cart (showroom, price tags, booklets). B2B price lists/commercial offers: clickable "Buy" in PDF/Excel. Support/chat bots: quick answers with an add to cart link. Retargeting (outside of GMC): ads with a direct link to the cart (with UTM). Key benefits
Instant add-to-cart via URL. Flexible matching: choose which field to use — model, sku, upc, ean, jan, isbn, mpn. Smart options handling: if the product has options (size/color, etc.), users are correctly redirected to the product page. Clean UX: after adding, the module redirects to /checkout/ without GET parameters (prevents duplicates on refresh). Fast GMC integration: use SKU/MPN/Model in links to easily match feed data. Cart compatibility
Default cart Simple cart @octemplates cart @29aleksey cart Platform compatibility
OpenCart 3.x / ocStore 3.x OpenCart 2.3 / ocStore 2.3 Google Merchant Center setup
Your feed already carries an identifier (e.g., model). In GMC, go to Settings → Business information → Payments and set “Add a cart or checkout page URL” using: Default cart: https://yourshop.com/index.php?route=checkout/checkout&model={id} Simple cart: https://yourshop.com/index.php?route=checkout/simplecheckout&model={id} @octemplates cart: https://yourshop.com/index.php?route=checkout/oct_smartcheckout&model={id} @29aleksey cart: https://yourshop.com/index.php?route=checkout/onepcheckout&model={id} If your checkout page uses SEO_URL, you can specify: https://yourshop.com/checkout?model={id} Users coming from ads can either open the product page or go straight to the cart with that item.
Link examples
Product with options:
https://demo.ocmodules.in.ua/checkout?model=SM-X910NZAA https://demo.ocmodules.in.ua/index.php?route=checkout/checkout&model=SM-X910NZAA Product without options:
https://demo.ocmodules.in.ua/checkout?model=SM-X826BZAREUC https://demo.ocmodules.in.ua/index.php?route=checkout/checkout&model=SM-X826BZAREUC Installation
Upload the modifier via the standard installer. Refresh the modifications cache. Go to System → Settings → Edit store settings → “Options” tab. Find “Product key for link generation” and choose the field that matches your GMC feed identifier. Save store settings. Test the links using the examples above. Questions?
Contact us before purchasing — we’ll help you assess whether the module fits your store.
License
Licensed for use on one online store.
Updated
Fast link to cart item
460грн
320 грн
1 4
This modification is designed to enhance the product page interface in OpenCart by allowing you to add tooltips to product options. It helps improve how customers perceive product information and makes the selection process more convenient and informative. The modification includes settings for text tooltips displayed as pop-up hints, helping users better understand what each option means.
Benefits of the Modification
Simplified understanding of product options: Pop-up tooltips allow you to provide more detailed information without cluttering the page. Improved user experience: Customers can get all the necessary information directly on the product page without switching tabs or dealing with technical details. Tooltips make the interface more interactive and visually appealing. Flexibility and customization: The store administrator can configure tooltips for each product option individually. Multilingual Support
The modification supports multilingual stores, allowing tooltips to be configured separately for each language version of the store. Conversion Boost
Tooltips help customers navigate product options faster and make purchase decisions more confidently, which can increase conversion rates and reduce cart abandonment. Compatibility
OpenCart 3.x Template Compatibility
The extension is compatible with the standard default template. For other templates, adaptation may be required (paid adaptation).
Installation
Run the SQL query from the file tips_for_product_options_query.sql in the database (taking into account the table prefix). Install the module via the OpenCart admin panel. Refresh the modifications. DEMO
Admin Page login/password: demo/demodemo Store Page License
The license applies to one domain and its subdomain.
Benefits of the Modification
Simplified understanding of product options: Pop-up tooltips allow you to provide more detailed information without cluttering the page. Improved user experience: Customers can get all the necessary information directly on the product page without switching tabs or dealing with technical details. Tooltips make the interface more interactive and visually appealing. Flexibility and customization: The store administrator can configure tooltips for each product option individually. Multilingual Support
The modification supports multilingual stores, allowing tooltips to be configured separately for each language version of the store. Conversion Boost
Tooltips help customers navigate product options faster and make purchase decisions more confidently, which can increase conversion rates and reduce cart abandonment. Compatibility
OpenCart 3.x Template Compatibility
The extension is compatible with the standard default template. For other templates, adaptation may be required (paid adaptation).
Installation
Run the SQL query from the file tips_for_product_options_query.sql in the database (taking into account the table prefix). Install the module via the OpenCart admin panel. Refresh the modifications. DEMO
Admin Page login/password: demo/demodemo Store Page License
The license applies to one domain and its subdomain.
Updated
Product Option Tooltips
250 грн
0 0
The module allows you to add a carrier waybill and a supplier invoice. It will be useful for sellers working in dropshipping mode.
The module was tested on OcStore 3.0.2.0, 3.0.3.7.
You can add the above values in the order view mode in the Admin. panels.
Displaying the above fields:
1. On the page for viewing an order in the Admin. panels.
2. On the order list page in the Admin. Panels.
3. On the status bar in the Admin. panel, provided that the module "Last orders" is displayed.
Installation:
1. It is necessary to make a query in the database (do not forget to change the table prefix if necessary):
ALTER TABLE `oc_order` ADD COLUMN IF NOT EXISTS `supplier_order` VARCHAR(255) NOT NULL AFTER `order_id`, ADD COLUMN IF NOT EXISTS `track_number` VARCHAR(255) NOT NULL AFTER `supplier_order`; 2. Installation is performed in the standard way through Add-ons-> Add-ons installation.
3. After installation, go to the add-ons manager and update the cache.
4. Go to Sales->Orders->View Order and you can enter values in the appeared fields "Supplier invoice" and "Carrier TTN".
The module was tested on OcStore 3.0.2.0, 3.0.3.7.
You can add the above values in the order view mode in the Admin. panels.
Displaying the above fields:
1. On the page for viewing an order in the Admin. panels.
2. On the order list page in the Admin. Panels.
3. On the status bar in the Admin. panel, provided that the module "Last orders" is displayed.
Installation:
1. It is necessary to make a query in the database (do not forget to change the table prefix if necessary):
ALTER TABLE `oc_order` ADD COLUMN IF NOT EXISTS `supplier_order` VARCHAR(255) NOT NULL AFTER `order_id`, ADD COLUMN IF NOT EXISTS `track_number` VARCHAR(255) NOT NULL AFTER `supplier_order`; 2. Installation is performed in the standard way through Add-ons-> Add-ons installation.
3. After installation, go to the add-ons manager and update the cache.
4. Go to Sales->Orders->View Order and you can enter values in the appeared fields "Supplier invoice" and "Carrier TTN".
Updated
Tracking numbers on the order page
Free
482
Ticket System is a full-featured customer support (HelpDesk) solution directly inside the OpenCart customer account and admin panel. The module allows customers to create tickets, communicate with the administrator in a chat format, and manage the status of their requests.
Main Features
For customers (Front-end)
My Tickets page in the customer account Create a new ticket: subject, priority, first message View conversation history in chat format Send messages without page reload (AJAX) Auto refresh every 15 seconds Ability to change ticket priority and status (Open / Completed) Automatic status change after customer reply → Waiting for admin response Access protection: guests are redirected to login page, customers cannot access чужие tickets For administrators (Back-end)
Dedicated ticket management page in admin panel All tickets list with filters, sorting and pagination Filtering by customer, status and priority Chat-style conversation view Reply to customers without page reload (AJAX) Change ticket status and priority Visual separation of customer and admin messages Automatic message refresh Modern Chat Interface
Messenger-style message design (Telegram style) Fixed message input field Auto scroll to latest message Compatibility
OpenCart 3.x Theme Compatibility
The extension is compatible with the default OpenCart theme. Adaptation may be required for third-party themes (paid service).
Installation
Install the module via OpenCart admin panel Refresh modifications Grant access permissions to administrator groups Go to “Tickets & Requests” → “Settings” and configure the module DEMO
Admin Page login/password: demo/demodemo Store Page login/password: [email protected]/demodemo License
The license is valid for one domain and its subdomain.
Main Features
For customers (Front-end)
My Tickets page in the customer account Create a new ticket: subject, priority, first message View conversation history in chat format Send messages without page reload (AJAX) Auto refresh every 15 seconds Ability to change ticket priority and status (Open / Completed) Automatic status change after customer reply → Waiting for admin response Access protection: guests are redirected to login page, customers cannot access чужие tickets For administrators (Back-end)
Dedicated ticket management page in admin panel All tickets list with filters, sorting and pagination Filtering by customer, status and priority Chat-style conversation view Reply to customers without page reload (AJAX) Change ticket status and priority Visual separation of customer and admin messages Automatic message refresh Modern Chat Interface
Messenger-style message design (Telegram style) Fixed message input field Auto scroll to latest message Compatibility
OpenCart 3.x Theme Compatibility
The extension is compatible with the default OpenCart theme. Adaptation may be required for third-party themes (paid service).
Installation
Install the module via OpenCart admin panel Refresh modifications Grant access permissions to administrator groups Go to “Tickets & Requests” → “Settings” and configure the module DEMO
Admin Page login/password: demo/demodemo Store Page login/password: [email protected]/demodemo License
The license is valid for one domain and its subdomain.
Updated
Ticket System
910грн
680 грн
0 0
This is a convenient tool for fast bulk editing of products in OpenCart. The module allows you to change categories and manufacturer for multiple products at once directly from the product list in the admin panel.
Main Features
Category Management
Bulk change of categories for selected products Assign multiple categories at once Set main category Convenient category selection via autocomplete Manufacturer Management
Bulk change of product manufacturer Quick manufacturer selection via autocomplete Apply changes to multiple products at once Interface & Usability
Convenient modal windows directly in the product list Instant application of changes Advantages
Time-saving when managing product catalog No need to open each product individually Simple and intuitive interface Fast bulk editing in just a few clicks Compatibility
OpenCart 3.x Installation
Install the module via OpenCart admin panel Refresh modifications DEMO
Admin Page login/password: demo/demodemo License
The license applies to one domain and its subdomains.
Main Features
Category Management
Bulk change of categories for selected products Assign multiple categories at once Set main category Convenient category selection via autocomplete Manufacturer Management
Bulk change of product manufacturer Quick manufacturer selection via autocomplete Apply changes to multiple products at once Interface & Usability
Convenient modal windows directly in the product list Instant application of changes Advantages
Time-saving when managing product catalog No need to open each product individually Simple and intuitive interface Fast bulk editing in just a few clicks Compatibility
OpenCart 3.x Installation
Install the module via OpenCart admin panel Refresh modifications DEMO
Admin Page login/password: demo/demodemo License
The license applies to one domain and its subdomains.
Updated
Mass Editing Categories and Manufacturer
320 грн
0 0
A simple module for collecting information on authorization of store personnel on the administration page.
The module was tested on OcStore 3.0.2.0, 3.0.3.7.
During installation, an additional table is created in the database "oc_user_online". Store files are not replaced, only new ones are added.
Installation order.
1. Install the file through the built-in extension installer.
2. Update modifiers.
3. Grant access to user groups to view and modify for "report/admin".
4. Go to Reports -> Administrators online.
Possible problems.
If, when going to the Reports -> Administrators online section, an error pops up that the page is unavailable, check if the "oc_user_online" table exists in the database. Table creation query:
CREATE TABLE IF NOT EXISTS `oc_user_online` ( `user_id` INT NOT NULL , `date_added` datetime NOT NULL) ENGINE = InnoDB CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
The module was tested on OcStore 3.0.2.0, 3.0.3.7.
During installation, an additional table is created in the database "oc_user_online". Store files are not replaced, only new ones are added.
Installation order.
1. Install the file through the built-in extension installer.
2. Update modifiers.
3. Grant access to user groups to view and modify for "report/admin".
4. Go to Reports -> Administrators online.
Possible problems.
If, when going to the Reports -> Administrators online section, an error pops up that the page is unavailable, check if the "oc_user_online" table exists in the database. Table creation query:
CREATE TABLE IF NOT EXISTS `oc_user_online` ( `user_id` INT NOT NULL , `date_added` datetime NOT NULL) ENGINE = InnoDB CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;
Updated
Administrator Authorization History
Free
103
This module is based on: OpenCart - Bots and Crawlers OnLine, which is free for Opencart 2. The author of the module is @Wild, but he has been offline for a long time, so I am publishing an adaptation for OcStore 3 without his consent. I only perform code adaptation.
The module displays the activity of bots on the site in Reports->Buyers online. Tracked bots are configured in the standard settings of the store in the System->Settings->Options tab in the Account section. It is possible to keep a log file of visiting bots (system/logs/useragents.log). Very useful for analyzing current visitors. Bots will not appear immediately, but the next time you visit the site.
Installation order
Execute the query in the database (don't forget to check the table prefix) ALTER TABLE `oc_customer_online` ADD COLUMN `bot_name` VARCHAR(64) NOT NULL AFTER `date_added`;
Install the file through the built-in extension installer.
Update modifiers.
Go to System->Settings->Options and check for the following items: Bot names from UserAgent and Write UserAgent to LOG (for debugging)
Save store settings.
Go to the Reports -> Users online section and check the module operation.
The module displays the activity of bots on the site in Reports->Buyers online. Tracked bots are configured in the standard settings of the store in the System->Settings->Options tab in the Account section. It is possible to keep a log file of visiting bots (system/logs/useragents.log). Very useful for analyzing current visitors. Bots will not appear immediately, but the next time you visit the site.
Installation order
Execute the query in the database (don't forget to check the table prefix) ALTER TABLE `oc_customer_online` ADD COLUMN `bot_name` VARCHAR(64) NOT NULL AFTER `date_added`;
Install the file through the built-in extension installer.
Update modifiers.
Go to System->Settings->Options and check for the following items: Bot names from UserAgent and Write UserAgent to LOG (for debugging)
Save store settings.
Go to the Reports -> Users online section and check the module operation.
Updated
Bots and Crawlers OnLine
Free
147
This module allows you to assign a registered user from the customer list to an existing order. This is useful when you need to link an order to a specific user, for example, if the order was placed without registration or if the user needs to be updated in the order after registering.
Advantages:
Ease of assigning a customer: The module allows you to quickly and easily assign a registered user to an order without the need to manually edit the order. Simplified order processing: Updating the customer’s data in the order helps synchronize the information. Flexibility: The module allows you to select any registered user from the list and link them to the order. Minimal effort: No need to manually update user data in the order. Convenience for administrators: It simplifies the work of administrators, as they can easily link a user to an order without needing to modify the order directly in the database. Installation method:
Install the module through the OpenCart admin panel. Update the modifications. Go to the Sales → Orders section in the admin panel, where a customer search field will appear in the customer table. Attention:
The module not only links the order to a registered user but also updates several important fields in the order. It updates the email, telephone, first name, and last name fields in the order with the user’s information. Additionally, if the user does not have an address, it will be added to their profile based on the order’s details.
Make sure that the data in the order is correct before applying the module, as updating the data may affect the order history.
Advantages:
Ease of assigning a customer: The module allows you to quickly and easily assign a registered user to an order without the need to manually edit the order. Simplified order processing: Updating the customer’s data in the order helps synchronize the information. Flexibility: The module allows you to select any registered user from the list and link them to the order. Minimal effort: No need to manually update user data in the order. Convenience for administrators: It simplifies the work of administrators, as they can easily link a user to an order without needing to modify the order directly in the database. Installation method:
Install the module through the OpenCart admin panel. Update the modifications. Go to the Sales → Orders section in the admin panel, where a customer search field will appear in the customer table. Attention:
The module not only links the order to a registered user but also updates several important fields in the order. It updates the email, telephone, first name, and last name fields in the order with the user’s information. Additionally, if the user does not have an address, it will be added to their profile based on the order’s details.
Make sure that the data in the order is correct before applying the module, as updating the data may affect the order history.
Updated
Assign Customer to Order
Free
81
AI Product Video — product video generation with Gemini Omni
AI Product Video is a module for OpenCart 3 and ocStore 3 that creates short product videos from photos and a text prompt. The completed MP4 file is automatically downloaded to the store server and linked to the corresponding product.
The current version works with Gemini Omni 1.1 Flash using a standard Gemini API key. The key is created in Google AI Studio and saved in the module settings.
The main package includes the “Product Video in a Pop-up Window” integration: manage generated and manually added videos on the product editing page and display them in the default theme’s gallery.
Key features
Product video generation with Gemini Omni 1.1 Flash. Three input modes: text only, the main photo, or the main photo together with additional images. Up to six images per job, including the main photo. Portrait 9:16 and landscape 16:9 formats. 360p, 720p, 1080p, and 4K resolutions. Duration from 3 to 10 seconds; one video per job. Automatic saving of the MP4 file and linking the video to the product. Queue processing from the admin panel without page reloads or via CRON. A global prompt template and a custom prompt for an individual product. According to Google’s specifications, the model generates videos at 24 frames per second. Videos in 1080p and 4K are produced using upscaling. Learn more: Gemini Omni Flash specifications and Google API release notes.
Main photo and additional images
The settings let you choose which input data to use for generation:
Text only — the video is generated from a prompt without sending any photos. Main image — only the product’s main photo is sent. Additional images — the main photo and images from the product gallery are sent in their sort order. Prompt and product information
The prompt is created from your template. You can insert the required product data using these variables:
{name} — product name; {description} — product description; {model} — model; {sku} — SKU; {attributes} — attributes and specifications. When adding an individual product to the queue, you can enter a custom prompt. If you leave the field empty, the global template from the settings is used.
You can separately configure instructions for added text, the language of text and speech, preservation of existing labels and logos, and audio: silent, ambient sounds, or background music. The “What to Avoid” field is appended to the prompt as an additional instruction.
These settings are sent to the model through the prompt. They do not physically remove the audio track or guarantee that added text will be blocked. How accurately the product’s appearance is preserved and instructions are followed depends on the model and the source materials.
Selecting products for generation
You can add the following to the queue:
an individual product selected through autocomplete; products with an exact model match; products from a selected category; products from a selected manufacturer; products without videos; all store products that match the specified filters. You can filter by product status and creation date, and set a limit on the number of products to add. Products that already have an active job are not added to the queue again.
Queue and manual processing
Adding products to the queue does not start generation by itself. Processing begins after clicking “Process Queue” or when CRON is called.
Sequential batch processing in the admin panel without page reloads. Display of job statuses, error messages, and Google operation IDs. Configurable number of jobs per worker call and concurrent Google operations. Generation settings saved for each job when it is added. Resume processing an existing operation by its ID without starting a new generation. Delete individual jobs, cancel them locally, and clear the queue. The “Stop” button prevents further manual worker calls from the browser. Cancelling a job locally does not cancel a paid operation already running on Google’s side. If the outcome of a start request is unknown, check the operation before creating a new job.
Automatic processing via CRON
The module provides a URL with a secret key and a command for your hosting scheduler. CRON has a separate enable/disable setting, so you can turn off automatic processing while keeping manual queue processing available.
Each call processes a limited number of jobs: it checks previously started operations, downloads completed results, and starts new jobs when capacity is available. The amount of work depends on the configured limits. The schedule is configured separately in your hosting control panel.
Manual processing and CRON use a shared worker protected against concurrent calls. After temporary polling or download errors, the existing operation is checked again. Queue processing does not run when the module itself is disabled.
Generated videos and file names
The “Generated Videos” tab lets you preview results, access the MP4 file, open the product or its editing page, and delete generated videos.
Files are saved in a selected folder within image/catalog/, for example image/catalog/ai-video/. File names are generated from a template using {name}, {model}, {sku}, {product_id}, and {number}.
For example, you can use the template {name}-{model}. Invalid characters are replaced with hyphens. Suffixes such as -2, -3, and so on are added only when names collide, to avoid overwriting another file.
Managing product videos
A “Video” tab is added to the product editing page. It lets you manage both AI-generated videos and videos added manually.
Add multiple videos to one product. Support for local and external video files, YouTube, YouTube Shorts, and Vimeo. Enable, disable, and sort videos individually. Preview videos in the admin panel. Select a local video file through the OpenCart file manager. Automatically convert YouTube, Shorts, and Vimeo links into video IDs. Videos on the product page
In the default theme, videos appear among the additional product images and open in a pop-up window. YouTube and Vimeo videos use video thumbnails; local and AI-generated videos use the product image. Both portrait and landscape videos are supported.
Schema.org VideoObject structured data is added to the product page, including information about the video, its thumbnail, and a link to the player or video file.
Theme compatibility
The extension is compatible with the standard default theme. Other themes may require adaptation, which is a paid service.
Google API access and billing
Generation requires a Gemini API key and an enabled paid tier with access to Gemini Omni Flash. Google API usage is paid for separately by the store owner and is not included in the module price.
The cost depends on the input data, generation settings, and actual API usage. Current rates are published on the official Google Gemini API Pricing page.
Requirements and operating details
OpenCart 3 or ocStore 3. PHP with the cURL and mbstring extensions. GD with WebP support if the source photos are in WebP format. Outbound HTTPS access to the Google API. A writable output folder within image/catalog/. A CRON scheduler for automatic queue processing. The generated prompt and selected product photos are sent to Google. Processing time, generation availability, and API limits depend on Google’s service and your account. Review the result before using it; a new generation may differ from the previous one.
Installation
Upload the ai_product_video_v_1_1_oc3.ocmod.zip archive through “Extensions → Installer”. Refresh modifications and clear the theme cache. Under “Extensions → Extensions → Modules”, find “AI Product Video” and click “Install”. Open the settings and enter your Gemini API key, video settings, image mode, and prompt template. Enable the module and save your changes. Add products to the queue and click “Process Queue” to start manual processing. For automatic processing, enable CRON in the module settings and add its URL or command to your hosting scheduler. The required tables are created when the module is installed.
Disabling and uninstalling the module
Disabling the module stops queue processing but does not delete completed product videos. Uninstalling the module from the admin panel removes its settings and queue history; saved video files and their product associations are retained.
License
One license covers one domain and its subdomains.
Google Gemini API services, video generation charges, third-party hosting configuration, and adaptation for custom themes are not included in the module license price.
AI Product Video is a module for OpenCart 3 and ocStore 3 that creates short product videos from photos and a text prompt. The completed MP4 file is automatically downloaded to the store server and linked to the corresponding product.
The current version works with Gemini Omni 1.1 Flash using a standard Gemini API key. The key is created in Google AI Studio and saved in the module settings.
The main package includes the “Product Video in a Pop-up Window” integration: manage generated and manually added videos on the product editing page and display them in the default theme’s gallery.
Key features
Product video generation with Gemini Omni 1.1 Flash. Three input modes: text only, the main photo, or the main photo together with additional images. Up to six images per job, including the main photo. Portrait 9:16 and landscape 16:9 formats. 360p, 720p, 1080p, and 4K resolutions. Duration from 3 to 10 seconds; one video per job. Automatic saving of the MP4 file and linking the video to the product. Queue processing from the admin panel without page reloads or via CRON. A global prompt template and a custom prompt for an individual product. According to Google’s specifications, the model generates videos at 24 frames per second. Videos in 1080p and 4K are produced using upscaling. Learn more: Gemini Omni Flash specifications and Google API release notes.
Main photo and additional images
The settings let you choose which input data to use for generation:
Text only — the video is generated from a prompt without sending any photos. Main image — only the product’s main photo is sent. Additional images — the main photo and images from the product gallery are sent in their sort order. Prompt and product information
The prompt is created from your template. You can insert the required product data using these variables:
{name} — product name; {description} — product description; {model} — model; {sku} — SKU; {attributes} — attributes and specifications. When adding an individual product to the queue, you can enter a custom prompt. If you leave the field empty, the global template from the settings is used.
You can separately configure instructions for added text, the language of text and speech, preservation of existing labels and logos, and audio: silent, ambient sounds, or background music. The “What to Avoid” field is appended to the prompt as an additional instruction.
These settings are sent to the model through the prompt. They do not physically remove the audio track or guarantee that added text will be blocked. How accurately the product’s appearance is preserved and instructions are followed depends on the model and the source materials.
Selecting products for generation
You can add the following to the queue:
an individual product selected through autocomplete; products with an exact model match; products from a selected category; products from a selected manufacturer; products without videos; all store products that match the specified filters. You can filter by product status and creation date, and set a limit on the number of products to add. Products that already have an active job are not added to the queue again.
Queue and manual processing
Adding products to the queue does not start generation by itself. Processing begins after clicking “Process Queue” or when CRON is called.
Sequential batch processing in the admin panel without page reloads. Display of job statuses, error messages, and Google operation IDs. Configurable number of jobs per worker call and concurrent Google operations. Generation settings saved for each job when it is added. Resume processing an existing operation by its ID without starting a new generation. Delete individual jobs, cancel them locally, and clear the queue. The “Stop” button prevents further manual worker calls from the browser. Cancelling a job locally does not cancel a paid operation already running on Google’s side. If the outcome of a start request is unknown, check the operation before creating a new job.
Automatic processing via CRON
The module provides a URL with a secret key and a command for your hosting scheduler. CRON has a separate enable/disable setting, so you can turn off automatic processing while keeping manual queue processing available.
Each call processes a limited number of jobs: it checks previously started operations, downloads completed results, and starts new jobs when capacity is available. The amount of work depends on the configured limits. The schedule is configured separately in your hosting control panel.
Manual processing and CRON use a shared worker protected against concurrent calls. After temporary polling or download errors, the existing operation is checked again. Queue processing does not run when the module itself is disabled.
Generated videos and file names
The “Generated Videos” tab lets you preview results, access the MP4 file, open the product or its editing page, and delete generated videos.
Files are saved in a selected folder within image/catalog/, for example image/catalog/ai-video/. File names are generated from a template using {name}, {model}, {sku}, {product_id}, and {number}.
For example, you can use the template {name}-{model}. Invalid characters are replaced with hyphens. Suffixes such as -2, -3, and so on are added only when names collide, to avoid overwriting another file.
Managing product videos
A “Video” tab is added to the product editing page. It lets you manage both AI-generated videos and videos added manually.
Add multiple videos to one product. Support for local and external video files, YouTube, YouTube Shorts, and Vimeo. Enable, disable, and sort videos individually. Preview videos in the admin panel. Select a local video file through the OpenCart file manager. Automatically convert YouTube, Shorts, and Vimeo links into video IDs. Videos on the product page
In the default theme, videos appear among the additional product images and open in a pop-up window. YouTube and Vimeo videos use video thumbnails; local and AI-generated videos use the product image. Both portrait and landscape videos are supported.
Schema.org VideoObject structured data is added to the product page, including information about the video, its thumbnail, and a link to the player or video file.
Theme compatibility
The extension is compatible with the standard default theme. Other themes may require adaptation, which is a paid service.
Google API access and billing
Generation requires a Gemini API key and an enabled paid tier with access to Gemini Omni Flash. Google API usage is paid for separately by the store owner and is not included in the module price.
The cost depends on the input data, generation settings, and actual API usage. Current rates are published on the official Google Gemini API Pricing page.
Requirements and operating details
OpenCart 3 or ocStore 3. PHP with the cURL and mbstring extensions. GD with WebP support if the source photos are in WebP format. Outbound HTTPS access to the Google API. A writable output folder within image/catalog/. A CRON scheduler for automatic queue processing. The generated prompt and selected product photos are sent to Google. Processing time, generation availability, and API limits depend on Google’s service and your account. Review the result before using it; a new generation may differ from the previous one.
Installation
Upload the ai_product_video_v_1_1_oc3.ocmod.zip archive through “Extensions → Installer”. Refresh modifications and clear the theme cache. Under “Extensions → Extensions → Modules”, find “AI Product Video” and click “Install”. Open the settings and enter your Gemini API key, video settings, image mode, and prompt template. Enable the module and save your changes. Add products to the queue and click “Process Queue” to start manual processing. For automatic processing, enable CRON in the module settings and add its URL or command to your hosting scheduler. The required tables are created when the module is installed.
Disabling and uninstalling the module
Disabling the module stops queue processing but does not delete completed product videos. Uninstalling the module from the admin panel removes its settings and queue history; saved video files and their product associations are retained.
License
One license covers one domain and its subdomains.
Google Gemini API services, video generation charges, third-party hosting configuration, and adaptation for custom themes are not included in the module license price.
Updated
AI Product Video — Product Video Generation + Pop-up Gallery
1,360грн
1,140 грн
0 1
Store Analytics Dashboard — GA4, Search Console and Google Ads in the OpenCart admin panel
Store Analytics Dashboard is a module for OpenCart and ocStore that brings store analytics, organic search metrics and advertising statistics together in a single widget on the main administrator dashboard.
View traffic, transactions, revenue, search queries, ad spend and conversions without constantly switching between Google services. CRON-based monitoring also delivers advertising status reports directly to Telegram.
Main features
A single widget for Google Analytics 4, Google Search Console and Google Ads Use GA4 on its own, combine it with Search Console, or connect Google Ads only GA4 traffic, transactions, revenue and key event metrics Statistics for channels, traffic sources and top revenue-generating products Search Console clicks, impressions, CTR, positions, queries and pages Ad spend, clicks, conversions, CPA, ROAS and campaign statuses CRON-based advertising monitoring with Telegram notifications Support for multiple Telegram recipients Interactive charts displaying several metric lines at once Tooltips for metrics, tables and chart points Preset reporting periods and custom date ranges Previous-period comparisons for key GA4 and Search Console metrics Report caching using native OpenCart functionality Detailed built-in service setup instructions No Composer installation or additional Google SDKs required Google Analytics 4: traffic and store performance
The widget displays key GA4 metrics for the selected period:
Users — active users reported by GA4 Sessions — site visits recorded by analytics Orders — transactions recorded in GA4 Revenue — total revenue reported by the GA4 totalRevenue metric Conversion — the transaction-to-session ratio calculated by the module Key events — events marked as important to the business in GA4 Key events per 100 sessions — a measure of how frequently target actions occur Average order value — GA4 revenue divided by the number of transactions These metrics show the current value, the previous-period value and the percentage change. For example, a selected 7-day period is compared with the preceding 7 days.
Important: the module uses GA4 data, not the OpenCart order database. Transaction counts and revenue can differ from internal store reports due to tracking behaviour, refunds, user consent and analytics blockers.
Channels, traffic sources and products
Top channels — sessions, transactions, key events and revenue by GA4 channel groups, including Organic Search, Paid Search, Direct and Referral Traffic sources — results by session source and medium, such as google / organic or google / cpc Top products — the five item names with the highest GA4 item revenue, showing units purchased and item revenue These sections help you compare traffic sources, identify channels that deliver results and see which products generate revenue.
Ecommerce events
A dedicated section displays counts of the main ecommerce events:
view_item — product view add_to_cart — add to cart begin_checkout — checkout started purchase — purchase Each event count is accompanied by a percentage relative to the first non-zero step. This compares independent event counts; it is not a sequential funnel tracking the same users through each step.
Google Search Console: store visibility in search
Connecting Search Console adds a Google organic search section to the widget:
Clicks — clicks to the site from search results Impressions — appearances of links to the site in search CTR — the ratio of clicks to impressions Average position — the average position of the site's highest result across impressions A trend chart and previous-period comparisons are available for the main metrics. Search query and page tables help assess demand, identify pages receiving organic traffic and find opportunities to improve content, titles and descriptions.
Search Console data covers ordinary Google search results and does not replace Google Ads advertising statistics.
Google Ads: ad spend and performance
Advertising statistics appear in the same widget alongside store analytics. No separate module or additional widget needs to be installed.
Cost — total advertising spend for the selected period Impressions — the number of times ads were shown Clicks — the number of clicks on ads CTR — clicks as a percentage of impressions CPC — average cost per click Conversions — target actions credited to advertising according to Google Ads settings CPA — average cost per conversion Conversion value — the total conversion values supplied to or configured in Google Ads ROAS — conversion value divided by advertising spend A campaign table displays statistics, statuses and reasons for limitations. A chart shows impressions, clicks and spend. Monetary values use the advertising account's currency, while reporting periods and check timestamps respect its timezone.
Conversions do not necessarily mean purchases only: they can include enquiries, phone calls and other configured goals. ROAS expresses the relationship between conversion value and spend; it is not net profit.
Advertising monitoring and Telegram notifications
The module can check advertising through CRON and send a report to Telegram. This helps you notice account issues, campaign configuration problems or missing expected activity.
Checks advertising account and campaign status Respects statuses, start and end dates, and ad schedules Detects missing impressions and spend within a configured window of expected activity Separate settings for the analysis window and reporting delay A report after every completed check, including when no problems are detected Brief impressions, clicks and spend statistics in the message Notifications about data retrieval errors and previously detected issues that are no longer observed Delivery to multiple recipients using comma-separated numeric chat IDs A test message button and the latest check result displayed in the widget Protection against simultaneous duplicate checks Set the CRON schedule on your hosting, for example every 2 hours. The module imposes no minimum launch interval. A ready-to-use HTTP command is provided, so PHP CLI is not required.
Important: this monitors advertising status and activity, not the account balance. Google Ads API does not expose an exact prepaid balance. An “OK” status means that none of the issues checked by the module were detected in the analysed period; it does not confirm that funds remain in the account.
Interactive charts
Charts can display several metrics at once. Use checkboxes to enable or disable individual lines:
GA4: sessions, transactions, key events and revenue Search Console: clicks, impressions, CTR and position Google Ads: impressions, clicks and spend Hovering over or clicking a point displays the metric name, date and value. Advertising spend includes the currency. When Ads spend and count metrics are displayed together, spend uses a separate right-hand axis.
Reporting periods and metric explanations
Available periods include today, yesterday, 7 days, 30 days, this month, last month and a custom date range. The period selector and refresh button are shared across the widget sections.
All 21 main metrics include explanatory tooltips describing what each metric means, how it is calculated and what to consider when assessing results. Tooltips are also available for table headings and supporting sections.
Detailed setup help
The module settings include a Help tab with step-by-step instructions:
Creating a Google Cloud service account and JSON key Connecting GA4 and finding the correct Property ID Connecting Search Console and specifying siteUrl Configuring Google Ads access and understanding the difference between Customer ID and MCC Creating a Telegram bot and obtaining chat IDs Setting up CRON, the activity window and reporting delay Troubleshooting common access, authorisation and message delivery errors Caching and widget settings
Reports use native OpenCart caching with a configurable lifetime in minutes. This reduces the number of Google API requests. The force-refresh button requests fresh report data, while CRON checks do not use the report cache.
Configure the widget width, display order, initial reporting period, default GA4 and Search Console chart lines, service connection settings and Telegram monitoring.
Connection and system requirements
OpenCart 3.x or ocStore 3.x Module code tested on PHP 7.1–8.5; compatibility with a particular PHP version also depends on the store core and other extensions PHP OpenSSL Outbound HTTPS requests through cURL or enabled HTTPS URL streams A Google Cloud project with the required service APIs enabled A service account JSON key with access to the relevant Google resources For Google Ads: approved API access for the Cloud project to production advertising accounts; Test access is insufficient For Telegram: a bot token and numeric recipient IDs For automatic monitoring: a CRON scheduler on the hosting server Authorisation runs on the server through a service account and does not require an interactive Google sign-in through a browser. One JSON key is used for the connected services, provided the appropriate access permissions have been granted.
Important considerations
The module reads previously collected data; it does not install a GA4 tag or ecommerce tracking on the site Purchase, revenue and product metrics require correctly configured ecommerce event tracking The module does not modify advertising campaigns, their budgets or the store's SEO settings Google service statistics may be delayed and revised after processing Monitoring analyses completed hours with the configured delay, not real-time activity For low-traffic campaigns, missing impressions over a short period do not necessarily indicate a payment problem Search Console requires the exact property URL or a value in the format sc-domain:example.com Installation
Upload the archive through Extensions → Installer. Open Extensions → Extensions and select the Dashboard extension type. Install Store Analytics Dashboard and open its settings. Add the service account JSON and configure the required services: GA4, Search Console and/or Google Ads. Grant the service account access within the relevant Google services. Configure the widget, enable the module and save the changes. If required, connect Telegram, check the test message and add the generated CRON command to your hosting scheduler.
Store Analytics Dashboard is a module for OpenCart and ocStore that brings store analytics, organic search metrics and advertising statistics together in a single widget on the main administrator dashboard.
View traffic, transactions, revenue, search queries, ad spend and conversions without constantly switching between Google services. CRON-based monitoring also delivers advertising status reports directly to Telegram.
Main features
A single widget for Google Analytics 4, Google Search Console and Google Ads Use GA4 on its own, combine it with Search Console, or connect Google Ads only GA4 traffic, transactions, revenue and key event metrics Statistics for channels, traffic sources and top revenue-generating products Search Console clicks, impressions, CTR, positions, queries and pages Ad spend, clicks, conversions, CPA, ROAS and campaign statuses CRON-based advertising monitoring with Telegram notifications Support for multiple Telegram recipients Interactive charts displaying several metric lines at once Tooltips for metrics, tables and chart points Preset reporting periods and custom date ranges Previous-period comparisons for key GA4 and Search Console metrics Report caching using native OpenCart functionality Detailed built-in service setup instructions No Composer installation or additional Google SDKs required Google Analytics 4: traffic and store performance
The widget displays key GA4 metrics for the selected period:
Users — active users reported by GA4 Sessions — site visits recorded by analytics Orders — transactions recorded in GA4 Revenue — total revenue reported by the GA4 totalRevenue metric Conversion — the transaction-to-session ratio calculated by the module Key events — events marked as important to the business in GA4 Key events per 100 sessions — a measure of how frequently target actions occur Average order value — GA4 revenue divided by the number of transactions These metrics show the current value, the previous-period value and the percentage change. For example, a selected 7-day period is compared with the preceding 7 days.
Important: the module uses GA4 data, not the OpenCart order database. Transaction counts and revenue can differ from internal store reports due to tracking behaviour, refunds, user consent and analytics blockers.
Channels, traffic sources and products
Top channels — sessions, transactions, key events and revenue by GA4 channel groups, including Organic Search, Paid Search, Direct and Referral Traffic sources — results by session source and medium, such as google / organic or google / cpc Top products — the five item names with the highest GA4 item revenue, showing units purchased and item revenue These sections help you compare traffic sources, identify channels that deliver results and see which products generate revenue.
Ecommerce events
A dedicated section displays counts of the main ecommerce events:
view_item — product view add_to_cart — add to cart begin_checkout — checkout started purchase — purchase Each event count is accompanied by a percentage relative to the first non-zero step. This compares independent event counts; it is not a sequential funnel tracking the same users through each step.
Google Search Console: store visibility in search
Connecting Search Console adds a Google organic search section to the widget:
Clicks — clicks to the site from search results Impressions — appearances of links to the site in search CTR — the ratio of clicks to impressions Average position — the average position of the site's highest result across impressions A trend chart and previous-period comparisons are available for the main metrics. Search query and page tables help assess demand, identify pages receiving organic traffic and find opportunities to improve content, titles and descriptions.
Search Console data covers ordinary Google search results and does not replace Google Ads advertising statistics.
Google Ads: ad spend and performance
Advertising statistics appear in the same widget alongside store analytics. No separate module or additional widget needs to be installed.
Cost — total advertising spend for the selected period Impressions — the number of times ads were shown Clicks — the number of clicks on ads CTR — clicks as a percentage of impressions CPC — average cost per click Conversions — target actions credited to advertising according to Google Ads settings CPA — average cost per conversion Conversion value — the total conversion values supplied to or configured in Google Ads ROAS — conversion value divided by advertising spend A campaign table displays statistics, statuses and reasons for limitations. A chart shows impressions, clicks and spend. Monetary values use the advertising account's currency, while reporting periods and check timestamps respect its timezone.
Conversions do not necessarily mean purchases only: they can include enquiries, phone calls and other configured goals. ROAS expresses the relationship between conversion value and spend; it is not net profit.
Advertising monitoring and Telegram notifications
The module can check advertising through CRON and send a report to Telegram. This helps you notice account issues, campaign configuration problems or missing expected activity.
Checks advertising account and campaign status Respects statuses, start and end dates, and ad schedules Detects missing impressions and spend within a configured window of expected activity Separate settings for the analysis window and reporting delay A report after every completed check, including when no problems are detected Brief impressions, clicks and spend statistics in the message Notifications about data retrieval errors and previously detected issues that are no longer observed Delivery to multiple recipients using comma-separated numeric chat IDs A test message button and the latest check result displayed in the widget Protection against simultaneous duplicate checks Set the CRON schedule on your hosting, for example every 2 hours. The module imposes no minimum launch interval. A ready-to-use HTTP command is provided, so PHP CLI is not required.
Important: this monitors advertising status and activity, not the account balance. Google Ads API does not expose an exact prepaid balance. An “OK” status means that none of the issues checked by the module were detected in the analysed period; it does not confirm that funds remain in the account.
Interactive charts
Charts can display several metrics at once. Use checkboxes to enable or disable individual lines:
GA4: sessions, transactions, key events and revenue Search Console: clicks, impressions, CTR and position Google Ads: impressions, clicks and spend Hovering over or clicking a point displays the metric name, date and value. Advertising spend includes the currency. When Ads spend and count metrics are displayed together, spend uses a separate right-hand axis.
Reporting periods and metric explanations
Available periods include today, yesterday, 7 days, 30 days, this month, last month and a custom date range. The period selector and refresh button are shared across the widget sections.
All 21 main metrics include explanatory tooltips describing what each metric means, how it is calculated and what to consider when assessing results. Tooltips are also available for table headings and supporting sections.
Detailed setup help
The module settings include a Help tab with step-by-step instructions:
Creating a Google Cloud service account and JSON key Connecting GA4 and finding the correct Property ID Connecting Search Console and specifying siteUrl Configuring Google Ads access and understanding the difference between Customer ID and MCC Creating a Telegram bot and obtaining chat IDs Setting up CRON, the activity window and reporting delay Troubleshooting common access, authorisation and message delivery errors Caching and widget settings
Reports use native OpenCart caching with a configurable lifetime in minutes. This reduces the number of Google API requests. The force-refresh button requests fresh report data, while CRON checks do not use the report cache.
Configure the widget width, display order, initial reporting period, default GA4 and Search Console chart lines, service connection settings and Telegram monitoring.
Connection and system requirements
OpenCart 3.x or ocStore 3.x Module code tested on PHP 7.1–8.5; compatibility with a particular PHP version also depends on the store core and other extensions PHP OpenSSL Outbound HTTPS requests through cURL or enabled HTTPS URL streams A Google Cloud project with the required service APIs enabled A service account JSON key with access to the relevant Google resources For Google Ads: approved API access for the Cloud project to production advertising accounts; Test access is insufficient For Telegram: a bot token and numeric recipient IDs For automatic monitoring: a CRON scheduler on the hosting server Authorisation runs on the server through a service account and does not require an interactive Google sign-in through a browser. One JSON key is used for the connected services, provided the appropriate access permissions have been granted.
Important considerations
The module reads previously collected data; it does not install a GA4 tag or ecommerce tracking on the site Purchase, revenue and product metrics require correctly configured ecommerce event tracking The module does not modify advertising campaigns, their budgets or the store's SEO settings Google service statistics may be delayed and revised after processing Monitoring analyses completed hours with the configured delay, not real-time activity For low-traffic campaigns, missing impressions over a short period do not necessarily indicate a payment problem Search Console requires the exact property URL or a value in the format sc-domain:example.com Installation
Upload the archive through Extensions → Installer. Open Extensions → Extensions and select the Dashboard extension type. Install Store Analytics Dashboard and open its settings. Add the service account JSON and configure the required services: GA4, Search Console and/or Google Ads. Grant the service account access within the relevant Google services. Configure the widget, enable the module and save the changes. If required, connect Telegram, check the test message and add the generated CRON command to your hosting scheduler.
Updated
Store Analytics Dashboard: GA4 + Search Console + ADs
Free
70
Courier Kyiv — Courier Address Delivery in Kyiv with a Street and Building Directory for OpenCart
Courier Kyiv is a courier delivery extension for OpenCart and ocStore that allows customers to select a street and building from a synchronized Kyiv address directory instead of entering the delivery address as free text.
Addresses are loaded from the Kyiv City State Administration address registry and stored in the store’s local database. This ensures that street and building suggestions work quickly and do not depend on the availability of an external API during each checkout.
Main Features
A separate courier delivery method for Kyiv Street selection from a dropdown list Building number selection from a dropdown list A separate field for the apartment number Address loading from the Kyiv City State Administration registry Storage of the address directory in dedicated store database tables Manual synchronization from the administration panel Automatic full synchronization via cron Street search by individual words regardless of their order Search by part of a street name Basic matching of common Ukrainian and Russian spelling variants Configurable suggestion limits for streets and buildings Fixed courier delivery cost OpenCart geo zone support Configurable sort order Support for guest and registered customers Ukrainian, Russian, and English interface localization Address Selection by the Customer
After selecting courier delivery, the customer completes the address step by step:
City — Kyiv, set automatically Street — selected from the address directory suggestions Building — selected from the list of buildings for the chosen street Apartment — entered manually by the customer The apartment number is entered separately because apartment data is not available in the public address registry. The street and building must be selected from the list, which helps prevent accidental errors and nonexistent addresses.
Street Search
The search is performed using individual words, so the order of words in the query does not matter. For example, the query Volodymyra Vysotskoho can find a name stored in the registry as Vysotskoho Volodymyra Boulevard.
Search by part of a name and basic matching of common Russian and Ukrainian variants are also supported. This helps customers find, for example, Beresteiskyi Avenue using an abbreviated or alternative spelling.
Kyiv City State Administration Address Directory
The extension receives city addresses from the Kyiv City State Administration address registry API. During synchronization, the complete available set of Kyiv streets and buildings is processed and then stored in separate OpenCart tables.
The city, streets, and buildings are stored separately Repeated synchronization updates existing records New addresses are added automatically Outdated records are removed after successful synchronization Duplicate city, street, and building records are merged Simultaneous execution of multiple synchronization processes is blocked Manual Synchronization
A Synchronize Addresses button is available in the extension settings. After synchronization is completed, the following information is displayed:
synchronization status number of cities number of streets number of buildings date and time of the latest successful completion error message if the update was not completed Automatic Updates via Cron
For regular directory updates, the extension generates a ready-to-use cron URL. Access to the URL is protected by a secret key between 16 and 128 characters long.
The URL can be added to the hosting or server task scheduler. Each run fully compares the local directory with the current API data.
Saving the Address in the Order
After validating the selected street and building, the extension creates the full delivery address and passes it to the standard OpenCart order creation process.
The street, building number, building section, and apartment are stored in the main delivery address field, shipping_address_1. The extension does not create the order separately and does not interfere with OpenCart’s standard order storage logic.
Multilingual Support
The administration panel and customer interface are localized in Ukrainian, Russian, and English.
If the API returns names in multiple languages, the extension can store the localized versions separately. If a translation for the current language is not available in the source, the primary registry name is used.
OCMOD Integration
Checkout integration is implemented through OCMOD. The extension does not require manual editing of OpenCart system files.
Compatibility
OpenCart 3.x ocStore 3.x PHP 7.3–8.3 Standard OpenCart 3.x checkout Ukrainian, Russian, and English localizations System Requirements
OpenCart or ocStore 3.x installed PHP 7.3–8.3 MySQL or MariaDB The PHP cURL extension or permission to make HTTPS requests through allow_url_fopen Server access to the Kyiv City State Administration API over HTTPS The ability to configure cron for automatic directory updates Important Limitations
The extension is intended only for address delivery within Kyiv The completeness and accuracy of addresses depend on the data returned by the Kyiv City State Administration registry Street names are displayed in the format provided by the source Some addresses in the source may not include a postal code or building section The apartment number is entered manually by the customer The first synchronization processes the entire address directory and may take several minutes For automatic updates, the server must have stable access to the external API When the extension is uninstalled, the address directory tables created by it are also removed Installation
Upload the courier_kyiv_v_1_0_oc3.ocmod.zip archive through Extensions → Installer Go to Extensions → Modifications and refresh the modification cache Go to Extensions → Extensions Select Shipping as the extension type Install the Courier Address Delivery in Kyiv extension Open the extension settings Select the geo zone and configure the delivery cost, sort order, and suggestion limit Save a secure cron key containing at least 16 characters Enable the extension and save the settings Run a full address synchronization from the administration panel Add the generated URL to the cron scheduler when necessary Test street and building selection while placing a test order DEMO
Admin Page login/password: demo/demodemo Store Page License
One license covers one domain and all of its subdomains.
Courier Kyiv is a courier delivery extension for OpenCart and ocStore that allows customers to select a street and building from a synchronized Kyiv address directory instead of entering the delivery address as free text.
Addresses are loaded from the Kyiv City State Administration address registry and stored in the store’s local database. This ensures that street and building suggestions work quickly and do not depend on the availability of an external API during each checkout.
Main Features
A separate courier delivery method for Kyiv Street selection from a dropdown list Building number selection from a dropdown list A separate field for the apartment number Address loading from the Kyiv City State Administration registry Storage of the address directory in dedicated store database tables Manual synchronization from the administration panel Automatic full synchronization via cron Street search by individual words regardless of their order Search by part of a street name Basic matching of common Ukrainian and Russian spelling variants Configurable suggestion limits for streets and buildings Fixed courier delivery cost OpenCart geo zone support Configurable sort order Support for guest and registered customers Ukrainian, Russian, and English interface localization Address Selection by the Customer
After selecting courier delivery, the customer completes the address step by step:
City — Kyiv, set automatically Street — selected from the address directory suggestions Building — selected from the list of buildings for the chosen street Apartment — entered manually by the customer The apartment number is entered separately because apartment data is not available in the public address registry. The street and building must be selected from the list, which helps prevent accidental errors and nonexistent addresses.
Street Search
The search is performed using individual words, so the order of words in the query does not matter. For example, the query Volodymyra Vysotskoho can find a name stored in the registry as Vysotskoho Volodymyra Boulevard.
Search by part of a name and basic matching of common Russian and Ukrainian variants are also supported. This helps customers find, for example, Beresteiskyi Avenue using an abbreviated or alternative spelling.
Kyiv City State Administration Address Directory
The extension receives city addresses from the Kyiv City State Administration address registry API. During synchronization, the complete available set of Kyiv streets and buildings is processed and then stored in separate OpenCart tables.
The city, streets, and buildings are stored separately Repeated synchronization updates existing records New addresses are added automatically Outdated records are removed after successful synchronization Duplicate city, street, and building records are merged Simultaneous execution of multiple synchronization processes is blocked Manual Synchronization
A Synchronize Addresses button is available in the extension settings. After synchronization is completed, the following information is displayed:
synchronization status number of cities number of streets number of buildings date and time of the latest successful completion error message if the update was not completed Automatic Updates via Cron
For regular directory updates, the extension generates a ready-to-use cron URL. Access to the URL is protected by a secret key between 16 and 128 characters long.
The URL can be added to the hosting or server task scheduler. Each run fully compares the local directory with the current API data.
Saving the Address in the Order
After validating the selected street and building, the extension creates the full delivery address and passes it to the standard OpenCart order creation process.
The street, building number, building section, and apartment are stored in the main delivery address field, shipping_address_1. The extension does not create the order separately and does not interfere with OpenCart’s standard order storage logic.
Multilingual Support
The administration panel and customer interface are localized in Ukrainian, Russian, and English.
If the API returns names in multiple languages, the extension can store the localized versions separately. If a translation for the current language is not available in the source, the primary registry name is used.
OCMOD Integration
Checkout integration is implemented through OCMOD. The extension does not require manual editing of OpenCart system files.
Compatibility
OpenCart 3.x ocStore 3.x PHP 7.3–8.3 Standard OpenCart 3.x checkout Ukrainian, Russian, and English localizations System Requirements
OpenCart or ocStore 3.x installed PHP 7.3–8.3 MySQL or MariaDB The PHP cURL extension or permission to make HTTPS requests through allow_url_fopen Server access to the Kyiv City State Administration API over HTTPS The ability to configure cron for automatic directory updates Important Limitations
The extension is intended only for address delivery within Kyiv The completeness and accuracy of addresses depend on the data returned by the Kyiv City State Administration registry Street names are displayed in the format provided by the source Some addresses in the source may not include a postal code or building section The apartment number is entered manually by the customer The first synchronization processes the entire address directory and may take several minutes For automatic updates, the server must have stable access to the external API When the extension is uninstalled, the address directory tables created by it are also removed Installation
Upload the courier_kyiv_v_1_0_oc3.ocmod.zip archive through Extensions → Installer Go to Extensions → Modifications and refresh the modification cache Go to Extensions → Extensions Select Shipping as the extension type Install the Courier Address Delivery in Kyiv extension Open the extension settings Select the geo zone and configure the delivery cost, sort order, and suggestion limit Save a secure cron key containing at least 16 characters Enable the extension and save the settings Run a full address synchronization from the administration panel Add the generated URL to the cron scheduler when necessary Test street and building selection while placing a test order DEMO
Admin Page login/password: demo/demodemo Store Page License
One license covers one domain and all of its subdomains.
Updated
Courier Kyiv - targeted delivery in Kiev
460 грн
0 1
The IndexNow module adds a tool for submitting website page URLs from OpenCart 3 and ocStore 3 to search engines using the IndexNow protocol.
The extension can automatically notify search engines when products, categories, manufacturers, and information pages are created, edited, or deleted. It also allows you to generate a URL queue for bulk submission via Cron.
Important Information About IndexNow
IndexNow is a protocol for quickly notifying search engines about new, updated, or deleted pages on a website. The module submits URLs through the IndexNow endpoint, but it does not guarantee page indexing.
Not all search engines use the IndexNow protocol. Support depends on each specific search engine, so URL submission through IndexNow does not replace standard SEO optimization, XML Sitemap, canonical URLs, robots.txt, or internal linking.
Important Information About URL Generation
The module uses its own URL generation mechanism for submitting URLs to IndexNow. It does not automatically read or reproduce all settings from third-party SEO URL or multilingual modules.
The URL format must be configured manually according to how links actually work on your website. Before bulk submission, it is recommended to enable debug mode and check the generated URLs.
Module Features
Automatically add URLs to the queue when products are created Automatically add URLs to the queue when products are edited Automatically add URLs to the queue when products are deleted Work with products, categories, manufacturers, and information pages Submit URLs immediately after a page is changed Generate a URL queue for bulk submission Add URLs manually Submit URLs in batches via Cron Store the history of successfully submitted URLs Avoid re-adding already submitted URLs during bulk scanning Keep URLs in the queue for retry if an error occurs View the submission log View the list of URLs submitted to IndexNow URL Settings
The module allows you to configure the URL format according to the structure of a specific website.
Short SEO URLs Full URLs with category paths Product URLs with the full category path Category URLs with full nesting URL ending: empty, /, or .html URLs for one language or all active languages Language prefixes, for example /ua/, /ru/, /en/ Separate domains or subdomains for different languages URL Configuration Examples
Website Without Language Prefixes
If all pages open without a language prefix, select the mode without prefixes.
https://example.com/product-url https://example.com/category/product-url Default Language Without Prefix, Other Languages With Prefixes
If the default language opens without a prefix and other languages use prefixes, leave the default language prefix empty and specify prefixes for the other languages.
https://example.com/product-url https://example.com/ua/product-url https://example.com/en/product-url Languages on Subdomains
If separate subdomains are used for languages, specify the base URL for each language.
https://example.com/product-url https://ua.example.com/product-url https://en.example.com/product-url URLs With .html Ending
If SEO URLs on the website use the .html ending, specify it in the module settings.
https://example.com/product-url.html https://example.com/category/product-url.html Recommended Setup Order
Install the module through the OpenCart admin panel Refresh modifications Go to the modules section and open IndexNow Enable the module Set or generate the IndexNow API key Configure the URL format according to your website structure Configure multilingual settings if the website uses multiple languages Enable debug mode Generate a test URL queue Check that the generated URLs match the real website URLs If the URLs are correct, disable debug mode Configure Cron for queue generation Configure Cron for URL submission Cron Jobs
For large websites, it is recommended to use two separate Cron jobs.
The first Cron gradually scans the website and generates the URL queue The second Cron submits URLs from the queue to IndexNow This approach allows the module to work with large catalogs and avoid exceeding submission limits. If an error occurs during submission, URLs remain in the queue and will be submitted again during the next Cron run.
Queue and Log
View URLs in the queue Pagination for the URL list Clear the entire queue Delete individual URLs from the queue Submission log Log pagination IndexNow response status List of URLs submitted to IndexNow Benefits
Fast notification of search engines about website changes Automation of new and updated page submission Convenient work with large catalogs Ability to check URLs before real submission Flexible configuration for multilingual websites Result control through the submission log Installation
Install the module through the OpenCart admin panel Refresh modifications Go to Extensions and open IndexNow Enable the module and set the API key Configure URL generation, multilingual settings, and Cron jobs DEMO
Admin Page login/password: demo/demodemo License
The license applies to one domain and its subdomains.
The extension can automatically notify search engines when products, categories, manufacturers, and information pages are created, edited, or deleted. It also allows you to generate a URL queue for bulk submission via Cron.
Important Information About IndexNow
IndexNow is a protocol for quickly notifying search engines about new, updated, or deleted pages on a website. The module submits URLs through the IndexNow endpoint, but it does not guarantee page indexing.
Not all search engines use the IndexNow protocol. Support depends on each specific search engine, so URL submission through IndexNow does not replace standard SEO optimization, XML Sitemap, canonical URLs, robots.txt, or internal linking.
Important Information About URL Generation
The module uses its own URL generation mechanism for submitting URLs to IndexNow. It does not automatically read or reproduce all settings from third-party SEO URL or multilingual modules.
The URL format must be configured manually according to how links actually work on your website. Before bulk submission, it is recommended to enable debug mode and check the generated URLs.
Module Features
Automatically add URLs to the queue when products are created Automatically add URLs to the queue when products are edited Automatically add URLs to the queue when products are deleted Work with products, categories, manufacturers, and information pages Submit URLs immediately after a page is changed Generate a URL queue for bulk submission Add URLs manually Submit URLs in batches via Cron Store the history of successfully submitted URLs Avoid re-adding already submitted URLs during bulk scanning Keep URLs in the queue for retry if an error occurs View the submission log View the list of URLs submitted to IndexNow URL Settings
The module allows you to configure the URL format according to the structure of a specific website.
Short SEO URLs Full URLs with category paths Product URLs with the full category path Category URLs with full nesting URL ending: empty, /, or .html URLs for one language or all active languages Language prefixes, for example /ua/, /ru/, /en/ Separate domains or subdomains for different languages URL Configuration Examples
Website Without Language Prefixes
If all pages open without a language prefix, select the mode without prefixes.
https://example.com/product-url https://example.com/category/product-url Default Language Without Prefix, Other Languages With Prefixes
If the default language opens without a prefix and other languages use prefixes, leave the default language prefix empty and specify prefixes for the other languages.
https://example.com/product-url https://example.com/ua/product-url https://example.com/en/product-url Languages on Subdomains
If separate subdomains are used for languages, specify the base URL for each language.
https://example.com/product-url https://ua.example.com/product-url https://en.example.com/product-url URLs With .html Ending
If SEO URLs on the website use the .html ending, specify it in the module settings.
https://example.com/product-url.html https://example.com/category/product-url.html Recommended Setup Order
Install the module through the OpenCart admin panel Refresh modifications Go to the modules section and open IndexNow Enable the module Set or generate the IndexNow API key Configure the URL format according to your website structure Configure multilingual settings if the website uses multiple languages Enable debug mode Generate a test URL queue Check that the generated URLs match the real website URLs If the URLs are correct, disable debug mode Configure Cron for queue generation Configure Cron for URL submission Cron Jobs
For large websites, it is recommended to use two separate Cron jobs.
The first Cron gradually scans the website and generates the URL queue The second Cron submits URLs from the queue to IndexNow This approach allows the module to work with large catalogs and avoid exceeding submission limits. If an error occurs during submission, URLs remain in the queue and will be submitted again during the next Cron run.
Queue and Log
View URLs in the queue Pagination for the URL list Clear the entire queue Delete individual URLs from the queue Submission log Log pagination IndexNow response status List of URLs submitted to IndexNow Benefits
Fast notification of search engines about website changes Automation of new and updated page submission Convenient work with large catalogs Ability to check URLs before real submission Flexible configuration for multilingual websites Result control through the submission log Installation
Install the module through the OpenCart admin panel Refresh modifications Go to Extensions and open IndexNow Enable the module and set the API key Configure URL generation, multilingual settings, and Cron jobs DEMO
Admin Page login/password: demo/demodemo License
The license applies to one domain and its subdomains.
Updated
IndexNow
680грн
460 грн
0 1
The AI LLM Feed extension adds a tool to OpenCart 3 and ocStore 3 for creating a structured store description for language models and AI agents in llms.txt and Markdown format.
The extension creates llms.txt and llms-full.txt files, as well as separate Markdown files for products, categories, manufacturers, and information pages. Updates are processed through a queue and Cron, allowing the extension to be used in stores with large catalogues.
Important information about llms.txt
llms.txt is a proposed open format for presenting essential website information to language models and AI agents. It helps provide an AI system with a clear website description and structured links to important pages without requiring it to analyse menus, JavaScript, and the entire HTML layout.
The llms.txt protocol is not currently used by every AI system. Its support and practical use are still developing, so publishing these files does not guarantee website crawling, inclusion of its pages in AI answers, or improved search rankings.
The extension does not replace XML or HTML Sitemaps, robots.txt, canonical URLs, Schema.org structured data, conventional SEO, internal linking, or page content available to users. It is an additional technical channel that helps prepare a website for the future development of AI search and AI agents.
The llms-full.txt file in this extension is an extended index containing links to selected sections. The extension intentionally does not combine the entire catalogue into one large text file: complete data is stored in separate Markdown files, making it easier to update and use.
Important information about URL generation
The extension includes its own mechanism for building links to products, categories, manufacturers, and information pages. SEO URLs are generated using the standard seo_url table, the category_path structure, and the extension’s own URL settings.
During generation, the extension does not call OpenCart’s standard URL rewriting mechanism and does not depend on third-party SEO modifications being executed. This reduces the risk of errors caused by conflicts or special behaviour in third-party SEO URL and multilingual extensions.
The link format must be configured to match the website’s actual structure: select language folders or separate domains, a full or short category path, and a URL suffix. Before starting a full generation, we recommend opening the product preview and confirming that the generated links match the storefront URLs.
Extension features
Create the root llms.txt file Create the additional llms-full.txt file Create separate Markdown files for products Create separate Markdown files for categories Create separate Markdown files for manufacturers Create separate Markdown files for information pages Create section indexes and a language index Export all, selected, or no records for each entity type Create a separate set of files for each active store language Add separate titles, descriptions, static text, and Sitemap URLs for each language Add separate HTML and XML Sitemaps to llms.txt and llms-full.txt Automatically add queue jobs when catalogue data changes Process the queue in batches via Cron Content modes
The extension lets you choose how llms.txt and llms-full.txt are generated.
Links only — the extension creates indexes, entity files, and structured links Static text only — llms.txt and llms-full.txt are created from the specified title, short description, manual text, and Sitemap URLs Static text + links — manual text is displayed after the short description, followed by automatically generated links Separate title, short description, text, HTML Sitemap, and XML Sitemap fields are provided for llms.txt and llms-full.txt. Values are configured separately for each active language.
Export settings
One of three modes can be selected for products, categories, manufacturers, and information pages.
Export all records Export selected records only Do not export this entity type When “Selected only” is enabled for categories or manufacturers, these settings are also applied to products. For example, files can be created only for products from selected categories or only for products from specific manufacturers.
Product Markdown file content
Depending on the settings, a product file can contain:
Product name and short description Link to the product page Product ID Model and SKU Manufacturer Main category Regular and special prices Availability status Last update date Product attributes Available options Cleaned description in plain text or Markdown format Main image Additional images with a configurable limit URL settings
The extension allows you to configure the link format to match the structure of a particular website.
Short SEO URLs Full URLs with parent category paths Product URLs with a full category path Category URLs with the complete hierarchy URL endings: no suffix, /, or .html Files for the default language only or for all active languages Language folders such as /ru/ or /en/ Separate domains, subdomains, or base URLs for different languages The internal OpenCart language code, such as uk-ua or en-gb, is used only for file storage and is not added to public URLs.
URL configuration examples
Website without language folders
When only the default language is exported and it does not use a language folder, the public URLs will look like this:
https://example.com/llms.txt https://example.com/llms-full.txt https://example.com/llms/products/145.md Default language without a folder, other languages with folders
If the default language opens without a prefix while other languages use folders, leave the default language field empty and enter the appropriate values for the other languages.
https://example.com/llms.txt https://example.com/ru/llms.txt https://example.com/en/llms.txt https://example.com/en/llms/products/145.md Languages on separate domains or subdomains
If separate domains or subdomains are used for languages, specify the base URL for each language in the extension settings.
https://example.com/llms.txt https://ru.example.com/llms.txt https://en.example.com/llms.txt SEO URLs ending in .html
If the store pages end in .html, specify it in the SEO URL suffix setting.
https://example.com/product-url.html https://example.com/category/product-url.html Automatic file updates
The extension uses standard OpenCart events. When a product, category, or information page is added, edited, deleted, or has its status changed using the quick action, the corresponding entity is added to the queue. Manufacturer changes are also added to the queue.
When a category is changed, the extension also adds related products and child categories to the queue. When a manufacturer is changed, its products are added to the queue. This is required because category names, paths, and manufacturers are used in product files and indexes.
Direct SQL queries do not trigger OpenCart events. If a third-party import changes the database directly, updating date_modified alone will not create a job. After such an import, run Full Reconcile or add the full catalogue to the queue manually.
Cron jobs
The extension provides separate URLs for different scenarios.
Regular Cron without action — processes the existing queue in batches. Add this URL to the scheduler with an interval of approximately 1–5 minutes action=full — adds the entire current catalogue to the queue. Run it manually after installation or when all files need to be generated again action=index — adds only root files and indexes to the queue. Use it after changing titles, descriptions, Sitemap URLs, language URLs, or section placement action=reconcile — removes stale records and adds the current catalogue to the queue. Run it manually after a direct import, bulk deletion, or file synchronisation problem URLs containing action=full, action=index, or action=reconcile should not be added to the regular recurring Cron job. They are intended for separate manual scenarios.
Queue, files, and log
View queued jobs Queue pagination and sorting Process the queue manually Delete an individual job View generated files and their public URLs File list pagination and sorting Delete an individual file Delete all generated files Localised operation, change, and error log Log pagination and sorting Clear the log Protection against simultaneous manual and Cron processing Advantages
Structured catalogue representation for AI systems Preparation for the future development of AI search and AI agents No API keys or paid AI services required Automatic file updates after standard catalogue changes Batch processing for large catalogues through a queue and Cron Flexible selection of products, categories, manufacturers, and information pages Separate content for each language Built-in link generation mechanism Support for language folders, domains, and subdomains Result monitoring through the file list and log Built-in detailed help with configuration examples Compatibility
OpenCart 3.x / ocStore 3.x PHP 7.x–8.x Ukrainian, English, and Russian localisations Access to a Cron scheduler Write permission for the OpenCart storage directory Installation
Upload the extension archive through Extensions / Installer Go to Extensions / Modifications and click Refresh Go to Extensions / Extensions Select the Feeds extension type Find AI LLM Feed and click Install Recommended configuration sequence
Enable the extension Enable llms.txt and, if required, llms-full.txt Select the content mode Enter the title, short description, text, and Sitemap URLs for the required languages Select the entity types and their export modes Configure the product Markdown file content Configure language folders or domains to match the website structure Configure the full category path and SEO URL suffix Check the generated Markdown using the product preview Save the settings Add a full generation to the queue once Configure a regular Cron job to process the queue Check the public llms.txt and llms-full.txt URLs If the server returns a 403 error when opening llms.txt or llms-full.txt, you may need to add an exception for these files to the standard FilesMatch rule in the .htaccess file. An example rule is provided in the extension help section.
DEMO
Admin Page login/password: demo/demodemo llms.txt llms-full.txt Licence
The licence covers one domain and its subdomains.
The extension creates llms.txt and llms-full.txt files, as well as separate Markdown files for products, categories, manufacturers, and information pages. Updates are processed through a queue and Cron, allowing the extension to be used in stores with large catalogues.
Important information about llms.txt
llms.txt is a proposed open format for presenting essential website information to language models and AI agents. It helps provide an AI system with a clear website description and structured links to important pages without requiring it to analyse menus, JavaScript, and the entire HTML layout.
The llms.txt protocol is not currently used by every AI system. Its support and practical use are still developing, so publishing these files does not guarantee website crawling, inclusion of its pages in AI answers, or improved search rankings.
The extension does not replace XML or HTML Sitemaps, robots.txt, canonical URLs, Schema.org structured data, conventional SEO, internal linking, or page content available to users. It is an additional technical channel that helps prepare a website for the future development of AI search and AI agents.
The llms-full.txt file in this extension is an extended index containing links to selected sections. The extension intentionally does not combine the entire catalogue into one large text file: complete data is stored in separate Markdown files, making it easier to update and use.
Important information about URL generation
The extension includes its own mechanism for building links to products, categories, manufacturers, and information pages. SEO URLs are generated using the standard seo_url table, the category_path structure, and the extension’s own URL settings.
During generation, the extension does not call OpenCart’s standard URL rewriting mechanism and does not depend on third-party SEO modifications being executed. This reduces the risk of errors caused by conflicts or special behaviour in third-party SEO URL and multilingual extensions.
The link format must be configured to match the website’s actual structure: select language folders or separate domains, a full or short category path, and a URL suffix. Before starting a full generation, we recommend opening the product preview and confirming that the generated links match the storefront URLs.
Extension features
Create the root llms.txt file Create the additional llms-full.txt file Create separate Markdown files for products Create separate Markdown files for categories Create separate Markdown files for manufacturers Create separate Markdown files for information pages Create section indexes and a language index Export all, selected, or no records for each entity type Create a separate set of files for each active store language Add separate titles, descriptions, static text, and Sitemap URLs for each language Add separate HTML and XML Sitemaps to llms.txt and llms-full.txt Automatically add queue jobs when catalogue data changes Process the queue in batches via Cron Content modes
The extension lets you choose how llms.txt and llms-full.txt are generated.
Links only — the extension creates indexes, entity files, and structured links Static text only — llms.txt and llms-full.txt are created from the specified title, short description, manual text, and Sitemap URLs Static text + links — manual text is displayed after the short description, followed by automatically generated links Separate title, short description, text, HTML Sitemap, and XML Sitemap fields are provided for llms.txt and llms-full.txt. Values are configured separately for each active language.
Export settings
One of three modes can be selected for products, categories, manufacturers, and information pages.
Export all records Export selected records only Do not export this entity type When “Selected only” is enabled for categories or manufacturers, these settings are also applied to products. For example, files can be created only for products from selected categories or only for products from specific manufacturers.
Product Markdown file content
Depending on the settings, a product file can contain:
Product name and short description Link to the product page Product ID Model and SKU Manufacturer Main category Regular and special prices Availability status Last update date Product attributes Available options Cleaned description in plain text or Markdown format Main image Additional images with a configurable limit URL settings
The extension allows you to configure the link format to match the structure of a particular website.
Short SEO URLs Full URLs with parent category paths Product URLs with a full category path Category URLs with the complete hierarchy URL endings: no suffix, /, or .html Files for the default language only or for all active languages Language folders such as /ru/ or /en/ Separate domains, subdomains, or base URLs for different languages The internal OpenCart language code, such as uk-ua or en-gb, is used only for file storage and is not added to public URLs.
URL configuration examples
Website without language folders
When only the default language is exported and it does not use a language folder, the public URLs will look like this:
https://example.com/llms.txt https://example.com/llms-full.txt https://example.com/llms/products/145.md Default language without a folder, other languages with folders
If the default language opens without a prefix while other languages use folders, leave the default language field empty and enter the appropriate values for the other languages.
https://example.com/llms.txt https://example.com/ru/llms.txt https://example.com/en/llms.txt https://example.com/en/llms/products/145.md Languages on separate domains or subdomains
If separate domains or subdomains are used for languages, specify the base URL for each language in the extension settings.
https://example.com/llms.txt https://ru.example.com/llms.txt https://en.example.com/llms.txt SEO URLs ending in .html
If the store pages end in .html, specify it in the SEO URL suffix setting.
https://example.com/product-url.html https://example.com/category/product-url.html Automatic file updates
The extension uses standard OpenCart events. When a product, category, or information page is added, edited, deleted, or has its status changed using the quick action, the corresponding entity is added to the queue. Manufacturer changes are also added to the queue.
When a category is changed, the extension also adds related products and child categories to the queue. When a manufacturer is changed, its products are added to the queue. This is required because category names, paths, and manufacturers are used in product files and indexes.
Direct SQL queries do not trigger OpenCart events. If a third-party import changes the database directly, updating date_modified alone will not create a job. After such an import, run Full Reconcile or add the full catalogue to the queue manually.
Cron jobs
The extension provides separate URLs for different scenarios.
Regular Cron without action — processes the existing queue in batches. Add this URL to the scheduler with an interval of approximately 1–5 minutes action=full — adds the entire current catalogue to the queue. Run it manually after installation or when all files need to be generated again action=index — adds only root files and indexes to the queue. Use it after changing titles, descriptions, Sitemap URLs, language URLs, or section placement action=reconcile — removes stale records and adds the current catalogue to the queue. Run it manually after a direct import, bulk deletion, or file synchronisation problem URLs containing action=full, action=index, or action=reconcile should not be added to the regular recurring Cron job. They are intended for separate manual scenarios.
Queue, files, and log
View queued jobs Queue pagination and sorting Process the queue manually Delete an individual job View generated files and their public URLs File list pagination and sorting Delete an individual file Delete all generated files Localised operation, change, and error log Log pagination and sorting Clear the log Protection against simultaneous manual and Cron processing Advantages
Structured catalogue representation for AI systems Preparation for the future development of AI search and AI agents No API keys or paid AI services required Automatic file updates after standard catalogue changes Batch processing for large catalogues through a queue and Cron Flexible selection of products, categories, manufacturers, and information pages Separate content for each language Built-in link generation mechanism Support for language folders, domains, and subdomains Result monitoring through the file list and log Built-in detailed help with configuration examples Compatibility
OpenCart 3.x / ocStore 3.x PHP 7.x–8.x Ukrainian, English, and Russian localisations Access to a Cron scheduler Write permission for the OpenCart storage directory Installation
Upload the extension archive through Extensions / Installer Go to Extensions / Modifications and click Refresh Go to Extensions / Extensions Select the Feeds extension type Find AI LLM Feed and click Install Recommended configuration sequence
Enable the extension Enable llms.txt and, if required, llms-full.txt Select the content mode Enter the title, short description, text, and Sitemap URLs for the required languages Select the entity types and their export modes Configure the product Markdown file content Configure language folders or domains to match the website structure Configure the full category path and SEO URL suffix Check the generated Markdown using the product preview Save the settings Add a full generation to the queue once Configure a regular Cron job to process the queue Check the public llms.txt and llms-full.txt URLs If the server returns a 403 error when opening llms.txt or llms-full.txt, you may need to add an exception for these files to the standard FilesMatch rule in the .htaccess file. An example rule is provided in the extension help section.
DEMO
Admin Page login/password: demo/demodemo llms.txt llms-full.txt Licence
The licence covers one domain and its subdomains.
Updated
AI LLM Feed
460грн
320 грн
0 1
The Dropship Partner Cabinet module adds a complete dropshipping partner management system to OpenCart. The extension combines partner registration, personalized prices, order creation, balance accounting, fund reservation, payouts, product XML (YML) feeds, and notifications in one dedicated cabinet.
Each partner receives a dedicated workspace where they can create orders for their customers, select a financial model, manage personal feeds, submit balance top-up and payout requests, review the financial journal, and configure notifications.
The administrator manages partners, available products, minimum markups, delivery and payment methods, order statuses, balances, payouts, the feed queue, and notification channels. Every financial change is recorded in a separate journal.
How the module works
A customer registers on the website and applies to join the partner program The administrator reviews the application, configures personal terms, and approves the partner The partner receives access to a dedicated dropshipping cabinet Partner prices are calculated from the product cost price and the administrator's minimum markup The partner can create orders for their customers without using the theme's standard cart Each order is created as a complete OpenCart order and appears in the standard administration area Financial operations follow the selected model: buyout / prepayment or commission sales The partner can create static product XML (YML) feeds with personalized prices Order, payout, top-up, and feed statuses can be sent by email or Telegram Module features
Accept applications to join the partner program Create partners manually in the administration area Move approved partners to a dedicated customer group Store the original customer group and restore it after a partner is blocked or deleted Set global and personal minimum markups Create markup rules for individual products, categories, and manufacturers Support percentage and fixed markups Create dropshipping orders through a dedicated form Work with the buyout / prepayment model Work with the commission model Track balance, reserved funds, pending earnings, and the amount available for payout Account for outbound and return delivery Create balance top-up requests Create payout requests Record every change in the financial journal Create multiple personal feed profiles for one partner Generate static XML (YML) feeds compatible with Prom.ua import Select feed language, currency, products, categories, manufacturers, and fields Map store categories to marketplace categories through portal_category_id Generate full feeds for initial import and compact feeds for fast price and stock updates Generate feeds manually or through a protected CRON task Send notifications through Telegram, email, or both channels Show administrators new applications, orders, payouts, top-ups, and feed errors Support Ukrainian, English, and Russian Dropshipping partner registration
A partner is a regular registered store customer for whom a separate partner profile is created. When applying, the customer provides:
Store name Store URL Contact email address Phone number in international format The administrator can approve, reject, or block an application. Only a partner with the Approved status receives access to the working sections.
After approval, the module moves the customer to the configured dropshipping customer group. The original group is remembered and restored after the partner is blocked, rejected, or deleted.
The administrator can also create a partner manually for an existing customer account.
Partner details
In the cabinet, the partner can edit their contact and payment details:
Store name Store URL Contact email address Phone number Payout recipient Tax ID / Company registration number IBAN The partner can see their unique ID. It can be included in a payment reference so the administrator can reliably identify the payer when processing a balance top-up.
Cost price
All calculations are based on the product cost price stored in product.cost. The modification adds a cost price field to the standard product editing form.
If the cost column has already been created by another purchase price module, Dropship Partner Cabinet uses the existing field. The cost column is not removed when this module is uninstalled.
A product with a zero cost price cannot participate in partner sales and is not exported to personal feeds.
Minimum markup rules
The administrator defines the minimum price below which a partner cannot sell a product. The calculation starts with the cost price.
Example: the cost price is 1,000 and the administrator's minimum markup is 5%. The partner's settlement price is 1,050.
The module supports:
A global minimum markup for all partners A personal minimum markup for an individual partner Rules for a specific product Rules for a category Rules for a manufacturer Percentage markup Fixed amount Rule priority:
Individual product Category Manufacturer Partner's personal markup Module's global markup If a product belongs to several categories with different rules, the rule that produces the highest final price is used.
Priority example: the manufacturer markup is 5%, the category markup is 8%, and a fixed amount of 150 is assigned to the product. For a product with a cost price of 1,000, the product rule takes priority and the settlement price is 1,150.
Creating orders
The partner creates orders through a dedicated cabinet form. The theme's standard cart and checkout are not used.
The partner selects a financial model Finds a product by name, model, or SKU Adds products to the order table Specifies the required quantity Sets their own selling price when needed Enters the actual recipient's details Selects a delivery and payment method Creates the order Autocomplete shows current product availability. Out-of-stock products are not hidden, but are clearly marked as unavailable. A quantity exceeding the available stock cannot be added.
The created order is compatible with the standard OpenCart order system. The partner remains the customer in the standard order, while the delivery details belong to the actual recipient.
Buyout / prepayment financial model
This model is suitable when the partner has already received payment from the buyer and must pay the store the settlement cost of the products.
Example:
Cost price — 1,000 Store's minimum markup — 5% Settlement amount — 1,050 Partner's selling price — 1,260 When the order is created, 1,050 is reserved on the partner's balance. After successful completion, the reserved amount is permanently deducted.
If the available balance is insufficient, the order is still saved but receives the financial status Insufficient funds — awaiting top-up. The administrator sees a warning and should not process the order until the balance has been replenished.
After a top-up, setting a processing status again attempts to create the reserve. The order cannot be completed without successfully reserving the settlement amount.
Commission financial model
The commission model is used when the store receives payment directly from the recipient and the partner earns the difference between the selling price and the settlement amount.
Example:
Store settlement amount — 1,050 Recipient's selling price — 1,260 Partner earnings — 210 After the order is handed over to the delivery service, 210 is recorded as pending earnings. Once the order is successfully completed, this amount becomes available for payout.
No advance balance top-up is required for a commission order. If the order is cancelled or returned, pending or already confirmed earnings are reversed.
Order statuses
The administrator maps OpenCart statuses to the processing stages of dropshipping orders:
Initial status — a new order that has not yet entered processing Order accepted for processing — the administrator has started assembling the order Handed over to delivery service — the shipment has been given to the carrier Order completed — the recipient has received the order Order cancelled — the order was cancelled or the shipment was returned Several OpenCart statuses can be assigned to one financial action. The same status cannot be used for different stages at the same time.
Reapplying the same status does not create duplicate reservations, deductions, or accruals. The module checks the order's current financial state before every operation.
The partner can see the order status history, dates, and administrator comments in the cabinet.
Recipient and delivery field builder
The administrator can create a custom set of order form fields and separate fields for every delivery method.
The following settings are available for every field:
Technical code Name in all store languages Field type Order field where the value will be stored Required status Status Sort order Regular text fields, multiline fields, a country list, and a dependent region / state list are supported.
Countries and regions are loaded from the store's local database. After a country is selected, the partner receives the corresponding list of regions.
Values from several fields can be directed to shipping_address_1 or shipping_address_2. The module combines them into a readable value with localized field names.
Example: “Street: Heroiv, Building: 22, Apartment: 3”.
Delivery and payment methods
The administrator creates the delivery methods and recipient payment methods available to partners.
Each delivery method has:
A technical code, for example dropship.novapost A name in all store languages Status Sort order A custom set of fields Courier delivery can request a city, street, building, and apartment. Branch delivery can request a city and branch number. Parcel locker delivery can request a city and locker number.
The technical delivery code is stored in shipping_code and the localized name in shipping_method. The payment code is stored in payment_code and its name in payment_method.
Outbound and return delivery
For every order, the administrator separately specifies:
Who pays for delivery Actual outbound delivery cost Delivery comment Return delivery cost Return comment If a successful delivery is paid by the recipient, its cost is not deducted from the partner's balance. If the partner pays for delivery, the actual amount is deducted from their balance.
If a shipment is returned, both outbound and return delivery costs are charged to the partner regardless of who was initially selected as the payer.
Before setting the shipped or completed status, the administrator must confirm the outbound delivery cost, even if it is zero. Cancellation requires separate confirmation of both outbound and return delivery.
Balance and reserved funds
The financial system separates several indicators:
Balance — the partner's own funds Reserved funds — funds reserved for buyout orders Pending earnings — income from commission orders that have not yet been completed Available for payout — confirmed income from completed commission orders The amount available for payout includes the free balance not currently reserved and confirmed commission earnings.
The administrator can manually credit or debit a partner's balance. The adjustment reason is saved in the financial journal and can be sent to the partner as a notification.
Balance top-ups
The administrator enters the store's payment details in the module settings:
Payment recipient Tax ID / Company registration number IBAN Support phone numbers Support email address The partner sees these details in the cabinet, makes a payment, and submits a top-up request. The request includes the amount and information the administrator can use to locate the payment.
The administrator verifies receipt and approves or rejects the request. The balance increases only after manual approval.
Partner payouts
A partner can submit a payout request for an amount that does not exceed their free balance and confirmed earnings.
To submit a request, the partner must provide:
Recipient Tax ID / Company registration number IBAN Funds are not transferred automatically. The administrator reviews the request, makes the payment manually, and assigns a status:
Pending Paid Rejected If a pending request is rejected or deleted, the amount reserved for payout is returned to the partner.
Financial journal
Every financial operation is recorded in a separate journal:
Reserving funds for an order Deducting the settlement amount Releasing a reserve Refunding product cost Deducting outbound delivery Deducting return delivery Accruing pending earnings Confirming commission earnings Balance top-up Payout Manual administrator adjustment For order-related operations, the order number and a link to the order are displayed. The journal shows changes to the balance, reserved funds, pending earnings, amount available for payout, and the comment.
Personal XML (YML) feeds
Every approved partner can create personal static product feeds. The maximum number of profiles is set globally by the administrator or individually for a particular partner.
A feed profile contains:
Custom name Language Currency Product availability mode Categories Manufacturers Additional markup Personal markup rules XML (YML) field set The partner can export:
All products Only in-stock products Only out-of-stock products The administrator can restrict the categories and manufacturers that partners are allowed to use in their feeds.
XML (YML) feed fields
The partner independently selects the data to export:
Product name Category Description Price Stock quantity Product URL Main and additional images Manufacturer Model SKU Attributes Weight Dimensions GTIN MPN The offer identifier and availability flag are always generated. The field used as the offer ID is selected by the administrator in the module settings.
The full field set is suitable for the initial product import. A compact feed containing, for example, only price and stock can be used to update an already imported catalog quickly.
Feed language and currency
For each profile, the partner selects one of the active store languages. Product names, descriptions, categories, and attributes entered in that language are included in the feed.
The module does not translate content automatically. If catalog data has not been entered in the required language, it cannot be generated automatically in the feed.
Prices are converted to one of the store's active currencies. The selected currency code is passed in currencyId.
Prom.ua categories
A numeric Prom.ua marketplace category ID can be specified for every store category. When filled in, the module exports it in the portal_category_id tag.
This maps the store's own catalog structure to marketplace categories without changing the categories in the store.
Feed markups
The feed's additional markup is applied after the administrator's minimum price.
Example:
Cost price — 1,000 Administrator's minimum markup — 5% Settlement price — 1,050 Feed's own markup — 20% Feed price — 1,260 The profile markup can be overridden for a specific product, category, or manufacturer. Personal feed rule priority is: product, category, manufacturer, then the profile's global markup.
Static files and CRON
Feeds are generated as static XML files. Requests from an external system to a feed URL do not run heavy SQL queries or rebuild the catalog in real time.
A partner can manually add their feed to the update queue The feed URL remains unchanged after regeneration A product, price, or stock change queues related feeds without deleting the previous file While a new version is generated, the previous successful file and its URL remain available Feeds are processed in batches Each CRON call uses the available PHP execution time and keeps a safety margin before the server limit When the time limit is reached, the next call resumes from the last processed product Notifications
The partner can select a notification channel:
Telegram Email All channels Available event types:
Order status change Feed generated successfully Feed generation error Payout status change Balance adjustment Top-up request status change Payout and top-up messages include the operation amount, new status, and administrator comment.
For Telegram, the administrator enters the bot token and each partner enters their own Chat ID. A separate Mail or SMTP transport can be configured independently of the store's main email settings.
Administration area
After installation, a dedicated dropshipping cabinet section appears in the administration area's left menu.
Administrators have access to:
General settings Partner list Adding and editing partners Dropshipping orders Payout requests Top-up requests Financial journals Feed list and queue Delivery and payment settings Order status settings Telegram and email settings Complete built-in documentation The administration header notification widget shows:
New partner applications New dropshipping orders Top-up requests Payout requests Feeds with errors The standard OpenCart order page displays a dedicated label linking to the dropshipping order and showing its financial status.
Dropshipping cabinet pages
The demo cabinet contains the following pages:
https://demo.ocmodules.in.ua/index.php?route=dropship/dropship — dashboard with financial indicators and quick links https://demo.ocmodules.in.ua/index.php?route=dropship/account — partner store, contacts, and banking details https://demo.ocmodules.in.ua/index.php?route=dropship/order — list of orders created by the partner https://demo.ocmodules.in.ua/index.php?route=dropship/order/create — dedicated form for creating an order for a recipient https://demo.ocmodules.in.ua/index.php?route=dropship/feed — profile list, generation statuses, and static URLs https://demo.ocmodules.in.ua/index.php?route=dropship/feed/add — create a personal XML (YML) feed https://demo.ocmodules.in.ua/index.php?route=dropship/finance — balance, top-ups, payouts, and financial journal https://demo.ocmodules.in.ua/index.php?route=dropship/notify — Telegram, email, and event type settings You must sign in with an approved partner account to view the working pages.
Security and data separation
All orders, finances, feeds, and notifications are linked to the internal partner_id A partner cannot view another partner's data Deleting a partner does not assign their previous orders to a new account Financial operations use a separate transaction journal Reprocessing a status does not duplicate deductions or accruals CRON is protected by a secret key Access to administration pages is controlled by the standard access and modify permissions Performance
Static XML files instead of generation on every request Batch processing of queued products Resume generation from the last processed product Use of the PHP time limit with a safety margin before process termination Selection of only the fields required for a particular feed Dedicated table indexes for partners, orders, finances, and the feed queue Preservation of the previous working file until the new generation completes successfully Support for catalogs containing tens of thousands of products Open source code and independence
The module code is not encoded or obfuscated. PHP, Twig, JavaScript, and XML files are available for viewing and editing.
The module does not use a license server, hidden telemetry, or remote libraries. Core calculations, orders, financial accounting, and feed generation are performed directly on the website.
External connections are made only for channels explicitly configured by the administrator: the Telegram bot, SMTP, and retrieval of static files by an external import system.
Theme compatibility
The module's customer-facing pages are adapted for the standard OpenCart theme. Third-party themes can use a different HTML structure, CSS classes, grid, and form styling, so the partner cabinet pages require a separate theme adaptation to display correctly.
Theme adaptation is not included in the base module package and is performed separately for the specific theme used by the store.
System requirements
MySQL or MariaDB Configured store base currency Completed product.cost values Write access for static XML files Ability to configure a recurring CRON task Telegram bot token for Telegram notifications Configured Mail or SMTP for email notifications Installation
Perform a clean installation of the main package through Extensions / Installer Go to Extensions / Modifications and refresh the modification cache Go to Extensions / Extensions Select the Modules extension type Find Dropship Partner Cabinet and click Install Open the settings and enable the module Select the partner customer group Configure minimum markups Configure order statuses Create delivery and payment methods Enter the store's payment details Configure Telegram and the email transport Add the CRON URL to the scheduler If needed, install the Dropshipping Cabinet Navigation module in the required layout position Uninstalling the module
Disabling the module does not delete partners, orders, financial history, or feed files.
A complete uninstall removes the module's own tables, events, and generated static feed files. Partners are returned to their original customer groups before removal.
The product.cost column is not removed because it may be used by other cost price modules.
We recommend creating a database backup before uninstalling the module from a live store.
Important notes
The module does not perform automatic bank transfers and does not connect to a payment system. Top-ups and payouts are reviewed and approved manually by the administrator.
For correct financial accounting, do not edit the module's own database tables manually. Balance, reserved funds, delivery costs, and commission earnings must be changed through the provided pages and statuses.
Products without a cost price cannot participate in partner calculations. Before launching the partner program, product.cost must be completed for the available catalog.
A recurring CRON task is required to update feeds automatically and process deferred notifications. The execution frequency depends on catalog activity and the number of partner feeds.
Theme compatibility
The module's customer-facing pages are adapted for the standard OpenCart theme. Third-party themes can use a different HTML structure, CSS classes, grid, and form styling, so the partner cabinet pages require a separate theme adaptation to display correctly.
Theme adaptation is not included in the base module package and is performed separately for the specific theme used by the store.
DEMO
Admin Page login/password: demo/demodemo Store Page login/password: [email protected]/demodemo License
The license covers one domain and its subdomains.
Each partner receives a dedicated workspace where they can create orders for their customers, select a financial model, manage personal feeds, submit balance top-up and payout requests, review the financial journal, and configure notifications.
The administrator manages partners, available products, minimum markups, delivery and payment methods, order statuses, balances, payouts, the feed queue, and notification channels. Every financial change is recorded in a separate journal.
How the module works
A customer registers on the website and applies to join the partner program The administrator reviews the application, configures personal terms, and approves the partner The partner receives access to a dedicated dropshipping cabinet Partner prices are calculated from the product cost price and the administrator's minimum markup The partner can create orders for their customers without using the theme's standard cart Each order is created as a complete OpenCart order and appears in the standard administration area Financial operations follow the selected model: buyout / prepayment or commission sales The partner can create static product XML (YML) feeds with personalized prices Order, payout, top-up, and feed statuses can be sent by email or Telegram Module features
Accept applications to join the partner program Create partners manually in the administration area Move approved partners to a dedicated customer group Store the original customer group and restore it after a partner is blocked or deleted Set global and personal minimum markups Create markup rules for individual products, categories, and manufacturers Support percentage and fixed markups Create dropshipping orders through a dedicated form Work with the buyout / prepayment model Work with the commission model Track balance, reserved funds, pending earnings, and the amount available for payout Account for outbound and return delivery Create balance top-up requests Create payout requests Record every change in the financial journal Create multiple personal feed profiles for one partner Generate static XML (YML) feeds compatible with Prom.ua import Select feed language, currency, products, categories, manufacturers, and fields Map store categories to marketplace categories through portal_category_id Generate full feeds for initial import and compact feeds for fast price and stock updates Generate feeds manually or through a protected CRON task Send notifications through Telegram, email, or both channels Show administrators new applications, orders, payouts, top-ups, and feed errors Support Ukrainian, English, and Russian Dropshipping partner registration
A partner is a regular registered store customer for whom a separate partner profile is created. When applying, the customer provides:
Store name Store URL Contact email address Phone number in international format The administrator can approve, reject, or block an application. Only a partner with the Approved status receives access to the working sections.
After approval, the module moves the customer to the configured dropshipping customer group. The original group is remembered and restored after the partner is blocked, rejected, or deleted.
The administrator can also create a partner manually for an existing customer account.
Partner details
In the cabinet, the partner can edit their contact and payment details:
Store name Store URL Contact email address Phone number Payout recipient Tax ID / Company registration number IBAN The partner can see their unique ID. It can be included in a payment reference so the administrator can reliably identify the payer when processing a balance top-up.
Cost price
All calculations are based on the product cost price stored in product.cost. The modification adds a cost price field to the standard product editing form.
If the cost column has already been created by another purchase price module, Dropship Partner Cabinet uses the existing field. The cost column is not removed when this module is uninstalled.
A product with a zero cost price cannot participate in partner sales and is not exported to personal feeds.
Minimum markup rules
The administrator defines the minimum price below which a partner cannot sell a product. The calculation starts with the cost price.
Example: the cost price is 1,000 and the administrator's minimum markup is 5%. The partner's settlement price is 1,050.
The module supports:
A global minimum markup for all partners A personal minimum markup for an individual partner Rules for a specific product Rules for a category Rules for a manufacturer Percentage markup Fixed amount Rule priority:
Individual product Category Manufacturer Partner's personal markup Module's global markup If a product belongs to several categories with different rules, the rule that produces the highest final price is used.
Priority example: the manufacturer markup is 5%, the category markup is 8%, and a fixed amount of 150 is assigned to the product. For a product with a cost price of 1,000, the product rule takes priority and the settlement price is 1,150.
Creating orders
The partner creates orders through a dedicated cabinet form. The theme's standard cart and checkout are not used.
The partner selects a financial model Finds a product by name, model, or SKU Adds products to the order table Specifies the required quantity Sets their own selling price when needed Enters the actual recipient's details Selects a delivery and payment method Creates the order Autocomplete shows current product availability. Out-of-stock products are not hidden, but are clearly marked as unavailable. A quantity exceeding the available stock cannot be added.
The created order is compatible with the standard OpenCart order system. The partner remains the customer in the standard order, while the delivery details belong to the actual recipient.
Buyout / prepayment financial model
This model is suitable when the partner has already received payment from the buyer and must pay the store the settlement cost of the products.
Example:
Cost price — 1,000 Store's minimum markup — 5% Settlement amount — 1,050 Partner's selling price — 1,260 When the order is created, 1,050 is reserved on the partner's balance. After successful completion, the reserved amount is permanently deducted.
If the available balance is insufficient, the order is still saved but receives the financial status Insufficient funds — awaiting top-up. The administrator sees a warning and should not process the order until the balance has been replenished.
After a top-up, setting a processing status again attempts to create the reserve. The order cannot be completed without successfully reserving the settlement amount.
Commission financial model
The commission model is used when the store receives payment directly from the recipient and the partner earns the difference between the selling price and the settlement amount.
Example:
Store settlement amount — 1,050 Recipient's selling price — 1,260 Partner earnings — 210 After the order is handed over to the delivery service, 210 is recorded as pending earnings. Once the order is successfully completed, this amount becomes available for payout.
No advance balance top-up is required for a commission order. If the order is cancelled or returned, pending or already confirmed earnings are reversed.
Order statuses
The administrator maps OpenCart statuses to the processing stages of dropshipping orders:
Initial status — a new order that has not yet entered processing Order accepted for processing — the administrator has started assembling the order Handed over to delivery service — the shipment has been given to the carrier Order completed — the recipient has received the order Order cancelled — the order was cancelled or the shipment was returned Several OpenCart statuses can be assigned to one financial action. The same status cannot be used for different stages at the same time.
Reapplying the same status does not create duplicate reservations, deductions, or accruals. The module checks the order's current financial state before every operation.
The partner can see the order status history, dates, and administrator comments in the cabinet.
Recipient and delivery field builder
The administrator can create a custom set of order form fields and separate fields for every delivery method.
The following settings are available for every field:
Technical code Name in all store languages Field type Order field where the value will be stored Required status Status Sort order Regular text fields, multiline fields, a country list, and a dependent region / state list are supported.
Countries and regions are loaded from the store's local database. After a country is selected, the partner receives the corresponding list of regions.
Values from several fields can be directed to shipping_address_1 or shipping_address_2. The module combines them into a readable value with localized field names.
Example: “Street: Heroiv, Building: 22, Apartment: 3”.
Delivery and payment methods
The administrator creates the delivery methods and recipient payment methods available to partners.
Each delivery method has:
A technical code, for example dropship.novapost A name in all store languages Status Sort order A custom set of fields Courier delivery can request a city, street, building, and apartment. Branch delivery can request a city and branch number. Parcel locker delivery can request a city and locker number.
The technical delivery code is stored in shipping_code and the localized name in shipping_method. The payment code is stored in payment_code and its name in payment_method.
Outbound and return delivery
For every order, the administrator separately specifies:
Who pays for delivery Actual outbound delivery cost Delivery comment Return delivery cost Return comment If a successful delivery is paid by the recipient, its cost is not deducted from the partner's balance. If the partner pays for delivery, the actual amount is deducted from their balance.
If a shipment is returned, both outbound and return delivery costs are charged to the partner regardless of who was initially selected as the payer.
Before setting the shipped or completed status, the administrator must confirm the outbound delivery cost, even if it is zero. Cancellation requires separate confirmation of both outbound and return delivery.
Balance and reserved funds
The financial system separates several indicators:
Balance — the partner's own funds Reserved funds — funds reserved for buyout orders Pending earnings — income from commission orders that have not yet been completed Available for payout — confirmed income from completed commission orders The amount available for payout includes the free balance not currently reserved and confirmed commission earnings.
The administrator can manually credit or debit a partner's balance. The adjustment reason is saved in the financial journal and can be sent to the partner as a notification.
Balance top-ups
The administrator enters the store's payment details in the module settings:
Payment recipient Tax ID / Company registration number IBAN Support phone numbers Support email address The partner sees these details in the cabinet, makes a payment, and submits a top-up request. The request includes the amount and information the administrator can use to locate the payment.
The administrator verifies receipt and approves or rejects the request. The balance increases only after manual approval.
Partner payouts
A partner can submit a payout request for an amount that does not exceed their free balance and confirmed earnings.
To submit a request, the partner must provide:
Recipient Tax ID / Company registration number IBAN Funds are not transferred automatically. The administrator reviews the request, makes the payment manually, and assigns a status:
Pending Paid Rejected If a pending request is rejected or deleted, the amount reserved for payout is returned to the partner.
Financial journal
Every financial operation is recorded in a separate journal:
Reserving funds for an order Deducting the settlement amount Releasing a reserve Refunding product cost Deducting outbound delivery Deducting return delivery Accruing pending earnings Confirming commission earnings Balance top-up Payout Manual administrator adjustment For order-related operations, the order number and a link to the order are displayed. The journal shows changes to the balance, reserved funds, pending earnings, amount available for payout, and the comment.
Personal XML (YML) feeds
Every approved partner can create personal static product feeds. The maximum number of profiles is set globally by the administrator or individually for a particular partner.
A feed profile contains:
Custom name Language Currency Product availability mode Categories Manufacturers Additional markup Personal markup rules XML (YML) field set The partner can export:
All products Only in-stock products Only out-of-stock products The administrator can restrict the categories and manufacturers that partners are allowed to use in their feeds.
XML (YML) feed fields
The partner independently selects the data to export:
Product name Category Description Price Stock quantity Product URL Main and additional images Manufacturer Model SKU Attributes Weight Dimensions GTIN MPN The offer identifier and availability flag are always generated. The field used as the offer ID is selected by the administrator in the module settings.
The full field set is suitable for the initial product import. A compact feed containing, for example, only price and stock can be used to update an already imported catalog quickly.
Feed language and currency
For each profile, the partner selects one of the active store languages. Product names, descriptions, categories, and attributes entered in that language are included in the feed.
The module does not translate content automatically. If catalog data has not been entered in the required language, it cannot be generated automatically in the feed.
Prices are converted to one of the store's active currencies. The selected currency code is passed in currencyId.
Prom.ua categories
A numeric Prom.ua marketplace category ID can be specified for every store category. When filled in, the module exports it in the portal_category_id tag.
This maps the store's own catalog structure to marketplace categories without changing the categories in the store.
Feed markups
The feed's additional markup is applied after the administrator's minimum price.
Example:
Cost price — 1,000 Administrator's minimum markup — 5% Settlement price — 1,050 Feed's own markup — 20% Feed price — 1,260 The profile markup can be overridden for a specific product, category, or manufacturer. Personal feed rule priority is: product, category, manufacturer, then the profile's global markup.
Static files and CRON
Feeds are generated as static XML files. Requests from an external system to a feed URL do not run heavy SQL queries or rebuild the catalog in real time.
A partner can manually add their feed to the update queue The feed URL remains unchanged after regeneration A product, price, or stock change queues related feeds without deleting the previous file While a new version is generated, the previous successful file and its URL remain available Feeds are processed in batches Each CRON call uses the available PHP execution time and keeps a safety margin before the server limit When the time limit is reached, the next call resumes from the last processed product Notifications
The partner can select a notification channel:
Telegram Email All channels Available event types:
Order status change Feed generated successfully Feed generation error Payout status change Balance adjustment Top-up request status change Payout and top-up messages include the operation amount, new status, and administrator comment.
For Telegram, the administrator enters the bot token and each partner enters their own Chat ID. A separate Mail or SMTP transport can be configured independently of the store's main email settings.
Administration area
After installation, a dedicated dropshipping cabinet section appears in the administration area's left menu.
Administrators have access to:
General settings Partner list Adding and editing partners Dropshipping orders Payout requests Top-up requests Financial journals Feed list and queue Delivery and payment settings Order status settings Telegram and email settings Complete built-in documentation The administration header notification widget shows:
New partner applications New dropshipping orders Top-up requests Payout requests Feeds with errors The standard OpenCart order page displays a dedicated label linking to the dropshipping order and showing its financial status.
Dropshipping cabinet pages
The demo cabinet contains the following pages:
https://demo.ocmodules.in.ua/index.php?route=dropship/dropship — dashboard with financial indicators and quick links https://demo.ocmodules.in.ua/index.php?route=dropship/account — partner store, contacts, and banking details https://demo.ocmodules.in.ua/index.php?route=dropship/order — list of orders created by the partner https://demo.ocmodules.in.ua/index.php?route=dropship/order/create — dedicated form for creating an order for a recipient https://demo.ocmodules.in.ua/index.php?route=dropship/feed — profile list, generation statuses, and static URLs https://demo.ocmodules.in.ua/index.php?route=dropship/feed/add — create a personal XML (YML) feed https://demo.ocmodules.in.ua/index.php?route=dropship/finance — balance, top-ups, payouts, and financial journal https://demo.ocmodules.in.ua/index.php?route=dropship/notify — Telegram, email, and event type settings You must sign in with an approved partner account to view the working pages.
Security and data separation
All orders, finances, feeds, and notifications are linked to the internal partner_id A partner cannot view another partner's data Deleting a partner does not assign their previous orders to a new account Financial operations use a separate transaction journal Reprocessing a status does not duplicate deductions or accruals CRON is protected by a secret key Access to administration pages is controlled by the standard access and modify permissions Performance
Static XML files instead of generation on every request Batch processing of queued products Resume generation from the last processed product Use of the PHP time limit with a safety margin before process termination Selection of only the fields required for a particular feed Dedicated table indexes for partners, orders, finances, and the feed queue Preservation of the previous working file until the new generation completes successfully Support for catalogs containing tens of thousands of products Open source code and independence
The module code is not encoded or obfuscated. PHP, Twig, JavaScript, and XML files are available for viewing and editing.
The module does not use a license server, hidden telemetry, or remote libraries. Core calculations, orders, financial accounting, and feed generation are performed directly on the website.
External connections are made only for channels explicitly configured by the administrator: the Telegram bot, SMTP, and retrieval of static files by an external import system.
Theme compatibility
The module's customer-facing pages are adapted for the standard OpenCart theme. Third-party themes can use a different HTML structure, CSS classes, grid, and form styling, so the partner cabinet pages require a separate theme adaptation to display correctly.
Theme adaptation is not included in the base module package and is performed separately for the specific theme used by the store.
System requirements
MySQL or MariaDB Configured store base currency Completed product.cost values Write access for static XML files Ability to configure a recurring CRON task Telegram bot token for Telegram notifications Configured Mail or SMTP for email notifications Installation
Perform a clean installation of the main package through Extensions / Installer Go to Extensions / Modifications and refresh the modification cache Go to Extensions / Extensions Select the Modules extension type Find Dropship Partner Cabinet and click Install Open the settings and enable the module Select the partner customer group Configure minimum markups Configure order statuses Create delivery and payment methods Enter the store's payment details Configure Telegram and the email transport Add the CRON URL to the scheduler If needed, install the Dropshipping Cabinet Navigation module in the required layout position Uninstalling the module
Disabling the module does not delete partners, orders, financial history, or feed files.
A complete uninstall removes the module's own tables, events, and generated static feed files. Partners are returned to their original customer groups before removal.
The product.cost column is not removed because it may be used by other cost price modules.
We recommend creating a database backup before uninstalling the module from a live store.
Important notes
The module does not perform automatic bank transfers and does not connect to a payment system. Top-ups and payouts are reviewed and approved manually by the administrator.
For correct financial accounting, do not edit the module's own database tables manually. Balance, reserved funds, delivery costs, and commission earnings must be changed through the provided pages and statuses.
Products without a cost price cannot participate in partner calculations. Before launching the partner program, product.cost must be completed for the available catalog.
A recurring CRON task is required to update feeds automatically and process deferred notifications. The execution frequency depends on catalog activity and the number of partner feeds.
Theme compatibility
The module's customer-facing pages are adapted for the standard OpenCart theme. Third-party themes can use a different HTML structure, CSS classes, grid, and form styling, so the partner cabinet pages require a separate theme adaptation to display correctly.
Theme adaptation is not included in the base module package and is performed separately for the specific theme used by the store.
DEMO
Admin Page login/password: demo/demodemo Store Page login/password: [email protected]/demodemo License
The license covers one domain and its subdomains.
Updated
Dropship Partner Cabinet
5,900грн
4,100 грн
0 1
This module allows users to independently delete their account from the customer dashboard, without administrator involvement.
This functionality complies with modern personal data protection requirements.
Key Features
Adds a new "Account Deletion" section to the customer account. Requires confirmation (entering a keyword) to avoid accidental deletion. Upon confirmation, the module permanently deletes the customer and all related personal data from the database. Supports multi-store and is compatible with OpenCart 3.x. Added link to Account module What is Deleted
When a customer deletes their account, the module removes all related data from the following tables:
customer — main account information. customer_activity — activity history. customer_affiliate — affiliate data. customer_approval — account approval status. customer_history — account history. customer_reward — reward points. customer_transaction — transactions and balance. customer_ip — login IP addresses. address — all saved addresses. If needed, you can extend the functionality by editing the model file.
Benefits
Simple installation via the built-in extension installer. Increases customer trust. Helps meet legal and privacy requirements. Compatible with most OpenCart themes. Distribution Terms
This modifier is provided "as is".
The author takes no responsibility for any consequences of its use.
It is strongly recommended to create a backup before installation.
Template Adaptation
The module comes with basic layout designed for the default OpenCart theme.
If you are using a third-party theme, template adaptation is a paid service.
The account deletion page is available at
https://yourdomain.com/index.php?route=account/delete
Replace yourdomain.com with your store’s domain.
This functionality complies with modern personal data protection requirements.
Key Features
Adds a new "Account Deletion" section to the customer account. Requires confirmation (entering a keyword) to avoid accidental deletion. Upon confirmation, the module permanently deletes the customer and all related personal data from the database. Supports multi-store and is compatible with OpenCart 3.x. Added link to Account module What is Deleted
When a customer deletes their account, the module removes all related data from the following tables:
customer — main account information. customer_activity — activity history. customer_affiliate — affiliate data. customer_approval — account approval status. customer_history — account history. customer_reward — reward points. customer_transaction — transactions and balance. customer_ip — login IP addresses. address — all saved addresses. If needed, you can extend the functionality by editing the model file.
Benefits
Simple installation via the built-in extension installer. Increases customer trust. Helps meet legal and privacy requirements. Compatible with most OpenCart themes. Distribution Terms
This modifier is provided "as is".
The author takes no responsibility for any consequences of its use.
It is strongly recommended to create a backup before installation.
Template Adaptation
The module comes with basic layout designed for the default OpenCart theme.
If you are using a third-party theme, template adaptation is a paid service.
The account deletion page is available at
https://yourdomain.com/index.php?route=account/delete
Replace yourdomain.com with your store’s domain.
Updated
Delete account
Free
33
The Content Popup module is designed to create popup windows with tabs that can be attached to products in your online store.
It allows you to display additional information in a convenient and visual way — such as size charts, care instructions, delivery and payment terms, warranty details, promotions, and much more.
The module supports bulk assignment by selected categories and manufacturers.
Main Features:
Create popup windows with tabbed content. Unlimited number of content tabs. Bulk add content to product groups by selected categories and manufacturers. Multilingual support. Ability to insert images, tables, text, and HTML content into tabs. Display popup trigger button on the product page. Example Use Cases:
Size chart — add a tab with size tables for different brands or categories. Care instructions — provide helpful product care information. Delivery and payment info — show details without leaving the product page. Promotions, warranty, or certificate information. Benefits:
Improves user experience — customers get all the necessary info without reloading the page. Reduces customer inquiries (especially about sizes and shipping terms). Flexible content assignment — easily update information for many products at once. Theme Compatibility:
default Adaptation for other themes is paid. Please contact before purchase!
Installation:
Upload the module archive via Extensions → Installer. Upload the theme adaptation archive via Extensions → Installer. Refresh modification cache (Extensions → Modifications → Refresh). Go to Extensions → Modules → Content Popup and click Install. Configure the module. After saving settings, always click "Add content to products". Template Compatibility:
The extension is compatible with the default template. Adaptation is required for other templates (paid adaptation).
DEMO
Admin Page login/password: demo/demodemo Store Page License:
Use is allowed in one online store only.
It allows you to display additional information in a convenient and visual way — such as size charts, care instructions, delivery and payment terms, warranty details, promotions, and much more.
The module supports bulk assignment by selected categories and manufacturers.
Main Features:
Create popup windows with tabbed content. Unlimited number of content tabs. Bulk add content to product groups by selected categories and manufacturers. Multilingual support. Ability to insert images, tables, text, and HTML content into tabs. Display popup trigger button on the product page. Example Use Cases:
Size chart — add a tab with size tables for different brands or categories. Care instructions — provide helpful product care information. Delivery and payment info — show details without leaving the product page. Promotions, warranty, or certificate information. Benefits:
Improves user experience — customers get all the necessary info without reloading the page. Reduces customer inquiries (especially about sizes and shipping terms). Flexible content assignment — easily update information for many products at once. Theme Compatibility:
default Adaptation for other themes is paid. Please contact before purchase!
Installation:
Upload the module archive via Extensions → Installer. Upload the theme adaptation archive via Extensions → Installer. Refresh modification cache (Extensions → Modifications → Refresh). Go to Extensions → Modules → Content Popup and click Install. Configure the module. After saving settings, always click "Add content to products". Template Compatibility:
The extension is compatible with the default template. Adaptation is required for other templates (paid adaptation).
DEMO
Admin Page login/password: demo/demodemo Store Page License:
Use is allowed in one online store only.
Updated
Content Popup
460грн
320 грн
0 9
This module automatically updates currency exchange rates in an OpenCart based online store using the official PrivatBank API. It supports correct price recalculation according to OpenCart’s internal logic and allows you to choose whether to use the buying or selling rate.
Module Features
Automatic currency rate updates via the PrivatBank API Support for buy and sell exchange rates Correct price recalculation in OpenCart Exchange rate updates via CRON User-friendly settings in the admin panel Supported Currencies
UAH (Ukrainian hryvnia) USD (US dollar) EUR (euro) (and other currencies available via the PrivatBank API) Requirements
cURL enabled Compatibility
OpenCart 3.x Installation
Install the module via the OpenCart admin panel Refresh the modifications Configure the module Set the currency rate provider in the store settings DEMO
Admin Page login/password: demo/demodemo License
Unlimited domains
Module Features
Automatic currency rate updates via the PrivatBank API Support for buy and sell exchange rates Correct price recalculation in OpenCart Exchange rate updates via CRON User-friendly settings in the admin panel Supported Currencies
UAH (Ukrainian hryvnia) USD (US dollar) EUR (euro) (and other currencies available via the PrivatBank API) Requirements
cURL enabled Compatibility
OpenCart 3.x Installation
Install the module via the OpenCart admin panel Refresh the modifications Configure the module Set the currency rate provider in the store settings DEMO
Admin Page login/password: demo/demodemo License
Unlimited domains
Updated
Курси валют ПриватБанку
Free
25