World Food Day: show what's in your food, on every product page

October 16 is World Food Day. If you sell food or drink on Shopify, it's a good day to check that every product page answers the questions shoppers ask in a shop: what's in it, and is it safe for me?

· 4 min read

In a shop, people turn the pack over. Online, they scroll for the same thing: ingredients, allergens, nutrition per 100 g. When it isn't there, they email you, or they buy somewhere else.

The problem: a nutrition table needs a table

Shopify's product fields can hold text, numbers and links, but not a table. So nutrition information ends up as a photo of the label (unreadable on a phone, invisible to search engines and screen readers) or pasted into the description, where every product looks a little different.

A Table field for every product

Cartsella Studio adds a Table field you fill in like a spreadsheet, right on the product. Start from the specification template or a blank grid, give it a header row ("Per 100 g", "Per portion"), and add a line per nutrient. Place it on your product page once, and every product shows its own table, styled to fit your theme.

The Cartsella Studio table editor filling in a table on a product, with buttons to add rows, columns, merge cells and add a header row

Fields worth adding for food and drink

Labelling rules differ from country to country, so check which information you're required to show where you sell. The fields above make it easy to show it consistently.

Make sure every product has it

On Pro and Agency, mark the nutrition table and the allergens as "Required for us" in a field guide, and explain what goes in each. The fill-in report lists every product still missing one, and "Next missing" takes your team from one to the next. Suppliers can read the guide through a share link, so their spec sheets arrive in the format you need.

Try it in staging first

Fill in a few products in your staging store, check how the table looks on a phone, then move the fields you choose to your live store from Metafields › From test store, with a preview first and 30 days of undo.

Read next: Why we built a Table field · Metafields · Field guides