A price in that update had fallen too far to be a real cut.

The message on your screen: “Batch would cut a price below the collapse floor” (HTTP 422)

What it means

One product in that update was priced at less than 5% of what that line has been worth. A drop that steep is far more often a decimal point in the wrong place than a sale, so the whole update was refused; nothing in your catalogue changed, and your shop window goes on serving what it already had.

What to do next

1. Read the detail under the status on the app's Overview: it names the product, the price your update carried, and the price it was judged against.
2. If the new price is a mistake in Odoo, correct it there and press Send an update now.
3. The price it is judged against is whichever is higher: the price that line carries now, or the highest price it has carried in the last thirty days. So a very deep cut needs both of them to come down.
4. If you did mean to cut that deep, take it down in steps. Each step becomes the price the line carries, and the deepest step lands once the old high is more than thirty days behind you.
5. A price that line has already been priced at, or below, inside those thirty days is never refused, so putting an old sale price back always goes through.
6. If the price named looks right to you and the update is still refused, send your connection reference and the product code through the contact form (zaltric.com/contact).

Still stuck?

The section “When something goes wrong” on the help page explains every message this screen can show. If that does not solve it, send us the whole message and your connection reference (shown on the app's Settings screen) through the contact form.