QuoteWerks Native Product Databases

QuoteWerks native product databases are pricelists that you create and store the lists of products and services that you will be quoting. You can have an unlimited number of these product databases, allowing you to easily manage your products and vendors.

You might ask, “Why would I set up more than one product database”? If you purchase products from several vendors you will want to store each vendor’s product information in a separate database. Storing each vendor’s products in a separate database makes it easier to manage the importing and updating of that vendor’s data. In addition, because many vendors carry the same items, with the same manufacturer part numbers, you must have them in separate database to avoid duplicate part numbers. That is why QuoteWerks uses the manufacturer part number field to uniquely identify a product inside a product database. If the same manufacturer part number is in the database for five different vendors, QuoteWerks would not know which one to use The only way to organize your products so that you only have 1 unique part number for multiple vendors is to have a product database for each vendor. This way you can easily find the product you are looking for by a unique part number in the appropriate vendor database for the specified manufacturer part number.

Lastly, this is critical if you want to use QuoteWerks’ price refreshing, price comparison, required items, substitute items, optional items and purchase order functions. QuoteWerks must be able to uniquely identify an item by its manufacturer part number and vendor for these features to work.

The QuoteWerks Product Import Wizard discussed in Importing Products allows you to import your vendor’s product and service information into a QuoteWerks native product database. It is required that you setup a product database for each vendor that you purchase products and services from. Please note, depending upon the network operating system, the initial QuoteWerks start up time may be lengthened by the number of product databases that you setup.

See the following topics for more information:

•Creating Native Product Sources

•Cloning an Existing Native Product Database

•Linking to an Existing Native Product Database

•Removing the Link to Any Existing Product Data Source

•Renaming an Existing Product Data Source

•Password-Protected Native Access Product Databases