Field Forge integrates with WooCommerce to let you add custom fields to products, variations, orders, and customers. Every WooCommerce content type is supported via location rules, and custom fields appear natively in the product editor alongside WooCommerce’s built-in fields. Perfect for custom product metadata (specifications, warranty info, custom attributes, internal SKUs, supplier data, etc.).
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.
Field Forge adds:
Post type is equal to "product"Applies to every WooCommerce product.
Post type is equal to "product"
AND
Post taxonomy is equal to "product_cat:electronics"Only products in the Electronics category get this field group.
Post type is equal to "product"
AND
Post format is equal to "simple"Post type is equal to "product_variation"Adds fields to individual variation edit screens.
Post type is equal to "shop_order"Adds custom fields to order edit screens (for internal notes, fulfillment status, etc.).
Current user role is equal to "customer"Adds custom fields to customer user profiles.
A repeater field for structured specifications:
Field Group: Product Specifications
Location: Post type is equal to "product"
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>Fields:
- Documentation (File, multiple)
- Installation Video (oEmbed)
- Warranty PDF (File)
- Product Manual (File)Useful for tech products or anything with extensive documentation.
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)Fields:
- Related Products (Relationship, filtered to product post type)
- Upsell Reason (Textarea — why this pairing works)WooCommerce variations can have custom fields too. Create a field group with location:
Post type is equal to "product_variation"And add fields that differ between variations (e.g., “Variation-specific weight,” “Bulk price break,” “Minimum order quantity for this variation”).
Access in templates via get_field('field_name', $variation_id).
For fulfillment workflows, custom order fields are useful:
Field Group: Order Fulfillment
Location: Post type is equal to "shop_order"
Fields:
- Fulfillment Status (Select: Pending, Processing, Shipped, Delivered)
- Tracking Number (Text)
- Estimated Delivery Date (Date Picker)
- Internal Notes (Textarea — visible only to admins)
- Courier (Select: UPS, FedEx, DHL, Local Courier)These appear on the order edit screen in WooCommerce admin. Useful for teams managing fulfillment manually or integrating with shipping services.
Add fields to customer user profiles:
Field Group: Customer Profile Extended
Location: Current user role is equal to "customer"
Fields:
- Preferred Contact Method (Radio: Email, Phone, SMS)
- Delivery Preferences (Checkbox: Leave at door, Signature required, Call before delivery)
- Customer Notes (Textarea — internal)
- VIP Customer (True/False)
- Birthday (Date Picker — for birthday promotions)Access via get_field('field_name', 'user_' . $user_id).
For stores with 1,000+ products, the N+1 query problem hits hard. Every product page that displays custom fields fires individual meta queries. A WooCommerce shop page listing 30 products with 10 custom fields each = 300+ meta queries per pageview.
Field Forge’s custom table storage eliminates this. Product custom field queries are batched into single SQL queries. Shop pages load 3–10x faster on large catalogs.
This matters especially for:
For headless WooCommerce setups (using Next.js, Astro, etc. for the storefront), Field Forge provides:
This means your headless frontend gets typed product data including custom fields without hand-writing type definitions.
TypeScript generation → · GraphQL generation →
If you’re currently using ACF for WooCommerce custom fields, migration is straightforward:
Your custom get_field('spec_name', $product_id) calls continue to work. Your have_rows('specifications') loops continue to work. No theme rewrites needed.
Get Field Forge — from $35/year →
WooCommerce integration is included in every plan — free and paid. (Repeaters, flexible content, and the TypeScript/GraphQL tooling shown above are part of the paid plans.)