iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Use Advanced Custom Fields (ACF) to add structured, product-specific information to WooCommerce’s product editor—then deliberately add that information to the product-page template if shoppers should see it. First choose the right kind of data: use WooCommerce attributes for shared characteristics customers may filter, ACF or native product metadata for descriptive facts about an individual product, and a product add-on extension for choices or paid options customers enter while ordering.
Choose the right place for product data
Decide what the information is for before building a field. WooCommerce attributes and custom fields solve different problems; neither an ACF field nor a native custom field automatically becomes a visible product-page element.
| What the data needs to do | Best fit | Why |
|---|---|---|
| Describe characteristics shared across products, such as color, size, or material, and support grouping or customer filtering | WooCommerce attributes | Attributes are product characteristics that can help customers navigate and filter products. See WooCommerce’s custom-fields documentation for the distinction. |
| Store descriptive information specific to a product, such as a care note or technical detail | An ACF field or native product custom field | Both can store product metadata. ACF provides a configurable field-building and editing interface; rendering the value on the storefront is a separate implementation step. |
| Let a shopper supply text, choose an option, or pay for a customization during purchase | A product add-on or custom-fields extension | This is order-time input rather than descriptive data maintained by the store. WooCommerce’s Product Add-Ons documentation describes field types, product or category targeting, conditions, and optional pricing. |
For example, if every mug has a material that shoppers should filter by, an attribute is the natural fit. If one mug has a product-specific care instruction, an ACF field can store it. If a shopper must enter a name to be printed on the mug, use an order-time add-on rather than treating that input as a product description.
Free tools Windows power users keep installed
One-click scans. No signup required.
Create an ACF field group for products
ACF adds extra content fields to WordPress editing screens. A field group collects related fields and controls where they appear; its location rules determine which editing screen receives the group. Follow the current ACF interface and documentation, since screen labels can change between plugin versions.
#1 Best Overall
- In WordPress, open the ACF field-group editor and create a field group for the product information you want editors to maintain.
- Add each field with an editor-friendly label, a stable field name for template references, and a field type suited to its value. For example, use a text field for a short specification or a longer text field for an instruction.
- Set the field group’s location rule to the WooCommerce product post type so it appears when editing products. ACF’s WooCommerce custom-fields guide discusses adding fields to products.
- Save the group, then open a product in the WordPress product editor and confirm the fields appear in the intended editing screen.
Use instructions to tell editors what belongs in a field, and mark a field required only when the store genuinely needs a value for every applicable product. Conditional logic can keep fields relevant when different products need different details. ACF’s getting-started guide covers field labels, names, types, instructions, required validation, conditional logic, location rules, and field values.
Enter and maintain values on each product
Edit the relevant WooCommerce product, fill in the assigned ACF fields, and update the product. Check more than one product if the group applies broadly: confirm that required information is complete and that fields intended for only certain products are shown appropriately. This is store-editor data stored with the product, not a customer’s purchase-time choice.
Display ACF values on the product page
Creating an admin field does not place its value on the storefront. WooCommerce’s custom-field documentation says displaying product metadata requires theme or site edits. ACF documents output in themes and notes integration with page builders, but the method depends on the active theme, builder, and product template.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Use a page builder or theme template
If the store’s builder or theme offers dynamic ACF field output in its product template, add a dynamic field element in the desired location and select the relevant ACF field. Preview a product with a value and one without a value to verify placement and empty-field behavior. The exact controls are builder-specific, so consult the documentation for the installed builder and theme rather than assuming a universal WordPress button.
Use a custom theme implementation
For a custom or child-theme product template, retrieve the field by its stable ACF field name and render it in the intended product-page location. Escape output for the context in which it is displayed, and decide how to handle empty values so the page does not show an empty label or unwanted blank space. ACF’s guide explains theme output; the appropriate template file and implementation depend on the store’s theme.
Keep the field’s purpose and output separate: ACF defines and stores the editor-facing value; the builder or theme decides where and how customers see it. If a site already has a customized product template, check its structure before changing theme files so updates do not overwrite the implementation.
Rank #4
When the ACF datastore matters
The ACF datastore is an opt-in feature that integrates ACF fields with Gutenberg’s native wp.data store; it is not a prerequisite for ordinary ACF fields on WooCommerce products. ACF’s datastore documentation, last updated May 14, 2026, lists ACF PRO 6.8.1 or later and WordPress 6.7 or later for that feature and includes a product post-type example. See Using the ACF Datastore if your implementation specifically depends on it.
Recommended Free Tools
Quick Recap
Check the result before publishing
- Verify the field group appears on product editing screens, not on unrelated post types.
- Enter representative values and confirm they save and remain associated with the correct product.
- Preview the product page to check that the value appears in the intended location and that an empty value does not leave a stray label.
- Test on the storefront layout customers use, including mobile if the theme or builder changes field placement across screen sizes.
- If the data should be filterable, confirm you chose an attribute rather than assuming a custom ACF field becomes a WooCommerce filter automatically.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
