Save product corrections against the version read
Purpose
An administrator opens a product and works from the version returned by that read.
How It Works
An administrator opens a product and works from the version returned by that read. Saving submits a replacement with the intended collections and optional values. Another writer’s intervening save causes a conflict instead of a silent overwrite. The console explains that conflict and offers a reload. Retired products require reactivation first. Update locks require an explicit change to the lock before replacement can proceed. Hidden console settings are resent from the loaded product. A failed save preserves the previous product and its collections. Confirmation configuration has its own omission behavior, so integrations need to distinguish replacement from an unchanged setting.
Relationships
This outcome uses create a product with a permanent identity.