hivein for OpenCart
Sales, catalogue and customer answers read straight from the OpenCart database, however modified it is.
Read-only SQL against the OpenCart store database, with the table prefix and any extension-added tables found by schema introspection rather than assumed.
- Read the schema before reading the data
- Report on orders from the tables that hold them
- Read the catalogue with its languages and options
- Keep multi-store answers apart
- See customers and the carts they left
What the OpenCart connector will do.
Read the schema before reading the data
An OpenCart install has a configurable table prefix and, more often than not, columns and tables added by extensions or a themer. Introspection will come first, so nothing depends on a stock layout.
Report on orders from the tables that hold them
oc_order carries the header, oc_order_product the lines, oc_order_total the sub-total, shipping and tax rows, and oc_order_history every status change. Revenue figures will be built from those rows, including the tax and shipping lines oc_order_total keeps separate.
Read the catalogue with its languages and options
Names and descriptions sit in oc_product_description per language, options in oc_product_option and oc_product_option_value, and category placement in oc_product_to_category.
Keep multi-store answers apart
oc_store plus the store_id carried by settings, layouts and product-to-store rows defines each storefront, and oc_setting holds the per-store configuration a figure depends on.
See customers and the carts they left
oc_customer and oc_customer_group cover accounts and their pricing tier, while oc_cart keeps rows for sessions that filled a basket and never checked out.
It will read your OpenCart data model, not a generic one.
The schema is read first, so a question that spans two of these is one question, not two lookups.
“Which products sold most last quarter once cancelled and refunded orders are left out”
“Find orders where the total rows do not add up to the order total”
“What tables has our extension developer added outside the stock schema”
“How many wholesale customers have not ordered since January”
OpenCart questions.
Why the database rather than the API?
OpenCart's api routes were built for the admin order editor and cover little beyond order and cart operations. Reporting questions are answered honestly from the database, which holds everything the storefront and admin display.
Our shop has been modified heavily. Does that break it?
That is the normal case for OpenCart, which is why the plan starts with introspection. Extra columns and extension tables are read as they are found instead of being matched against a stock 3.x or 4.x layout.
Will it write to the database?
The connection is planned as a MySQL user with SELECT rights only, so nothing can be changed through it. Any write support would be a separate step you grant explicitly.
More templates like this one.
BtBotble
Closed sourceYour Botble store's catalogue, orders, pages and SEO, changed through Botble's own rules rather than raw SQL.
Tools from your schemaOpen template → — Botble
Shopify
Closed sourceAsk about orders, stock and customers in your store; catalogue and fulfilment edits wait for confirmation.
32 actionsOpen template → — ShopifyWcWooCommerce
Open sourceAnswer order, stock and refund questions against your WooCommerce store's own data.
TemplateOpen template → — WooCommerce
Magento
Open sourceOrders, quotes and catalogue attributes across every website and store view of a single Magento install.
In developmentSee the plan → — Magento
Medusa
Open sourceAsk your Medusa backend about orders, stock and price lists without writing another admin API call.
In developmentSee the plan → — Medusa
PrestaShop
Open sourceOrders, combinations, carts and cart rules from a PrestaShop shop, read through its built-in Webservice API.
In developmentSee the plan → — PrestaShopSaSaleor
Open sourceOne place to ask about Saleor orders, channel pricing and warehouse stock without writing GraphQL.
In developmentSee the plan → — Saleor
Shopware
Open sourceSales-channel-scoped answers about orders, rules and Flow Builder in Shopware 6, through the Admin API.
In developmentSee the plan → — ShopwareWant OpenCart next?
Tell us what you would want it to do. Connector order follows demand, and the platforms people ask for get built first.