--- id: CON-ACC-PRD-003 name: Product Selling Settings (Superseded) feature: FEAT-ACC-PRD-03 product_area: accounting module: products revision: 3 status: superseded product_intent: proposed implementation_evidence: observed source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f definition: Selling settings describe optional facets of a product rather than a separate broad business concept. owned_by: MOD-ACC-PRD synonyms: - Selling configuration not_to_be_confused_with: - An independently owned business record facets: - name: Bundle meaning: This setting belongs to the product’s selling configuration. used_for: Explaining the product facet retained in the Product concept. - name: Quantity discount (bulk pricing) meaning: This setting belongs to the product’s selling configuration. used_for: Explaining the product facet retained in the Product concept. - name: Purchase limit meaning: This setting belongs to the product’s selling configuration. used_for: Explaining the product facet retained in the Product concept. - name: Tasks to generate meaning: This setting belongs to the product’s selling configuration. used_for: Explaining the product facet retained in the Product concept. - name: Confirmation e-mail meaning: This setting belongs to the product’s selling configuration. used_for: Explaining the product facet retained in the Product concept. relationships: - to: CON-ACC-PRD-001 statement: Selling settings are facets of the product. provenance: documented source: 'rhythm-v2-docs:specs/CONVENTIONS.md#5.0a Key Concept (`CON`)' acted_on_by: [] visible_to: - ACT-ACC-006 - ACT-ACC-007 - ACT-ACC-011 evidence: - 'react-console:components/accounting-config/products/product-bulk-pricing-section.tsx' - 'react-console:components/accounting-config/products/product-common-sections.tsx' - 'react-console:components/accounting-config/products/product-section-types.ts' - 'react-console:components/accounting-config/products/product-task-generation-section.tsx' - 'services-accounting:docs/accounting/products.md' - 'services-accounting:modules/products/db/product-bulk-pricing-rules.table.ts' - 'services-accounting:modules/products/db/product-bundle-components.table.ts' - 'services-accounting:modules/products/db/product-task-templates.table.ts' - 'services-accounting:modules/products/db/products.table.ts' - 'services-accounting:modules/products/services/confirmation-emails/confirmation-email-templates.ts' - 'services-accounting:modules/products/services/persistence/communication-templates.ts' - 'services-accounting:modules/products/services/persistence/task-configurations.ts' - 'services-accounting:modules/products/services/rules/product-rules.ts' supersedes: - react-console acceptance inventory CAP-ACC-PRD-009 - react-console acceptance inventory CAP-ACC-PRD-010 - react-console acceptance inventory CAP-ACC-PRD-011 - react-console acceptance inventory CAP-ACC-PRD-012 - react-console acceptance inventory CAP-ACC-PRD-013 --- # Product Selling Settings (Superseded) ## What It Is This retained concept records the earlier attempt to explain a product’s optional selling settings as a separate business noun. Examination places those settings within Product, where they describe the offer staff configure. The identifier remains available so earlier references can be followed without mistaking it for an additional active concept. Product is the continuing explanation for readers learning this part of the catalogue. This change concerns the planning structure. It does not remove the selling capabilities or discard their evidence. Quantity discounts, bundle allocations, purchase ceilings, task instructions and confirmation choices remain represented in the capability layer. Their explanations now sit beside the product’s other facets, giving a product manager one place to understand what the catalogue record carries. ## What It Is Not Selling Settings does not introduce another independently owned business record or another catalogue lifecycle. The group describes optional configuration associated with a product. It also does not represent an order, an invoice, a delivered task or a sent message. Those outcomes involve the applications that consume the configuration and need their own contracts and proof. ## How It Is Used Readers following an earlier planning reference arrive here and continue to Product. Staff still work through the named selling capabilities, and the Selling Settings feature continues to group those outcomes for review. The superseded concept provides historical traceability while the active concept explains the business meaning. A reviewer should use the capability layer to assess validation, refusals and preservation during editing. This retained explanation supplies no competing rule set. Where an earlier expectation differs from the pinned implementation, the findings register carries the disagreement and the decision still required. ## Its Facets The retained facet names identify the material moved into Product: Bundle, Quantity Discount, Purchase Limit, Tasks to Generate and Confirmation E-mail. Each describes a different aspect of the same offer. Their continuing definitions belong to the Product concept, while their detailed constraints belong to the corresponding capabilities. Keeping these roles distinct avoids turning each setting into a separate broad concept merely because it has its own storage or editor section. ## How It Relates Product provides the parent business meaning. Price explains the associated pricing vocabulary, and Accounting Setup explains financial destinations and revenue treatment. Selling Settings remains a feature grouping within this structure, rather than adding another peer noun. Downstream sales and communication responsibilities remain relationships to other modules. ## What It Could Become The product should extend the Product facets when selling configuration grows. A future independently owned business concept would need a separate justification based on its meaning and lifecycle. This historical identifier remains superseded so later work can preserve traceability without recreating a second home for the same explanation.