Designed for real-world connectivity. Not offline-first. Cloud-enabled with graceful degradation.

Stale-But-Safe Data

When Wi-Fi drops, you see the last confirmed state. Not blank screens.

This is why we show stale data instead of blank screens. The last confirmed state is always safer than no state at all. It prevents guest frustration, keeps operations moving, and reduces errors born from uncertainty.

Queued Actions & Automatic Retry

Staff actions queue locally. Retries happen automatically when you reconnect.

When your internet is poor or offline:

• Check-ins, bed assignments, and housekeeping updates are saved locally on the phone.
• A "pending sync" indicator shows staff what hasn't synced yet.
• When reconnected, Dormaflow automatically retries all pending actions.
• If a retry fails (e.g., the bed was already assigned), you get a clear error and can fix it manually.
• Manual overrides are always available—you can force-correct a stale state yourself.

You're never stuck. There's always a path forward, whether automatic retry works or you need to manually fix something.

OTA Sync Degradation

Your bookings remain visible even if OTA sync is delayed.

Dormaflow syncs to Booking.com, Hostelworld, and other OTAs. When that sync is delayed or fails:

• Dormaflow continues to show your current occupancy in-app.
• OTAs may show outdated availability temporarily.
• A status indicator shows whether OTA sync is active or delayed.
• You can manually trigger a resync anytime.
• Once connectivity recovers, Dormaflow catches the OTA systems up to your actual state.

Double-booking risk is minimized because Dormaflow's internal state is always the source of truth. OTA updates are eventually consistent, not immediate-sync dependent.

Payment Processing During Connectivity Issues

Stripe is required for direct bookings, but you have fallbacks.

Direct bookings through your Dormaflow website require Stripe connectivity to process payments. If Stripe is unreachable or your internet is down:

• The booking page shows a "payment temporarily unavailable" message.
• You can still check in guests with cash or other offline payment methods.
• Dormaflow will notify you when payments come back online.
• Walk-in check-ins work fully offline—only Stripe-processed direct bookings are affected.

You're not blocked from operating. You just can't process card payments until connectivity returns. This is honest about dependencies without pretending magic can happen offline.

Manual Recovery Controls

You stay in control. You can override and fix things yourself.

From the operational dashboard, you can:

• Force-sync OTA channels: Manually trigger a resync if Booking.com is out of date.
• Override bed status: If a bed is incorrectly marked clean or occupied, fix it immediately.
• Clear pending retry queues: If a check-in queued but sync failed, acknowledge and retry manually.
• Reassign occupancy: If occupancy counts drift, recalculate and correct them.
• View audit logs: See exactly what happened and when, for every action.

No waiting for support. No feeling locked out of your own data. You fix it and move on.