Find Jobs
Hire Freelancers

Reverse Auction WebSite Development

min $3000 USD

Zaprt
Objavljeno pred približno 14 leti

min $3000 USD

Plačilo ob dostavi
There will be only one type of auction supported which is a reverse auction where the minimum unique bid wins. If there are no unique bids at the end of an auction, a search is performed for the smallest group of matching bids (2 matching bids for example), and the person in that group that bid first is the winner. Here comes the necessity of SEO, providing that the key words will be products names. There are two parts to the web site that need to be developed, the first is the user centric pages, and the second is the administration console that will allow a site administrator to manage the site on a day to day basis. The admin console should allow the control of a variety of settings as described in this document. For a good example of what we are trying to replicate, please see HYPERLINK "http://www.bidster.com/"[login to view URL] General design Pages design has been developed so far, so you will need to implement it. The critical aspects of the design is that it should be multi region capable. In that regard, the site needs to be designed in such a way that multiple languages (English and Russian by the launch time, and Spanish for the future) can be supported. In terms of language support, the site would have a single reference language, namely English, and would allow the administrator to configure additional languages via the admin console. A dictionary system should allow the administrator to define text to be inserted at appropriate control points in the site. Multi language support (e.g. English, Russian plus others) Multi currency support (e.g. USD, GBP). This feature should be developed for the future references, however, by the launch time only Dollar USA should be supported. In terms of technology, the implementation should be restricted to the use of commonly used open source technologies. Primarily, the target language should be PHP using a mysql database as the data store. Stored procedures are acceptable, however little or no business logic should be in stored procedures. Implemented in PHP, Mysql database Client side JavaScript (form validation, AJAX etc...) Cookies (saved preferences etc...) Flash animation for upcoming auctions We are open to discuss SEO options and suggestions. However, we would rather take a slow approach at the beginning, experimenting with the best keywords to purchase, and developing the best keywords tactic for the successful launch of the project. Multi Language The multi language features should be configurable by the administrator via the admin console. Ideally a dictionary system in the database should be used to lookup the appropriate text that needs to be inserted into the web page at various control points. The administrator should be able to manage the content for the various languages that are supported via the CMS interface. The user should be able to switch to the language of choice by clicking an appropriate link easily visible on all pages (english | russian) for example. Please bear in mind that one of the supported languages for the site will be Russian, and therefore the cyrillic alphabet needs to be supported by whatever character set you decide to use for the database. Pages & Sections Home (Live Auctions | Upcoming Auctions | Closed Auctions) How it works (including FAQ) Customer's account Auctions history News About us Contact us (including feedback form) Terms & Conditions Privacy Statement Administrator Console Login Input fields to enter a username and password should be available in the header of every page as well as a “Forgot Password” and “Registration” link. In case of forgotten passwords, a page should be displayed that allows the user to enter their email address. An email should be generated that contains text from an administrator defined template which includes their username and password details. If the user selects the registration link, they should be directed to a page to enter registration details as described in the next section. Once a user has logged in successfully, their name should be displayed in the header of all pages (as opposed to login fields). In addition, the following links should be visible: My Account (see later) Add Funds (see later) Recommend a friend and earn more money to your account “Recommend a friend and get earn more money to your account” holds a very important marketing function, as it increases the number of Bidamin's customers. However, a customer earns some money only after his/her referee makes his/her first bid. Money earned on the account are virtual, can be used only for purchasing bids, the amount can be managed by an administrator via admin console, and communicated to customers via News page (as well as by emails, if necessary). Registration When a user registers we wish to capture the following fields: Username Password Email address First Name Last Name Gender Date of birth Address Line 1 Address Line 2 (optional) City Post code Country Mobile number Would you like to recommend a friend and earn some money to your account? Use of client side Javascript for validation is required. Check that the username is available when lost focus on that field (print error message in red below the text field if it is already taken). User needs to type in their password twice to confirm it is correct, highlight in red text if they do not match. User needs to type in their email address twice to confirm it is correct, alert in red text if they do no match. The selection of countries in the drop down box should configurable by the administrator. Include check boxes to force the user to indicate that they have read the Terms & Conditions as well as the Privacy statement. Links to these should be provided to make these easy to access, and they should open in a new browser window. The user should also be able to opt out of receiving any news letters or other promotional material. By default, this should be set so that they will receive such materials via email. Finally, the user should be required to enter a security code visible in an included image to prevent fraudulent accounts from being created by non human users. Once they have submitted the registration form, the resulting page should indicate that they will receive an email in which they will need to confirm the account registration by clicking on a link. The account should not be enabled until they have clicked on this link and thereby confirmed that their email address is correct. Reverse Auction Specification There is only a single type of auction that needs to be supported, namely a reverse auction where the minimum unique bid wins. In order to place a bid, a user needs to purchase the right to bid. The cost of a bid should be configurable per product. Generally speaking, the more expensive the product, the higher the cost of bidding on that product, but that is at the discretion of the administrator. A user account will have a balance of funds which they can add to using various payment methods described in a later section. Once they have adequate funds on their account, they will be able to register bids. An auction should be configurable using the following properties: Product name Product description Product description URL (link to external page, usually manufacturers web site) Price Start date and time (yyyy-mm-dd HH:MM) Expiry date and time (yyyy-mm-dd HH:MM) Cost per bid (expressed in reference currency) Image of the target product (to be stored in the database) After an auction time is finished, the winner will be selected by the software. All other customers will be provided with the opportunity to purchase the item for the price indicated on the Bidamin site, minus bids cost made. The system should calculate the final price and to display it to a customer with a short explanation (Sorry, you have not won the name of the item. Would you like to buy it for the remaining balance of ….....?) The administrator should be able to use the admin console to create or amend auction details as above. Auctions configured with future start dates should become visible as upcoming auctions. Upcoming auctions should be visible to users so that they can be made aware of what is coming in the following weeks. What the user should see for a given auction The user should be able to see the following details on an auction listing: Product name Product description Product image Price Cost per bid Count down timer to auction close (if auction is live) Count down timer to auction open (if auction is not yet open) The username of the person who currently has the lowest unique bid The count down timers and the username of the currently winning bidder should be changing dynamically in the page using the appropriate Javascript / AJAX calls. The user should not have to refresh the page to get this information. Placing a bid A user needs to be logged in to place a bid. If a user is not logged in and they click a bid button on one of the auctions, they should be redirected to a login page. After a successful login, they should be redirected back to the page from which they were redirected to login. To place a bid, a user must specify a bid number. A text field that only allows numeric data to be entered should be available to allow a user to enter a bid number (it must be a positive number). The price should be expressed in the smallest monetary quantity of the currency (cents for USD). Therefore an amount entered as 934 implies $9.34. To enter a bid, the user should simply type in the numeric value and then click the bid button. Once a user clicks “Bid”, they should be presented with immediate feedback on the outcome of their bid by dynamically changing the html of the page. At this stage, we identity 5 possible outcomes upon a bid being placed. You do not have adequate funds to place a new bid Congratulations, your bid is unique and currently the lowest! Your bid is unique but unfortunately not the lowest Your bid is not unique You have already bid this value, please try again As described earlier, there is a cost associated with placing a bid on a given product, which is defined for each auction. Each user account will maintain a balance of funds in their preferred currency. If they bid on a product and do not have adequate funds, their bid request is void and the appropriate feedback is presented. Successful bids, which are defined by outcomes 2, 3 and 4 above, should result in a new bid record and the appropriate debit to be made on the users account. The available funds displayed for the current user should be adjusted accordingly. The last scenario is when the user accidently bids a price which they have already placed on this auction. In this case, the user's bid should be ignored and they should not be charged. In case where they happen to capture the lowest unique bid, their username should be immediately reflected as the currently winning bidder. Appropriate icons should be displayed with each of the statements above which are characteristic of success, failure or a near miss. The exact design of these icons should be reviewed when candidates are available, but please consult HYPERLINK "http://www.bidster.com/"http://www.bidster.com. Technically speaking, hitting the “Bid” button should trigger an AJAX call to the server to place the bid and establish the result of the operation. Client side Javascript should be used to modify the page to describe the outcome as detailed above. Bid Records Each time a user bids, a record of their bid needs to be created in the database. As much information as possible should be captured at this stage, to include at least the following details: Auction id Date & time of bid (local to the server) Username of the bidder Amount of the bid The auction id should be the unique identifier to the auction record that captures all aspects of the auction as described above. A database table that captures these bid records should later allow for bid history reports to be constructed for both users as well as the site administrator. History reports is the other competitive advantage of our site, as it allows customers to follow other auction participant's bid strategy, and to build their own bids strategy, based on this knowledge. Auction Termination and Items Purchasing Process An auction is terminated by virtue of it reaching the expiry date. Once an auction has expired, users should no longer be able to bid on that auction. However, he/she should be able to purchase the item he/she previously bided on. This possibility should be displayed in the site, and a relevant email should be automatically generated and sent to the customer. Web pages displaying live auctions should obviously filter out any auction that has not started or is expired. The site should include distinct pages to display closed and upcoming auctions. Once an auction is terminated, the software needs to select a winner. The minimum unique bid wins. If there are no unique bids, the software should find the smallest group of matching bids (I.e starting with 2 then 3 then 4 etc...) and select the first person in that group to bid as the winner. That selection can be made on the basis of the date time field on the bid record. Once an auction has completed, the administrator should be able to see a list of completed auctions in the admin console. From the console, it should be possible to see a complete report of the auction, as well as easily identify the winning bid. Associated with the winning record should be actions to control the work flow for notifying the winner, invoicing, and generating a shipping note. The system should also contain all the information about purchases made by customers after loosing the auctions. User Account Once a user has logged in, a My Account link should become visible to them. The account page for the user should allow them to view and amend their details which they provided during registration. Any changes to their email address requires a verification that the address is genuine. In addition, their account balance should be visible. A link to add funds to the account should be available, and various payment options provided. Paypal & credit card payments should be supported, and SMS will be required, as well as one additional local payment system (details of which will be provided further). A logged in user should be able to refer a friend once they have made 1 or more bids in any auction (i.e. their account has displayed some level of activity). The refer a friend feature should credit the users account with a configurable amount of money. Their account should only be credited once the friend has signed up and credited their account with some configurable monetary value. These money are only virtual and can be only used for purchasing bids. Administrators Console Various content management features need to be supported via the administrator console. A list of required features is as follows: Multi language features Site settings (languages, users, auctions) Configure funding plans (see HYPERLINK "http://www.bidster.com/"[login to view URL]) Banner adverts News letters Email templates to be triggered on certain events (registration email, auction won, an offer to purchase the item by remaining balance, promotional emails etc) List of closed auctions List of purchases made It needs to be in Java. Please send your proposals. Those companies having already worked with Reverse Auctions (other auctions) will have an advantage. Please only applicants from the UK
ID projekta: 616951

