Commerce systems on Medusa, and the work that happens around the order
Headless commerce on Medusa. A backend that is yours, not rented
Medusa v2 is an open-source commerce framework you host yourself: your database, your business rules, your deployment. The storefront is a separate application that talks to it over an API, so a redesign is a frontend project rather than a replatform, and a rule that does not fit the default gets written rather than worked around.
Marketplace integrations. Allegro inside the admin you already use
Selling on a marketplace usually means running a second system that disagrees with the first one. We bring offers and orders into the store you already operate and reconcile marketplace buyers against the customer and invoice-recipient records you actually bill, because the person holding the account is often not the company on the invoice.
Pricing and margin control. Currencies and costs on the same record
Prices that follow the exchange rate instead of a quarterly spreadsheet, and net purchase cost recorded against the variant it belongs to. Once both sit on the same record, margin and break-even price are numbers somebody reads rather than a reconstruction somebody performs at month end.
Invoicing and KSeF. Documents raised where the order already is
Invoices issued from the order itself and filed with KSeF for the B2B ones the law requires, and the documents somebody raised by hand outside the shop matched back against the orders they belong to. Compliance work belongs in the system that knows what was sold, to whom and for how much.
Subscription and usage billing. Charge for what was actually used
A metered product needs a trustworthy event log before it needs a price. We build the ingestion path, deduplicate events on the way in so a retried delivery is free rather than a second charge, and rate the result into subscriptions and invoices.
Commerce automation. The work that surrounds an order
ERP, accounting, warehouse and courier systems fed from the store rather than from somebody re-typing between them. We trace where data is copied by hand today, settle which system owns which field, and build flows that fail loudly instead of quietly.
A store is not a page with a basket on it. It is a catalogue, a set of prices, invoices, marketplace listings, a warehouse and an accounting system that all have to agree with each other every day.
We build that on Medusa v2 - an open-source commerce framework that runs on your infrastructure rather than someone's plan. Commerce logic here is code, not a settings screen with a ceiling, so when your process does not match the default you change the default instead of working around it.
We know the stack from the inside. Our own platform's usage billing is built on a Medusa store we host ourselves, and seven of the plugins that came out of that work are published with their documentation.
If your selling is spread across systems that disagree, get in touch. We start from the place where somebody is retyping data today.
Medusa is MIT-licensed and self-hosted. The database is yours, the code is yours, and none of the terms change because a vendor rewrote its pricing page or retired the tier you were on.
Commerce logic is code here, not a settings panel with a limit. A pricing rule, a fulfilment step or an integration your business genuinely needs gets built into the system rather than bolted to the outside of it.
Our own platform's subscription and usage billing is built on a Medusa store we host. The awkward parts - deduplicating metered events, reconciling invoices, keeping a marketplace and a catalogue in agreement - are problems we have already had to solve for ourselves.
Purchase cost, currency and selling price sit on the same record, so profitability shows up in the admin instead of in an export somebody assembles once a month and nobody quite trusts.
Marketplace status, invoices and costs render as extra columns in the store's own product table. Three integrations add three columns rather than three near-identical product lists nobody keeps in sync.
Seven of the plugins behind this are published with their documentation, so you can read what we built before you buy it and whoever maintains it after us can read it too.
Read testimonials from companies that trusted us
Delivered well ahead of the deadline.
ZanReal's individual approach is impressive.
Knowledge and business intuition make them a valuable partner.
Quick solutions that reduced costs by 99%.
Technical guides, security insights, and what we've learned building with AI.
Curious about what's next?
View all postsTell us where the numbers stop agreeing - the marketplace nobody has time to reconcile, the invoices issued by hand, the margin that only exists in a spreadsheet.
We will look at what you run today and propose the first piece worth building, which is usually smaller than expected.
Let us do the heavy lifting. Every week we distill the most important AI developments into a focused 5-minute briefing - so you stay ahead without the noise.
Find out more
