one solution may be to have 2 (or more) main tables for your customer, one contains the common information
the other is an extension table containg key pairs
a 3rd table groups and identifes the key pair
table Prod 'existing table
ProdID 'system generated Id
etc....
table ProdExt
ProdID 'fk to table product
KeyID 'fk to table keypair
KeyValue 'contians the required value
table KeyPair
KeyID 'system generated Id
KeyName 'descriptuion of key eg "ProductHeight"
KeyGroupID 'fk in KeyType
SortSeq 'allows you to control the sequence in which the key pair should be presented
table KeyType
KeyGroupID 'system generated Id
KeyGroupDesc ' description eg 'measurements
-you could extend KeyType to include some form of hierarchy
its not necessarily the way I'd want to do it, but it could meet your requirements. I'd want to bottom out why some customers have different information requirements, and try to work out if that difference is because you don't have all the information required at present, or if your teacher wants to find out if you have been awake this last 4 months.
HTH