Storat
A pre-launch marketplace prototype exploring vendor catalogues, B2B accounts, shipping, reviews, fraud checks, and a visual page builder while its tenancy architecture is being redesigned.
- Problem
- A multi-vendor marketplace must separate each seller's data while also supporting operator, seller, shopper, and business-buyer workflows.
- Approach
- The current prototype validates marketplace workflows and a commerce-aware page builder. Tenant isolation and the production backend are being redesigned and are not presented here as launch-ready.
The problem in context
A multi-vendor marketplace has to support different roles without confusing their responsibilities. Operators, sellers, shoppers, and business buyers each need a different view, while seller data must remain separated before the system can be treated as production-ready.
Who it is for
The current prototype explores vendor catalogues, B2B accounts, shipping, reviews, fraud checks, and operator and buyer workflows. These flows are being used to test the product model rather than to claim a launched marketplace.
One decision being tested
The prototype includes a visual page builder with commerce-aware blocks such as product grids, collection rows, and offer bands. This tests whether a seller-facing editor can remain useful without detaching page composition from catalogue data.
Current boundary
Tenant isolation is a production requirement under active redesign; the current prototype must not be treated as proof that the boundary is complete. The production backend is also being redesigned.
From the product
The Storat storefront home page — a full-width hero over a row of shipping, payment and returns badges.
Have something to build?
Email us in Arabic or English, whichever is easier, or call us directly.
Contact detailsDirect contact
- contact@jiwar.io
- +962 7 9174 8028
- Amman, Jordan