> 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/specs-metafield.md).
# Specs 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 Specs, 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. specifications). Together they form custom.specifications, which is the address used in your theme to pull the value.
Field Data Type — Controls what kind of data the field holds. For Specs, a Multi-line text field is recommended. Technical specifications are product-specific and vary widely depending on the device type (phone, laptop, headphones, router, etc.). A free-text field allows your team to document all relevant specs for each product without being restricted to predefined options. If you want to support formatting such as bold headers, bullet points, or a table structure 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: Specs — displayed in bold as a visual header when editing product values (1–50 characters, no HTML)
* Name: specifications — must be unique within your Product fields (3–64 characters, letters, digits, underscores or dashes only)
* Description: Optionally add a note like Full technical 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 phones, only for laptops, etc.)
* Make visible to the Storefront API: Leave checked (default) — this makes the specs accessible in themes and custom storefronts
Click Next to continue.
Page 2 — Advanced Settings:
* Repeatable section: Leave unchecked — specs are a single block of technical 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 first spec in the section header when collapsed can help your team quickly identify products when scanning the product list.
* Show as collapsed when editing: Optionally check this — specs can be lengthy, so collapsing the section by default keeps the product edit page tidy. Editors can expand it when needed.
* 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 Specs 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 Specs Field Once the section is saved, click + Add field to add the actual field inside it. Fill in the details:
* Label: Specs
* Namespace: accentuate (ACF's default, or use your own e.g. tech)
* Key: specifications
* Field Data Type: Select Multi-line text — this gives your team a spacious text area to document full technical specifications per product. If you want to support formatting such as bold headers, bullet-pointed feature lists, or a table layout for easier scanning, choose Rich Text instead.
Step 5 — Save Click Save. Your Specs field will now appear inside its section on every product edit page in your Shopify admin, giving your team a dedicated space to enter detailed technical specifications for each product.
***
### Populating Specs Values on Products
One by one: Open any product in Shopify Admin, scroll to the Specs section added by ACF, type or paste the full technical specifications into the text area, and save. This is the most practical method for specs content since every product's specifications are unique and require careful attention to accuracy.
CSV import: Use the Export button to download a CSV template, fill in the specifications column for each product row, then re-import via the Import button. This is the fastest method when migrating specs from an existing product database or manufacturer datasheets.
***
### Displaying Specs 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 Specs field, position it on the page (typically in a dedicated Specifications or Technical Details section, or inside a collapsible accordion), and save. It will display automatically for any product with specs content added.
Liquid Code (all themes): Add this to your product template file where you want the specifications to appear:
For Multi-line text:
```
{% if product.metafields.custom.specifications %}
Technical Specifications:
{{ product.metafields.custom.specifications.value }}
{% endif %}
For Rich Text:
{% if product.metafields.custom.specifications %}
Technical Specifications:
{{ product.metafields.custom.specifications.value }}
{% endif %}
```
If you used a custom namespace (e.g. tech), replace custom with your namespace name.
***
### Tips & Best Practices
* Use manufacturer specs as your source — always source specifications directly from the manufacturer's official datasheet or product manual. Never estimate or guess at technical details.
* Be consistent with your format — decide on a standard structure for all specs entries and apply it across your range. For example: begin with the processor, then RAM, then storage, then display, then battery, then ports, then weight/dimensions. Consistency makes your product pages feel professional and easy to compare.
* Include the information customers actually compare — focus on the specs that matter most to your target customers. For a laptop, that's typically processor, RAM, storage, display size/resolution, battery life, and weight. For headphones, it's driver size, frequency response, impedance, and cable length.
* Use Rich Text for better readability — if specifications are lengthy or complex, choose Rich Text and format specs with headers, bullet points, or even a simple table layout. For example, separate storage options into a bulleted list rather than a paragraph.
* Keep a master spec document — maintain an internal reference document with approved specs for each product, sourced from official manufacturer documentation. Use this as your source of truth when populating ACF via CSV or one by one.
* Use "Show as collapsed when editing" — enabling this on Page 2 of setup keeps the product edit page tidy for your team, since detailed specs take up significant vertical space.
* Consider creating a Specs comparison table — once all products are tagged with specs, use this data to create comparison tables or spec sheets on your category pages, helping shoppers make informed decisions.
* Update specs when products are refreshed — monitor for product updates or new versions from manufacturers and update your specs field accordingly. Out-of-date specs damage customer trust.
* Don't duplicate Compatibility data — if you have a separate Compatibility metafield, avoid repeating compatible devices in the specs field. Keep specs focused on technical performance metrics, and use Compatibility for device compatibility information.
* 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 Specs as translatable if you need localised specification language for different markets, particularly for hardware that may have regional variants.
***
### Quick Reference
| Setting | Value |
| ---------------- | ------------------------------------------------------------------------------------- |
| Scope | Products |
| Section Title | Specs |
| Section Name | specifications |
| Field Label | Specs |
| Namespace | custom |
| Key | specifications |
| Full Identifier | custom.specifications |
| Field Data Type | Multi-line text (or Rich Text for formatting) |
| Storefront API | Enabled (checked by default) |
| Liquid Reference | {{ product.metafields.custom.specifications.value }} |
| Tip | Enable "Show as collapsed when editing" to keep the product edit page tidy |
| Best Practice | Use Rich Text with headers and bullet points for lengthy specs to improve readability |
***
For further details, visit the official ACF documentation at help.accentuate.io
---
# 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/specs-metafield.md?ask=
```
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.