Will the store connect to our ERP stock and accounts?

Yes, that is the point of the build. Orders, stock, prices and invoices are synced with ERPNext so the store sells what is actually in the warehouse and every sale lands in the books. If you keep Tally for accounts, we agree which records flow there and how.

How is a commerce project priced?

By scope, with no platform commission on your sales. The price is driven by the catalogue, the number of channels (web, B2B portal, shop counter), payment and shipping partners, ERP integration and any custom checkout or pricing logic. You get a written scope and price before work starts.

What decides how long it takes?

Payments, shipping, tax and email have to be set up on every project; after that, time depends on catalogue size, how many integrations there are, B2B rules and how much content has to move. We give a timeline in writing after the assessment.

Can you move our existing store without losing search rankings?

Yes. We crawl the live store first, keep URLs where we can and map a redirect for every one that has to change before cut-over. The full plan is on the Shopify to Medusa migration page.

Are GST invoices handled for online orders?

Yes. Because you own the order and invoice layer, GST invoices, e-invoices and e-way bills are produced from the ERP for each order rather than from a separate plug-in.

Who owns the store and the customer data?

You do. The code, the customer list and the order history live on infrastructure you control, and you can move or run it yourself at any time.

What happens after launch?

You can keep us on support or managed hosting, or take it in-house with our handover notes. Either way the store, the ERP link and the payment setup are documented.

Practice · Omnicommerce

End-to-end commerce engineering — storefront, back office, payments, POS.

For brands, distributors and retailers selling online, to dealers and over the counter: one store and one order flow, tied to your stock and accounts.

Book a demo See it live

On the map

Where your customers meet the business, on the map.

The storefront, portals and counter sit on the Customers floor, connected to the same stock, prices and accounts as everything else. Click any building to open it.

Industry

orders · payments · complaints

tasks · approvals · attendance

purchases · bills · payments

everything in · answers out

CUSTOMERS

Customers — every way an order can reach you

Twelve front doors. One catalogue, one stock figure, one customer record behind all of them.

CUSTOMERSsell everywhere without selling the same unit twice→ orders, payments and complaints come in← prices, stock and delivery updates go back out

PUT TOGETHER

Sell the same item on the website, on WhatsApp and at the counter — it is one stock figure, so it cannot be sold twice, and every one of those orders is billed the same way.

What each one actually does

▸ click any component to see what it does

Your industry

Inside the Core — how one order runs the whole business

Nobody types the same thing twice. Each document is built from the one before it.

Book a Free Demo

Explore the full ecosystem — commerce and marketing maps too →

Practice capabilities

One engagement, every layer of commerce.

We define the order flow: checkout creates the agreed ERP or CRM record, fulfilment receives a task, the customer receives a permitted update, and analytics measures the result.

Headless storefronts

Custom D2C and B2B storefronts on Medusa.js and Next.js, brand-owned.

Payments & checkout

Razorpay, Stripe, COD, wallets and split settlements, with B2B terms built in.

ERP, CRM & back-office

ERPNext can own selected inventory, pricing, order and accounting records. Mautic, Chatwoot and PostHog remain separate applications connected through defined integrations.

Unified POS & retail

POS and storefront can share selected stock and customer records through the integration design. Multi-store inventory, returns, loyalty and GST receipting are scoped to the operating model.

Custom commerce logic

Tiered B2B pricing, quote-to-cash, approvals and subscriptions, held in the platform.

Operator & agent dashboards

Dashboards for operations, support and field teams, including the Polygin WhatsApp console.

Engagement shapes

Three shapes of commerce engagement.

Each starts with a demo or a written plan, then a written scope led by a principal consultant.

D2C storefronts at scale

Conversion-focused direct-to-consumer commerce for the markets, payments and fulfilment model agreed in scope. From catalogue architecture and merchandising to fulfilment orchestration.

Headless Medusa.js + Next.js
Razorpay / Stripe / COD split routing
Multi-warehouse reservation logic
Returns, exchanges, store credit
Brand-owned checkout and agreed platform costs

B2B & wholesale commerce

Quote-, approval- and contract-driven commerce for distributors and manufacturers, on the ERP's data.

Customer-specific pricing & catalogues
Quote-to-cash with approval gates
Credit terms and invoicing workflows
ERPNext order & inventory sync

Omnichannel, retail & marketplaces

Online, in-store and marketplace selling with defined stock, order and customer-record ownership. POS, marketplace and storefront integrations are validated against the selected source of truth.

Unified POS, web and marketplace stock
Click-and-collect, ship-from-store
GST & e-invoice compliant receipts
Polygin WhatsApp order comms

Delivery boundary

Designed around the workflow in scope.

