Change safety
Exactly what changes in your store, and when
Pricebreeze writes to WooCommerce only after you explicitly approve, only what you approved, and only after re-reading the store to confirm nothing moved in the meantime. Below is the precise mechanism, without generalities.
No write without your approval. No exceptions.
Previous prices are stored before every write.
No product is ever deleted.
Every change is read back from the store after writing.
The review gate
Whatever you do not select never leaves this screen
The review screen shows every price list row next to your product: old cost, new cost, current retail, the margin left, and the price suggested by your own rule. You select row by row or in bulk.
The button always states how many changes will be sent. There is no path through the system that writes to WooCommerce without passing this selection.
In Pricebreeze
214
rows read and matched
In your store
186
only what you approved
At the moment of writing
Four reasons Pricebreeze refuses to write
Even after you approve, the system re-reads your store at the moment it sends. If anything is not as you saw it, the row is excluded and told to you with its reason. It does not try to resolve the difference on its own.
Moisturising cream 200 mlAL-2210
The product is running a sale right now. A new regular price would silently change the discount your customer sees. We leave it alone.
12,9014,50On saleCutlery set, 24 piecesKR-118
The price changed in WooCommerce after you reviewed it. Someone else, or another tool, got there first. Your approval was for a different number, so it is not applied.
8,409,20Changed in storeTravel caseTX-905
The product is no longer in the store. Pricebreeze does not create products and does not guess which other one you meant.
5,60No longer thereSoy candle 180 gNV-034
The change is already live in the store. It is not written again, so your history does not fill up with writes that changed nothing.
Already applied
Excluded rows are not lost. They land in the report with their reason, so you decide what happens to each one.
1Stored before the write
- Regular price
- 12,90
- Sale price
- empty
- Stock status
- in stock
2New price written
12,9014,50
Undo this push
The stored numbers are written back, exactly as they were.
Undo
Restoring is not a promise. It is stored data.
Before writing anything to a product, Pricebreeze stores its current values: regular price, sale price and stock status. This happens per product, before the write, not after.
Undo recalculates nothing. It reads those stored numbers and writes them back. That is why it still works if other changes happened in between.
After the write
Nothing counts as applied until we read it back
After each batch, Pricebreeze reads the products back from WooCommerce and compares them with what it sent. A row counts as verified only if the store returns the price that was written. Writes go out in batches, backing off when the store struggles, so it is never overloaded.
186changes verified
- 186verified in the store
- 4excluded with a reason
- 24rows merged onto a shared product
The same result stays in your history. Undo covers the whole push and stays available for as long as your plan keeps history.
Discontinued products
When it refuses to suggest discontinuation
If a product that matched before is missing from the new file, the supplier may have dropped it. Or they may have sent you a partial file. Three checks keep those apart.
5
Minimum history
Without at least five previous matches for this supplier, no discontinuation is suggested at all. There is not enough knowledge yet.
30%
Too much missing
If more than 30% of what used to match is missing, the likely explanation is a partial file, not half your catalogue disappearing. Suggestions stop.
60%
File too small
If the file carries fewer than 60% of the rows of the previous one from the same supplier, it is treated as an extract. No discontinuation suggested.
And once the checks pass, a suggestion stays a suggestion: the product is proposed as out of stock or draft, goes through the same review as prices, and is never deleted.
Where the AI stops
It reads and recognises. It does not decide.
The AI does one thing here: it turns a messy file into rows with a code, a name and a price. Anything involving money is handled by code that returns the same result every time.
No arithmetic from the model
Retail prices come only from your own rule: a multiplier or a target margin, with the rounding you chose. Amounts live in whole cents, never in floating point.
A file is data, never instructions
If a cell contains text that looks like an instruction to a model or a spreadsheet formula, the row is flagged and sent to the ones needing attention. Nothing is ever executed.
A bad read is never learned
A supplier's layout is stored only after an import you approved. A file that was read wrong and cancelled leaves no trace in memory.
Uncertainty becomes a question
A cost change above 50%, a margin above 90%, a negative cost, a price that can be read two ways: all flagged and placed first on the review screen instead of being guessed.
What else is worth knowing before you connect a store
See it on a file before you connect anything
You should not have to trust a tool with your store just to find out how it works.
No card. Cancel any time.