Written answers
Text, textarea, email, telephone and URL.
CHOOSE THE RIGHT CONTROLS
Edit Classic & Checkout Blocks fields
All nine Free custom field types work in Classic and Checkout Blocks. Editing an existing WooCommerce address field is a different task. Here is where to start.
Add a custom question View full compatibilityCartdini documentation · Content reviewed for Free 1.8.11 and Pro 1.8.11. Recorded examples identify their tested setup.
In this guide
WooCommerce 11.2.1: a delayed cart response can replace newer customer email or address details. Since Pro 1.8.2, Cartdini protects newer customer details from its own successful paid-choice responses and refreshes address-dependent totals before ordering. This is a scoped fix: unrelated WooCommerce or extension cart responses can still replace newer details. Read the known Blocks issue and staging checks before using this setup with shoppers.
01 · IDENTIFY
Check what your store uses.
Open WooCommerce → Cartdini to see the detected checkout implementation. Test the actual checkout page; a structural editor preview is not a test of the Checkout block.
Cartdini requires WordPress 6.7+, WooCommerce 9.9+ and PHP 8.0+. Your WooCommerce version may require newer WordPress or PHP versions. Check the requirements.
02 · ADD A QUESTION
Use Extra questions for new information.
Choices
Select, checkbox and radio.
Numbers
Number fields with configurable limits and steps.
These nine types work in both Classic and Blocks. Choose Order information, Contact information or Billing + shipping as appropriate. Contact/address answers may also be stored on customer profiles by WooCommerce.
Checkout Blocks placement: order questions follow WooCommerce’s Order information block. To show them before Payment, edit the assigned checkout page and move that block before Payment in List View, then save the page and test checkout. Cartdini’s question arrows reorder questions, not checkout sections. The structural preview is not the exact storefront layout.
If the native Order information block is unavailable, Cartdini’s custom-input fallback appears before payment or submission. An existing block keeps its chosen position; WooCommerce may restore a missing block. Check the actual checkout rather than relying on the editor preview.
Configure required answers, validation and display destinations, then save the custom-field configuration. Follow the delivery-instructions example.
03 · EDIT AN EXISTING FIELD
Use the native settings separately.
See the shared settings screen
Genuine Cartdini Free 1.8.11 administration screen from a fictional store, captured 8 November 2026.
Shared address controls
In Existing fields, shared Company, Phone and Address line 2 settings control visibility and requirements. Ten shared address fields allow label/order changes.
Hidden on checkout hides a shared native address input. WooCommerce can still store existing address data or values submitted through its API, including on the order and saved customer address. This setting does not reject or erase that data; Cartdini custom questions have separate controls.
These settings can also affect Classic checkout. An explicit Classic override takes precedence.
Checkout button text
Free can customize the default Blocks Place Order text. A payment method or another extension may supply its own button text.
Native address/button settings have a separate save action from Extra questions. They are not included in custom-field templates, transfers or restore history.
What stays controlled by WooCommerce?
Country-specific validation, hidden fields and supported native inputs stay in place. Blocks contact email, address placeholders and section content remain under WooCommerce and the native checkout editor. Classic has additional supported text overrides. Compare the exact controls.
WHEN YOU USE PRO
More inputs, with clear boundaries.
Date, time, multiselect, checkbox groups, conditional questions and requirements work in both checkouts. Private uploads, repeatable groups and fixed priced choices also work in both, at the order location only.
Standalone Pro Date questions also support lead days, available weekdays and excluded dates, checked on the server. Configure date availability; these rules do not reserve delivery capacity or appointment slots.
Check the limits for files, groups and fees before setting them up.
Older saved rules in Checkout Blocks
Expanded grouped conditions, conditional requirements and advanced inputs use Cartdini’s registered Blocks integration with server validation on WooCommerce 9.9+.
Older workflows on WooCommerce’s native additional-fields path keep their earlier limits: field rules use select/checkbox sources, while cart, product, category, role, shipping/payment and conditional contact rules require WooCommerce 10.1+. Review a legacy native text-source rule into the expanded group format before using it in Blocks. The editor identifies unavailable workflows.
04 · VERIFY THE RESULT
Change the answer. Finish the order.
- Test guests and signed-in shoppers, including separate addresses where supported.
- Check required-answer errors and retry after an incomplete submission. Oversized answers are rejected before payment; shorten the retained input and retry.
- For Pro, change condition sources and inspect hidden answers, date rules, files or fees as applicable. Check customer details and tax after overlapping address and paid-choice updates. A failed paid-choice request displays a WooCommerce notice; follow it and retry before ordering.
- Complete a test order and confirm saved answers and the order/email destinations you enabled.
Your theme, gateway and other extensions remain part of this check. Use the full staging checklist.
Next: a conditional question