The third support ticket that week was the breaking point. A customer ordering catering for 50 people had left the gate code blank, again, because the checkout form didn't even ask for it. Meanwhile, another buyer complained about the 'Delivery Notes' field appearing when they'd only purchased a digital gift card. WooCommerce's one-size-fits-all checkout was costing us orders, and I knew there had to be a better way than hacking together custom ACF fields or writing brittle conditional logic for every edge case.
That's when I found the NEXU Advanced Checkout Field Editor for WooCommerce. Unlike most checkout plugins that just let you add more global fields, this one finally solved the core issue: per-product fields with cart-aware logic. No more forcing customers to wade through irrelevant questions, and no more chasing missing details after checkout.
The Problem with WooCommerce's Default Checkout
WooCommerce's native checkout assumes every order is the same: a billing address, a shipping address (if physical), and payment. But real stores don't work like that. A restaurant's takeout order needs a time slot and gate code, while a digital menu PDF shouldn't even show shipping fields. My first attempt was using Advanced Custom Fields (ACF) to inject fields conditionally, but it required custom JavaScript to hide/show them based on cart contents, and broke every time WooCommerce updated.
The real issue wasn't just missing fields; it was context. A 'Delivery Instructions' textarea is useless if it appears for every order, but critical if it only shows when a customer adds a catering platter to their cart. I needed a way to tie fields to specific products and dynamically adjust based on what was in the cart.
How Per-Product Fields Actually Work
The NEXU plugin adds a 'Checkout Fields' tab directly to the WooCommerce product editor. For a pizza delivery item, I added:
- A time slot dropdown (with 15-minute increments)
- A gate code text field (required only for apartment deliveries)
- A textarea for drop-off notes (e.g., 'Leave at front desk')
Fields only appear when that product is in the cart. Even better, the plugin's cart-based conditional logic lets you show/hide fields based on categories or attributes. For example:
- Show a 'Dietary Restrictions' field if any item in the cart is tagged 'gluten-free'.
- Require an 'ID Upload' for alcohol orders, but hide it for everything else.
Why This Beats Custom Code
Before this, I'd tried:
-
Hooking into
woocommerce_checkout_fields: Worked for global fields, but couldn't handle per-product logic without a mess ofifstatements. - ACF + JavaScript: Fragile, slow, and broke with cached checkouts.
- Separate checkout pages: A maintenance nightmare for stores with dozens of products.
The NEXU plugin handles all this visually, no code, no conflicts with WooCommerce Blocks, and full compatibility with WPML for multilingual stores. Field data even flows into order emails and the admin panel, so the kitchen staff sees the gate code and the customer gets a confirmation with their delivery notes.
The Result: Fewer Abandoned Carts, No More Support Tickets
Since implementing per-product fields:
- Abandonment rates dropped because customers only see relevant questions.
- Fulfillment errors vanished, no more last-minute calls for missing gate codes.
- Checkouts feel intentional, not like a generic form dumped on every order.
The plugin's drag-and-drop builder also let me clean up the global fields (e.g., renaming 'Address Line 2' to 'Apartment/Suite'), which further reduced confusion. For developers, the ability to export/import field configurations as JSON is a lifesaver for staging-to-production syncs or replicating setups across client sites.
If you're tired of WooCommerce's checkout treating a $200 catering order the same as a $5 gift card, try the NEXU Advanced Checkout Field Editor. It's the only solution I've found that respects the complexity of real-world orders, without requiring you to build it from scratch.
Top comments (0)