Product Configuration Does Not Opt Into Custom Fields

Context

The architecture ruling replaces the earlier shared custom-map choice with explicit opt-in capability. The product registration omits that capability.

Decision

Products does not declare custom-field capability, rejects custom values at the HTTP boundary and registers standard read-only metadata, with no custom-field support on prices or setups.

Alternatives Considered

Share one custom-field map across product kinds. The approved opt-in decision supersedes the earlier map design for Accounting products.

Consequences

Specialized application attributes can remain on domain extensions. This design introduces no product custom-field support.