Case Study

Sweet & Coffee

Separate Valux delivery for Sweet and Coffee: a Laravel sweets-and-coffee ordering product with its own product scope—not a fork of another client repo. Architecturally it used the same tri-portal pattern Valux often shipped: localized consumer web, JSON under `/api` and `/api/user`, `{lang}/dashboard` for staff, `{lang}/store` for vendors, cart and checkout flows, and mobile-friendly token checks. Original repository is not retained; this case study is reconstructed at pattern level only. The diagram is illustrative of that layout, not a line-by-line export.

LaravelPHPMySQLREST APIMobileMultilingual

Standalone Valux buildTri-portalDelivery domainRepo archived

Impact

Gave Sweet & Coffee its own delivery-ready channel with operational levers comparable to other Valux marketplace launches.

Problem

Sweets and delivery buyers expect fast catalog browse, dependable checkout, and clear handoff to vendors—without operators losing control of menus or stock.

Solution

Built Sweet & Coffee as its own Laravel codebase: web or app clients against shared APIs, staff dashboards for catalog and orders, vendor consoles for fulfillment—domain tuned to food retail and delivery, with clear separation between customer, operator, and vendor surfaces.

Highlighted implementation

Route map (illustrative Valux commerce layout)

PHP

// Typical RouteServiceProvider::map split used on Valux marketplace deliveries:
$this->mapApiRoutes();
$this->mapWebRoutes();
$this->mapAdminRoutes();
$this->mapUserRoutes();
$this->mapStoreRoutes();

Testing & quality

When live: regression around checkout, vendor order lists, and admin price or availability edits; exact PHPUnit version depended on the Laravel generation shipped at the time.

Architecture

API Structure

Tri-portal layout typical of Valux commerce work: public catalog JSON, authenticated user routes for cart, orders, and favorites-style resources, plus admin and vendor Blade areas under locale-prefixed paths.

Data Flow

Customer selection and checkout persist through Laravel into MySQL; vendors adjust offer lines; admins reconcile disputes or outages from one dashboard.

Backend Decisions

Used a full marketplace-style split (customer API, admin, vendor) so delivery workloads had vendor isolation and operator visibility instead of a single anonymous storefront.

Sweet & Coffee architecture diagram — High-level diagram of web dashboard, REST API, Laravel layers, and MySQL.

Challenges

Peak-time ordering spikes and menu changes mid-service window; multilingual campaigns when locale middleware was enabled for that deployment.

Technical Decisions

Standard Valux route map (`mapApiRoutes`, `mapWebRoutes`, `mapAdminRoutes`, `mapUserRoutes`, `mapStoreRoutes`) sized for delivery operations with full admin and vendor surfaces—a distinct project and schema for this brand.