Adding prices

[rsciolino]

I have all data entered into Catalog with the exception of prices. What would be the quickest way to add prices for about 800 products? I have tried exporting to a spreadsheet but have not been able to have excel properly display the data.

[garyhay]

Use the ActinicCatalog.mdb file in the site 1 folder

[Jan]

Prices are a bit complex because they can be stored in several places, these are the options that I know of.

I have described how they are stored on the database at the end of this email but it's horribly complicated and you might be better off not reading it.

It you are only using prices entered for each product then you should be able to use hierarchical importing from an excel spreadsheet to update the prices. When you use hierarchical importing you only have to include the fields you want to maintain externally so it becomes quite easy.

If you are using the whole range of product pricing available I would suggest setting up the prices in catalog and then exporting them and maintaining them externally after that.

If you decide to edit then on the database and use product pricing only, just open the table called products and edit the prices, the prices are stored * 100. For £4.50 is stored as 450.

Regards.

Jan.

====== database pricing summary follows.

1) Prices are stored against products. These prices will be used by products that have the pricing model set to 'product price' and also by permutations and components that are linked to products and have the prices set to 'use linked product price'.

2) Prices are stored as pricing records against permutations. These are held in the productProperties table, the record type is 4. These records will be created when you set override pricing in the permutation tab. The nParentPropertyID will be set to the permutations id in this case.


3) Prices are stored as pricing records against components. These are held in the productProperties table, the record type is 4. These records will be created when you set up price schedules on the component tab. The nParentPropertyID will be set to the component in this case.

4) Prices are stored as pricing records against products. These are held in the productProperties table, the record type is 4. These records will be created when you set up price schedules on the component tab. The nParentPropertyID will be set to the 0 in this case and the sProductRef will be set to the products reference.

In business prices are also changed by the settings in the price schedule table - but only when customers are logged in and then they are calculated from the retail price so you don't have to worry about these when setting prices.