Basket Overview

Setting up an inBASKET site is not a difficult thing to do, but there is a lot involved. This overview should help you to understand all the components and where they go, etc.

There are really two main aspects to an inBASKET site. The first involves creating the configuration file and all the support files. The second is the actual "store front" that the customers see.

inBASKET Files

In addition to the configuration file, you will need to create several other files for inBASKET. The name and location of each of these files is entirely up to you since you specify them in the config file, but we reccomend placing them all in the ms2 directory and using a common prefix. Our demo uses basket.* for all file names, so that's what we'll assume here.

More details about each file, along with sample files, can be found in subsequent pages.

basket.frm

This is the order form file. It is an HTML file that contains an input form, usually prompting for shipping and payment info from the customer. This file doesn't get used until the customer already has something in their basket and they wish to submit the order.

basket.hdr

This is the header file. It is actually just an HTML file that is used to form the header or top portion of any pages that inBASKET generates.

basket.ftr

This is the footer file. It is actually just an HTML file that is used to form the footer or bottom portion of any pages that inBASKET generates.

basket.msg

This is the message file. It is actually an HTML file that is included in the bottom left corner of the basket contents display. This would normally be used to provide brief instructions for customers or to highlight a special sale, etc.

basket.mai

This is the mail file. It is a plain text "template" for the email message that gets sent to the customer when they submit an order.

basket.cou

This is the country list file. It is used to generate a pull-down list of country options in the order form file. You could simply embed the list right in your order form file, but then there would be no way of retaining the currently selected country value if/when the customer makes a mistake and has to redo part of the form. A sample country list is provided for you on the order form description page.

basket.pro

This is the province list file. It works exactly like the country list file except it is for provinces and states.

basket.mth

This is the payment method file. It works exactly like the country and province list files except it lists the available payment methods (eg: cheque, money order, credit card, etc).

basket.end

This is the "end" file. It works exactly like the header file except it is only used at the very end of a transaction, after the customer has submitted their order successfully.

basket.end2

This is an alternate "end" file that is used if the payment method was via one of the real-time credit card processing companies or i-Check. The idea is that the first "end" file might say something like "Print this page and send it along with your {method} to..." while this one might just say "Thanks for your order!"

Your Store Front

These are normal HTML files that are located in your regular web directory (normally the www directory). You can place all your products on a single web page, or spread them out over as many pages as you need - it makes no difference to inBASKET.

It is common for each individual product to have it's own "Add to basket" button, but you can define your pages to add multiple products with a single button. It's entirely up to you and how you create your pages. The key to remember is that each button represents a separate input form (ie: <form ...> ... </form>).

For more details about creating the input forms, read Creating the store pages.

<< BACK