Medusa POS
Cross-platform POS app for Medusa built with React + Tauri 2.
Website: pos.nari.ge · Download · Getting started
This project is under active development. APIs, behavior, and UX may change.
Medusa POS is an independent open-source project and is not officially affiliated with Medusa.
Compatibility
| Capability | Vanilla Medusa (admin.product.list) | Medusa + POS plugin/custom /pos endpoints |
|---|
| Add product to cart | ✅ | ✅ |
| Reliable inventory check before adding | ❌ (variant inventory_quantity may be missing) | ✅ |
| Context-aware computed variant price | ❌ (raw prices array) | ✅ |
| Inventory kit availability checks | ❌ | ✅ |
Medusa Version Tested
If your backend is older/newer, behavior can differ (especially pricing and inventory fields).
Quick Start
Prerequisites
Install
yarn install
Run
# Browser (UI-only)
yarn dev
# Desktop (recommended)
yarn tauri dev
Important: full app flow requires Tauri runtime. This project stores backend configuration in
Tauri storage/config files on first setup, so yarn dev is only for limited UI work. Use
yarn tauri dev for real usage and testing.
Build / Lint
yarn build
yarn lint
yarn typecheck
Core Features
- Checkout UI with barcode scanning, cart, payment dialog
- Park an in-progress sale and resume it from any till
- Draft order creation and updates through Medusa Admin APIs
- Receipt printing (network / USB / system printer), cash drawer trigger
- Order list and order detail views, with refunds from the order page
- Settings for API/store, printers, branding, preferences
- Multi-store backend configuration
Environment
Use .env, .env.staging, or .env.production:
VITE_BACKEND_URL=https://your-medusa-instance.example.com/
The backend URL can also be configured at runtime via Store Setup.
Medusa API Support Notes
| Topic | Support in Medusa (current observed behavior) |
|---|
Creating admin payment collections with payments[], provider_id, provider_data in one call | ❌ Not supported by current AdminCreatePaymentCollection typing/API shape (still order_id + amount only); since 2.16 a provider_id can be passed when marking a collection as paid |
This has no effect in the app, which records the provider through a payment session (or markAsPaid with provider_id) after creating the collection.
For every known limitation of the app — with impact, workarounds and the path to a fix — see Known limitations.
Downloads
Prebuilt binaries are available on the Releases page for each tagged version.
| Platform | Architecture | Format |
|---|
| Windows | x86_64 | .msi installer |
| macOS | Apple Silicon (aarch64) | .dmg disk image |
| macOS | Intel (x86_64) | .dmg disk image |
| Linux | x86_64 | .AppImage |
All builds include signed updater artifacts so the app can auto-update itself after installation.
Code signing notice
Windows — The MSI installer is not code-signed with a trusted certificate. Windows SmartScreen will show an "Unknown Publisher" warning on first install. You can bypass it by clicking More info → Run anyway.
macOS — The DMG is ad-hoc signed but not notarized with an Apple Developer ID. macOS Gatekeeper will block it by default. To open it, right-click the app → Open, or run xattr -cr /Applications/Medusa\ POS.app after dragging it to Applications.
Linux — No code signing is required. The AppImage runs directly after making it executable (chmod +x).
Roadmap
We're actively building out Medusa POS into a full-featured retail system. Here's what's coming:
- Medusa POS plugin (released) — The custom backend endpoints that power inventory checks, context-aware pricing, and kit support are available as a standalone Medusa plugin:
@narisolutions/medusa-plugin-pos.
- Cash reconciliation (v1) (released) — Open/close register flow that guides staff through end-of-shift cash counting, compares the drawer against expected totals, and records any discrepancies. Optional — enable it in Settings.
- Payment provider integrations — Native support for physical card readers and payment terminals, with real provider IDs recorded against each order for accurate reporting.
- Manual card transactions (released) — Accept card payments through any external terminal and record the method used against the order, no payment provider integration required.
- Bank transfer — Take a payment by bank transfer, confirmed at the counter or recorded later from the order; unpaid receipts print the store's bank details with the order number as the payment reference.
- Draft orders & parked sales (released) — A dedicated Parked sales tab lets staff park an in-progress sale and pick it up later, from any till. Stock is not held while a sale is parked; availability is re-checked on resume and the operator is told what changed. Holding stock is planned.
- Refunds & partial refunds (released) — Full or partial refunds against a captured payment from the order page, with a reason recorded against the refund and the drawer opened for cash.
- Returns, exchanges & additional charges (released) — Complete the post-sale lifecycle from the order page: take goods back (restocked or written off as damaged), swap them for other products, or add items to an existing order, with a printed slip and a full activity trail.
- Catalog browsing (released) — Browse the catalog from the checkout by category, as cards or a list, alongside search and barcode scanning.
- Quotations — Create and send formal quotations to customers directly from the POS, useful for large or made-to-order purchases.
- Accounting & Z-Reports (v2) (coming soon) — End-of-day Z-Reports across all payment methods, built on top of v1's closed register sessions, with history and PDF/CSV export.
- Role management — Roles defined and enforced by the Medusa backend, once Medusa supports them; the POS adds no role system of its own.
Useful Links
