Every one of these is a field that can be changed with a single click, a single line in a bulk CSV import, or a single API call from a third-party app — and every one has a real cost attached when the new value is wrong.
1. Price
The most direct cost on this list. A price that's wrong sells at the wrong number until someone notices, and every order placed in that window goes out at the mistaken price. A decimal shifted by one place is the classic version of this mistake.
2. Compare-at price
Not the price a customer pays, but the reference price a strike-through discount is measured against. Clearing it accidentally makes a real sale look like it isn't one; setting it incorrectly can make a product look artificially discounted (or not discounted at all) compared to what was intended.
3. Inventory policy
Whether a variant can still be sold once its tracked quantity reaches zero. Flipped on by mistake, a store can sell stock it doesn't have — an oversell that isn't visible anywhere on the storefront until the order can't actually be fulfilled.
4. Status (published / draft)
A product flipped to draft stops selling immediately and silently — no error, no warning, just a product that's no longer visible anywhere a customer would find it. Depending on how it happened, it can go unnoticed until someone asks why sales on that item dropped to zero.
5. Title
An emptied or garbled title is rarely intentional — it's the kind of thing a bad bulk find-and-replace or a broken import produces, and it's immediately visible to any customer who lands on the product page.
6. Description (HTML)
Bulk edits sometimes clear a description before repopulating it, which is often deliberate mid-process — but a description that's emptied and stays that way is a different problem: lost SEO content and a broken-looking product page.
7. Product type
Used for collections, filtering, and reporting behind the scenes. A wrong product type doesn't break the storefront outright, but it can quietly misfile a product out of the collection or filter a customer expects to find it in.
8. Vendor
Routine catalogue admin most of the time, but a wrong vendor value can break vendor-based filtering, reporting, or any automation keyed off that field.
9. Handle
The URL slug for the product. Changed on purpose fairly often (as SEO work), but changed by accident it breaks every existing link and bookmark pointing at the old URL.
10. Tags
Feed into search, filtering, collections, and any automation that reads them. A bulk tag operation gone wrong can silently remove a product from a collection or filter a customer relies on to find it.
11. Availability (derived, not directly set)
Unlike the other ten, nobody sets this one directly — it's derived from whether inventory is tracked plus the current quantity, so it moves on its own as stock changes. It's not revertible the way the others are, because there's no mutation that sets it directly; it simply follows from the fields that do.
The pattern across all eleven
None of these are exotic settings — they're ordinary fields that get touched constantly, by staff, by bulk imports, and by third-party apps. The common failure isn't a dramatic one; it's a routine edit landing on the wrong product, the wrong value, or both, and nobody noticing until it's already cost something. Watching these eleven specifically — rather than everything on a product record — is a deliberate scope: they're the fields where a mistake has a same-day, checkable cost, not a cosmetic one.