Case Study

Larapee

Unified ERP, POS, and ecommerce operations platform

LaravelReact NativeReactRabbitMQDocker

Role

Led full-stack delivery across backend architecture, dashboard UX, and mobile integration contracts to keep business workflows consistent across channels.

Timeline

2024 - Present

Screens

Larapee admin operations dashboard — 01
Admin Control Center
Operations dashboard view for cross-branch sales, low-stock signals, and queue health in one command surface.
Admin operations screen (architecture-aware dashboard layout).
Click image to view full size.

Larapee mobile delivery workflow design — 02
Mobile Client Experience
Role-based mobile UX for delivery and customer flows, including order pickup state, route updates, and confirmation actions.
Mobile design direction for production workflow screens.
Click image to view full size.

Larapee event-driven architecture diagram — 03
Event-Driven System Flow
Illustrates how POS transactions are queued, consumed, and synchronized into ERP reporting and realtime operational surfaces.
Architecture diagram: POS -> Queue -> ERP + Mobile + Dashboard.
Click image to view full size.

Overview

Larapee is an end-to-end operating platform for retail teams. It connects point-of-sale activity, inventory movement, purchasing, and ecommerce into one reliable workflow so operations can execute faster with fewer reconciliation issues.

Product Context

The product serves teams that need a daily operating system for sales, stock, and reporting. The core requirement is consistency across channels: branch POS, central admin, and mobile-facing workflows.

Primary Goals

Keep POS operations responsive during heavy sales periods.
Synchronize operational events into ERP analytics with minimal delay.
Provide role-aware interfaces for cashier, manager, and operations teams.
Maintain a deployment model that is repeatable in local and production environments.

Architecture

Laravel 12 API and domain layer backed by MySQL for core transactional data.
Redis used for cache and queue-adjacent performance support.
RabbitMQ event pipeline to stream POS events into downstream ERP and reporting flows.
Inertia.js with React + TypeScript for back-office dashboard UX.
Two React Native clients consuming Laravel APIs for role-specific mobile workflows.
Dockerized services for deterministic environment setup and CI parity.

Larapee Monorepo App Surfaces

This project is delivered as multiple product surfaces in one repository. Each app has different user responsibilities and reliability requirements.

apps/pos-electron

Enterprise desktop POS client with offline-first outbox, auto sync, and manual retry flow.

apps/customer-mobile

React Native customer app for catalog browsing, cart flow, and order tracking.

apps/delivery-mobile

React Native delivery app for shipment workflow, location updates, and proof handling.

Responsibilities

Designed and implemented bounded contexts for sales, inventory, and reconciliation.
Defined API contracts and validation rules shared between web and mobile clients.
Built operational dashboards with attention to readability under high information density.
Implemented queue-driven synchronization handlers and retry-safe worker flows.
Reviewed schema and index design to keep reporting queries performant.

Challenge Deep Dive

Event ordering across distributed sales sources

Situation

Different POS terminals could emit bursts of events under unstable network conditions, creating potential ordering conflicts.

Solution

Introduced idempotent consumers, deterministic event keys, and replay-safe handlers in the RabbitMQ processing path.

Impact

Reduced reconciliation inconsistencies and improved trust in near real-time analytics.

Web and mobile feature parity

Situation

Role-specific flows evolved quickly and risked divergence between dashboard and mobile surfaces.

Solution

Centralized contracts at API and domain layers, then aligned UI states around shared business statuses rather than screen-local assumptions.

Impact

Improved delivery speed while keeping behavior consistent across clients.

Production Safety Notes

Service/action separation keeps heavy business logic out of controllers.
Sync status is explicit (`syncing`, `success`, `failed`) with retry-safe re-entry guards.
Push listeners are queue-backed and deduped via short-lived cache locks.
API order creation supports idempotency keys to prevent duplicate writes.
Rate limiting, lockout handling, branch-scoped access, and security headers are applied.
CORS is allowlist-based with strict `CORS_ALLOWED_ORIGINS` configuration.
Storefront query path is bounded and filterable for predictable performance.

Pre-Production Checklist

Set strict `CORS_ALLOWED_ORIGINS` for real domains only.
Run at least one queue worker (`queue:work rabbitmq ...`).
Set `APP_DEBUG=false` in production.
Keep DB and RabbitMQ management ports private.
Use HTTPS and validate HSTS behind reverse proxy.

Quick Start Paths

Backend

.env

docker compose up -d app web db rabbitmq

php artisan migrate --seed

POS desktop

cd apps/pos-electron && npm install && npm run dev

Customer mobile

cd apps/customer-mobile && npm install && npm run start:lan

Delivery mobile

cd apps/delivery-mobile && npm install && npm run start:lan

Outcomes

More reliable real-time visibility from POS actions to management dashboards.
Faster onboarding for new environments due to standardized Docker setup.
Cleaner operational workflows for role-based daily usage.

Learnings

