Symptom
Trying to fix a category code: partial PUT and full PUT both return 200 and the value doesn't change. Confirmed in both approved and draft state.
Confirmed case
Dozens of items went through name and brand edits; category code was unchanged on every one. Outerwear was sitting in a phone-accessory category with no way to fix it.
"There is no fix" is the fix
Miscategorized means delete and re-create. And items under review or sanction can't be deleted either, so even that is off the table.
★ Find out which values must be final at creation before you write the creation code. Don't assume "we'll fix it later."
Met the same property on another channel: category ID immutable after creation (NotChangable). When different channels impose the same constraint, it isn't coincidence; it's a property of the domain.
Sub-resources have a different unit
A "stop sales" call on the parent item's path returns 404. Stopping sales and changing stock work only on the child resource (the option-level ID), never the parent. Before reading a 404 as "no such feature," look for the child-resource path. Which unit each operation binds to belongs on the same pre-coding checklist as the values that are final at creation.