Product modeling defines how products, bundles, and options are structured within the system. A well-designed model improves performance, simplifies maintenance, and ensures a consistent user experience. Poor modeling practices such as unnecessary complexity, inconsistent naming, or excessive SKUs—can lead to confusion, integration challenges, and higher maintenance costs.

Core principles for product modeling:

• Simplicity: Keep product structures straightforward. Avoid unnecessary layers in standalones, bundles, sub-bundles, and option groups. Simple models improve performance and reduce maintenance effort.
• Standardization: Use consistent naming conventions for products, attributes, and rules. This minimizes confusion and ensures long-term maintainability.
• Maintainability: Prefer reusable, generic attributes over product-specific ones. This supports multiple products and simplifies future updates.
• Product Structure over Rules: Use product structures (bundles, options) instead of relying heavily on constraint or validation rules. For example, default an option within a bundle rather than adding it through a rule.
• Minimal SKUs: Avoid creating separate SKUs for every possible option combination (e.g., color and storage variants of a phone) instead use attributes or configuration logic.

Following are the core principles of Modeling Attributes and Options:

• Attributes: Define the inherent characteristics of a product—such as color, size, or material. They appear as fields to the end user but do not generate separate line items in the cart.
• Attribute Groups: Collections of attributes organized for better structure and reusability, which are then linked to products.
• Options: Represent additional products or services that can be included with a bundle. Each selected option generates its own line item in the cart.
• Option Groups: Organize and manage options and are tied specifically to bundle products for easier configuration.

Use Attributes when

• Define variations or characteristics of a single product (e.g., T-shirt color, laptop RAM size).
• Apply when pricing and availability remain consistent and are tied to the main product.
• Use for non-tangible selections, such as country, region, or internal configuration choices.
• Prevent SKU proliferation, avoid creating separate products for every possible combination; manage differences through attributes instead.

Use Options when:

• Offer add-ons or supplementary products (e.g., a mouse or extended warranty with a laptop).
• Apply when pricing or availability can vary independently from the main product.
• Use for tangible, standalone items that can be included in a bundle but are not typically sold separately.