Operations, delivery, inventory, admin controls, and ecommerce management.
A deeper look at what TMS already covers.
This page exists for serious prospects who want to understand scope before they talk. The platform is not one dashboard with a few labels; it is a layered operating system across intake, workflow, workforce, delivery, inventory, and growth.
Execution-facing modules for attendance, notices, tasks, payroll, and floor visibility.
Modules that connect management actions with what teams actually do on the ground.
Core Boutique Operations
Main boutique/tailor workflow modules used in admin dashboard and staff app.
Create and manage boutique orders, alteration requests, QR labels, and measurement slips.
Ecom catalog/order management in admin dashboard.
Task tracking, staff execution, task discussions, and order workflow visibility in the staff app.
Allocate order tasks/sequences to staff.
Dispatch handoff, tracking, delivery workflow, and delivery status handling.
Inventory module and stock tracking screens.
Reusable media library references for orders, tasks, measurements, and masters.
Chat and internal communication features.
Staff notice board and notices listing.
Staff Workforce & HR
Attendance, leave (including approvals), payroll, and staff operations used in web admin/staff app.
Staff profiles and staff master management.
Mark/view attendance and attendance dashboard.
Leave requests and leave approval workflow (single toggle).
Implemented: Separate toggle for leave approval workflow.
Payroll processing, salary management, and staff payslip screens (single toggle).
Implemented: Staff salary view and payslip access.
Face-based attendance feature.
IP-restricted attendance feature.
Location/geofence attendance controls.
Office location setup and advanced attendance support (geofence/IP/location-based attendance configuration).
Partially implemented: Break time tracking and management (settings/API ready, full UI pending).
Partially implemented: Database/API infrastructure ready; full expense workflow pending implementation.
Partially implemented: Database/API infrastructure ready; full document system pending implementation.
Optional / Future Business Features
Useful future add-ons for boutique growth. Implementation status clearly marked.
Partially implemented: Admin data utilities for CSV import/export (basic functionality exists).
Partially implemented: Server-side backup system (basic functionality exists).
Modules are not just static labels in the UI.
The SaaS platform can control tenant entitlements, so different clients can run different module combinations.
This matters because not every boutique needs the exact same operating depth from day one.
It also means the commercial story is stronger: onboarding can start with the right scope and grow later.
If the scope looks right, the next move is a guided conversation.
The best next step is not guessing from a page forever. It is a short discussion about your order flow, team structure, current tooling, and which modules matter first for your boutique.