User Feedback
OcBox AI Remarketing & Advanced Analytics — every OpenCart analytics and remarketing tool rolled into one module
|
Ads and analytics · OcBox team
Ads eating your budget with too few orders?
Our paid-ads specialist Kristina will set up and fine-tune your Google Ads and Meta campaigns and wire up GA4 so every dollar you spend comes back as orders. Hundreds of e-commerce projects behind her, real numbers instead of guesswork.
|
The $40 price includes one year of updates from the OcBox Team. License renewal after that is $40 per year. Turnkey installation is a separate $40 service. The license covers the shop domain and a test domain.
Thanks to everyone who helped with development and testing
This module grew on the live stores of our alpha testers: your bug reports, screenshots from ad managers and feedback in the support topic over the past months are what turned it into what it is now. Everyone who really helped (tested, reported what did not work, showed conflicts with other modules, suggested needed features) — gets a lifetime free license for this module. Just send a private message to OcBox, remind us who you are and how you helped, and we issue a license for your domain, no questions asked. Thank you!
Every ad pixel, server-side conversion API, GDPR consent layer, Google product feed, UTM reports, Telegram notifications and AI helpers — in one module, from one admin tab. Fill in the IDs and tokens once, and every store event (product view, cart, checkout, purchase, search, sign-up) fires into your ad platforms automatically, with client+server deduplication, proper currency and complete product data. One payment, no monthly subscriptions, no lock-in to third-party services.
🔒 Your data, yours alone. No hidden back-doors
Everything the module collects goes exclusively into YOUR advertising and analytics accounts (Google Analytics 4, Google Ads, Meta Pixel, TikTok, Pinterest, Snapchat, X, Bing UET, Criteo, Hotjar, Clarity), which you connected yourself with your own IDs and tokens. The module does not phone home to the developer and collects nothing "for the author". No OcBox pixel, no background request, no server-side send fires to our domains, apart from the license check on your domain (with no shopper data, no orders, no traffic — only "valid domain, yes/no").
There is no hidden code in the module that would siphon your traffic, customers or orders somewhere else. Yes, the code is ionCube-compiled, but solely to protect the license (domain binding, as with any professional paid product), not to hide anything from you. Unlike some solutions on the market that quietly leak your order list or traffic to a third-party author's backend, here it is all transparent: data flies where you told it to in settings, and nowhere else. We are happy to walk any client through the full list of the module's outbound requests via the browser network inspector or a server-side tcpdump.
🤖 AI capabilities
The module ships with two AI helpers that do two distinct jobs: one helps you with setup, the other watches your reports and points out where to look:
1. AI setup assistant
Walks you through connecting GA4, Meta Pixel, Google Ads, TikTok, Pinterest, Snapchat, X (Twitter), Microsoft UET, Criteo and the rest of the pixels step by step. Verifies that you correctly entered the Measurement ID, Access Token, Pixel ID and CAPI token; drops a link telling you where in the Google / Meta / TikTok admin to grab the ID you need; warns you when a server token is missing or when an event is formally enabled but not actually firing (for example because the conversion label is missing or the visitor's consent is blocking that channel). A newcomer who has never touched Consent Mode v2 or the Conversions API will not get lost — they can stand up the store's entire marketing stack from zero in 15 minutes.
2. AI report analysis (insights)
The module watches your data itself and flags things you personally would not have noticed: a sharp drop in sales from the "Facebook Ads" source vs. last week, a spike in Direct with no matching UTMs (a tag has fallen off somewhere), a top product dropping out of the top ten, a change in average order value, odd behaviour from a new traffic source, a hole in the funnel at a specific checkout step. It compares the chosen period against the previous equal-length one and, in plain language (no charts you still have to interpret), points at what to look at: check a specific campaign's settings, promote a specific product higher in its category, adjust bids, fix a broken tag in that newsletter.
Both helpers run on your OpenAI key — you can paste it directly into the module in a dedicated field, or the shared store-wide key from other OcBox modules (AI Chat, AI Product Editor, SEO FAQ AI, AI Photo Studio) is picked up automatically. The key is stored encrypted with the store key. Only anonymised numbers and setting flags are sent to the model — no shopper data, no order numbers, no email, no phone, no addresses.
What you get — in detail
This is not a marketing blurb but a working checklist of everything the module actually does. Each part is turned on separately, so you decide which pixels and features to enable.
Google Analytics 4 — client-side gtag plus server-side sending
You enter a Measurement ID (G-XXXXXXXXXX) and, optionally, an API Secret, and the module takes it from there: gtag.js drops onto every page, and the same events fly in parallel over Measurement Protocol straight from your server. The full set of store events, view_item, view_item_list, add_to_cart, view_cart, begin_checkout, add_shipping_info, add_payment_info, purchase, search, sign_up, is built in the exact shape GA4 expects, with the proper ecommerce.items, currency, brand, and positions. Each item in an event carries everything GA4 wants: id, name, brand, up to five category levels, the chosen variant (colour, size), the price after discount, the discount itself in money, the applied coupon code, quantity, and the store domain. Empty fields are not sent, so the reports stay clean. A "Send test event" button verifies the wiring in a second and results show up in DebugView, and tracking is enabled by default right after install so you do not have to open settings to turn it on.
The server path running alongside the client path is not cosmetic: modern ad blockers strip up to half of client-side events, and without the server dupe GA4 conversions dip, reports start to lie, and the Google Ads campaign optimiser learns on incomplete data, which skews bids.
Google Ads — conversions plus remarketing with no template edits
Google Ads is wired up from the same tab. You enter a Conversion ID (AW-XXXXXXXXX), conversion labels in the purchase=LABEL format, and flip the remarketing switch on. From then on the module sends every completed purchase to Google Ads with the correct amount and currency for that specific order, and builds a remarketing audience out of product-page visits. Events are deduplicated by event_id, so Smart Bidding gets a clean signal rather than doubled purchases. Without this, Google Ads never sees the real conversions, the bidding algorithm never learns, cost per acquisition climbs, and return on ad spend sinks.
Meta Pixel — Facebook and Instagram, with Conversions API
Meta comes in as a pair: the client fbq pixel and the server Conversions API, both firing the same events with a shared event_id. You just drop Pixel ID and Access Token into the "Meta" tab, and Meta collapses the duplicates on its side, so the Ads Manager report counts every purchase exactly once even when the shopper is on an ad blocker. Test Event Code for live checks is supported, and the Access Token is stored in the database encrypted with the store key and decrypted only at the moment of the API call. After iOS 14, ATT and modern ad blockers, Facebook without the server half misses 30-50% of conversions and purchase-optimised campaigns stall on "insufficient data", so the server CAPI here is not a bonus but a precondition for them to keep running.
TikTok — pixel plus Events API
TikTok follows the same pattern. You paste a Pixel ID and Access Token from TikTok Events Manager, and the module fires ViewContent, AddToCart, InitiateCheckout, PlaceAnOrder, CompletePayment, and the rest from client and server at the same time. The "Test event" button verifies the link and lets you see the event live in TikTok Test Events. Without it, TikTok ads burn budget blind because the purchase optimiser has no signal and keeps spending on cold audiences that do not buy.
Pinterest, X (Twitter), Snapchat, Microsoft UET (Bing), Criteo — every pixel in one place
Five smaller ad networks live together on a single "Other pixels" tab. You enter your IDs (Pinterest Tag ID, X Pixel, Snapchat Pixel, Microsoft UET, Criteo Partner ID and Account ID), and each pixel is injected into the storefront with the correct standard events. The format of every ID is validated right in the form, so if you paste the wrong thing the field highlights immediately. Criteo gets exactly the event names OneTag expects: viewHome, viewList, viewItem, viewBasket, trackTransaction. Without this, Pinterest, Snapchat, Bing and Criteo remarketing starts from an empty audience and takes months to warm up instead of being productive within weeks.
Hotjar and Microsoft Clarity — heatmaps and session recording
Heatmaps and session recordings come up in a few seconds. Paste in a Hotjar Site ID and a Clarity Project ID, and the module injects both scripts onto every page of the store. A few hours later you have a real picture of where people click, where they abandon carts, which buttons no one notices. Microsoft Clarity is fully free and surfaces sessions almost in real time. Without this layer, the store is optimised on hunches, and conversations with the designer turn into "I think this would look better" instead of simply opening a real recording and watching what the shopper actually does.
Google Consent Mode v2 + cookie banner — GDPR without a separate plugin
Google Consent Mode v2 and the cookie banner are built in, so there is no separate GDPR plugin to maintain. Until the visitor consents, ad storage stays in "denied", ad events do not fire, and GA4 runs in anonymous mode. The banner can sit at the bottom, the top, or the centre of the page, with "Accept all" and "Only necessary" buttons; the four consent categories (necessary, analytics, marketing, functional) are exposed separately, and every provider is pinned to its category. Server-side sending checks consent the same way: without it, the event simply does not go out. The "Accept all" button keeps working even on stores where another module breaks JS, because the handlers are self-contained, the cookie is written, the consent update is sent, and the banner closes regardless of foreign scripts. A "Cookie settings" trigger is always visible in the page corner so the shopper can change their choice at any time, and there is a separate "Strict opt-in" mode for jurisdictions that do not accept Consent Mode v2 and require full opt-in-first. Skip this and the path is straightforward: complaints, GDPR fines, plus Google since March 2024 discards a share of data in European reports from stores without Consent Mode v2.
"Data Layer only" mode — running through Google Tag Manager
If the store already lives on Google Tag Manager and you want GTM to manage all tags (GA4, Google Ads, Facebook, TikTok), the "Data Layer only" switch on the "Data Layer" tab flips that mode on. With it on, the module stops loading gtag.js by itself, stops duplicating pixel config in head, and stops sending its own server-side events to the networks. The dataLayer continues to be populated cleanly and in order, every entry carries an event_source: "ocbox" tag for quick diagnostics, and GTM takes it from there. If there is no GTM, the switch simply stays off and nothing changes in behaviour. Without this separation, the module and GTM fire the same tags in parallel, phantom x2 events show up in reports, and Tag Assistant starts throwing warnings about double firing.
UTM attribution — see which ad brought every order
UTM attribution works without an extra module. For every visitor the module remembers utm_source, utm_medium, utm_campaign, utm_term, utm_content, first and last referrer, and landing page, and attaches all of it to the completed order. The admin then shows exactly which campaign, ad, Instagram post, or email blast brought a specific order, rather than a vague "came from Google". The traffic source is frozen at the moment of order placement, so manually completing an order status later in the admin never overwrites it with Direct. Without this, you only ever see the top-level source (google, direct) and cannot tell which campaign actually made money and which one burned the budget.
Reports + CSV export + Conversion Paths — live statistics inside the admin
Live statistics sit right inside the admin, with no separate BI tool required. The "Dashboard" tab gathers period buttons ("Today", "Yesterday", "Last 7 days", "Last 30 days", "This month", "Last month", "Custom range" with "From" and "To" fields), tiles for "Total orders", "Total sum", and "Average order value", a "Traffic sources with sales" table, and a "Conversion paths" block with a paginated per-order view showing customer name, product name, sum, and the chain of sources leading up to the purchase. Navigation includes "First / Last / Page NNN → Go", and the whole selection dumps out via a "CSV Export" button that opens in Excel with the same filters applied. Without this, stock OpenCart has no source reports at all, and hand-merging Google, Meta and TikTok in Excel every month becomes a job on its own.
Built-in tracking self-check — proves everything works
A tracking self-check is baked into the module to prove that all these gears are actually turning. On the "AI Assistant" tab you hit "Start check" and walk the store the way a shopper would: category, product, add to cart, checkout, test order. Come back to the module, and a table shows one row per stage (category list view, product view, add to cart, begin checkout, add shipping, add payment, purchase), each row telling you whether the event was captured, whether it fired exactly once (green "OK"), whether it doubled up (yellow "Duplicate"), and whether it carried valid data (currency, sum, item count, order id). The source of each event is shown too: dataLayer, client pixel, or server-side send. If something fell off, the module tells you exactly at which step to look. Capture auto-turns-off after 30 minutes and no shopper PII is ever written. Without this, the whole setup rests on faith: you configure everything and have no way to confirm that GA4 and Meta really receive the right events with the right data.
Conflict detector — warns when another module fires the same events
When another tracker lives on the same page, the module notices it for you. It watches the client-side dataLayer and, if it sees view_item, add_to_cart, view_cart, begin_checkout, purchase and other e-commerce events sent by someone other than OcBox (another remarketing or analytics module running in parallel, for example), records it and raises a yellow warning on the "AI Assistant" tab listing the offending events with a suggestion: either enable "Data Layer only" or turn those same events off in the other module. When nothing conflicts, a clean green "no conflicts detected" tick shows instead. Without this watch, two modules fire the same purchases into GA4 and Facebook in parallel, reports show x2 conversions, and the ROAS optimiser drifts off reality.
AI setup assistant + AI insights in reports
Two separate AI services live inside the module. The "AI assistant" button sends OpenAI an anonymised snapshot of your config (which providers are on, whether server tokens are set, which events are active) and returns a plain-language read-out: what already works, what is missing, what to do next. A second button, "AI insights", on the Dashboard compares the chosen period to the previous one of equal length, spots anomalies (sales spikes or dips, changes in top products, a source behaving oddly) and produces a short takeaway with recommendations. The OpenAI key can be entered right in the module on the "AI Assistant" tab, or left empty, in which case the shared store-wide key from other OcBox modules (AI Chat, Product Editor) is picked up. The key is stored encrypted, and no customer data is sent, just numbers and flags. Without this, it is easy to make the classic launch mistake: you drop in a pixel, forget the Access Token, never notice that the server side is dead, and burn ad budget on blind tracking for months.
Google Merchant product feed — dynamic remarketing out of the box
A Google Merchant product feed is already inside the module, no separate extension to buy. It serves a ready XML with the full Merchant Center field set: id, title, description, up to ten additional images, price and sale_price with proper tax handling, availability (in_stock, preorder, backorder, out_of_stock), brand, GTIN, MPN, product_type, google_product_category, shipping with shipping_weight in the correct units, custom labels, and multipack. Build runs on a schedule in the background, writes atomically to a temp file, and swaps in as the current feed in a single move, so Google never reads a half-written XML. The public URL responds instantly, in milliseconds, even on a 30-50k product catalogue; a "Build now" button triggers a background rebuild on demand, the ready cron command is shown right on the settings page, and a "Feed build status" block shows when the last build ran, how many products went in, the file size, and the last build message. All of this is the foundation for Performance Max, Shopping campaigns, and Google Ads dynamic remarketing, because without a feed those have nothing to work with and you are left running text-only ads.
Google Customer Reviews — post-purchase survey and rating badge
Google Customer Reviews is wired in as well. You enter a Merchant ID and set an expected delivery window, and on the "Thank you for your order" page Google asks the customer to leave an opt-in review, while the site footer shows a badge with your average Google Customer Reviews rating. That is the real five-star icon from Google, not a third-party "bought a badge". Without it, your store has no Google merchant reviews at all, no yellow stars next to your listing in the SERP, and CTR predictably lags behind competitors who do.
Telegram notifications — new order and status change straight to chat (with group topic support)
Telegram notifications work without any external service in between. You create a bot with @BotFather, drop in the Bot Token, auto-detect the Chat ID with one click (you can list several comma-separated: your own, managers, a support group), and every new order lands in Telegram instantly, while status changes come through filtered by whichever statuses you picked. If your team works in a Telegram group split into forum topics, the Chat ID can be the group ID, a colon, and the topic ID (-1001234567890:42), and the message lands in the "Orders" topic rather than the general chat; formats can be mixed in the same comma-separated list. The message body is assembled from a template with macros like {order_id}, {customer_name}, {total}, {products}, and more. Without this, the familiar story plays out: the order arrives at night, you see it in the morning, and the customer has already moved on to a competitor who replied faster.
Custom scripts — drop in third-party tags with no template edits
Third-party tags go in without touching the theme. Need a Google domain verification tag, another chat widget, one more counter, or a pixel for a very niche network? The "Custom scripts" tab accepts all of them: pick a position (head, body-start, body-end), choose which pages to inject on, mark whether GDPR consent is required and under which category. Existing tags are not just add-or-delete; they are editable too, with the pencil icon next to the trash opening the same form with saved values. Without a place like this, every third-party tag ends up pasted into the theme by hand and vanishes or collides at the next theme update.
Client + server with dedup — accurate conversions in spite of ad blockers
Client and server work as a pair with the same event_id on every event, and the network counts each event exactly once. On top of that, purchase has its own safeguard: the module remembers every already-sent order so double-counting a purchase is impossible by construction. One shopper action yields exactly one event, even if the theme fires "Add to cart" twice via jQuery and modern fetch, because the module filters out the noise within a short window. Product data in every event is always complete (name, brand, price with sale and tax in the shopper's currency, quantity), with no zero prices and no empty brands, and the module converts amounts into the order currency so ROAS math works out. Without this layer, almost anything can go wrong: the client pixel loses half its events to ad blockers, client and server without a shared id double up, zero prices creep into reports, or every purchase suddenly fires twice, and sorting that out after the fact is expensive.
Custom checkout — Chameleon, quickcheckout and the like
Custom checkouts (Chameleon, quickcheckout, non-standard ocStore themes) are handled automatically. Most trackers only listen to the stock OpenCart checkout, so on custom themes the middle funnel steps simply vanish. Here the module recognises any checkout page by the presence of checkout in the URL and listens for shipping and payment changes both through classic form-urlencoded submits and through AJAX with a JSON body. The shipping_tier or payment_type field always carries the human-readable method name (for example, "Nova Poshta") instead of an internal code, and one method change yields exactly one event, even if the theme repaints the form several times. Without this, the GA4 "Cart → Checkout → Shipping → Payment → Purchase" funnel comes out with empty middle steps and the conversion math is wrong.
Secrets encryption — Access Tokens and API Secrets no one reads from the database
Every sensitive field in the database is encrypted. Meta Access Token, TikTok Access Token, GA4 API Secret and other secrets are not stored in plain text; OpenCart's built-in encryption uses the store key, and the values are decrypted only at the moment an API call is made. A dumped database without that key does not hand an attacker your ad account tokens. Flood protection on top of this works off the real visitor IP even behind Cloudflare and similar CDNs, so legitimate traffic is not clipped. Without this, a leaked database backup means every one of your ad accounts is leaked too, and someone else can run ads on your dollar.
Universality — works via OpenCart events, on any theme, OpenCart 2.3 and 3.x
No theme edits are required. Every pixel and script is injected via the module's own OCMOD, and this works on any theme (LuxShop, CyberStore, Chameleon, Prime, stock Default, anything else) automatically. Store event data flows through OpenCart's built-in events without rewriting controllers or templates, so updating the theme does not break the module. There are two separate builds: one for OpenCart 3.x (.twig files) and one for OpenCart 2.3 (.tpl files), pick the one for your branch. On OpenCart 2.3 the dataLayer, consent banner and events for product view, add-to-cart, checkout and payment all render in full, not only the server-side purchase logging. The classic "paste GA4 into header.tpl" approach breaks on every theme update or template swap, and that is exactly what this avoids.
Setup wizard — 15 minutes from zero to working tracking
For a first install there is a step-by-step wizard with "where to find each ID" hints. The "Setup wizard" button at the top of the module page walks you through the minimum useful set of steps: connect GA4, add Meta Pixel plus CAPI, TikTok, the consent banner, Telegram, a test event, and the tracking self-check. Once completed, the flag is remembered and the wizard does not pop up on its own, but the button changes to "Run the wizard again" so you can walk through it another time, for example after a module update or when adding another store into the same admin. Without this, a first-time setup drags on for days while you read Meta, TikTok and Google docs for each item in turn.
What this means in plain terms
Previously, to wire all of your marketing into an OpenCart store, you had to: paste GA4 into the theme, then Meta Pixel separately, then TikTok separately, then Google Ads, then figure out server-side (usually you didn't), install a separate Google Merchant feed module, install a separate Telegram module, wrestle with the GDPR banner on its own, merge UTMs into Excel by hand, and pay freelancers for the setup. OcBox AI Remarketing rolls all of that into a single admin tab. Fill in your IDs once, tick the boxes you want, walk the wizard, watch the self-check go green — and your store stops being blind to your ads.
Why OcBox over a typical analytics setup
A short side-by-side, without naming any specific competing developer or module. The left column is what OcBox AI Remarketing does out of the box; the middle column is the typical scenario where the same jobs are covered by separate modules from different authors (one per system); the right column is what stock OpenCart gives you with no add-ons at all.
| Capability | OcBox (our module) | Typical analytics module / separate modules | Stock OpenCart |
|---|---|---|---|
| GA4, Google Ads, Meta Pixel, TikTok, Pinterest, X, Snapchat, Bing UET, Criteo in a single module | ✅ | usually a separate module per platform | ❌ |
| 🤖 AI setup assistant: walks GA4, Google Ads, Meta, TikTok connection step by step, checks tokens and tells you what still doesn't work | ✅ | ❌ | ❌ |
| 🤖 AI insights on store reports: sales anomalies, changes in top products, traffic-source behavior, period-over-period comparison with recommendations | ✅ | ❌ | ❌ |
| Setup wizard (step-by-step GA4, pixels and consent connection, no manual code paste into the theme) | ✅ | ❌ (all by hand, paste codes into the theme template) | ❌ |
| Server-side tracking (GA4 Measurement Protocol, Meta CAPI, TikTok Events API) that bypasses ad-blockers | ✅ | partial, often client-side pixel only | ❌ |
| Google Consent Mode v2 + built-in cookie consent banner | ✅ | usually a separate consent module | ❌ |
| No event duplication: one shopper action = exactly one event (shared event_id client+server) | ✅ | partial, doubled views and purchases are a common issue | ❌ |
| Full GA4 e-commerce: cart, checkout steps, purchase with items, brand and totals | ✅ | partial, mid-funnel steps often lost on custom checkouts | ❌ |
| Google Merchant feed (XML for Google Shopping) with scheduled refresh | ✅ | usually a separate module | ❌ |
| Telegram order notifications, including into a specific group topic | ✅ | usually a separate module, without group topic support | ❌ |
| Built-in tracking self-check + conflict detector against other counters | ✅ | none | ❌ |
| Works on OpenCart 2.3 and 3.x, including custom checkout pages (Chameleon, quickcheckout and the like) | ✅ | partial, half-support for 2.3 or custom checkouts is common | ❌ |
| "Data Layer only" mode for Google Tag Manager when GTM owns the tags | ✅ | partial, module and GTM often duplicate the same tags | ❌ |
| Reports, conversion paths and UTM attribution right in the store admin | ✅ | partial, often Google Analytics only and not tied to actual orders | ❌ |
The wording "usually a separate module", "partial" and "none" refers to typical scenarios in the niche, not to a specific product from a specific author. Your particular module may cover one or another of these features to some degree; the point of the table is not to bash anyone, but to show how many different jobs a single OcBox module closes instead of a stack of separate ones.
Who this module is for
For any OpenCart or ocStore shop that has ever paid for Google Ads, Meta or TikTok advertising and noticed that the ad platform reports never match the real orders. Especially — for stores without a dedicated marketer, where the owner does everything and has no time to dig into the theme or fight Consent Mode. And especially for OpenCart 2.3 stores where other trackers often only run in half-mode.
Compatibility
The module runs on OpenCart 3.0 and ocStore 3.0, and equally on OpenCart 2.3 and ocStore 2.3: two separate builds, we compile the one you need for your branch. PHP 7.x to 8.x, MySQL 5.7+, any theme (stock Default, Cyberstore, Prime, Chameleon, LuxShop and any other). The ionCube compilation for your domain is done automatically after payment.
License renewal for updates
The module price includes one year of support from the OcBox Team. After 12 months from the purchase date the module keeps working; to keep receiving new versions you renew at $40/year. The annual fee covers new module versions. Recompilation for a new domain, on-server install, consultations and personal support are not included and are ordered separately.
How to buy and receive the module
There is no downloadable file on this listing page, it is a showcase for the module. The flow is simple: click "Buy" on this page and complete the purchase through the forum, or send a private message to OcBox. Once payment lands we confirm your working domain (and, optionally, a test one), generate a licensed ionCube build locked to your domain for one year, and give you download access to the module together with install instructions in three languages. For those who prefer not to install it themselves there is the "Installation and setup" service for $40 available as an option next to the module (we install it on your server via FTP/SSH, wire up GA4/Meta/TikTok from your IDs, enable the consent banner, and walk you through usage). One year of updates is included in the price.
Found a bug in the module?
Post in the support topic or send us a private message with a link to the page, what you did, what happened, and the error text. How to turn on error display, find the error log and see errors in the browser console in five minutes, step by step with screenshots: How to enable, find and report errors on an OpenCart site (article in Ukrainian). A report like that lets us fix the problem much faster.
Recommended paid OcBox modules
|
Smart Related $30: related products |
SEO FAQ AI $30: AI FAQ + Schema.org |
AI Product Editor $50: bulk editor like Excel |
|
Image Pro $15: WebP, watermark |
Filter $30: smart filter + SEO |
Category Manager $30: visual category manager |
|
AI Smart Search $200: AI search with synonyms |
AI Chat $100: AI consultant 24/7 |
AI Photo Studio $50: AI photo editing |
|
PaymentHub $80: payment hub |
ShippingHub $80: shipping hub |
SmartOrder $30: fast checkout |
|
Shipping Rules $30: shipping rules |
AI Мегарепорти $20: reports and Telegram digest |
Product Bundles $30: product bundles |
|
Simple Super Search $50: fuzzy search without Sphinx |
OcBox MEGA $30: theme and modules bundle |
AI Quiz $50: AI product quiz |
|
Універсальний імпорт $50: supplier price import |
Відгуки Pro $30: reviews with photo and video |
Варіанти товару $30: size and color matrix |
OcBox MEGA is out: a ready-made store for OpenCart 3
A theme plus seven OcBox modules in one bundle: SmartOrder fast checkout, live search, filter, analytics and remarketing, reviews with photos, structured data and social login. Install it, set your colors and home page blocks, and the store is ready to sell.
$30 instead of $200 for the first 100 buyers.
Subscribe to our channel: t.me/ocboxchannel
Характеристики
-
Recently Browsing 0 members
- No registered users viewing this page.

