> 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/power-requirements.md). # Power Requirements ### 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 Power Requirements, 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. power\_requirements). Together they form custom.power\_requirements, which is the address used in your theme to pull the value. Field Data Type — Controls what kind of data the field holds. For Power Requirements, a Multi-line text field is recommended. Power specifications vary widely depending on product type — a smartphone's battery capacity and charging spec differ completely from a laptop's power adapter requirements, which differ from a desktop monitor's power consumption. A free-text field allows your team to document all relevant power information for each product without being restricted to predefined options. If you want to support formatting such as headers 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: Power Requirements — displayed in bold as a visual header when editing product values (1–50 characters, no HTML) * Name: power\_requirements — must be unique within your Product fields (3–64 characters, letters, digits, underscores or dashes only) * Description: Optionally add a note like Battery capacity, charging specifications, and power consumption details 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 batteries, only for laptops, etc.) * Make visible to the Storefront API: Leave checked (default) — this makes the power requirement values accessible in themes and custom storefronts Click Next to continue. Page 2 — Advanced Settings: * Repeatable section: Leave unchecked — power requirements 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 battery capacity or wattage in the section header when collapsed can help your team quickly identify power specs when scanning products. * Show as collapsed when editing: Optionally check this — power specifications can be detailed, 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 Power Requirements 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 Power Requirements Field Once the section is saved, click + Add field to add the actual field inside it. Fill in the details: * Label: Power Requirements * Namespace: accentuate (ACF's default, or use your own e.g. tech) * Key: power\_requirements * Field Data Type: Select Multi-line text — this gives your team a spacious text area to document all relevant power information per product. If you want to format power specs with headers or bullet points, choose Rich Text instead. Step 5 — Save Click Save. Your Power Requirements field will now appear inside its section on every product edit page in your Shopify admin, giving your team a dedicated space to enter power specifications for each product. *** ### Populating Power Requirements Values on Products One by one: Open any product in Shopify Admin, scroll to the Power Requirements section added by ACF, type or paste the power and battery specifications into the text area, and save. This is the most practical method since every product's power requirements are unique. Bulk edit: Back on the Product Custom Fields screen, click Edit Values to open the table/bulk edit view. The Power Requirements column will be visible for each product. This is useful for reviewing power specs across multiple products or making small corrections. CSV import: Use the Export button to download a CSV template, fill in the power\_requirements column for each product row, then re-import via the Import button. This is useful when migrating power data from an existing product database or manufacturer datasheets. *** ### Displaying Power Requirements 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 Power Requirements field, position it on the page (typically in a Specifications or Technical Details section), and save. It will display automatically for any product with power requirements added. Liquid Code (all themes): Add this to your product template file where you want the power requirements to appear: For Multi-line text: ``` {% if product.metafields.custom.power_requirements %}
Power Requirements:

{{ product.metafields.custom.power_requirements.value }}

{% endif %} ``` For Rich Text: ``` {% if product.metafields.custom.power_requirements %}
Power Requirements: {{ product.metafields.custom.power_requirements.value }}
{% 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 power requirements directly from the manufacturer's official datasheet or product manual. Never estimate power specifications. * Include all relevant power information — depending on the product type, include: * For batteries: capacity (mAh, Wh), voltage, chemistry type (Li-Ion, LiPo, etc.) * For rechargeable devices: charging speed (fast charge specifications, wattage), charging standards (USB-C Power Delivery, proprietary), battery life (hours of use) * For AC-powered devices: input voltage, power consumption (watts), power adapter output (voltage and amperage) * For wireless devices: any special power requirements (e.g. minimum USB power for operation) * Be specific with charging standards — note the exact charging specifications: "USB-C Power Delivery 65W", "Fast Charge 30W", "Qi Wireless Charging", etc. This helps shoppers know if their existing chargers will work. * Include battery life information — for portable devices, include estimated battery life under typical use conditions. For example: "Up to 15 hours typical use, 25 hours standby mode" or "7-hour continuous playback time". * Be consistent with units — decide on standard units (watts, volts, amps, mAh, Wh) and apply them uniformly across your entire product range. Always include the unit symbol (W, V, A, mAh, Wh) to avoid confusion. * Use Rich Text for better readability — if you're listing multiple power specifications (battery capacity, charging speed, adapter wattage, power consumption, standby time, etc.), use Rich Text with headers or bullet points. For example: * Battery Capacity: 5000 mAh (18.5 Wh) * Charging: USB-C Power Delivery 65W Fast Charge * Battery Life: Up to 12 hours typical use * Power Consumption: 15W typical operation * Include power delivery information for chargers — if you're selling power adapters or chargers, note the output power clearly and which devices it's designed to charge at optimal speed. * Note energy efficiency ratings — if the product has energy efficiency certifications (ENERGY STAR, EnerGuide, etc.), include that information. * Keep a master spec document — maintain an internal reference document with approved power requirements 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 refreshed — monitor for product refreshes or redesigns from manufacturers. Battery capacity and charging speeds sometimes change between generations, and outdated specs damage customer trust. * Don't duplicate Specs field — if you have a separate Specs metafield, avoid repeating power requirements in both fields. Keep Specs focused on general technical performance, and keep Power Requirements focused specifically on power and battery 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 Power Requirements as translatable if you serve markets that use different power standards or terminologies. *** ### Quick Reference | Setting | Value | | ---------------- | ----------------------------------------------------------------------------------- | | Scope | Products | | Section Title | Power Requirements | | Section Name | power\_requirements | | Field Label | Power Requirements | | Namespace | custom | | Key | power\_requirements | | Full Identifier | custom.power\_requirements | | Field Data Type | Multi-line text (or Rich Text for formatted specs) | | Storefront API | Enabled (checked by default) | | Liquid Reference | {{ product.metafields.custom.power\_requirements.value }} | | Best Practice | Include battery capacity, charging standards, and battery life for portable devices | | Best Practice | Include input voltage and power consumption for AC-powered devices | | Best Practice | Always include measurement units (W, V, mAh, Wh, etc.) | | Best Practice | Be specific with charging standards (e.g., USB-C PD 65W, Qi Wireless) | *** 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/power-requirements.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.