Cartdini – Checkout Field Editor for WooCommerce

By Plugins.shop

0+ active installationsVersion 1.8.15

Customize WooCommerce checkout fields: add gift notes, delivery instructions and billing details. Works with Classic Checkout and Checkout Blocks.

Description

Add custom WooCommerce checkout fields without code. Collect gift messages, delivery instructions and purchase references; keep customers’ answers with the order.

Nine Free field types work in Classic Checkout and Checkout Blocks. No Cartdini account, license or subscription.

Custom checkout fields included in Free

  • Nine types: text, textarea, dropdown select, checkbox, radio buttons, email, telephone, number and URL.
  • Up to 100 questions: Order information, Contact or shared billing/shipping addresses.
  • Field controls: labels, help, supported placeholders, optional/required answers and supported text/number limits.
  • Editor: reorder, duplicate, disable and structurally preview questions; save explicitly.
  • Saved answers: select display on supported admin/customer order pages and emails.
  • Storage: High-Performance Order Storage (HPOS) and legacy orders.

Practical questions for your store

  • Add a gift message textarea for the packing team.
  • Collect delivery instructions or an additional contact number alongside an address.
  • Collect a purchase order number as text; this does not create purchase orders or change payment methods.
  • Offer a dropdown or radio question for an order preference, without adding a charge.

Address questions share billing/shipping definitions. Virtual orders preserve saved shipping answers instead of replacing them with billing answers.

Manage existing checkout fields

Checkout manager controls differ by checkout:

  • Classic: supported labels, placeholders and positions; six optional-field visibility/requirement controls and individual resets.
  • Blocks: shared Company, Phone and Address line 2 visibility/requirements, supported address labels/order and default Place Order text. Shared settings can affect Classic; explicit Classic overrides win. Native settings save separately.

Essential address/email validation and country requirements stay with WooCommerce. Blocks contact email, address placeholders and sections remain native; gateways may override button text. Cartdini does not remove every required field.

For shared native address settings, Hidden on checkout hides the input. Saved address data and values submitted through WooCommerce’s API may still be stored, including on the shopper’s order and saved customer addresses. This is a visibility control, not a rule that rejects or erases native address data. Cartdini custom questions use separate controls.

Setup guides | Compatibility and limitations | Support

Optional Cartdini Pro add-on

Separate paid Cartdini Pro adds conditional fields, fixed paid extras for eligible choices, private uploads, date availability rules, time/multiple-choice inputs, repeatable groups, reusable setups and order-answer CSV tools. Uploads/groups are order-only.

Pro functionality is implemented in the separate, optional add-on, not unlocked inside Free. The active add-on requires an initial license activation for its editing/tools. Disconnecting its license leaves its saved checkout behavior running; deactivating the add-on pauses Pro-only behavior. Free retains saved Pro settings and protects their rule sources against incompatible edits to prevent data loss. Other Free fields remain editable without a license. Pro is not auto-installed. Previews never publish fields, upload files or charge shoppers.

Related WooCommerce plugins from Plugins.shop

Optional tools from our team for your WooCommerce store:

None is required or auto-installed. Check their requirements; links do not imply automatic integration or guaranteed compatibility.

Privacy and local preferences

