How to read an event
An event groups the changes that arrived together: a CSV import, an app or a manual edit. For every field, Reversa shows three values and, from them, what would happen if you undo the event.
What an event is
Changes that Shopify reports within a few minutes and with the same pattern are grouped into one event. An import that changes 300 prices shows up as one event with 300 products, not as 300 separate changes.
While an event is open it can receive more changes for 10 minutes. The alert and the likely source are worked out when it closes.
The three columns: before, after the change and now
- Before
- The value of the field right before the event, according to the catalog copy and Reversa’s history.
- After the change
- The value the event left.
- Now
- The value the field has in the store today. If it differs from "After the change", something changed it after the event.
Comparing the three values is what we call three-way undo: it lets you undo what the event changed without overwriting what was fixed afterwards.
The results: reverts, kept, not touched
- Reverts
- The field still has the value the event left and, according to the history, nobody has touched it since. When you undo, it goes back to its previous value.
- Kept
- Someone changed the field after the event, for example fixing it by hand. Reversa keeps the current value and does not overwrite it unless you choose to. These fields appear at the top, under "Need attention".
- Not touched
- Inventory changes. Stock changes with every sale, so it is recorded for you to see what happened, but it is never reverted.
- Already has its previous value
- The field already went back to its earlier value some other way: there is nothing to write.
If something no longer exists (for example, a deleted product or an image with no copy), the undo screen says so and does not try to restore it.
Likely source and confidence
Shopify does not say who makes each edit. Reversa infers the source from the pattern of the event (many products in a few minutes, the same factor on every price…) and shows it as the likely source: CSV import, manual edit, Shopify admin, an app, or another app or integration.
- High, medium or low confidence
- How sure the inference is. With low confidence, review the event more carefully before undoing.
- Confirmed
- Only appears when Shopify or your team says so. In the event, the question "Who did this?" lets you confirm it; your answer is recorded and helps recognize the same pattern next time.
For inventory changes, Shopify usually names the app or person that adjusted stock, and Reversa shows it when Shopify provides it.
An example
A 15:04 import multiplies the price of 312 products by 100. At 15:20 a teammate fixes 6 of them by hand. In the event, the fields nobody touched show as "reverts", the 6 fixed ones as "kept" and the stock changes of those hours as "not touched". This is an illustrative example with made-up data.
Frequently asked questions
Why is a field marked "kept" if I did not touch it?
Because its current value differs from the one the event left. Another person, another app or a sync may have changed it. Check the "Now" value before deciding.
What does it mean that the event is still open?
That it can receive more changes for 10 minutes. When it closes, Reversa works out the likely source and decides whether to alert. You can close it earlier with "Close event now".