Operational software quality depends more on consistency than visual polish alone.
Clear domain language across teams reduces both bugs and discussion overhead.
Queue systems need first-class observability from day one, not as an afterthought.

Back to Projects Source

Case Study

Larapee

Unified ERP, POS, and ecommerce operations platform

LaravelReact NativeReactRabbitMQDocker

Role

Led full-stack delivery across backend architecture, dashboard UX, and mobile integration contracts to keep business workflows consistent across channels.

Timeline

2024 - Present

Screens

Overview

Product Context

Primary Goals

Keep POS operations responsive during heavy sales periods.
Synchronize operational events into ERP analytics with minimal delay.
Provide role-aware interfaces for cashier, manager, and operations teams.
Maintain a deployment model that is repeatable in local and production environments.

Architecture

Laravel 12 API and domain layer backed by MySQL for core transactional data.
Redis used for cache and queue-adjacent performance support.
RabbitMQ event pipeline to stream POS events into downstream ERP and reporting flows.
Inertia.js with React + TypeScript for back-office dashboard UX.
Two React Native clients consuming Laravel APIs for role-specific mobile workflows.
Dockerized services for deterministic environment setup and CI parity.

Larapee Monorepo App Surfaces

This project is delivered as multiple product surfaces in one repository. Each app has different user responsibilities and reliability requirements.

apps/pos-electron

Enterprise desktop POS client with offline-first outbox, auto sync, and manual retry flow.

apps/customer-mobile

React Native customer app for catalog browsing, cart flow, and order tracking.

apps/delivery-mobile

React Native delivery app for shipment workflow, location updates, and proof handling.

Responsibilities

Designed and implemented bounded contexts for sales, inventory, and reconciliation.
Defined API contracts and validation rules shared between web and mobile clients.
Built operational dashboards with attention to readability under high information density.
Implemented queue-driven synchronization handlers and retry-safe worker flows.
Reviewed schema and index design to keep reporting queries performant.

Challenge Deep Dive

Event ordering across distributed sales sources

Situation

Different POS terminals could emit bursts of events under unstable network conditions, creating potential ordering conflicts.

Solution

Introduced idempotent consumers, deterministic event keys, and replay-safe handlers in the RabbitMQ processing path.

Impact

Reduced reconciliation inconsistencies and improved trust in near real-time analytics.

Web and mobile feature parity

Situation

Role-specific flows evolved quickly and risked divergence between dashboard and mobile surfaces.

Solution

Centralized contracts at API and domain layers, then aligned UI states around shared business statuses rather than screen-local assumptions.

Impact

Improved delivery speed while keeping behavior consistent across clients.

Production Safety Notes

Service/action separation keeps heavy business logic out of controllers.
Sync status is explicit (`syncing`, `success`, `failed`) with retry-safe re-entry guards.
Push listeners are queue-backed and deduped via short-lived cache locks.
API order creation supports idempotency keys to prevent duplicate writes.
Rate limiting, lockout handling, branch-scoped access, and security headers are applied.
CORS is allowlist-based with strict `CORS_ALLOWED_ORIGINS` configuration.
Storefront query path is bounded and filterable for predictable performance.

Pre-Production Checklist

Set strict `CORS_ALLOWED_ORIGINS` for real domains only.
Run at least one queue worker (`queue:work rabbitmq ...`).
Set `APP_DEBUG=false` in production.
Keep DB and RabbitMQ management ports private.
Use HTTPS and validate HSTS behind reverse proxy.

Quick Start Paths

Backend

.env

docker compose up -d app web db rabbitmq

php artisan migrate --seed

POS desktop

cd apps/pos-electron && npm install && npm run dev

Customer mobile

cd apps/customer-mobile && npm install && npm run start:lan

Delivery mobile

cd apps/delivery-mobile && npm install && npm run start:lan

Outcomes

More reliable real-time visibility from POS actions to management dashboards.
Faster onboarding for new environments due to standardized Docker setup.
Cleaner operational workflows for role-based daily usage.

Learnings

Operational software quality depends more on consistency than visual polish alone.
Clear domain language across teams reduces both bugs and discussion overhead.
Queue systems need first-class observability from day one, not as an afterthought.

Larapee

Screens

Admin Control Center

Mobile Client Experience

Event-Driven System Flow

Overview

Product Context

Primary Goals

Architecture

Larapee Monorepo App Surfaces

Responsibilities

Challenge Deep Dive

Event ordering across distributed sales sources

Web and mobile feature parity

Production Safety Notes

Pre-Production Checklist

Quick Start Paths

Outcomes

Learnings

Larapee

Screens

Admin Control Center

Mobile Client Experience

Event-Driven System Flow

Overview

Product Context

Primary Goals

Architecture

Larapee Monorepo App Surfaces

Responsibilities

Challenge Deep Dive

Event ordering across distributed sales sources

Web and mobile feature parity

Production Safety Notes

Pre-Production Checklist

Quick Start Paths

Outcomes

Learnings