2015
Lenzera — videographer marketplace
Three portals, booking, pricing and payments.
Full-stack developer
The challenge
Connect multiple user roles with ordering and payment workflows in a single product.
What I built
- Developed interfaces and backend features across three portals.
- Worked on pricing, chat and payment flows.
Results
- Implemented core marketplace modules across three user portals.
Components & connections
User portals
- Customer portalVideo production orders and communication with the videographer.
- Videographer portalVideographer order workflow.
- Admin portalMarketplace administration.
Shared order model
- Orders & bookingA shared order model across all three portals.
Commercial operations & data
- Pricing & paymentsOrder pricing and payment workflows.
- ChatCommunication between order participants.
- Marketplace dataShared product data in MySQL.
- Customer portal→Orders & bookingorder
- Videographer portal→Orders & bookingorder workflow
- Admin portal→Orders & bookingmanagement
- Orders & booking→Pricing & paymentspayment
- Orders & booking→Chatdiscussion
- Orders & booking→Marketplace datadata
Engineering takeaway
Context
A marketplace with customer, provider and administrator interfaces.
- Consistent order logic across different user roles.
Approach
Connected the user portals through a shared model of orders and commercial operations.
- Separate role-specific interfaces around a shared order model.
Lessons & resources
- Different role interfaces must rely on one consistent domain model.
- Lenzera case study ↗
Marketplace case study published by Tepia.
Stack
- Laravel
- jQuery
- MySQL