A recurring billing system and affiliate program for a membership subscription services type of site is required. It will be implemented in a LAMP environment on AWS EC2. We strongly prefer quotes that are based on existing software, but will consider totally custom solutions. Totally custom solutions and modifications to existing packages must be well documented. Bidders must be willing to submit samples of documentation of project(s) in their portfolio. We prefer, but do not require, that the PEAR Framework or similar tools be used if your bid is for a totally custom solution. Only bidders with significant ecommerce experience using PHP and MySQL will be considered. Please do not bid if your portfolio does not support this kind of experience. References will be required and will be checked. This may not be necessary if you have a high rating on this site. Experience with AWS EC2 is a plus, but not required. We prefer a quote that includes installation, setup and configuration. However, we will also consider handling installation ourselves for established packages that work as specified out of the box and that are well documented. The quote should include a break down of the costs, including the standard package (even if we buy it directly from a different party), customization costs and any extra service charges.
## Deliverables
1 Shopping cart: 1.1 User login to maintain demographic and billing data. Availability of billing history info is preferred, but not necessary. 1.2 Different subscription lengths (i.e. 3 months, 12 months) 1.3 Renewals can have a different subscription length than the first year. (i.e. 1st year can have a two month bonus for a total of 14 mos, 2nd year is 12 mos. 1.4 Group packages with discounts (i.e. Family packs would create multiple subscriptions for several individuals.) 1.5 Optional one time services which can be processed by Admin against credit card on file without additional subscriber approval. 1.6 Coupons (see affiliate program for more on coupon codes) 1.6.2 Coupons for discounts 1.6.2.1 pct discount 1.6.2.2 fixed dollar amount discount 1.6.3 Coupons to extend period, ie ??" one free month. 1.6.4 Multiple coupons 1.6.4.1 Allow multiple types of coupons. Example: allow one coupon for four free weeks that is associated with a marketing partner to be added to a temporary coupon such as “Get two free weeks if you sign up by end of month.??, for a total of six free weeks. 1.6.4.2 Prevent multiple use of the same type of coupon. i.e. if coupons are associated with two different marketing partners. 1.6.5 Manage on-line affiliate and off-line marketing partner conflicts. 1.6.5.1 Credit for sale assigned to marketing partner 1.6.5.1.1 Off-line coupon code wins when the affiliate cookie is set in a different (earlier) session. 1.6.5.1.2 On-line referral wins when the affiliate cookie is set in the same session. 1.6.5.2 If losing offer is better than the winning offer, the offer is extended to match the terms of the loser. 1.6.6 Coupon code source 1.6.6.1 Discount codes can be entered by customer 1.6.6.2 Discount codes can be automatic based on variables from URL query string or cookies. The codes can be the same as affiliate codes. 1.7 Account reactivation charge calculation based on length of inactive period, Example: If reactivated 5 months after expiration and cost/per month is $2, the additional charge is $10. 1.8 Tie into major CC processing platform such as [login to view URL], The platform has not yet been chosen. 2 Affiliate program: 2.1 Web referrals 2.2 Off-line referrals/coupons. Coupons do double duty for discounts and affiliate tracking. This is a preferred feature, but is not essential if the rest of the coupon system meets specs. 2.3 Two affiliate levels preferred, but one is okay. 2.4 Affiliate control panel and reporting 2.5 Banner and other marketing tools management 2.6 Cookies management. Prefer management through admin control panel, but we can also modify code if instructions are included in the user’s manual. 2.6.2 Control time to expire 2.6.3 Control priority of referrer (First or last referring partner wins) 3 Interaction with the services portion of the site 3.1 Security for the billing and affiliate systems will be separate from the rest of the site’s security. 3.2 When transactions are completed, the billing system would send an http request to set off provisioning of the order. 4 Other considerations: 4.1 Prefer a single integrated package, but will consider a separate affiliate package, such as iDevAffiliate and Jrox. 4.2 A built-in simple CMS or integration with a light-weight CMS environment will be considered as a positive. We will only be using the CMS for the brochure portion of the site, which is pretty simple, so complex and feature rich CMSs are not preferred. 4.3 Prefer Smarty templates compatible system, but this is not an essential requirement. If we implement with a standalone CMS, it will probably be Smarty compatible. 5 Deliverables 5.1 Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 5.2 All deliverables for custom work will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all custom work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
## Platform
LAMP (CentOS) environment on AWS EC2.