What I owned
- Marketplace product architecture
- Storefront and shop-discovery experience
- Backend and admin workflow direction
- Variant, inventory, promotion, and order modeling
02 / Marketplace venture
SUQO
My pre-launch marketplace venture for Bangladesh, spanning customer discovery and the operational systems behind shops, catalogue, stock, orders, and returns.
Marketplace ventureSUQO
ShopsCatalogueVariantsMediaInventory
Overview
The screen is only one part of the product.
- Problem
- A marketplace is not a larger product grid. Shop ownership, variants, stock, promotions, and order states must remain coherent as the system grows.
- Product
- A substantially built storefront and operations system designed around multiple shops, a unified catalogue, customer and account flows, checkout, and admin control.
- My role
- Product architecture, storefront UX, backend structure, admin workflows, and commerce data modeling.
- Outcome / status
- A substantially built pre-launch marketplace venture now progressing toward shop and merchant onboarding.
Ownership
What I carried across the line.
Systems involved
- Shops
- Catalogue
- Variants
- Media
- Inventory
- Cart
- Checkout
- Accounts
- Promotions
- Coupons
- Orders
- Returns
- Admin operations
Stack in context
- Next.js
- Laravel
- Filament
- MySQL
- APIs
Product judgment
Decisions, constraints, and verification.
Important decisions
- 01Model ownership and inventory rules before polishing the storefront.
- 02Separate customer-facing simplicity from operational complexity.
- 03Design order and return states as workflows, not labels.
Constraints
- Stock consistency across shops
- Seller permissions
- Operational clarity as catalogue volume grows
QA / deployment thinking
- Variant and stock edge cases
- Role and ownership checks
- Order-state and return-path scenarios