2

I am struggling with a good backend approach. Each order item will need an Rx associated with it, and it should also be accessible/editable from the customer account page.

Should I make this its own EAV? Would this be better off a customer attribute or an order attribute? Any guidance or a similar extension to get me started would be awesome.

4

I would handle this with resource models that map to custom tables. No doubtedly you'll be asked to write some reporting or dashboards some day and having it in (flat-ish) tables with simple normalization will make it much easier than if you were to create as customer-centric EAV.

  • 1
    Interesting! That's a great idea. So have something like a rx_item table that maps to customer, order_item IDs? – kevando Nov 5 '13 at 22:58
  • Precisely. This is how magento handles all sorts of things like wishlists and registry – philwinkle Nov 5 '13 at 23:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.