Saved answers stay in your WordPress/WooCommerce database; unfinished Classic answers can also be held temporarily in the shopper’s browser tab. Free sends no answers or administrator preferences to Cartdini. Request necessary information only and explain purpose, recipients and retention in your privacy policy. Suggested wording: Settings > Privacy.

  • Editor browser storage: administrator drafts hold field settings, not shopper/preview answers, files or credentials. Full-screen/contextual dismissals use browser storage; WordPress navigation is visible by default.
  • Classic shopper drafts: a bounded same-tab copy holds supported unsent Cartdini answers for up to 30 minutes of inactivity, scoped to the current cart and signed-in identity. It excludes native WooCommerce fields, files, upload references and credentials. Closing the tab or clearing browser storage removes the copy. Expired or invalid copies are removed when the draft script next runs; server privacy tools cannot erase browser-held copies remotely. A random cart-generation marker is kept in the existing WooCommerce session, without storing draft answers there.
  • Pro previews: On/Off persists per administrator/store across browsers/updates. It controls optional previews/suggestions, not real Pro workflows; Explore Pro stays available. Remembered tasks require an explicit remember/pricing action, use local administrator metadata and expire after seven days.
  • Local action counts: off by default. When enabled, preview opens, pricing clicks and matching workflow saves are counted for 90 days, not purchases/conversion rates. No shopper answers/license keys; disabling clears counts. Expired tasks/counts use WordPress cron and support privacy export/erasure. Previewing is not consent to measurement.
  • Review invitation: only in Cartdini settings after 30 days and qualifying checkout use on three dates; disabled on development/local/staging sites. Eligibility stores a first-use time and at most three dates, no order IDs/customer details/answers. Local per-administrator/store review/dismissal preferences persist across updates and support export/erasure. Remind in 30 days or stop permanently; no payment verification, review-submission tracking or external analytics.

The optional More Plugins screen bundles artwork/descriptions; opening it sends no request and installs nothing. Product links open Plugins.shop. Free makes no external service requests; following documentation/support/pricing links opens that website. Pro license connections are separately disclosed and require explicit administrator action.

Source and licenses

Readable PHP/JavaScript/CSS need no build. Dependencies/translations: assets/SOURCE.md. Local fonts make no requests; SIL license: assets/fonts/OFL.txt. Plugin license: GPLv2 or later, LICENSE.txt.

Installation

Requires WordPress 6.7+, PHP 8.0+, WooCommerce 9.9+ and JavaScript for the editor.

  1. Activate WooCommerce, then install Cartdini through Plugins > Add New or upload the Free ZIP.
  2. Activate Cartdini. Ordinary single activation opens the editor; otherwise open WooCommerce > Cartdini.
  3. Add a question, review its type/location and choose Save questions & fields.
  4. Test checkout, missing/invalid answers and saved order/email answers before going live.

Fresh installs enable no sample questions. Save applies changes; reactivation resumes saved settings.

Back up; replace without uninstalling. Keep Free active and update it before Pro. The matched releases are Free 1.8.15 and Pro 1.8.15; existing compatible Pro releases remain supported (minimum Free 1.8.4). With the matched pair, authorized administrators manage the separate add-on in Cartdini > Settings > License & updates. Settings/history are retained. Update pre-1.8.0 pairs together; incompatible Pro features pause. Recovery details: administration-notes.txt.

FAQ

Can I add a gift note or delivery instructions for free?

Yes: add a textarea, label it and choose its location. Conditional display requires Pro. Gift notes are separate from WooCommerce’s native “Add a note to your order” option; label them distinctly.

Does it work with the block checkout?

Yes: all nine Free types support both. Existing-field controls differ as described above. Test your theme/gateways; not every third-party checkout builder is supported.

Why does my custom field appear after payment?

Order questions follow the Order information block in your Checkout page. Move that block before Payment in the page editor if preferred. Question-reorder arrows do not move sections. The structural preview is not your exact storefront layout.

Where are checkout answers saved?

With orders and, for supported contact/address fields, customer accounts. Order-only notes are not account-prefilled. Display settings control supported order/email output; hiding answers does not delete them. CSV export and optional Orders-list answer columns require Pro.

What if I leave before saving?

Drafts last up to 24 hours in the same browser tab for your administrator/store. Closing it or clearing storage may remove them. Recovery requires review and Save. Follow retry/reload guidance after conflicts; custom questions and native Blocks settings save separately.

Are unfinished shopper answers kept when returning from the cart?

On Classic checkout, supported Cartdini answers can be recovered in the same browser tab and current cart session, for up to 30 minutes of inactivity. This uses browser session storage, not a saved order or cross-device account draft. Successful checkout, an emptied cart, identity changes or changed field settings invalidate recovery. A failed payment attempt does not invalidate recovery by itself. Files and upload references use the separate Pro upload flow. Browser restrictions can prevent recovery; required answers and prices are still checked at checkout. This does not change WooCommerce’s own fields or add draft recovery to Checkout Blocks.

