yunior1250/carwash-mockup

Purpose and delivery model

This is a static Spanish-language business/POS interface for a car-wash (“lavadero”) operation, including cashier workflows, customer history, expenses, reporting, and SaaS administration. The application is delivered as standalone HTML pages with shared styling; no server, package manifest, or backend service is present in the repository.

Entry points and navigation surfaces

index.html is the likely public/root entry point. Operational navigation appears centered on panel.html and selector-lavadero.html, which likely select an operating location before entering cashier and service workflows. SaaS-level navigation is separated into dedicated administrative pages such as saas-lavaderos.html.

Paths:

• index.html

• panel.html

• selector-lavadero.html

Operational transaction workflow

The core business flow appears to be: register a wash/service, collect payment, manage cash closure, and settle totals. registrar-servicio.html captures service activity; cobro.html handles payment; cierre-caja.html closes the cash register; and liquidacion.html supports settlement/reconciliation. anticipo.html and gasto.html represent cash movements that affect the register outside ordinary service payments.

Paths:

• registrar-servicio.html

• cobro.html

• cierre-caja.html

Customer and receivables domain

Customer-facing records and debt tracking are explicit parts of the product boundary. historial-cliente.html provides prior customer/service visibility, while deuda-personal.html covers outstanding personal debt or credit balances. These pages are downstream consumers of service and payment records, even though persistence implementation is not visible here.

Paths:

• historial-cliente.html

• deuda-personal.html

• cobro.html

Reporting and data portability

Business review is represented by reportes.html, while exportar-datos.html exposes data extraction/export. These are reporting boundaries: transactional screens produce the operational records; report/export screens aggregate or serialize them for users or external analysis. No database, API client, or export format implementation is evident from the supplied tree.

Paths:

• reportes.html

• exportar-datos.html

• cierre-caja.html

SaaS tenancy and administration

A distinct SaaS administration area models multi-tenant organizational structure and access control. saas-lavadero-alta.html likely onboards wash businesses, saas-lavaderos.html manages them, saas-sucursales.html handles branches, and saas-permisos.html controls permissions. saas-cuentas.html and saas-marca.html suggest account and branding administration. This is conceptually separate from day-to-day cashier operation but supplies the tenant/location/user context it requires.

Paths:

• saas-lavaderos.html

• saas-sucursales.html

• saas-permisos.html

Shared presentation and build-related scripts

estilos.css is the only visible shared frontend asset and is therefore the primary visual consistency boundary across pages. capturar.py and construir.py are the only non-HTML/CSS files; their names suggest screenshot/capture and build/generation automation, but their roles cannot be confirmed without contents. There are no visible runtime dependencies, cloud infrastructure definitions, databases, or external service integrations.

Paths:

• estilos.css

• capturar.py

• construir.py