# BizMtaani launch-readiness status

## Included in this update

- Admin report for service bookings and product orders.
- Inclusive custom date-range filtering using the Africa/Nairobi application timezone.
- Separate service and product metrics, with activity/status/provider/customer filters.
- Provider check-in restricted to the existing secure QR verification route.
- Explicit service-start transition and timestamp before normal completion.
- QR verification method recorded on the check-in event.
- No online payment collection, commission calculation, escrow, or provider payout is enabled.

## Still required before a public launch

The following are not represented as implemented in this archive and need a separate implementation and acceptance pass:

- Auditable manual QR-verification exception request and approval workflow.
- Customer completion confirmation and provider completion-request workflow.
- Full customer/provider no-show reporting, grace period configuration, customer dispute and admin resolution.
- Booking dispute resolution interface and payment hold rules for a future payments phase.
- CSV export for admin report (not included in this update).
- Full browser/device testing and end-to-end testing against the target XAMPP/MySQL installation.
- Live shared-hosting deployment test, SMTP delivery test and backup/restore test.

## Future payments

Future payment integration must remain separate from booking verification. A QR scan proves that the booking credential was presented and validated; it does not prove the service was performed. A future payment release must additionally require service completion and customer confirmation or an audited exception resolution. Payment QR receipts must be distinct from booking verification tokens. Any actual platform-held funds, escrow-like arrangement, refunds and payouts require a supported payment-provider settlement model and appropriate legal/compliance review.

## Deployment safety

Apply migrations to a backup or staging copy first. Preserve `.env`, use strong unique production credentials, set `APP_DEBUG=false`, configure HTTPS and SMTP, and verify private storage is not web-accessible. Do not use demo accounts or seed data in production.
