Events Marketplace
Daawa
Event and wedding equipment marketplace on a Valux Laravel 5.7-style marketplace stack: mobile-led JSON APIs, `/api/user` account flows, localized admin dashboard, vendor store portal, and MySQL-backed catalog—adapted for rentals and logistics-heavy SKUs. Original codebase is unavailable; narrative is inferred from that Valux marketplace pattern only. The diagram shows the generic five-route layout, not a line-specific export for Daawa.
Problem
What was broken
Event planners need discoverable inventory and dependable reservation or order states without opaque phone tag.
Solution
How we fixed it
Implemented the standard Valux split so equipment listings, customer inquiries, and vendor stock lived under familiar route and middleware boundaries—tailored to events and weddings.
Challenges
What made this hard
Rental calendars, damage deposits, or transport logistics vary by SKU; keeping the data model flexible without abandoning the shared Valux conventions.
Architecture
How the system is shaped
API Structure
Guest catalog and messaging-style JSON surfaces plus authenticated user APIs; admin routes for categories, products, requests, and user controls; vendor routes for store inventory and orders—pattern-level only without the lost repo.
Data Flow
Clients pull equipment categories and availability from APIs → bookings or orders persist centrally → vendors and admins reconcile fulfillment or disputes.
Backend Decisions
Matched Valux marketplace defaults (token-checked mobile, localized dashboards) so operational staff could reuse internal playbooks from similar Valux deliveries.
Decisions
Why this stack and shape
Stayed on the lightweight 5.x Valux footprint for speed to market; Collective-style forms in admin where comparable Valux projects used them.