Product is a central part of database. Product mean industrial products, product’s family, materials and other types of productions.

Each product can have a list of * Product properties.

Each product should be assigned to category.

Product code and name

Product short name (code) are optional. Use it for common abbreviation or system identifier of product.

Name is required field and contain full name of product.

Example - look at PVC page. PVC is a short name, Polyvinyl chloride - full name.


Use short name and full name for correct, regular naming. For organization-specific trade-name (or manufacturer code) use the local code field in linked org‘s list! See more Local code.

External code

For each product you can assign the code for linking with external on-line databases. Now available 4 chemical databases (use it for chemical products and substances):

  • PubChem
  • ChemSpider
  • ZINC
  • ChEBI

Example from Unsymmetrical dimethylhydrazine page:

External database Example of code Resulting link (auto generating)
PubChem 5976
ChemSpider 5756
ZINC no data  
ChEBI 18853

Product templates and inheriting

Each product can have the list of inherited products. In real world it’s mean what:

  • ‘product1’ (child) are designed based on ‘product2’ (parent) OR
  • ‘product2’ (parent) is a product-family, and ‘product1’ (child) are product from this family.

Child product inherits the properties from child - and can overwrite it values.


Do not confuse inheriting and BOM! Inherit - mean designed based on. BOM mean included to assembly!

You can mark parent product as ‘template’. This mean what it used as basic pattern for ease the data filling of inherited product. Use it for basic (abstract) products or for product family.


Look at Most used templates page on site.

Examples from base - PVC


Screen-shot taken at 20 jan 2015.

Polyvinyl chloride product template have two inherited product:

Some properties (melting point, for example) of rigid and flexible PVC are equal to base PVC, and some properties (density, for example) - are not equal.

Examples from base - A320neo

A320neo product have two editions:

In real world A320neo is a family, and each airline species should be with PW or CMF engine, which mean different BOM and technical specification for each of them.

Examples from base - Basic material template

Some templates hierarchy could be very complex - see Basic material template for example. Such abstract template can’t contain precise values - only list of common properties.

Product properties

Each product can have a list of measurable and enumerable properties. Property value can be own by itself or inherited from parent product.

For overview - see the screen-shot of example 102NU70 Bipolar transistor.


Screen-shot taken at 20 jan 2015.

  • Inherited - value are equal to same value in parent product
  • Overrided - property inherited from parent, but value are different
  • Own - property doesn’t inherited

Measurable parameters

  • Measurable property type
  • Amount equality type ( = by default, <= or < )
  • Amount (integer, float, fraction, proportion) with optional equality type ( = equal by default, =< great or equal, < great )
  • Maximum amount (integer or float)
  • Engineering tolerance (integer or float)
  • Unit
  • Measurement condition ( Measurement conditions in properties)

Amount can be:

Numerical type Example 1 Example 2
Integer 125 -15487000
Float 154.48 -7e8
Fraction 1/9 -4 3/4
Proportion 1:8 7:9

Enumerable parameters


Bill of materials for this product.

  • Position (optional)
  • Subpoduct
  • Amount
  • Unit (optional)

Linked orgs

List of organizations, linked with product - manufacturers, sellers etc. Described in Organization linked product page.