This document will discuss options and process for having an e-commerce site created to complement your WiscWeb site.
Please note that the payment content will neither be hosted within nor be editable from the larger WiscWeb project. It will be hosted in a separate account with DoIT Web Hosting*. However, it can be styled, by DoIT's Web and Mobile Solutions team (WaMS)**, to look like the rest of your website. It will receive its own sub-directory location within the larger charge.wisc.edu domain (i.e. https://charge.wisc.edu/yourprojectname) and you can link out to this location from your WiscWeb site.
*You may be charged a monthly fee for the hosting of the site. Currently, the hosting of charge.wisc.edu is covered but this may not be an option in the future.
**DoIT's Web and Mobile Solutions team (WaMS) works on a cost-recovery basis and therefore, development of the payment piece, as well as stylistic embellishments, will incur charges.
(1) With a Shopping CartA shopping cart storefront is usually a very complex site. But in general the point of commonality is the shopping cart page. No matter how large the site is everything ends up on the shopping cart page. This page is interfaced to the CashNet pages in the same way as a shopping cart site. All information about shipping, tax, rebates, etc is collected on the shopping cart page and stored in a local database. The amount is then sent to CashNet and the customer continues as in the other setups.(2) Without a Shopping CartA simple storefront will be one page long and contain all the items that are for sale. The user indicates which items they wish to purchase, fills out their customer information and submits the form. The rest of the process works like the simple registration.
(3) Simple RegistrationA simple registration page can contain information such as name, institution, email, multiple registration types, food preferences or lodging requirements. All the data requested fits on one page and none of the information on the page changes dynamically. It's a simple HTML page that customer fills it out and submits it all at once.(4) Dynamic RegistrationA dynamic registration page has some element that can change each time the page is loaded. An example is a registration page where the customer has to select among different sessions. As sessions fill up they are automatically taken off the page. This type of page requires a database on the back end which is queries each time the page is brought up. Once the page is brought up the rest of the process works like the Simple registration page.