hivein for PrestaShop
Orders, combinations, carts and cart rules from a PrestaShop shop, read through its built-in Webservice API.
Through the PrestaShop Webservice API, authenticating with a webservice key sent as the HTTP Basic username and reading JSON rather than the default XML.
- Follow an order through its state history
- Work at combination level, not product level
- Read discounts as PrestaShop models them
- Look at carts and the carriers behind them
- Respect the multistore layout
What the PrestaShop connector will do.
Follow an order through its state history
Orders, order_details, order_payments and order_histories are separate resources. Read together they show when an order left Awaiting payment, what was actually paid and which lines it carried.
Work at combination level, not product level
Variants are combinations built from product_options and product_option_values, each with its own reference, price impact and stock_availables row. Stock and sales questions will resolve to the combination that sold.
Read discounts as PrestaShop models them
Catalogue discounts live in specific_prices, scoped by shop, currency, country and customer group, while vouchers are cart_rules with their own date windows and usage limits. The two will be reported separately.
Look at carts and the carriers behind them
The carts resource keeps rows that never became orders, and carriers with their zones and price ranges explain the delivery figure on the ones that did.
Respect the multistore layout
Shops, shop_groups and shop_urls describe which storefront a record belongs to, so a multistore install can be read one shop at a time, with each answer naming the shop it came from.
It will read your PrestaShop 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 orders have been awaiting bank wire payment for more than five days”
“Show me combinations with no stock that are still available for order”
“How many carts were created last week with no order behind them”
“Which cart rules expire this month and how often has each been used”
PrestaShop questions.
Does PrestaShop need an extra module for this?
No. The Webservice API ships with PrestaShop and is switched on under Advanced parameters, where you generate a key. Each key carries its own per-resource permission grid, so the assistant only reaches the resources you tick.
Which PrestaShop versions are planned?
The work targets 1.7 and 8.x, which share the same webservice resource names and object model. Version 1.6 exposes a narrower set and differs on several resources, so it sits outside the first version.
The Webservice returns XML. Is that a problem?
XML is only the default. The endpoint accepts output_format=JSON on 1.7 and later, which is what the connector will request, and in either case you read an answer rather than a payload.
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 → — MedusaOpOpenCart
Open sourceSales, catalogue and customer answers read straight from the OpenCart database, however modified it is.
In developmentSee the plan → — OpenCartSaSaleor
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 PrestaShop next?
Tell us what you would want it to do. Connector order follows demand, and the platforms people ask for get built first.