All sale items reverted back to old price.

Technical Q&A
1

Hi there!

Today, all our products on “sale” reverted back to the original price. My team and I didn’t do this. We had set a sale and compare price over a week ago.

Additionally, product names have changed back to how we entered them in our system but we had changed this view on the website.

We are very stuck and need help urgently please!

2

Things don’t change without something triggering it, so there are a few things to be looking at. If it was a single item that had changed I’d think a staff member was part of that. Since it’s not a single item, and you’re suggesting content has also reverted it makes me assume you’ve got some product management app, an ERP, third party POS connector - or something - in place. Do you have something that syncs data from another system?

That’s what I would look into first, along with any app you have installed that can modify products.

3

Hello @frankiemcleod ,

There is already a good answer in this thread - do you use any 3rd party solutions to manage product information and prices?

Regards,
Anastasia

4

Hi Jason!

Thank you for replying to me.
No we don’t have a third party in place.
Many product descriptions have also been taken out of the website and names have changed… it’s very bizzare!
A staff member hasn’t done it either. We are trying to manually change it all back, but again a few things keep changing.

Thank you for your help,

Frankie

5

Hi Anastasia,

No we don’t have any third party involvement.

It’s really weird.. and not tot mention stressful!

Thank you,

Frankie

6

Hello @frankiemcleod ,

So the last option is that there was set a limit (final date) for sale prices. This can explain prices, but not the product names. No other ideas.

Regards,
Anastasia

7

Hi @frankiemcleod,

I found your thread where all sale prices unexpectedly reverted and your team had to restore them manually, while some values continued changing.

Did you ever identify what triggered it?

I’m researching safer Shopify pricing workflows. What would have helped most at the time: a change audit showing exactly what caused it, an alert when prices diverged, or a selective rollback to a known-good state?

8

@souffhy95 of your three, the selective rollback is the one that would have ended Frankie’s week, and it depends on the first: you cannot roll back to a known-good state unless something kept that state.

Reading the original symptoms with that in mind: sale prices, compare-at prices, titles and descriptions all going back to older values at once is not a sale end date. It is a whole product record being written from an older copy. Something held its own version of the catalogue and pushed it. A CSV re-import, or a sync that was disconnected and reconnected, does exactly this, and the product timeline in admin shows “updated via API” at the minute it happened.

An alert on divergence is useful, but it also needs a baseline to diverge from, so the baseline is the thing to build first: a stored copy of each product, per field, with the time. With that, “what changed” is a comparison, the fix is a write of only the fields that moved, and you see the list of writes before you approve it. That is the model StoreVault runs on: versions kept as products change, a plan shown before any restore, and overwritten fields can be undone afterwards.