Catalog Product Records Across Commerce Facets

Context

Planning groups the product as one broad noun, while the service module boundary follows presentation versus purchase-participant responsibilities.

Decision

Catalog and Merchandise share one product concept inside Commerce while owning its presentation and goods facets separately.

Alternatives Considered

Combine both facets into one source module. The goods participant has its own purchase and inventory responsibilities in the existing architecture.

Consequences

Both service contracts identify the shared product object and describe the facets they hold. Listing validation reads goods delivery rather than storing another delivery setting. The facet split introduces no macroservice network boundary.