Support Log in
Field Forge Integrations

Field Forge + WooCommerce — Product Custom Fields

Field Forge has no WooCommerce-specific code. A product is an ordinary post type, so field groups work on it as on any other post type. The values are stored in Field Forge’s own table, not in wp_postmeta, so WooCommerce’s wc/v3 API, the product CSV export and product filters do not see them. Variations, orders and customers are not covered. A location rule on the product post type puts a field group in a metabox on the product edit screen, and templates read the values with get_field(). Good for custom product metadata (specifications, warranty info, custom attributes, internal SKUs, supplier data and similar).


What Field Forge adds to WooCommerce

WooCommerce has its own product custom fields (product attributes, custom meta), but they’re limited to simple key-value pairs. For anything more complex — structured specifications, multi-image galleries, repeating feature lists, product-specific custom content blocks — you need a custom fields plugin.

With Field Forge you can add:

  • Field groups on the product post type, chosen by a location rule
  • Nested fields via Repeater and Flexible Content fields (PRO), for example a “Product Specifications” repeater with sub-fields
  • Image and file fields for extra product media
  • Relational fields for linking products to other content
  • Rich text (WYSIWYG) for custom product sections

Location rules for WooCommerce

All products

Post Type is equal to Products

Applies to every WooCommerce product. The Post Type list shows the WooCommerce product post type under the name Products.

Products in specific category

Use a Post Taxonomy rule. Pick Post Taxonomy in the first list, then pick the product category in the value list, where the terms are grouped by taxonomy and the product categories are under Product categories. With Post Taxonomy is equal to a product category, the field group is shown on the products that have that category. A new product has no category yet, so such a group appears once the product is saved with that category.

Variations, orders and customers

These are not covered. Field Forge draws a field group as a metabox on the post edit screen, and the location rule offers the public post types. A product variation has no edit screen of its own, orders are not offered by the location rule (and with WooCommerce’s order storage tables the order screen is not a post edit screen), and Field Forge has no user profile screen, so field groups do not appear there.


Example field groups for WooCommerce

Product Specifications

A repeater field for structured specifications:

Field Group: Product Specifications
Location: Post Type is equal to Products

Fields:
  - Specifications (Repeater)
      - Spec Name (Text, required)
      - Spec Value (Text, required)
      - Unit (Text, optional — e.g., "kg", "GB", "MHz")

Render on the frontend:

<dl class="product-specs">
    <?php if (have_rows('specifications')) : ?>
        <?php while (have_rows('specifications')) : the_row(); ?>
            <dt><?php the_sub_field('spec_name'); ?></dt>
            <dd>
                <?php the_sub_field('spec_value'); ?>
                <?php if ($unit = get_sub_field('unit')) : ?>
                    <span><?php echo esc_html($unit); ?></span>
                <?php endif; ?>
            </dd>
        <?php endwhile; ?>
    <?php endif; ?>
</dl>

Product Downloads and Resources

Fields:
  - Documentation (File, multiple)
  - Installation Video (oEmbed)
  - Warranty PDF (File)
  - Product Manual (File)

Useful for tech products or anything with extensive documentation.

Custom Product Attributes (beyond WooCommerce’s built-in)

Fields:
  - Warranty Period (Select: 1 year, 2 years, 5 years, Lifetime)
  - Shipping Class Override (Select from custom options)
  - Supplier Code (Text — internal use only)
  - Discontinuation Date (Date Picker)

Related Products (with more detail than WooCommerce defaults)

Fields:
  - Related Products (Relationship, filtered to product post type)
  - Upsell Reason (Textarea — why this pairing works)

Where the values are stored

Field Forge keeps field values in its own table, wp_fieldforge_values, not in wp_postmeta. Read them in templates with get_field('field_name'). WooCommerce’s own tools that read post meta, its wc/v3 REST API, the product CSV export and product filters do not see them. If something else must read a value from wp_postmeta, such as a price that WooCommerce sorts by, copy it there yourself from the fieldforge/value_updated action, or turn on Sync to PostMeta in Field Forge > Settings, which writes the value under the field name (not under WooCommerce’s own keys such as _price).

REST API

For post types with show_in_rest, such as products, a field marked show_in_rest appears in the fieldforge property of the standard WordPress endpoint (for products /wp/v2/product), and /wp-json/fieldforge/v1/fields/{id} returns the values of a post to users who may read it. Both are in the free plugin. WooCommerce’s wc/v3 API does not include them.

Headless storefronts

Field Forge PRO generates TypeScript types and, with WPGraphQL, GraphQL types for field groups: TypeScript generation, GraphQL generation.


Migrating from ACF + WooCommerce

If you’re currently using ACF for WooCommerce custom fields, migration is straightforward:

  1. Install Field Forge alongside ACF
  2. Run the ACF importer (Field Forge > Tools): it brings the field groups and their values across; Repeater, Group, Flexible Content and Clone fields need PRO
  3. ACF code in your theme keeps working via the compat layer
  4. Deactivate ACF
  5. Product templates that call only the template functions Field Forge defines keep working

Your custom get_field('spec_name', $product_id) calls continue to work. Your have_rows('specifications') loops continue to work. No theme rewrites needed.


Ready to add custom fields to WooCommerce?

See pricing →

Field groups on products work in every plan, free and paid. Repeater and Flexible Content fields and the TypeScript and GraphQL tooling are PRO.

Forge AI Assistant Online

Hi! I'm the Field Forge AI assistant. Ask me anything about the plugin — setup, features, troubleshooting, or development.

Just now
Powered by Forge AI · Browse docs