What are you trying to change?
Add a new checkout question
Start with a text field, dropdown or checkbox in Free. These work in Classic and Checkout Blocks. Add one optional field first, save it, and place a test order.
Follow the first-field guide ↗Rename or hide an existing checkout field
Cartdini’s Classic controls cover company, phone, address line 2 and order notes. Existing Blocks fields use WooCommerce’s available block settings. Essential address and payment fields are not controlled by Cartdini.
See the supported controls ↗A field or follow-up isn’t appearing
Check that the field is enabled and its location is correct. Blocks supports text, select and checkbox inputs; other types are Classic-only. Pro follow-ups must meet their saved conditions.
Check Blocks field support ↗Check a conditional rule ↗Undo changes or deactivate Cartdini
To stop all Cartdini checkout changes, deactivate Pro if installed, then Free. Configuration and historical answers remain stored. Reactivating an existing installation resumes its saved configuration; Cartdini’s display hooks stop while Free is inactive.
Read the data and deactivation details ↗Contact & product support
Maintained by A.M.E.X. Internet Marketing ltd.
support@cartdini.comEmail us for setup, billing or privacy questions.
Include your WordPress, WooCommerce, PHP and Cartdini versions; Classic or Blocks checkout; the field settings; and the steps that trigger the issue. Redact customer data and credentials.
Read the field guide ↗Billing & lost keys
Pro subscriptions are not open yet. When billing is available, use Stripe to see invoices, change your payment method or cancel renewal. For a lost download key or refund request, contact support from your purchasing email with the Stripe receipt or invoice number.
Support must verify purchase ownership before reissuing access. A receipt number alone is not proof of ownership.
Downloads & billing ↗Found a security issue?
Contact the support address privately with the affected version and steps to reproduce it. Avoid including live customer data, passwords or payment information. Please do not publish an exploit before we can investigate.
Every report needs investigation. Security updates, backups and testing remain part of running a store; no plugin can promise permanent freedom from defects.
Before you send a ticket
- Use a staging copy and back up your configuration and database.
- Check the Classic/Blocks compatibility table. Extra Pro input types are Classic-only.
- Try the smallest configuration that reproduces the problem.
- Record the error and versions; remove personal data from any screenshot or log.