just a few words and links to help:
props/evars once set up for a report suite can be used for whatever you want. but i would strongly recommend not to mix it up, unless you run out of props/evars. i mean, try to use the same prop/evar for the same intent and name it accordingly.
Traffic Props and Conversion eVars
i would recommend to use the same props/evars over all different report suites. this way, you can use segments, calculated metrics, workspace projects over different report suites without any problems.
there was a similar question with a good answer from adam:
Do the props, eVars and events have to be the same across multiple reporting suites?
btw: if you try to catch product/prices, better use the predefined "product variable": products
as far as i know there is no "best practice" or guidance, which props/evars/events are used for each single case. you can almost do whatever you want. i recommend to always have a separate documentation on what you've done (and why). mabe the post here might help you: How to make Adobe Analytics tagging map aka solution design requirements for SiteCatalyst implementation |