ALL WORK · CASE 12

MANIYARI

A multi-vendor marketplace that gets small sellers online without an IT department — shops, catalogs, payments and orders from one system that stays out of the way.

SECTOR
E-COMMERCE · MARKETPLACE
SCOPE
FULL BUILD — VENDOR TO ADMIN
THREAD
LARAVEL · BLADE · MYSQL
STATUS
IN PRODUCTION
MANIYARI product interface

ORDER STATE MACHINE — EVERY PURCHASE WALKS THIS PATH

LISTED
ORDERED
PAID
SHIPPED
DELIVERED

PAYMENT FAILS → ORDER HELD → RETRY OR RELEASE STOCK — INVENTORY NEVER LIES

01 — WARP

What had to be true first

Maniyari's constraint was its users: local vendors with no technical staff, moving online for the first time. The warp was a vendor model simple enough to onboard in minutes but structured enough to keep a marketplace honest — shops, catalogs, inventory and orders as first-class records with clear ownership.

02 — WEFT

What we wove through it

Onto it went the marketplace: vendor onboarding and shop management, product listing with category and inventory control, order tracking on both sides of the sale, secure payment integration, and search and filtering that makes a many-vendor catalog feel like one shop. The admin dashboard runs the whole bazaar.

03 — BEAT

How it was pressed tight

Marketplace code fails at the seams — payment confirmed but stock gone, orders split across vendors, a seller editing a product mid-purchase. Those seams got the review and the tests: inventory is authoritative, payment states drive order states, and no order can exist in a state the machine doesn't name.

04 — WEAR

Life in production

Maniyari operates in production with vendors selling who had never sold online before. Sellers manage products, orders and payments from one screen, buyers get a coherent storefront, and the platform scales by adding vendors, not engineers.

NEXT CASE — 13

GOFLYNT
NEXT.JS · REACT · TAILWIND