Momo Fabric by MMBM Software StudioMomo Fabric by MMBM Software Studio
Momo Fabric
MMBM Software Studio
DELIVERED · ERP / POS · 2026
Momo Fabric
An offline-first textile ERP and POS combining a desktop selling experience with a web owner dashboard for centralized multi-branch retail and wholesale control.
Offline-firstsales continue through connectivity loss
Multi-branchcentral owner visibility and stock workflows
5payment methods supported
Retail + wholesaletwo commercial flows in one system
CASE STUDY
Textile inventory is not a generic SKU problem.
Fabric operations have extra dimensions: code, color, category, roll and metre, with stock moving between branches and being sold through both retail and wholesale workflows. The system had to reflect that operating model while remaining usable when internet access was unreliable.
01 · Challenge
Represent physical textile stock accurately.
Inventory needed to preserve the attributes the business actually uses while supporting transfers, sales, returns and remaining-stock visibility without reducing everything to simplistic product counts.
02 · Architecture
Desktop POS locally; owner control on the web.
The POS uses a Tauri/React experience for branch operations. Fastify APIs, PostgreSQL and Prisma provide the central data layer, while the Next.js owner dashboard exposes cross-branch management and reporting.
03 · Offline strategy
Local transaction continuity with automatic recovery.
Transactions can be stored locally when connectivity drops and synchronized after reconnection, allowing the selling workflow to continue instead of making internet availability a point-of-sale dependency.
BUSINESS COVERAGE
ERP depth behind the checkout screen.
Momo Fabric connects inventory, selling and account-style workflows instead of treating the POS as a standalone application.
01
Fabric inventory
Code, color, category, roll and metre modelling with stock availability and branch-level movement.
02
Stock transfers
Move inventory between branches while preserving central visibility.
03
Retail & wholesale
Separate operational needs supported within one sales platform.
04
Returns & exchanges
Reverse and replace transactions without losing the surrounding stock/account context.
05
Customer credit
Track customers, balances and credit-oriented selling workflows.
06
Supplier ledgers
Supplier accounts and running transaction history for business control.
07
Expenses & reporting
Operational expenses and management visibility alongside sales information.
08
Checkout hardware
Barcode flow, five payment methods and thermal-receipt-oriented output.
DESIGN DECISION
Reliability mattered more than architectural fashion.
The system is deliberately split around operational reality: the branch needs fast local selling, while the owner needs centralized web visibility. Offline storage and synchronization sit between those requirements.
DELIVERY
Built, delivered and moved into real operation.
The project progressed from requirements and data modelling through frontend, backend, database, desktop packaging, synchronization logic and deployment. It now serves as MMBM’s strongest proof of end-to-end ERP/POS delivery.
Tell us what your team does today, where it breaks, and what a better workflow should look like.
Like this project
Posted Oct 29, 2026
Offline-first textile ERP/POS combining a Tauri desktop POS with a Next.js owner dashboard for multi-branch retail and wholesale, with offline sync and fabric-a