> 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/food-and-beverage/preparation-method-metafield.md).
# Preparation Method 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 Preparation Method, 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. preparation\_method). Together they form custom.preparation\_method, which is the address used in your theme to pull the value.
Field Data Type — Controls what kind of data the field holds. For Preparation Method, a Multi-line text field is recommended. Preparation instructions are product-specific and often detailed — brewing temperature for tea, cooking time for frozen meals, mixing ratios for powders, or steeping duration for coffee. A free-text field allows your team to document complete preparation instructions for each product without being restricted to predefined options. If you want to support formatting such as numbered steps or bullet points, 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: Preparation Method — displayed in bold as a visual header when editing product values (1–50 characters, no HTML)
* Name: preparation\_method — must be unique within your Product fields (3–64 characters, letters, digits, underscores or dashes only)
* Description: Optionally add a note like Step-by-step instructions for preparing, brewing, cooking, or using this product — 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 beverages, only for frozen meals, etc.)
* Make visible to the Storefront API: Leave checked (default) — this makes the preparation instructions accessible in themes and custom storefronts
Click Next to continue.
Page 2 — Advanced Settings:
* Repeatable section: Leave unchecked — preparation method is a single set of instructions 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 step in the section header when collapsed can help your team quickly identify preparation type when scanning products.
* Show as collapsed when editing: Optionally check this — preparation instructions 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 Preparation Method section to always appear on products, even before instructions 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 Preparation Method Field Once the section is saved, click + Add field to add the actual field inside it. Fill in the details:
* Label: Preparation Method
* Namespace: accentuate (ACF's default, or use your own e.g. food)
* Key: preparation\_method
* Field Data Type: Select Multi-line text — this gives your team a spacious text area to document complete preparation instructions per product. If you want to support formatting such as numbered steps or bullet points, choose Rich Text instead.
Step 5 — Save Click Save. Your Preparation Method field will now appear inside its section on every product edit page in your Shopify admin, giving your team a dedicated space to enter preparation instructions for each product.
***
### Populating Preparation Method Values on Products
One by one: Open any product in Shopify Admin, scroll to the Preparation Method section added by ACF, type or paste the complete preparation instructions into the text area, and save. This is the most practical method since every product's preparation method is unique.
CSV import: Use the Export button to download a CSV template, fill in the preparation\_method column for each product row, then re-import via the Import button. This is useful when migrating preparation data from an existing product database or supplier information.
***
### Displaying Preparation Method 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 Preparation Method field, position it on the page (typically in a How to Use or Instructions section, or inside a collapsible accordion), and save. It will display automatically for any product with preparation instructions documented.
Liquid Code (all themes): Add this to your product template file where you want the preparation instructions to appear:
For Multi-line text:
`{% if product.metafields.custom.preparation_method %}`
``
`
Preparation Instructions:`
`
{{ product.metafields.custom.preparation_method.value }}
`
`
`
`Preparation Instructions:`
`{{ product.metafields.custom.preparation_method.value }}`
`
`
`{% endif %}`
If you used a custom namespace (e.g. food), replace custom with your namespace name.
***
### Tips & Best Practices
* Clear, step-by-step instructions are critical — customers need to understand exactly how to prepare your product. Vague or incomplete instructions lead to poor results and customer disappointment.
* Include all relevant details — depending on the product type, include:
* Water temperature and amount (for beverages)
* Cooking time and temperature (for frozen meals, baked goods)
* Steeping or brewing duration (for tea, coffee)
* Mixing ratios (for powders, concentrates)
* Equipment needed (blender, microwave, stovetop)
* Yield or servings information
* Tips for best results
* Use numbered steps for clarity — for multi-step preparation, use Rich Text with numbered steps rather than paragraph form. Numbered lists are much easier to follow: "1. Boil water to 200°F. 2. Add 1 teaspoon product. 3. Steep for 5 minutes."
* Be specific with measurements and temperatures — vague language like "add hot water" or "cook until done" is unhelpful. Be precise: "Add 8 fl oz water heated to 195-205°F", "Bake at 350°F for 18-22 minutes until golden brown".
* Include storage notes if relevant — if a prepared product should be consumed immediately or can be stored, note this: "Best enjoyed immediately. May be refrigerated for up to 24 hours."
* Use Rich Text for complex instructions — if preparation is multi-step or has multiple variants, use Rich Text with headers or bullet points. For example:
* Hot Brewing: 1. Boil water to 200°F. 2. Add 1 teaspoon...
* Cold Brew: 1. Mix 1 part concentrate...
* Iced: Brew hot, cool, add ice
* Source instructions from manufacturers — obtain preparation instructions from your supplier or product manufacturer. Never make up or guess at cooking times or temperatures.
* Include equipment suggestions — note what tools or appliances work best: "Works with any standard coffee maker, pour-over, or French press", "Microwave safe (2-3 minutes) or stovetop (5-7 minutes)".
* Add troubleshooting tips — if customers commonly make mistakes, include tips: "If too strong, use less product or shorter steeping time. If too weak, increase product amount or steeping duration."
* Include allergen warnings if relevant — if preparation creates steam, dust, or other allergen-carrying particles, include a note: "May produce airborne particles — use in well-ventilated area if you have nut allergies".
* Update when recipes or methods change — if a supplier changes formulation or recommended preparation, update instructions accordingly.
* Keep a master recipe/instruction document — maintain an internal reference document with approved preparation instructions for each product, sourced from official supplier documentation.
* Consider dietary variations — if your product can be prepared multiple ways for different diets, include variants: "For Vegan: Use plant-based milk. For Dairy-Free: Use coconut milk. For Standard: Use regular milk."
* Use "Show as collapsed when editing" — enable this on Page 2 of setup if preparation instructions are lengthy, so the product edit page stays tidy for your team.
* Pair with other product information — display Preparation Method alongside Shelf Life, Ingredients, and Dietary Tags on the product page. Together they give customers complete product understanding.
* 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 Preparation Method as translatable if you serve markets where preparation terminology or cooking appliances differ by region.
***
### Quick Reference
| Setting | Value |
| ---------------- | ---------------------------------------------------------- |
| Scope | Products |
| Section Title | Preparation Method |
| Section Name | preparation\_method |
| Field Label | Preparation Method |
| Namespace | custom |
| Key | preparation\_method |
| Full Identifier | custom.preparation\_method |
| Field Data Type | Multi-line text (or Rich Text for numbered steps) |
| Storefront API | Enabled (checked by default) |
| Liquid Reference | {{ product.metafields.custom.preparation\_method.value }} |
| Best Practice | Use numbered steps for multi-step instructions |
| Best Practice | Be specific with temperatures, times, and measurements |
| Best Practice | Include equipment suggestions and yield information |
| Best Practice | Use Rich Text with headers for variants or complex recipes |
| Critical | Always source from manufacturer; never guess cooking times |
***
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, and the optional `goal` query parameter:
```
GET https://help.accentuate.io/use-case-guides/food-and-beverage/preparation-method-metafield.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.