Mato Crafts
Mato Crafts is a live Next.js and Sanity CMS commerce platform for a handcrafted polymer-clay jewelry brand in Patan Dhoka, Lalitpur. Yumesh took ownership of most of the full-stack work after the initial phase, evolving a functional but generic storefront into a bilingual commerce and operational system for product discovery, orders, variants, inventory, barcode handling, stall sales, and delivery workflows.
Role
Full-stack Developer
Association
Niyalo Creatives
01
The context
The problem, people, and outcome in view.
The initial product was a generic e-commerce build for simple products. It did not yet have a distinctive customer experience, Nepali-language support, robust variant selection, inventory control, barcode operations, stall management, or delivery workflows.
For a handcrafted-jewelry studio, that separation was a real product limitation: online catalogue data, physical stock, variants, and event-stall sales all needed to stay understandable to customers and manageable for the team.
02
The contribution
A clear view of what I owned.
Full-stack Developer
Responsibilities
- The storefront is live. The owner has assessed the overall functionality positively and continues to provide small UI and operational refinements.
Capabilities applied
03
The work
From decisions to the working product.
Process
I owned approximately 80% of the platform implementation: frontend, backend workflows, CMS structure, inventory, barcode and stall operations, delivery architecture, and ongoing refinement.
Satish Bajagain contributed during the early phase. His contributions included direction for Nepali-language support, dashboard and event-space design exploration, and early variant-checkout ideas that were later superseded by barcode-based variant and inventory workflows. Public credit: https://github.com/BajagainSatish
Solution
A branded, responsive English/Nepali storefront with CMS-managed product and editorial content. Variant-aware product selection and cart identity that preserves the exact selected combination. Barcode inventory units with availability states including available, reserved, at stall, sold, and void. Warehouse-to-stall transfers and dashboard-based stall-sale operations. Barcode-label PDF generation and virtual-print support, ready for physical-printer validation. Customer accounts, cart and wishlist persistence, custom orders, and role-aware operational dashboards. Courier integration architecture for Packrs and Pick N Drop, with explicit configuration and provider limitations. Analytics events, error monitoring, and automated unit/integration coverage for key flows.
04
The result
Proof over promises.
The storefront is live. The owner has assessed the overall functionality positively and continues to provide small UI and operational refinements.
Sales activation is not yet completed. An observed estimate of approximately 3,000 monthly users needs an analytics source and reporting month before public use.
Physical barcode and receipt-printing validation is pending the client purchasing compatible hardware. Packrs is the current delivery path. Pick N Drop migration remains in validation because the required provider documentation and verified integration path are incomplete.
05
Build notes
The tools and details that carried it through.
Technology
Showing 10 of 30Selected product details
- A branded, responsive English/Nepali storefront with CMS-managed product and editorial content.
- Variant-aware product selection and cart identity that preserves the exact selected combination.
- Barcode inventory units with availability states including available, reserved, at stall, sold, and void.
- Warehouse-to-stall transfers and dashboard-based stall-sale operations.
- Barcode-label PDF generation and virtual-print support, ready for physical-printer validation.
- Customer accounts, cart and wishlist persistence, custom orders, and role-aware operational dashboards.
- Courier integration architecture for Packrs and Pick N Drop, with explicit configuration and provider limitations.
- Analytics events, error monitoring, and automated unit/integration coverage for key flows.
Explore further
06
Connected work
Proof and writing from this project.
Project proof
Showing 5 of 18Frontend / Next.js
Mato Crafts: Next.js application architecture
Structured a Next.js App Router application with clear server/client responsibilities and API routes. The architecture supports both the public storefront and internal operational workflows in one codebase.
Frontend / State Management & Local Persistence
Mato Crafts: React state design
Built cart state that treats each selected product-variant combination as a distinct purchasable item. This keeps option selection, cart identity, and inventory-sensitive ordering aligned.
Frontend / TypeScript
Mato Crafts: TypeScript domain modelling
Modelled product variants, inventory units, orders, transfers, and shipment state as explicit TypeScript concepts. The types make operational relationships visible and reduce ambiguity across commerce workflows.
CMS / Sanity CMS
Mato Crafts: Sanity CMS modelling
Connected structured product, editorial, order, and operational records to the storefront and studio. The Sanity model lets the business manage content and operations from shared data rather than scattered page edits.
Frontend / Tailwind CSS
Mato Crafts: Responsive commerce UI
Built responsive customer flows for discovery, product selection, cart, checkout, accounts, and custom orders. The interface gives shoppers a simple path while retaining the detail needed for variant-aware products.
Related writing
2 articlesEngineering Note
How I designed barcode and stall inventory for Mato Crafts
The operational design behind turning product variants into traceable inventory units for warehouse and event-stall sales.
Read articleCase Study
From storefront to stall: building the operational side of Mato Crafts
How a simple storefront became a bilingual commerce and inventory system for a handcrafted-jewelry studio.
Read articleWorks / 01 of 08