hivein for Medusa
Ask your Medusa backend about orders, stock and price lists without writing another admin API call.
hivein will call the Medusa Admin REST API on your own backend, authenticated with a secret API key or an admin JWT session.
- Read orders the way support does
- Build draft orders for manual sales
- Work at variant level, not product level
- Explain regional pricing
- Follow fulfillments and returns
What the Medusa connector will do.
Read orders the way support does
List and filter orders by payment status, fulfillment status, region or customer, and expand the line items, shipping methods and totals behind each one.
Build draft orders for manual sales
Create a draft order for a named customer, add variants and custom line items with the price you specify, then convert it into a real order when it is agreed.
Work at variant level, not product level
Medusa hangs price, SKU and inventory off the variant. Variants, their options and the inventory items linked to them will be read together, so stock answers land per SKU and per stock location.
Explain regional pricing
A region sets currency, countries and payment providers, tax rates live in the Tax module's tax regions, and price lists override prices for a sale or a customer group. An answer will name which of those produced the price a customer saw.
Follow fulfillments and returns
Create a fulfillment for selected order items, record shipping, and read the returns, exchanges and claims attached to an order.
It will read your Medusa 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 in the EU region are paid but still unfulfilled after three days”
“Create a draft order for this wholesale customer with 12 units of the linen shirt at the trade price”
“Which variants of the winter jacket are out of stock in the Berlin stock location”
“What price list is the discount on this order coming from and when does it expire”
Medusa questions.
Does hivein need my Medusa backend to be publicly reachable?
Yes. Medusa is self-hosted, so hivein will call the admin API at whatever URL your backend is deployed to. A staging deployment works just as well as production for trying it out.
Will it work with Medusa v1 as well as v2?
The integration is being built against the v2 Admin API, where modules such as pricing, inventory, tax and fulfillment are separated. v1 support depends on demand, since several v1 endpoints were reshaped in v2.
Can it change orders, or only read them?
Writes such as creating a draft order or a fulfillment are treated as actions and go through a confirmation step before anything is sent to your backend. Read-only questions run without asking.
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 → — MagentoOpOpenCart
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 → — 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 Medusa next?
Tell us what you would want it to do. Connector order follows demand, and the platforms people ask for get built first.