Catalog mode and product permissions

Catalog mode separates who may edit product details from who owns the canonical product name. It complements, rather than replaces, org:products:edit.

Two independent decisions

First, ordinary authorization determines whether the caller may edit the existing product. Second, effective catalog mode and organization type determine whether logistics fields may be changed. With catalog mode off, an authorized editor may edit logistics fields subject to other rules. With it on, only an authorized PARTNER may edit existing-product logistics; create remains open. The dashboard omits inaccessible keys, while the server enforces the rule when logistics keys are present.

The name is a separate domain rule. For catalog STOCK products, the server generates the name at creation and regenerates it on update only when a name component changes. This avoids trusting a client-generated canonical name while also avoiding surprising renames during unrelated edits. The gateway PUT is intentionally separate and never resolves catalog mode or generates names.

Ownership and trade-off

A partner can maintain a shared catalog; vendors consume that catalog and cannot mutate its logistics fields while catalog mode is active. The trade-off is stronger consistency at the cost of vendor-side flexibility. Vendor post-stock locks further prevent changes to identity/logistics fields after inventory exists.

See permissions, field access, and name generation for exact rules.