Muebles JYN Control
Before this system, operations were handled in spreadsheets and scattered records. That caused information loss, slow manual lookups, and low visibility over project status and payment follow-up. The platform centralizes everything in one place with a clear operational view for administrators and staff.
Challenge
The administration workflow depended mostly on spreadsheets and manual controls, with data-loss risk and no reliable visual view of project progress or payment tracking.
Solution
Built an internal platform with a visual dashboard, status filters, progress logs, project-level payment tracking, and Google Drive integration. Added role-based access (ADMIN/OPERATIVO) and action auditing to improve operational control and traceability.
Results
- - Centralized project, client, and delivery control instead of disconnected spreadsheets
- - Better visibility for administrators over project status and payment flow
- - Lower information-loss risk and less time spent on manual searches
- - Financial summary per project with clear payment tracking
- - Solid functional base for real daily operations
Technical system profile
Overview
Muebles J&N Control is an internal system for daily furniture business operations: projects, customers, payments, progress logs, Drive files, and calendar with role permissions.
Problem solved
- - Centralizes commercial and production operations in one panel
- - Standardizes project follow-up for status, dates, payments, and documents
- - Reduces manual work with Google Drive and unified calendar integration
- - Improves administrative control with audit logs and user management
Stack and technologies
- - Next.js (App Router)
- - React 19
- - Tailwind CSS
- - Prisma
- - PostgreSQL
- - Better Auth
- - Google Drive API OAuth2
How it is organized
- - src/app: routes and screen composition
- - src/features: domain modules (projects/customers/events/auth/audit)
- - src/lib: shared infrastructure (auth, prisma, drive)
- - src/shared/server-actions: authorization and result wrappers
Main workflow
- - User interaction in UI triggers a Server Action
- - Input and role permissions are validated
- - Domain service/use-case executes business logic
- - Data is persisted in Prisma or files are managed in Drive
- - Route/state revalidation and UI feedback are returned
Key modules
- - Projects: CRUD, payments, progress logs, files, financial dashboard
- - Customers: create, update, archive, tax data
- - Calendar: project deliveries plus manual events
- - Auth/Admin: login, ADMIN/OPERATIVO roles, user management
- - Audit: traceability for critical actions
Strengths
- - Clear and maintainable domain-based architecture
- - Consistent role-based authorization
- - Real business integrations
- - Quality workflow with lint/typecheck/tests
Risks / technical debt
- - Possible partial states if Drive or DB fails mid-operation
- - Some actions return limited error feedback
- - No visible active scheduler for EventReminder
- - Missing deeper e2e/integration test coverage
Do you need to build or improve a software system?
I can help you translate business needs into a robust, maintainable technical solution.