Fallback mode
Fallback is optional replacement UI when live availability checkout should not take over— outages, quota limits, or a deliberate contact-first workflow.
Configure it under Booking Engine → Checkout & fallback.
Master switches
| Setting | Meaning |
|---|---|
| Enable fallback | Turns fallback features on globally (individual triggers still apply). |
| Always use fallback | Forces fallback even when quotes succeed—useful for brochure sites that never push visitors into instant booking. |
Presentation modes
| Mode | Visitor sees |
|---|---|
| Inline content | Rich text/HTML configured in WordPress—shortcodes allowed inside it. |
| Link only | A single prominent button linking to your contact page or booking policy PDF. |
When fallback triggers automatically
Separate checkboxes decide whether fallback replaces booking UI when:
- Quote empty / no inventory (
bec_fallback_empty_quote). - Provider errors belong to categories such as rate limiting, authentication failures, quota issues, validation problems, server errors, etc.
If categories do not match your scenario, visitors might see neither fallback nor checkout until you adjust triggers—see Common issues.
[bec_fallback] vs automatic injection
| Mechanism | Placement |
|---|---|
[bec_fallback] shortcode | You decide exactly where fallback markup appears—sidebar, footer, page builder zone. |
| Automatic append on singular units | Plugin filters page content after fetching quotes—shows fallback instead of booking CTA when rules match. |
Multilingual sites (WPML / Polylang)
Two option-backed strings on Checkout & fallback are registered for translation when WPML or Polylang is active:
- Fallback link label.
- Fallback inline HTML content.
After you save those fields, translate them in WPML String Translation (context Booking Engine Connector) or Polylang’s string UI. Locale selection for provider calls can be adjusted with the bec_provider_locale filter—see Post meta reference pointers for developers.