Origin 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 Origin, 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. origin). Together they form custom.origin, which is the address used in your theme to pull the value.

Field Data Type — Controls what kind of data the field holds. For Origin, a Multi Select is recommended. A single food or beverage product can be sourced from multiple regions or countries simultaneously — for example, a coffee blend might combine beans from Brazil, Colombia, and Ethiopia; or a product might have a primary origin plus secondary sourcing locations. Multi Select allows all relevant origin information to be tagged clearly, helping shoppers understand where their food comes from.

---

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: Origin — displayed in bold as a visual header when editing product values (1–50 characters, no HTML)

• Name: origin — must be unique within your Product fields (3–64 characters, letters, digits, underscores or dashes only)

• Description: Optionally add a note like Geographic origin, sourcing location, and country or region where this product comes from — supports Markdown

• Color: Leave as the default #dfe3e8, or choose a colour to visually distinguish this section from others in your Food & Beverage 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 coffee, only for chocolate, etc.)

• Make visible to the Storefront API: Leave checked (default) — this makes the origin values accessible in themes and custom storefronts

Click Next to continue.

Page 2 — Advanced Settings:

• Repeatable section: Leave unchecked — origin is a single set of values per product, not a repeating block.

• Include value of first text field: Leave unchecked — not needed for a select-type field.

• Show as collapsed when editing: Leave unchecked — keeps the section expanded by default so it is easy to find and fill in when editing a product.

• 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 Origin section to always appear on products, even before any values have been assigned.

• 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 Origin Field Once the section is saved, click + Add field to add the actual field inside it. Fill in the details:

• Label: Origin