This page describes a reference approach, not an automatic bundle. We agree the systems, record ownership, interfaces, approvals, delivery gates and handover before implementation. Published outcomes are used only where their client-approved basis is clear.

Why the practice

An engineering practice, not an agency.

An open-source engineering practice across commerce, ERP and automation — principal-led, scoped in writing, run on infrastructure you own.

Get a written plan

ScopedPlatform, payment and operating costs

3Engagement models

PhasedDiscover, build, validate and hand over

OwnedAgreed source, data and infrastructure terms

Commerce projects — FAQs

Stay on Shopify if it does what you need and the platform and app fees are not hurting. Medusa earns its place when you need dealer pricing, quotes and approvals, a checkout Shopify will not let you change, or a store that shares stock and accounts with your ERP. We will tell you plainly if staying is the better call.

Shopify to Medusa migration →The Shopify to Medusa migration guide →All commerce articles →

Proof and next steps

See the work, then try it

Case studies

Splendx · B2B commerce · multi-warehouse operatorSplendx — multi-warehouse B2B commerce, integrated end-to-end.Read the case study Lamongie · textile commerceLamongie — one platform serving both a dealer network and retail buyers.Read the case study

All case studies

See it live

ERPNext

An online order, start to finish

A shop order is picked, shipped, billed and paid, and nobody types it twice.

Sales Order → Pick List → Delivery Note → Sales Invoice → Payment Entry

See it live Ride it in MithUniverse

ERPNext

A sale at the shop counter

Bill at the counter, even offline; the day closes itself into stock and the books.

POS Opening Entry → Sales Invoice → POS Closing Entry

See it live Ride it in MithUniverse

ERPNext

A return, handled cleanly

The customer asks in the portal; the goods come back and the refund posts itself.

Sales Invoice → Credit Note → Payment Entry

See it live Ride it in MithUniverse

All live demos

POS & Retail Billing on Medusa.js

Omnichannel POS on Medusa.js — MIT · v2.14.1 · Multiple Sales Channels · Online + Offline Inventory Sync · 5,000+ Retail Orders / 500+ Store Locations Pattern

View product

End-to-end commerce engineering — storefront, back office, payments, POS.

Where your customers meet the business, on the map.

Inside the Core — how one order runs the whole business

One engagement, every layer of commerce.

Headless storefronts

Payments & checkout

ERP, CRM & back-office

Unified POS & retail

Custom commerce logic

Operator & agent dashboards

Three shapes of commerce engagement.

D2C storefronts at scale

B2B & wholesale commerce

Omnichannel, retail & marketplaces

Designed around the workflow in scope.

An engineering practice, not an agency.

Commerce projects — FAQs

See the work, then try it

Case studies

See it live

An online order, start to finish

A sale at the shop counter

A return, handled cleanly

Related

See your order flow, end to end.

POS & Retail Billing on Medusa.js

End-to-end commerce engineering — storefront, back office, payments, POS.

Where your customers meet the business, on the map.

Inside the Core — how one order runs the whole business

CRM · leads & follow-ups

Sales · quotes & orders

eCommerce · the online shop

POS & Retail · the counter

Helpdesk · complaints & warranty

Buying · purchase orders

Stock · what you have, where

Manufacturing · make to order

Quality · checked before it ships

Maintenance · machines & upkeep

Accounting · books & GST

Assets · what you own

Subscriptions · recurring billing

Compliance · rules, kept current

HR & Payroll · people & salaries

Projects · time & cost

CUSTOMERSevery way an order can reach you

YOUR TEAMyour people, on whatever device the job needs

SUPPLIERS & PARTNERSbuying, shipping, banking, filing

WHAT THE NUMBERS SAYdashboards, margins and what happens next

COMMUNICATIONevery channel your customers use, filed on the record it belongs to

One engagement, every layer of commerce.

Headless storefronts

Payments & checkout

ERP, CRM & back-office

Unified POS & retail

Custom commerce logic

Operator & agent dashboards

Three shapes of commerce engagement.

D2C storefronts at scale

B2B & wholesale commerce

Omnichannel, retail & marketplaces

Designed around the workflow in scope.

An engineering practice, not an agency.

Commerce projects — FAQs

Should we build on Medusa or stay on Shopify?

Will the store connect to our ERP stock and accounts?

How is a commerce project priced?

What decides how long it takes?

Can you move our existing store without losing search rankings?

Are GST invoices handled for online orders?

Who owns the store and the customer data?

What happens after launch?

See the work, then try it

Case studies

See it live

An online order, start to finish

A sale at the shop counter

A return, handled cleanly

Related

See your order flow, end to end.

Commerce products the practice builds

POS & Retail Billing on Medusa.js