WooCommerce custom product data splits into two distinct systems that are commonly confused: backend fields (specs, certifications, metadata managed by staff) and customer-facing add-ons (inputs that affect pricing and flow through cart/checkout). ACF is purpose-built for the backend path — attaching structured field groups to products via location rules, with manual output via hooks or template overrides. It cannot natively handle pricing logic, cart item data, or order line item meta. For customer-facing inputs that modify price and persist through orders, dedicated plugins like Product Add-Ons for WooCommerce handle the full transactional pipeline automatically. The guide also covers variation-specific data, HPOS compatibility, performance pitfalls (avoid heavy ACF fields in shop loops), and best practices like using CRUD APIs and storing customizations in version-controlled plugins.
Table of contents
Three types of custom product data in WooCommerceTwo WooCommerce product data pathsPath A method: Adding and displaying backend product dataPath B method: Where product add-ons make the most senseVariation-specific data and advanced scenariosKeeping custom product data maintainable and future-proofChoosing the right path and stabilizing your data flowSort: