Language Fallback
Fallback behavior is implemented in practical query and route-resolution paths, especially around translated slugs and locale-aware entity loading.
Language Fallback Rules
How it works in the app
I did not find a broad admin-facing fallback policy engine, but fallback-like behavior exists where it matters operationally. Webshop product resolution can fall back from base slug lookup to translated slug lookup, and repositories pass locale hints for translatable queries.
So the current implementation is best described as translation-aware querying with practical fallback behavior rather than a separate configurable fallback product.
Included in the current implementation
Locale hints on translated queries
Translated slug lookup in webshop routes
Primary-locale-first save flows
Practical fallback in key access paths
Need localization behavior that still resolves the right content when translations vary?
Indexed PIM already uses translation-aware lookup logic in the places where fallback matters most.