Question

I have a ‘customers’ table. Each record contains a customer name, email, address, etc.

I have an ‘skus’ table. Each record contains the name of an SKU. e.g. “Super Software Bundle”.

An SKU represents a purchaseable item at a single price point. The purchased item can include one or more products.

e.g. The SKU record named “Super Software Bundle” may represent two products: product1 and product2.

For usability/ease reasons, other tables need to keep track of not only skus purchased, but the individual products a customer may have access to.

Question: how should I represent the variable sized nature of the SKUs in the database, where an SKU can represent from 1 to n products? Thanks for any help.

Answer 1

You will need a third table, that manages the relation between SKU and products, as a product may be part of more than one SKU (I guess). You have to model a m:n-relation.

product

• id
• name
• price
• …

sku

• id
• name
• price
• …

sku_product

• id
• sku_id
• product_id