Separating product details from essential product information

[QbDesu]

I suggest separating product details such as caffeine, alcohol, energy, sugar to be their own thing and not part of the essential product information itself. It's also kind of weird that caffeine and sugar have specific units based on grams while the unit for energy is part of the servers configuration.

I would like to have it separate because it is kind of arbitrary information and not really essential for the transactions themselves. I mean there is also these:

• halal : boolean
• kosher : boolean
• vegan : boolean
• vegetarian : boolean
• peanut : boolean
• milk : boolean
• gluten : boolean
• lactose : boolean
• lipids/fats : integer
• carbs : integer
• proteins : integer
• weight : integer

I am not really suggesting adding all these but just list them so you see where I'm coming from. I would also suggest these details being their own thing and not clearly defining which details are expected/allowed and which aren't.

[YtvwlD]

Good point. This was initially designed for drinks.

[uwap]

Also I'm surprised that not the entire nutrition label, but only parts of it are specified in the specs. There might be different capabilities depending on the application, but I feel like it would be nice to have them included in the specs.

[uwap]

My idea would be to create an endpoint that will provide product information like this:

GET products/label or GET products/{id}/label

{
  "kcal": 308,
  "kj": 1300, // both kcal and kj included makes the server option unneccessary
  "fat": 7.3, // grams per 100 volume_unit.
  "saturated_fat": 4.2,
  "carbs": 43,
  "sugar": 22,
  "protein": 4.2,
  "salt": 3.2,
  "fiber": 0.2,
  "alcohol": 4.2,
  "caffeine": 25,
  "volume_amount": 500, // amount per piece
  "volume_unit": "ml", // "g" or "ml". this would mean 500ml per bottle/piece/unit
  "vegan": false, // whether it is labeled as vegan on the package
  "vegetarian": true, // whether it is labeled as vegetarian or vegan on the package
}

Ideally, to fully provide the whole label, allergens and ingredients should be listed. This is however not as simple as providing as list of strings, as different services may use different languages and also support multiple languages. This would be a more complicated topic and require more work.

What do you think about an endpoint like this? It could be used to show nutritional labels when developing a UI.

The normal product endpoint would then be reduced to:
GET products or GET products/{id}

{
    "id": 0,
    "name": "string",
    "price": 150,
    "created_at": "2023-07-04T12:11:20Z",
    "updated_at": "2023-07-04T12:11:20Z",
    "active": true,
    "image": 0
}