What happens if I remove a field or delete Cartdini?

Removing a field keeps historical answers. Deactivation/deletion retains settings, recovery data and saved answers. With Free and WooCommerce active, WordPress privacy tools export account/order answers; erasure removes account answers and follows WooCommerce order-retention settings. Keep compatible Pro active to erase private uploads; no license is needed for erasure. Failed/unreadable storage remains retryable, preserving order identity/answers until private-file erasure is checked safely. Removing both plugins leaves retained data outside their privacy tools.

What if I switch accounts in another checkout tab?

Checkout Blocks submissions with Cartdini questions are tied to the WordPress sign-in session that opened the checkout. After a sign-in change, reload checkout and review the current shopper’s details rather than retrying old answers. Cartdini rejects outdated submissions before checkout writes. This does not add Blocks draft recovery or independently change WooCommerce’s own address-saving behavior. Custom Store API clients must send the checkout-context header described in administration-notes.txt.

Screenshots

Changelog

1.8.15

  • Reject outdated Checkout Blocks submissions before customer or order writes after a WordPress sign-in session change, including unchanged retries with a refreshed WooCommerce nonce.
  • Bind native and custom Cartdini inputs to the initial checkout context, including batch requests, and reload idle checkout views when a changed sign-in context is detected.
  • Preserve ordinary guest checkout and account creation within an accepted request. Custom Store API integrations must supply the documented checkout-context header.

1.8.14

  • Recover supported unsent Classic checkout answers in the same browser tab and cart session, with bounded expiry and cart, identity and completed-checkout isolation.
  • Name the saved dependent questions that prevent incompatible source changes and provide a safe Review question action without removing their rules.
  • Extend new order snapshots for the optional add-on’s repeatable date presentation without changing raw values, CSV or older snapshots.

1.8.13

  • Explain how to resolve a disabled question that is still referenced by saved rules, without silently removing those rules.
  • Retain answer-type information on new order snapshots and provide a presentation-only extension point; raw saved answers and historical snapshots are preserved.
  • Keep checkout placement, native validation and concurrent-edit protection unchanged.

1.8.12

  • Support administrator-only settings panels from separately installed add-ons inside the Cartdini workspace, without adding premium functionality to Free.
  • Keep unfinished checkout edits when switching to the separate Pro license panel, and preserve existing Pro compatibility during upgrades.
  • Replace unreadable server-response errors with clear recovery guidance; failed or unconfirmed saves retain the current draft and existing revision protection.

1.8.11

  • Improve PHP formatting and developer documentation without changing checkout, storage or concurrent-edit protection.
  • Explain why saved Pro-dependent fields remain protected when the separate add-on is missing or editing is unavailable; independent Free fields remain editable.
  • Align current upgrade guidance with the separate Pro 1.8.11 release; existing Pro 1.8.7 remains compatible.

1.8.10

  • Clarify shared native address controls with “Hidden on checkout” and accessible help explaining that WooCommerce may still store saved or API-submitted address values.
  • Preserve checkout validation, address-saving behavior, customer profiles and order history; no new storage restriction is introduced.

1.8.9

  • Preserve editor save bodies in browser-based WordPress Playground using WordPress REST method override. Keep both revision checks and the save lock.
  • Report missing or invalid save requests separately from genuine concurrent-edit conflicts.

1.8.8

  • Preserve saved shipping answers on virtual Checkout Blocks orders; retain normal physical-order copying.
  • Exclude nonapplicable shipping answers from order details and emails.
  • Harden customer identity checks and remove obsolete answers from reused checkout drafts, preserving history.
  • Make busy or failed preference erasure retryable.
  • Remain compatible with Pro 1.8.7; no Pro update required.

Full release notes and earlier versions: changelog.txt.