Več o projektu

9 ponudb
Projekt na daljavo
Aktivno pred 14 leti

Želite zaslužiti?

Prednosti oddajanja ponudb na Freelancerju

Nastavite svoj proračun in časovni okvir
Prejmite plačilo za svoje delo
Povzetek predloga
Registracija in oddajanje ponudb sta brezplačna
9 freelancerjev je oddalo ponudbo s povprečno vrednostjo $3.889 USD za to delo
Avatar uporabnika
i am interested.
$4.500 USD v 45 dneh
5,0 (1 ocena)
2,6
2,6
Avatar uporabnika
Please check PM.
$3.000 USD v 50 dneh
0,0 (1 ocena)
0,0
0,0
Avatar uporabnika
We are Kathmandu/Nepal based web development co., developed more than 400 auction web sites till date, We've lowest, highest, penny and dubli clone script which support multi-languages and sms bidding. Our script is using by USA, UK, European, Australian companies, We support 2yrs free of charge after releasing the project. Kindly discuss with me at pmb.
$4.500 USD v 31 dneh
0,0 (0 ocen)
0,0
0,0
Avatar uporabnika
Dear Sir or Madam our team can work on this project timely and professionally. we have enough experience to handle your requirements. we can convinced that SSH(Spring + Struts +Hibernate) structure will be the most appropriate solution for this project. yours truly
$3.000 USD v 60 dneh
0,0 (0 ocen)
0,0
0,0
Avatar uporabnika
Pleae check PMB for dtails.
$5.000 USD v 60 dneh
0,0 (0 ocen)
0,0
0,0
Avatar uporabnika
The project will be written in java, javascript and PHP mainly to give the exact result of your wish.
$3.000 USD v 60 dneh
0,0 (0 ocen)
0,0
0,0
Avatar uporabnika
Hi, Based in north London. Please check PMB for details. Cheers Sahil Polydiam Infosoft
$5.000 USD v 45 dneh
0,0 (0 ocen)
0,0
0,0
Avatar uporabnika
We are a new company based in Austin, TX. Our partners have over 10 years of experience in these areas.
$3.500 USD v 45 dneh
0,0 (0 ocen)
0,0
0,0

O stranki

Zastava UNITED KINGDOM
London, United Kingdom
0,0
0
Član(ica) od feb. 19, 2010

Verifikacija stranke

Hvala! Po e-pošti smo vam poslali povezavo za prevzem brezplačnega dobropisa.
Pri pošiljanju vašega e-sporočila je šlo nekaj narobe. Poskusite znova.
Registrirani uporabniki Skupaj objavljenih del
Freelancer ® is a registered Trademark of Freelancer Technology Pty Limited (ACN 142 189 759)
Copyright © 2024 Freelancer Technology Pty Limited (ACN 142 189 759)
Nalaganje predogleda
Geolociranje je bilo dovoljeno.
Vaša prijavna seja je potekla, zato ste bili odjavljeni. Prosimo, da se znova prijavite.