Skip to main content

Product Specification block

Written by Jalal
Updated over 2 weeks ago

The Product Specification block lets you display important product details like material, size, weight, care instructions, and more in a clean, structured list.

This helps customers quickly understand your product and improves trust and conversions.

How to add the Product Specification block

  1. Go to Online Store → Themes

  2. Click Customize

  3. Open a Product page

  4. In the left sidebar, open the Main product section

  5. Click Add block

  6. Select Product Specification

  7. Enter your specifications in the Specifications field

How to format specifications

Each specification must follow this format:

Label: Value

Add one specification per line. You can enter more specifications using commas.

Each comma , creates a new line item in the list.

Example:

Material: 100% Cotton,Fit: Regular fit,Weight: 250 g,Care: Machine wash cold,Origin: Made in Italy,Warranty: 1 year

Important rules

1) Always include a colon

:

Correct:

  • Material: 100% Cotton

Not supported / won’t render properly:

  • Material 100% Cotton

2) Don’t leave empty values

Avoid:

  • Material:,Fit: Regular


Why “one per line” doesn’t work

If you press Enter (new line), the theme does not treat it as a new specification item.

Only commas , are used to split the list into separate rows.

So if you want separate bullets/rows, use commas.

Metafields support (recommended for large catalogs)

This block also supports product metafields, so you can manage specifications directly from each product instead of editing the theme.

How to set up

  1. Go to Settings → Metafields and metaobjects → Products

  2. Click Add definition

  3. Create a metafield:

    • Name: Specifications

    • Type: List → Single line text

  4. Save it

Then open any product and add values like:

Material: 100% Cotton
Fit: Regular fit
Weight: 250 g

After selecting the metafield in the block it will display the specification block for the products that have values added in the metafield.

Did this answer your question?