Multi site LAMP Project

Hello there. We are looking into building a semi complex web project that has several fronts to it. Enclosed is a diagram of the project. Basically there are a minimum 4 products that will each have 3 different front ends (unique graphical sets and domain names) that lead to the same single end page for SSL processing. Domain names are for example only: Eg. Site 1 [login to view URL] for product 1 [login to view URL] for product1 [login to view URL] for product 1 [login to view URL] for product 2 [login to view URL] for product 2 [login to view URL] for product 2 [login to view URL] for product 3 [login to view URL] for product3 [login to view URL] for product 3 [login to view URL] for product 4 [login to view URL] for product4 [login to view URL] for product 4 = TOTAL 12 unique frontend websites on separate domains each with 1 backend to process for all of them. A control panel type system will control the sites and allow for me to easily change images and text. I would prefer a common CMS software like CAKEPHP or joomla or other, I leave his to you to decide the one thatsuits my project the best. v One ssl secured checkout page will connect to my merchant account(s) to process orders to allow for payment of the item (no shopping cart is needed as only one item will be purchased at time of purchase).This ssl processing page will be located on another hosting server (different hosting company different IP( and can allow the opportunity to have more than one processing server to accommodate load balancing or failover should the need(s) arise. modularity EG. [login to view URL] (That will be a domain NOT shared with any of the 12 above) v When a client visits the payment site for payment processing from the ‘landing page’; it is important that banners and the name is consistent so the client knows they are dealing with the official payment processor for this site on the payment page. Parameters will be needed for tracking purposes so knowing which of the 12 sites the client arrived from is already there. v This site will house the database to allow clients to log in and verify their invoice, as well as eventually buy new addons and / or contact us for customer service or other needs. Each site will as well allow for each person who has purchased the product to redownload it (all purchases are downloaded) and will be regulated by the database that will know how long a support the client has. i am presuming all backend components will be open source based on the LAMP structure (LiNuX, mySQL, PHP, no licencing charges, all should be compatible with mainstream hosting accounts), If you propose an alternate solution, let me know It is imperative that any replies you have will: -ask me any further questions to clarify -offer me a round about budget (separate of hosting, ssl and -other requirements not included that I am responsible for) -round about timeframe from the starting point to get started -any changes to my plan, and why they are preferred -any examples of any or all portions of this project that you may have done previously A summary of functionalities and necessities in order for the project to be fruitful: FRONT END WEBSITES: · 12 unique front end websites (I will provide the text for them). Each will be on separate domain name o Separate website defined as: Different template, layout, graphics including logo which are all relevant to the domain name they are attributed to and are pleasing to the eye. All is to be prepared / supplied by the bidder at a price that is included in the entire bid, except the text. SEO / submission to free sites / spiders is to be done and may include 1-2 revisions 4 weeks after site launch) Reference sites can be provided as the process moves along. · For each of the sites for the same product eg. 3 sites will sell the same product, the site can be similar but appear different (different layout and domain name). The text will remain mostly the same. · Product sold on each site is only one item. This item can be augmented by client with radio buttons to increase the sale price. NOTE: all products sold are software and need no shipping, taxes, nor any related issues Eg. Antivirus software with 1 year support or 2 years support or premium support Additional option of free upgrades to new version · Google Analytics installed for each ‘domain index page (12 pages / landing page) so tracking can be done for statistical purposes · 12 Sites to be a simple page: 1 Main page with product description, 1 FAQ page,1 support page (links to mother page)and about us page. Not many pages in all! · Initially the front end pages may be located on a hosting account that is separate from the back end server. There is as well the possibility that there can be several separate front end servers eg. · Server1 hosting 6 front ends, · Server2 hosting 6 front ends. Shared hosting packages are able to host many (100s) of front end sites. Let me know the specifics you are considering to outline. BACK END FUNCTIONALITY: · Allow ssl payment processing from all above sites with graphical banners and text letting the client know that they are being processed by the corresponding processing agent company of the site they intended to purchase from. · Although commencing with one backend site, the ability of this backend site to be hosted on a different physical server in a different location from the front end pages. · Standard payment processing by credit card merchant account in SSL mode and paypal payments accepted as well as needed. Processor(s) should be able to be shut off and reactivated easily by myself. · The ability to make host changes to verify the payment site is PCI compliant as per report from the merchant company. (not as important, but still present) CLIENT FULFILLMENT: · Clients wishing to log into the members area / support area can do so by hitting the link on the site they originally visited. Eg. [login to view URL] support / members area. They enter their credentials here, but are forwarded to the common members area of members.processingsite.com. From here, they are presented with their options: o Support / members options shall include: § Redownload their software § Attempt to contact client services (embedded email form. Client should only be able to have one open ‘support ticket’ at a time § Visit the members area. Members area is where they can get other free softwares and information. This is a simple page that offers user the ability to download a choice of softwares. § Get their invoice information regarding past purchases. § Reset their access password if they forgot it § Be upsold on other products / renew service contract o Billing information: This shall as well be present and predominately on the home page of [login to view URL] (13th site that actually is a separate front end to the payment processing site) where clients who will see on their credit card the billing descriptor of webprocessngsite and not the specific site they originally visited. If clients do not recall that they purchased with us, they will claim a costly chargeback to us. Client shall be able when they click on link on this page whose caption is “received a charge from webprocessing site but do not remember it?” o They will be able to enter a choice of: § Their email address § Their invoice number § As well as their last name. Clients will then view an online version of their original order. o NOTE: All forms for client data entry are to be protected with CAPTHA type feature. PURCHASING PROCESS The purchasing process is designed to make client purchases to be as seamless and simple for the client. Client proceeds to BUY NOW. They are prompted to enter their name zip code /area code and email address. These parameters along with the site the sale came from are sent to the new site for processing. Pricing info, banners, the clients username and email are all presented here. Client is now offered the option of paying by Credit card merchant account or Paypal. Captcha protects the payment page continuing. In either case, client enters their payment information. If successful, they are immediately prompted to download the product they purchased. At the same time, client is sent an email invoice that contains their username (email address), password, as well as what they have purchased. A duplicate is sent to an internal email address. Client is as well provided links to support pages, FAQ and download page for the product. As part of the payment process, client is offered to purchase a one year 2 year or lifetime plan. These plans should expire on the set dates. All database, configurations, and other pertinent info should be placed into an automated backup that his stored on an alternate host. Preliminarily, all the sites may appear on the same host, but this may very well change. This provision must be integrated on the get-go. Change information delivered to clients (email) Have a portal where open tickets for support can be reached as well as replied to View basic stats of sales and what site they originated from, etc etc.. eg Main site [login to view URL] As the presence of these extra sites selling the same products are meant to be promoted by affiliates, this site will serve as the hub for the affiliate center. Enticements, a list of some of the sites available to be promoted, and other information is to be housed on this site and promoted as well as the customer login to see their invoice for users who have forgotten what the bill is for, Other items to be included: The ability for me to specify the denial of site access (front and back end) to certain IP ranges Backups of both font and back end sites Simple reporting of sales and generated sales and their origin by site they arrived from Ability to offer clients refunds