# Yatoon 4.4.1 multi-store validation

Run this checklist on at least three staging sites with different themes, caching stacks, staff counts, and Square accounts. Do not use real card details or customer data on staging.

## Before testing

1. Open **Yatoon Booking > Operations > Reliability**.
2. Create a database snapshot and download diagnostics.
3. Record WordPress, PHP, theme, cache/CDN, timezone, Square location, staff count, and service count.

## Required flows

- Fresh install and upgrade from the previous production version.
- Connect Square, run Sync bookings, and verify the Square sync health card.
- Create a one-service appointment and confirm it in Yatoon calendar and Square Calendar/POS.
- Add a sequential service that uses another employee; verify staff, service order, total time, and success message.
- Try adding a service past closing, across a break, on a Closed Date, with a busy employee, and with an exhausted shared resource; every case must be rejected without changing Square or local rows.
- Submit the same Change Services request in two browsers; only one request may write.
- Reschedule, partially cancel, fully cancel, take payment, and verify reminders.
- Verify desktop Chrome/Edge, iPhone Safari, Android Chrome/Samsung Internet, and the active WordPress theme.
- Disconnect the network during a sync, restore it, retry the failed job, and verify recovery.
- Restore the database snapshot on staging and confirm counts and schedules.

## Evidence to retain

- Before/after diagnostics JSON.
- Screenshots of Yatoon and Square appointment segments.
- Exact local time, timezone, service duration, assigned staff, and Square booking ID.
- Any failure message with secrets and customer details removed.

Production rollout requires all required flows to pass on every participating staging site.