Blog Sections Open
Combining Shopkeeper Compare with Flexible TV Data
Product comparison works best when attributes are structured consistently enough to be compared across the catalog.
This donor asked how to combine Shopkeeper comparison features with more flexible TV editing approaches such as ParamEdit or MultiTV-style data entry.
The Main Design Tension
Flexible product fields are easy for editors, but comparison features need stable attribute keys and values. If every product stores attributes differently, comparison tables become unreliable very quickly.
Practical Rule
- Define which attributes must be comparable across the whole catalog.
- Keep those attributes structured and normalized.
- Use flexible editing helpers only where they do not undermine consistent comparison logic.
This is less about one specific snippet and more about data modeling. Comparison features succeed or fail based on attribute structure long before the front-end template is built.
Saving eForm Leads into the Database
A practical pattern for recording eForm submissions in a database for later export or follow-up work.
Sending eForm Submissions to Multiple Recipients
How to deliver one eForm submission to several recipients when a comma-separated address list is not enough in your setup.