M2 Product entity structure

Get Started. It's Free
or sign up with your email address
Rocket clouds
M2 Product entity structure by Mind Map: M2 Product entity structure

1. Placeholder / template

1.1. Build bundles on the fly

2. Utilize M2 bundle structure

2.1. Thoughts

2.1.1. Use custom options for related products; i.e. stones for a ring

2.1.2. Use virtual product for Ring size?

3. Considerations

3.1. Desire a consistent structure between DN/1215 products

3.1.1. Rings Rings are not sold without a stone option being selected Must support preconfigured (current DN) as well as ring builder approach.

3.1.2. Simulant & other gemstones Stone sold with a ring... or loose

3.2. Pure carbon stones from multiple outside vendors

3.2.1. Qty 1

3.2.2. Lots of rolling inventory

3.3. Upsells

3.3.1. Services as virtual products Certified stones Warranties Engravings Ring resize

3.3.2. Metals

3.3.3. Stones sizes

3.3.4. Matching bands

3.3.5. Mens bands

3.4. Desire to keep product structure straightforward to be manageable by a PIM in the future.

3.5. Attrs

3.5.1. Some rings only accept certain stones; shape or min/max size

3.5.2. Ring sizes do not currently affect price... except for eternity bands

3.5.3. Some competitors do ring size selection as separate/last step at end of Ring building

3.5.4. Ring material as a configurable?

3.6. Most inventory is "pull" meaning we take the order and source it (inventory isn't an issue).

3.7. Semi-custom support

3.8. Images of combined products i.e. ring/stone

4. Custom/loose bundling approach

4.1. 1

4.1.1. Native product types but related by a custom "parent product" or set ID (presentation managed in FE) Quote items Ring (ID:1) Stone Warranty Matching band Stud earrings Cart /order View altered to display the children under the parent; sorted by attribute set. Notes Supports all native product types

5. Custom product type

6. Extended Bundle Structure