You need permission to view upsell strategies.
Version history is a read-only investigation tool. It does not restore an earlier strategy for you.
Recent history is retained for up to 120 days and the page loads up to 100 recent entries.
Deleted strategy history may be available only while it remains inside the retention period.
In the Shopify admin, go to Apps > Order Editing.
Select Upsell Strategies.
Open the strategy you want to investigate.
Open the strategy action menu.
Select Open version history.
The Version history page shows a timeline of recent events for that strategy. Each entry includes the event, a summary, when it happened, and the fields that changed when those details are available.
Review the newest timeline entries first.
Use search to find an event by summary, user, or field name.
Select an entry to open its historical details.
Check who or what made the change and when it occurred.
Compare the values in the available views.
The timeline can include strategy creation, publishing, moving back to draft, archiving, scheduling, targeting changes, module changes, discount changes, detail changes, split-test events, and deletion events.
Automated or assisted changes may identify the system or workflow responsible instead of an individual staff member.
Use the detail tabs to understand what was stored around an event.
View | What it shows | When to use it |
|---|---|---|
After | The recorded strategy values after the event | Confirm the configuration produced by the change |
Before | The recorded values before the event | Identify what was replaced or removed |
Raw JSON diff | A technical field-level comparison | Give support or a developer exact evidence when the formatted view is not enough |
Not every event has both before and after values. Creation may have only an after state. Deletion may have only the last available state. Older or incomplete records may contain fewer details.
Order Editing can provide a plain-language summary of a recorded change. Use it as a quick guide, then verify important details in the actual field comparison.
A status-change card can show when a strategy moved between Draft, Live, Scheduled, Archived, or another supported state. This is useful when investigating why a customer stopped receiving an offer even though the product configuration did not change.
Check the recorded time alongside scheduling and market settings. Store time zone, scheduled start and end times, and the moment a staff member published a strategy can all affect what customers received.
Version history does not include a restore button. If you need to return to an earlier configuration:
Open the historical entry that contains the desired state.
Record the relevant placement, market, targeting, products, offer, design, and advanced settings.
Return to the current strategy in a separate tab.
Move the strategy to Draft or pause customer traffic if your change process requires it.
Manually update the current fields to match the approved historical values.
Save the strategy.
Preview and test the experience.
Publish the strategy only after the recreated configuration is correct.
Be careful with products, collections, customer segments, selling plans, or extensions that no longer exist. A historical value can be valid evidence of what was configured without being valid for the store today.
Identify the order time and the strategy that was expected to match.
Open that strategy's version history.
Find changes shortly before and after the order time.
Check status, scheduling, placement, market, targeting, module order, products, discount, and advanced settings.
Compare the history with the order's market and customer details.
Review the strategy matching information and order events for the same time.
Version history shows changes to the strategy. It does not by itself prove that the strategy matched a particular customer. Use order and matching evidence alongside it.
Make a small, approved change to a draft test strategy.
Save the strategy.
Reopen Version history.
Confirm a new event appears.
Open it and verify Before and After show the expected field change.
Revert or complete the test strategy through the normal editor.
History can take a short time to appear after a save. Refresh the page before assuming an event is missing.
No. The history view is read-only. Use the recorded values to manually recreate an approved earlier configuration.
Version records are retained for up to 120 days. The page retrieves up to 100 recent entries, so high-change strategies can reach the entry limit sooner.
It may be outside the retention period, beyond the 100-entry view, or from before that field was recorded. Confirm the time range and contact support if a recent expected save is absent.
Not necessarily. Treat the summary as an overview and use Before, After, and Raw JSON diff for the recorded detail.
The entry shows the available actor information. Some automated, migrated, or system-generated events may not identify an individual staff member.
