> For the complete documentation index, see [llms.txt](https://help.accentuate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.accentuate.io/use-case-guides/tech-and-electronics/dimensions-weight-metafield.md).

# Dimensions / Weight Metafield

### Prerequisites

Before you begin, make sure you have:

* An active Shopify store
* Accentuate Custom Fields installed from the Shopify App Store
* Staff permissions to access Apps in your Shopify admin
* (Recommended) An Online Store 2.0 theme, which allows metafield values to be displayed via the theme editor without touching code

***

### Key Concepts to Know First

Scope — The Shopify object the metafield attaches to. For Dimensions / Weight, this will be Products.

Namespace & Key — The unique identifier for your field. The namespace groups related fields (e.g. custom) and the key is the specific field name (e.g. dimensions\_weight). Together they form custom.dimensions\_weight, which is the address used in your theme to pull the value.

Field Data Type — Controls what kind of data the field holds. For Dimensions / Weight, a Multi-line text field is recommended. Physical specifications vary widely depending on product type (laptop dimensions differ completely from monitor dimensions, which differ from cable length). A free-text field allows your team to document all relevant size and weight information for each product without being restricted to predefined options. If you want to support formatting such as headers or bullet points for easier scanning, choose Rich Text instead.

***

### Step-by-Step Guide

Step 1 — Open ACF from your Shopify Admin Go to your Shopify Admin, click Apps in the left sidebar, and open Accentuate Custom Fields. You'll land on the ACF dashboard, which shows the Metafields and metaobjects section with cards for Products, Shops, Metaobjects, and Customers.

Step 2 — Open Product Metafields In the Products card, click the Metafields button. This takes you into the Product Custom Fields screen where you can see all existing fields listed with their types and manage your definitions.

Step 3 — Add a New Section Click the + Add section button in the top-right area of the Product Custom Fields screen. An Add Section modal will open across two pages.

Page 1 — Basic Details:

* Title: Dimensions / Weight — displayed in bold as a visual header when editing product values (1–50 characters, no HTML)
* Name: dimensions\_weight — must be unique within your Product fields (3–64 characters, letters, digits, underscores or dashes only)
* Description: Optionally add a note like Physical dimensions and weight specifications for this product — supports Markdown
* Color: Leave as the default #dfe3e8, or choose a colour to visually distinguish this section from others in your Tech & Electronics field setup
* All fields in this section apply to: Leave as All types unless you want to restrict this to specific product types (e.g. only for laptops, only for monitors, etc.)
* Make visible to the Storefront API: Leave checked (default) — this makes the dimensions and weight values accessible in themes and custom storefronts

Click Next to continue.

Page 2 — Advanced Settings:

* Repeatable section: Leave unchecked — dimensions and weight are a single block of information per product, not a repeating block.
* Include value of first text field: Optionally check this — since the field is a text field, showing a preview of the weight in the section header when collapsed can help your team quickly identify the size/weight profile of a product when scanning the product list.
* Show as collapsed when editing: Optionally check this — physical specs are typically brief, so collapsing the section by default is optional. It can keep the product edit page tidy without hiding critical information.
* Hide section: Leave unchecked — checking this would make the section invisible in the editor entirely.
* Show section even if empty: Optionally check this if you want the Dimensions / Weight section to always appear on products, even before specifications have been added.
* Exclude from layout: Leave unchecked — only tick this if you want the section excluded from ACF's layout editing tools.

Click Done to save the section.

Step 4 — Add the Dimensions / Weight Field Once the section is saved, click + Add field to add the actual field inside it. Fill in the details:

* Label: Dimensions / Weight
* Namespace: accentuate (ACF's default, or use your own e.g. tech)
* Key: dimensions\_weight
* Field Data Type: Select Multi-line text — this gives your team a spacious text area to document all relevant size and weight information per product. If you want to format dimensions with headers or bullet points for easier scanning, choose Rich Text instead.

Step 5 — Save Click Save. Your Dimensions / Weight field will now appear inside its section on every product edit page in your Shopify admin, giving your team a dedicated space to enter physical specifications for each product.

***

### Populating Dimensions / Weight Values on Products

One by one: Open any product in Shopify Admin, scroll to the Dimensions / Weight section added by ACF, type or paste the dimensional and weight specifications into the text area, and save. This is the most practical method since every product's physical specifications are unique.

CSV import: Use the Export button to download a CSV template, fill in the dimensions\_weight column for each product row, then re-import via the Import button. This is useful when migrating dimension and weight data from an existing product database or manufacturer datasheets.

***

### Displaying Dimensions / Weight on Your Storefront

Theme Editor (no code, OS 2.0 themes): Go to Online Store → Themes → Customize. Open a product template, click Add Block, select an ACF or Metafield block, choose the Dimensions / Weight field, position it on the page (typically in a Specifications or Product Details section), and save. It will display automatically for any product with specifications added.

Liquid Code (all themes): Add this to your product template file where you want the dimensions and weight to appear:

For Multi-line text:

```
{% if product.metafields.custom.dimensions_weight %}
  <div class="dimensions-weight">
    <strong>Dimensions & Weight:</strong>
    <p>{{ product.metafields.custom.dimensions_weight.value }}</p>
  </div>
{% endif %}
For Rich Text:
{% if product.metafields.custom.dimensions_weight %}
  <div class="dimensions-weight">
    <strong>Dimensions & Weight:</strong>
    {{ product.metafields.custom.dimensions_weight.value }}
  </div>
{% endif %}
```

If you used a custom namespace (e.g. tech), replace custom with your namespace name.

***

### Tips & Best Practices

* Use manufacturer specifications as your source — always source dimensions and weight directly from the manufacturer's official datasheet or product manual. Never estimate physical specifications.
* Include all relevant dimensions — depending on the product type, include all applicable measurements. For a laptop: width × depth × thickness. For a monitor: width × height × depth and bezel width. For a cable: total length and connector types. Be comprehensive.
* Be consistent with units — decide on a standard unit system (metric or imperial, or both) and apply it uniformly across your entire product range. For example: always use centimeters and kilograms, or always use inches and pounds. Include the unit in every measurement (cm, kg, in, lbs) to avoid confusion.
* Include weight with and without packaging — for portable products, consider listing both the device weight and the shipping weight (with packaging). Shoppers caring about portability want to know device weight; logistics teams want to know shipping weight.
* Use Rich Text for better readability — if you're listing many dimensions (width, depth, height, bezel, footprint, stand dimensions, cable length, etc.), use Rich Text with headers or bullet points. For example:
* Closed Dimensions: 12 × 8 × 0.3 inches
* Weight: 2.7 lbs
* Stand Base: 8 × 6 inches
* Round dimensions appropriately — use precision that reflects the product's design. A laptop dimension might be 12.5 × 8.2 × 0.3 inches. A desktop monitor might be 27" × 16" × 2". Don't over-specify or under-specify.
* Include mounting information — for products that mount (TVs, monitors, wall-mounted speakers), note VESA mounting patterns or other relevant mounting specs so shoppers know if their existing mounts will work.
* Note dimensions with popular reference points — for portability, you might add a comparison: "Weighs 3.2 lbs — lighter than a standard laptop". This helps shoppers intuitively understand size and weight.
* Keep a master spec document — maintain an internal reference document with approved dimensions and weight for each product, sourced from official manufacturer documentation. Use this as your source of truth when populating ACF via CSV or one by one.
* Update when products are redesigned — monitor for product refreshes or redesigns from manufacturers. Physical dimensions sometimes change between generations, and outdated specs damage customer trust.
* Don't duplicate Specs field — if you have a separate Specs metafield, avoid repeating dimensions and weight information in both fields. Keep Specs focused on technical performance metrics, and keep Dimensions / Weight focused on physical size.
* Avoid the shopify namespace — it is reserved by Shopify and can cause conflicts. Use custom or a brand-specific name like tech.
* Multi-language stores — ACF supports translatable metafields. Mark Dimensions / Weight as translatable if you serve markets that use different measurement standards (metric vs imperial).

***

### Quick Reference

| Setting          | Value                                                                                        |
| ---------------- | -------------------------------------------------------------------------------------------- |
| Scope            | Products                                                                                     |
| Section Title    | Dimensions / Weight                                                                          |
| Section Name     | dimensions\_weight                                                                           |
| Field Label      | Dimensions / Weight                                                                          |
| Namespace        | custom                                                                                       |
| Key              | dimensions\_weight                                                                           |
| Full Identifier  | custom.dimensions\_weight                                                                    |
| Field Data Type  | Multi-line text (or Rich Text for formatted specs)                                           |
| Storefront API   | Enabled (checked by default)                                                                 |
| Liquid Reference | {{ product.metafields.custom.dimensions\_weight.value }}                                     |
| Best Practice    | Include all relevant dimensions for the product type (width, depth, height, thickness, etc.) |
| Best Practice    | Always include measurement units (cm, kg, inches, lbs, etc.)                                 |
| Best Practice    | Use consistent unit system across all products                                               |

***

For further details, visit the official ACF documentation at help.accentuate.io

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.accentuate.io/use-case-guides/tech-and-electronics/dimensions-weight-metafield.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
