Config History shows every change made to your store’s configuration, who made it, when, and exactly what changed. If a change caused unexpected behavior, you can restore any previous version to roll it back.
Prerequisites
- Your store must be connected to Layers.
- You need dashboard access with permission to view store settings.
Open Config History
- In the Layers dashboard, go to Settings.
- Select Config History (under the Access & Security category, or search for “history” in the sidebar).
The page shows a chronological table of every configuration change, newest first.
What is tracked
Config History covers these item types:
- Merchandising rules (including pin positions and expressions)
- Ranking rules (including promote, demote, pin, and sort actions)
- Search rules (including targeting conditions and request modifications)
- Sort orders (including priority rules and soft-boost expressions)
Each entry records:
- Time - When the change happened.
- Type - Which item type was affected.
- Item - The name of the specific rule or sort order.
- Event - Whether the item was created, updated, deleted, or restored.
- Changed fields - Which fields were modified (for updates).
- By - The team member or system actor that made the change.
View change details
- Find the entry in the Config History table.
- Click the View details icon on the row.
- Review the before-and-after diff for each changed field.
The detail dialog shows the exact old and new values side by side, so you can see precisely what changed.
Restore a previous version
- Find the entry for the item you want to roll back.
- Click the History & restore icon on the row.
- In the drawer that opens, browse the full version history for that item.
- Select the version you want to restore and confirm.
Restoring a version creates a new entry in the Config History table with the event restored, so the restore itself is tracked and can be undone by restoring yet another version.
Restoring a merchandising rule version also restores its pin positions. If you have rearranged pins since the snapshot was taken, the restore replaces your current pin layout with the one from the snapshot.
Troubleshooting
The table is empty
Config History starts recording from the point the feature was enabled. Changes made before that date are not captured.
A change does not show the author
Some changes triggered by background processes (such as scheduled sync jobs) may show a system actor instead of a team member email.
Next steps
