[consulting] Affiliate module requirements

[Alex Rollin]

I think you are right about the database integration being
the key piece for one shopping cart.  Perhaps that is a solution.

They do not have an API per se, but they do have some
advanced configuration scripts that disclose some of the
hooks for passing affiliate data, and some of the html forms
are equally verbose.

I think you are right about the complexity of integration.
Most of my clients can barely understand an affiliate
program, much less administer one, but that doesn't mean
they don't need the functionality, and therein lies the rub.

I have been working on my specs, though, and I will continue
to do so because the specifications for one project have an
interesting simplicity to them that I think will complement whatever
wants to happen with the core affiliate module.


On 5/19/06, Jenny Hsueh <lists at ondemand-network.com> wrote:
>
> Just about to say, in terms of ecommerce/affiliate user experience and
> functionality,  1shoppingcart will be the model that  we would like to
> see Drupal implementation to follow.
>
> I wonder would it be more cost effective that we provide a bridge
> between drupal and 1shoppingcart (or similar commercial services)?
> 1shoppingcart services fee is quite reasonable with loads of features
> and stable implementation. In fact, this is the ecommerce/affiliate
> solution  we would recommend to our clients, of course the downside is
> that currently  there is no integration with drupal user accounts.  I
> think the way 1shopping cart works should work especially well if you
> have a network/networks  of related drupal sites, i.e. users can
> purchase goods from different sites and you manage it from one place and
> be able to follow up intelligently, also with tiered affiliate
> features,  each site owner within the "networked" sites can set their
> own commission rate for the products on different sites  (although we
> have not tried  out this scenario yet, but in theory it should work like
> this).
>
> A robust ecommerce and affiliate program  seems pretty involved
> especially in a networked multi-site environment. Personally we don't
> want to take the accountability for ecommerce software integration, a
> bridged solution between Drupal to some stable commercial software will
> be ideal.
>
> Jenny
>
> Alex Rollin wrote:
>
> > Quick additions that come to mind are the following.
> >
> > I admit these are hefty.  I do not understand how this would operate
> > along with the ecommerce module, really, and I am prepared to be
> > fliexible in case the integration is simply too complex.  These pieces
> > are really here because the customers are looking to replace 1shopping
> > cart so they can use the ecommerce database in addition to intergated
> > mail functions, and these are the features they are looking at
> replacing.
> >
> > Multiple Affiliate Programs
> > Ability to ban affiliate from one program, but admit to another program.
> > Payouts in percentage and fixed dollar amount.
> > Different payouts for the same product under different programs.
> > 2nd tier affiliate signup tracking. (New affiliates bringing in new
> > affiliates)
> > Different payouts on per product basis for 1st and 2nd tier affiliates.
> >
> > A points system is really important.  To enable additional currencies
> > and different forms of trade, a point system is key.
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>



-- 
Alex Rollin
alex (dot) rollin (at) gmail (dot) com
http://coera.us/alexrollin
skypeto.discursives
415.676.1510.mobile
410.531.0495.office
8630M Guilford Road #215
Columbia MD, 21046
<a href='http://www.rapleaf.com/profile/show/dExCLmSV'><br><img
alt="alexrollin's Rapleaf Score" border="0" src="
http://www.rapleaf.com/sig/dExCLmSV.jpg" /><br></a>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20060519/0142e078/attachment.htm