Debating Method To Track Member Fees - Over Thinking It
Posted: Wed Sep 30, 2009 12:57 pm
Hey,
Members of a website I am developing use it to sell their product via paypal. It tracks the sales, handles the transaction/etc. After each sale, a fee is assessed based on the product price When they log into their admin panel, they view their profits, fees due, etc. I currently track fee totals by month as well as paid fees by month.
I was wondering if I should use an 'upgrade' to this system where, in case they want to pay more than once, I simply have a table called 'all_fees' and it's tied to their user_id. Should they make 3 payments per month or 5 or whatever, based on the fluctuating fees that amass from their sales each day, this table would allow me to delete from it anytime fees are paid.
This way, the fee total is a 'live snapshot of fees' and not confused with monthly fees/etc . In short, is it best to just host a table for fees and delete all references to it once payment is made and not try to track 'per month' as I was originally doing ?
Thanks for your time.
PS In case you are wondering why I initially tracked per month, the original idea was that they could pay once per month. While this system works now, I wanted to see if it was more efficient and logical to not limit the # of payments/etc.
Members of a website I am developing use it to sell their product via paypal. It tracks the sales, handles the transaction/etc. After each sale, a fee is assessed based on the product price When they log into their admin panel, they view their profits, fees due, etc. I currently track fee totals by month as well as paid fees by month.
I was wondering if I should use an 'upgrade' to this system where, in case they want to pay more than once, I simply have a table called 'all_fees' and it's tied to their user_id. Should they make 3 payments per month or 5 or whatever, based on the fluctuating fees that amass from their sales each day, this table would allow me to delete from it anytime fees are paid.
This way, the fee total is a 'live snapshot of fees' and not confused with monthly fees/etc . In short, is it best to just host a table for fees and delete all references to it once payment is made and not try to track 'per month' as I was originally doing ?
Thanks for your time.
PS In case you are wondering why I initially tracked per month, the original idea was that they could pay once per month. While this system works now, I wanted to see if it was more efficient and logical to not limit the # of payments/etc.