hivein for Shopware
Sales-channel-scoped answers about orders, rules and Flow Builder in Shopware 6, through the Admin API.
Through the Shopware 6 Admin API over OAuth 2.0 client credentials, using the client id and secret of an integration you create in the Administration, which carries whichever roles you assign it.
- Query entities with Admin API criteria
- Scope answers by sales channel
- Explain what the rule builder decided
- Trace order, transaction and delivery states
- Show what Flow Builder is automating
What the Shopware connector will do.
Query entities with Admin API criteria
A single POST to /api/search/order carries filters, associations and aggregations in one request, so an order comes back with its transactions and deliveries attached and can be counted across them.
Scope answers by sales channel
Each sales channel has its own domains, languages, currencies and product visibility rows. A product hidden in one channel and live in another will be reported per channel, with the channel named.
Explain what the rule builder decided
Rules and their nested conditions govern which shipping methods, payment methods and promotions a cart is offered, so a question about why an option disappeared can be traced to the condition that matched.
Trace order, transaction and delivery states
Shopware runs three state machines per order, one each for the order, the payment transaction and the delivery, plus generated documents such as invoices and credit notes. A stuck order will be named by the state machine that is actually stuck.
Show what Flow Builder is automating
Flows attach sequences to platform events such as checkout.order.placed. Reading flows and their sequences shows which events already send mail, set tags or move a status before anyone adds another.
It will read your Shopware 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 shipping methods depend on a rule and what does that rule check”
“Show me orders whose payment transaction has been in progress for more than three days”
“Which flows are triggered when an order is placed”
“How many products are hidden in the B2B sales channel but visible in the main one”
Shopware questions.
Does this cover Shopware 5?
No. Shopware 5 exposes a different REST API and a different data model. The Admin API, the criteria syntax and the entity names described here all belong to Shopware 6.
Self-hosted or Shopware Cloud?
Both reach the same Admin API. You create an integration under Settings, give it the roles it should have, and the connector authenticates with that client id and secret.
Can it read the rule builder's nested conditions?
Rules are stored as a tree of condition entities, so the nesting is readable rather than opaque. That is what allows a specific answer about why a payment method was or was not offered.
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 → — OpenCart
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 → — SaleorWant Shopware next?
Tell us what you would want it to do. Connector order follows demand, and the platforms people ask for get built first.