Ubercart Marketplace adds multiple seller support to the Ubercart module. It includes a series of modules that limit the access to Ubercart functions for sellers. Additional functionality is added to support this from both a marketplace seller's point of view and the store administrator's view. Sellers (with the proper access permissions) gain the ability to view their products, track and fulfill their orders, and monitor their sales reports. Store administrators can view seller reports based on seller order statuses and seller sales.

The uc_addresses module adds support for one or more addresses in the user's profile. When users register, they must provide an address. Users can then add more addresses and edit or delete existing addresses. One address must be designated as the default address and cannot be deleted (but it can be edited).

The Ubercart order process is altered so that users select delivery and billing addresses from their collection of addresses rather than from previous orders. Any new addresses entered during the order process are automatically added to the user's list.

From business point of view, shopkeepers basically want their clients to:

1. Find a product
2. Add the pruduct(s) to the cart
3. Proceed to checkout and pay

This module integrates Ubercart with CiviCRM. This version has been tested with CiviCRM 1.9 and CiviCRM 2.0.

When a customer buys something from the Ubercart store, the name and address information they provide is added to the CiviCRM contact database. If the customer has a simple contact record generated by synching CiviCRM from the Drupal user table, that record is updated with the new information. If no contact record exists, one is created.

Repeat customers are your best customers; you can rely on them to keep coming back to your store so long as you provide the goods or services they need. They are a steady revenue stream, an easy sell. But to quickly close the sale you need to make it easier for them to find and purchase more of the same stuff they've ordered previously.

A copy/paste of the UberCart documentation found at http://www.ubercart.org/docs/user. This is without any editing except to create the TOC.
It is hoped that after some editing, a PDF version will also be available.
Note that OpenOffice.org is required to view the file ( http://www.openoffice.org )

Of course, the community may contribute, which is why it is in an editable format.

Currently a very very simple module to give email validation to attributes who have names containing the word "email". Could be modified to offer any other type of validation.

Done to scratch a itch, but may be useful for other people.

Normal use at your own risk, no warranty etc stuff applies.

This module fills a void in Ubercart, since it depends on javascript, that there is no notification of any kind that javascript is required. If the user does not have javascript enabled, they are redirected on checkout to a page with information on how to enable javascript.

Tracking information is probably the most important thing the customer is interested in seeing after an order is placed! The customer wants to know "Where's my stuff?", and you don't want him bugging you about it.

This module lets your customer (or you, the admin) track shipped packages. It uses a hook to interface with installed shipping methods, so it can support tracking packages sent by any carrier, provided the hook is implemented. This module comes with hooks pre-written for FedEx, UPS and USPS.

The manufacturer module lets you list manufacturers in a taxonomy vocabulary and assign them to products. It also adds a few manufacturer specific pages and form settings to store information you might require for your products' manufacturers.

Advanced users may consider simply making their own manufacturer type with CCK and assigning them using a node reference field from the products for greater flexibility.