Rates run out — the check that is not about configuration
A hotel that was ready in August stops being sellable in February. Load rates further ahead.
Every other readiness check asks "was this configured", and configuration does not rot. Rates do.
When a hotel is created, rates are loaded for a horizon — some months ahead, not forever. Then the horizon arrives. A hotel that was perfectly ready in August silently stops being sellable in February, and the first anybody knows is a booking that will not price, taken on the telephone, in front of a guest.
So the Onboarding board asks how far ahead each hotel's rate sheet reaches, and warns before it becomes an outage rather than after.
- The warning appears well before the end, which is the only useful time to see it.
- Extending is an administrator's job: load the next period's rates on the rate plans.
- "4,000 rates exist" is the wrong reassurance when all 4,000 are in the past. Read the date the board shows, not the count.