iMarks
02-25-08, 08:44 PM
How much would something like this cost? Just a very rough budgeting cost for now is fine so I can pass the info on to my client to see if it's cost-effective. Please email me offline at iMarksWeb.com - Thanks!
Affiliate Custom Module/Component Requirements:
(1) If affiliate link was not used to access the site, customer is presented with a list of affiliates on a checkout page.
Each affiliate is a charity. It's possible we'd want an extra checkout page for usability.
(2) Affilate list can be filtered by interest area and/or state and/or keyword search at discretion of user.
This implies custom affiliate fields that can be changed on AFAD/AFED, and maybe a new table for allowable interest areas that the merchant can change. The merchant may want to suppress some affiliates from the list based on another custom field, but they could still link to the site to get a payout.
(3) There may be 100 or more affiliates to choose from, hence the need for filtering functionality.
(4) Customer selects an affiliate to credit the purchase to (if site was not accessed through affiliate link).
(5) Amount of affiliate payout is based on products selected.
A percentage is associated with each product. I can figure the amount using Toolkit and pass it to the module in a global variable on the BASK page or later. This applies whether the customer selects an affiliate, or the affiliate link was used to access the site.
(6) Payout is applied to affiliate between OPAY and INVC.
(7) If refund is required, credit must be subtracted from affiliate payout.
This implies an association of orders to affiliate and/or affiliate recorded with order information and/or ability for merchant to change affiliate's payout total.
Affiliate Custom Module/Component Requirements:
(1) If affiliate link was not used to access the site, customer is presented with a list of affiliates on a checkout page.
Each affiliate is a charity. It's possible we'd want an extra checkout page for usability.
(2) Affilate list can be filtered by interest area and/or state and/or keyword search at discretion of user.
This implies custom affiliate fields that can be changed on AFAD/AFED, and maybe a new table for allowable interest areas that the merchant can change. The merchant may want to suppress some affiliates from the list based on another custom field, but they could still link to the site to get a payout.
(3) There may be 100 or more affiliates to choose from, hence the need for filtering functionality.
(4) Customer selects an affiliate to credit the purchase to (if site was not accessed through affiliate link).
(5) Amount of affiliate payout is based on products selected.
A percentage is associated with each product. I can figure the amount using Toolkit and pass it to the module in a global variable on the BASK page or later. This applies whether the customer selects an affiliate, or the affiliate link was used to access the site.
(6) Payout is applied to affiliate between OPAY and INVC.
(7) If refund is required, credit must be subtracted from affiliate payout.
This implies an association of orders to affiliate and/or affiliate recorded with order information and/or ability for merchant to change affiliate's payout total.