Various inconsistencies appear in the store's product pages. Recent examples include:
Inconsistencies between different one-to-many relationships (or incorrect cascade rules for many-to-many relationships) lead to problems where a collection supposedly includes a book, but the book apparently is not a part of the collection.
The least expensive option, apart from modifying the schema, is to run a script that checks each table's joins, to catch any inverse relationship inconsistencies.
The more time-consuming option is to ensure that inverse (many-to-many) relationships exist, and that cascade rules are properly configured to eliminate any inconsistencies between relationships in the first place, regardless of the type of query.
I realize that serving up product pages requires complex queries, and that caching comes into play, but the existing system of customers reporting product page issues, then employees fixing the issue, should be considered antiquated, given what automation can and should do.
Please consider putting some automatic detection or prevention into place to prevent pricing or bundle issues from occurring in the first place.
This concept also applies to dynamic pricing. If a person can determine which products are eligible for dynamic pricing, then a script or rule could automatically check or ensure that the right collections do have dynamic pricing enabled.
