Announcement:Materials and articles for ProductCart 5 can be found at our brand new support center.

Create an account to edit articles | See Formatting Syntax for Wiki syntax | We look forward to your contribution!

Database Structure - How Build To Order Prices are stored

BTO and configuration prices

When you assign a Standard Product or a Build To Order Only Item to a Build To Order Product, the prices for those items are saved separately from their original price. This allows you, for example, to charge less for a “Hard Disk” when it's part of a customizable desktop computer compared to when the same product is sold as a stand-alone product.

You can assign the following prices for each item that is part of a Build To Order product configuration:

How the different configuration prices are saved to the database

Regular configuration items

They are saved to the configSpec_products table

  • specProduct = ID of the BTO product
  • configProduct = ID of the configuration item
  • price = online price
  • Wprice = wholesale price

Additional charges

They are saved to the configSpec_Charges table

  • specProduct = ID of the BTO product
  • configProduct = ID of the configuration item
  • price = online price
  • Wprice = wholesale price

Pricing category prices

In both cases, pricing category prices are saved to the pcCC_BTO_Pricing table:

  • idCustomerCategory = Pricing category ID
  • idBTOProduct = ID of the BTO product
  • idBTOItem = ID of the BTO configuration item
  • pcCC_BTO_Price = price for that item when the customer belongs to this pricing category

QR Code
QR Code Database Structure - How Build To Order Prices are stored (generated for current page)