Mushik
Launching after Razorpay approval
Silk and handloom sarees, sold on my own engine. The core is a headless commerce API in plain PHP with no runtime dependencies, so it runs on cheap shared hosting. The admin and the store are static Next.js sites that talk to it, and two Flutter apps keep the shop's books.
CatalogueVariantsPrice listsCouponsCartCheckoutRazorpayGST invoicesRefundsCredit notesWalletInventoryPurchase ordersShippingLabelsTrackingReturnsWhatsApp ordersReviewsWishlistBack in stockAbandoned cartsSEOSitemapsBlogOTP sign-inRolesReportsImport and exportWebhooks
What it does
- Catalogue
- Products, attributes, options and variants, price lists, quantity tiers and search with synonyms.
- Selling
- A server-side cart and quote, coupons and automatic offers, wishlist, back-in-stock alerts and abandoned-cart recovery.
- Money
- Razorpay with signed webhooks, GST invoices with CGST, SGST and IGST, refunds, credit notes and a store-credit wallet. Every amount is an integer of paise.
- Operations
- Stock and purchase orders, shipping zones and rate cards, dispatch and tracking, address labels by the batch, and returns.
- WhatsApp orders
- Take an order over chat or the phone, send a payment link, or record cash.
- Growth
- Reviews and Q&A with verified buyers, SEO with structured data and sitemaps, pages and a blog.
- Platform
- Customer sign-in by OTP, staff roles and permissions, reports, catalogue import and export, and outgoing webhooks.
- The shop's books
- Flutter apps for bills, expenses and hand-taken orders. They work offline and sync when the signal is back.
What I'm cooking
- Payments go live once Razorpay approves
- White-label: the next shop is a rebrand, not a rebuild
Built with
- PHP
- MySQL
- Next.js
- TypeScript
- Tailwind CSS
- Flutter
- Razorpay
Next
Uncut
Full-page screenshots as one seamless image, no stitching seams.