• Namespace: accentuate (ACF's default, or use your own e.g. food)

• Key: origin

• Field Data Type: Select Multi Select — this allows multiple origin locations to be assigned to a single product at the same time

Step 5 — Add Your Origin Options Once Multi Select is chosen, add each allowed value one by one:

Coffee Origins:

• Brazil

• Colombia

• Ethiopia

• Kenya

• Peru

• Vietnam

• Indonesia

• Guatemala

• Honduras

• Costa Rica

• Uganda

• Tanzania

• Rwanda

• Panama

• Mexico

• Single-Origin (Specify Region)

Chocolate & Cocoa Origins:

• Ecuador

• Ghana

• Ivory Coast / Côte d'Ivoire

• Madagascar

• Peru

• Dominican Republic

• Venezuela

• Cameroon

• Comoros

• Single-Origin Cacao

Wine & Beverage Origins:

• France

• Italy

• Spain

• Portugal

• Argentina

• Chile

• Australia

• New Zealand

• California

• Washington

• Oregon

• Napa Valley

• Sonoma

• Bordeaux

• Tuscany

• Rioja

Olive Oil & Mediterranean:

• Spain

• Italy

• Greece

• Portugal

• Morocco

• Tunisia

• Turkey

• Extra Virgin (Single-Origin)

Spice Origins:

• India

• Indonesia

• Vietnam

• Thailand

• Madagascar

• Sri Lanka

• Zanzibar

• Mexico

• Turkey

• Morocco

• Ethiopia

Honey & Sweeteners:

• New Zealand (Manuka)

• Australia

• Canada

• France

• Spain

• Raw Honey (Specify Region)

• Maple (Canada)

Specialty & Gourmet:

• Japan (Matcha, Sake, etc.)

• France (Wine, Cheese, etc.)

• Italy (Pasta, Olive Oil, etc.)

• Switzerland (Chocolate, etc.)

• Belgium (Chocolate, Beer, etc.)

• Scotland (Whisky, etc.)

• Mexico (Vanilla, Chiles, etc.)

Domestic & Regional:

• Locally Sourced

• Domestically Produced

• USA-Made

• Canadian-Made

• European-Made

• Artisan Producer (Specify)

Blend / Multi-Origin:

• Blend (Multiple Origins)

• Regional Blend

Add, remove, or rename options at any time to match your store's specific range — existing product values are preserved when you edit the list.

Step 6 — Save Click Save. Your Origin field will now appear inside its section on every product edit page in your Shopify admin.

---

Populating Origin Values on Products

One by one: Open any product in Shopify Admin, scroll to the Origin section added by ACF, select all applicable origin locations from the multi-select dropdown, and save.

CSV import: Use the Export button to download a CSV template, fill in the origin column for each product row (separate multiple values with the delimiter shown in the template), then re-import via the Import button. Best for large catalogs or when importing products with multi-origin sourcing.

---

Displaying Origin 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 Origin field, position it on the page (typically in the product description or key details section), and save. It will display automatically for any product with values set.

Liquid Code (all themes): Add this to your product template file where you want the origin information to appear:

{% if product.metafields.custom.origin %}

<div class="origin">

<strong>Origin:</strong>

{% for location in product.metafields.custom.origin.value %}

<span class="origin-tag">{{ location }}</span>

{% unless forloop.last %}, {% endunless %}

{% endfor %}

</div>

{% endif %}

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

---

Tips & Best Practices

• Origin is a growing consumer priority — many shoppers care deeply about where their food comes from, whether for quality, sustainability, fair trade, or local support reasons. Clear origin tagging helps these shoppers find products aligned with their values.

• Be specific with geography — instead of tagging broadly "Central America", tag the specific country or region: "Colombia", "Honduras", "Guatemala". Specificity helps shoppers understand exactly where their product comes from.

• For blends, list all source origins — if a product blends beans, fruits, or ingredients from multiple countries, tag all of them. For example, a coffee blend might be tagged as "Brazil", "Colombia", and "Ethiopia" simultaneously.

• Use Origin for collection filtering — connect origin as a filter in Online Store → Navigation → Filter menus. Shoppers looking for "Single-Origin Ethiopian Coffee" or "Locally Sourced Honey" can then filter directly.

• Use Origin to build sourcing-based collections — create automated collections for each origin (e.g. "All Peruvian Coffee", "All Italian Wines") by filtering on custom.origin. These collections help shoppers explore products by geographic origin.

• Distinguish single-origin from blends — include tags like "Single-Origin" or "Blend" to help shoppers understand whether a product is from one place or multiple. This distinction matters to many specialty food buyers.

• Include "Locally Sourced" for regional products — if your store sells locally-made or locally-sourced products, tag them as "Locally Sourced" in addition to the specific location. This helps shoppers support local producers.

• Keep naming consistent — decide on a format (e.g., country names vs. region names, with or without qualifiers) and apply it uniformly. Consistency makes filtering work smoothly and prevents duplicate filter values.

• Update with seasonal variations — if you sell seasonal products from different origins at different times of year, update origin tags accordingly.

• Pair Origin with other sourcing information — if you have separate metafields for Fair Trade, Organic, or Certifications, display Origin alongside them. Together they tell a complete story about where the product comes from and how it's made.

• Display origin with visual elements — consider styling origin tags with small flags or country icons on product pages and collection cards for a more visual, worldly presentation.

• Be accurate with origin claims — only tag origins that are verified. False origin claims (e.g., claiming a product is "Single-Origin Ethiopian" when it contains beans from multiple countries) damage trust and may violate advertising regulations.

• Document sourcing relationships — maintain internal documentation of your supplier relationships and sourcing practices. Use this to confidently tag origin information.

• Consider terroir and quality implications — origin often signals quality and flavor characteristics. For specialty products like coffee, tea, chocolate, and wine, origin is a primary quality indicator shoppers use.

• Avoid the shopify namespace — it is reserved by Shopify and can cause conflicts. Use custom or a brand-specific name like food.

• Multi-language stores — ACF supports translatable metafields. Mark Origin as translatable if you serve markets where regional naming conventions differ (e.g., "Ivory Coast" vs. "Côte d'Ivoire").

---

Quick Reference

Setting	Value
Scope	Products
Section Title	Origin
Section Name	origin
Field Label	Origin
Namespace	custom
Key	origin
Full Identifier	custom.origin
Field Data Type	Multi Select
Options	Brazil, Colombia, Ethiopia, Kenya, Peru, Vietnam, Ecuador, Ghana, France, Italy, Spain, Japan, Locally Sourced, Single-Origin, Blend, and more (see Step 5)
Storefront API	Enabled (checked by default)
Liquid Reference	{{ product.metafields.custom.origin.value }}
Best Practice	Be specific with country/region names; avoid vague geographic terms
Best Practice	For blends, tag all source origins separately
Best Practice	Include "Single-Origin" or "Blend" tags to clarify sourcing type

---

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