.How do I fix “Outdated schema detected” after an update?
Most Common Cause
This usually happens after a Shopware update when the database migrations
did not finish correctly. The fastest fix is to run the pending migrations and refresh the DAL schema using
bin/console database:migrate --all followed by bin/console dal:refresh:index. In many
stores, that clears the warning immediately after cache clear and re-login.
Quick Diagnostic — check these first
Rules out: incomplete core or plugin schema updates
Rules out: extensions using old entity definitions
Rules out: stale schema cache or outdated index data
Rules out: timeout or memory issues during update
Rules out: partial deployment or rollback mismatch
Cause 1 Pending database migrations
Shopware compares entity definitions in code against the actual database schema. If migrations stop midway, Shopware sees missing columns, indexes, or table structures and throws the outdated schema warning.
Fix: SSH into the server and run the migration commands again. Use the commands below in order, then clear cache and reload the admin:
bin/console database:migrate --all
bin/console database:migrate-destructive --all
bin/console dal:refresh:index
bin/console cache:clearCause 2 Outdated or incompatible plugins
Third-party plugins often register their own entities and database tables. After a core update, an older plugin version may still expect old schema definitions and trigger the warning even when Shopware core itself is fine.
Fix: Update all plugins first, especially ERP, search, and B2B extensions. Then reinstall or refresh plugin migrations using:
bin/console plugin:update --all
bin/console plugin:refreshCause 3 Cached entity metadata
Sometimes the schema is already correct, but the compiled container or cached metadata still references older definitions. This happens a lot after manual deployments or CI/CD updates without a proper warm-up sequence.
Fix: Fully clear the cache, rebuild the administration if needed, and warm the cache again before testing:
bin/console cache:clear
bin/console cache:warmup
bin/build-administration.shCause 4 Broken deployment or rollback
This is the ugly one. The codebase may already be on the new version while the database is still on the previous release. We see this after failed Composer installs, deployment timeouts, or emergency rollbacks.
Fix: Compare the installed Shopware version in Composer with the migration status in the database. Restore from backup if migrations partially changed production tables. Do not keep rerunning destructive migrations blindly on a live store.
Related Answers
Was this answer helpful?
Your feedback helps us improve our answers.
Still need help?
Talk to our Shopware experts
We've handled GDPR/CCPA compliance for dozens of EU & US Shopware stores.