So I’m in the process of migrating some of my CMS collections over to E-commerce collections… but I see a bigger design flaw.
The issue I’m seeing here is that the
Custom Fields for
Products is only creating 1 set of custom fields for general
Products. The issue here is that products are not all the same… and I also find that in the future this could be
There’s also tons of space left here for adding of other Collections. It seems like it’s also extra clutter to have a separate E-Commerce section with essentially the same functionality as the CMS.
My question is that why not just add E-commerce as a field type instead of a collection? This way we could keep our existing CMS collections and simply add E-commerce attributes to a CMS collection.
We need specific custom fields for specific collections… not just 1 product collection. Does that make sense…
- Courses have… Title, Price, etc. & Intro Summary, Course Videos Count, Course Worksheets
- E-books have… Title, Price, etc. & E-book Book Images, Audio URLs
- Services have… Title, Price, etc. & Service Guarantees, Service FAQs
We would then not need to add every different type of collection (Courses, E-books, etc.) to a single Products collection.
Essentially, it would be easy enough to (instead of adding a reference field) you add an E-commerce field which adds all the same fields as are in the
Products collection… But adds them exclusively to a CMS item.
This means that it becomes data enrichment to the bulk of CMS content rather than the exclusive primary collection attributes which flip the enrichment onto a single set of custom fields… in essence limiting the user from adding high quality data sets to their E-commerce items.