CASE STUDY · SYSTEM

Boutique HolisticHub ERP

Operational ERP for a tailoring / boutique workshop: appointments, alterations queues, MRP shortages, and invoice revenue — Laravel API + Vue SPA.

Live systemProduction systemRead the publication ↓

TECHNICAL PUBLICATION

How it is built

USE CASE

Business challenge

Workshop operations lived in spreadsheets and ad-hoc flows. Staff needed one desk for bookings, alterations urgency, inventory shortages, and client invoicing.

SYSTEM ARCHITECTURE

Architecture & data

HolisticHub pattern: Sanctum-authenticated Vue SPA against a Laravel API. Spatie roles/permissions, branch-aware settings, audit. Dashboard cards for today’s appointments, open/urgent alterations, MRP shortages, and invoice revenue trend.

BACKEND

API design & authentication

Laravel Sanctum SPA tokens, Spatie permission gates on modules, optional Google 2FA on the product family.

IMPLEMENTATION

Implementation & stack

Module CRUD via API resources; Pinia stores; Tailwind admin chrome shared with Clinic HolisticHubPro. Uploads and PDF/CSV exports where the workshop needs them.

SCALING

Performance & operations

Typical VPS PHP-FPM + Nginx + MySQL. Indexes and list APIs rather than loading entire ledgers into the browser.

STACK

As shipped

Delivery packages

7 components

What this system runs on

The stack as deployed for Boutique HolisticHub ERP — chosen for the system's constraints, not for fashion.

LaravelPHP 8Vue 3PiniaSanctumSpatie permissionsMySQL

RELATED WORK

More systems

All systems

ENGAGE

Need a system like this?

Operational platforms, APIs, and AI-integrated systems — scoped as an engineer, with a stack and a boundary.