Mr. J

ajay2188

Mr. J Dev Dynamic Checkout Fields lets store owners add fully configurable custom fields to the WooCommerce checkout page. Fields can be shown conditionally based on cart total, shipping country, or product presence — all managed via a clean split-panel admin UI without writing any code.
Field Types:
<ul>
<li>Text — single-line text input</li>
<li>Textarea — multi-line text area (4 rows, resizable)</li>
<li>Dropdown — select from a list of predefined options (you define one option per line)</li>
<li>Checkbox — a simple yes/no toggle</li>
</ul>
Conditional Display (show field only when):
<ul>
<li>Always — field is always visible at checkout</li>
<li>Cart total is greater than ₹X — e.g. show a “Gift wrapping note” field only for orders above ₹500</li>
<li>Shipping country equals — show field only for specific countries (2-letter ISO code, e.g. IN, US, GB)</li>
<li>Product ID is in cart — show a field only when a specific product is being purchased</li>
</ul>
Note: Conditions apply to the classic shortcode checkout only. In the block checkout, all registered fields are always shown.
Validation:
<ul>
<li>Mark any field as required — WooCommerce will block checkout if left empty</li>
<li>Optional regex pattern — e.g. <code>^[0-9]{10}$</code> to enforce a 10-digit phone format</li>
<li>Regex is applied to Text fields only; Checkbox and Dropdown use WooCommerce’s built-in validation</li>
</ul>
Checkout Compatibility:
<ul>
<li>Classic Checkout (shortcode <code>[woocommerce_checkout]</code>) — full support including conditions</li>
<li>Block Checkout (WooCommerce 8.9+) — fields registered via the Additional Checkout Fields API and appear in the “Order” section of the block checkout automatically. Textarea type falls back to a single-line text field in block mode (the Block API has no native textarea type)</li>
</ul>
Data Handling:
<ul>
<li>Field values are saved as order meta on checkout submit</li>
<li>Displayed in the admin order detail page (below billing address)</li>
<li>Included in WooCommerce order emails — both HTML and plain-text formats</li>
</ul>
Admin UI (split-panel layout):
<ul>
<li>Left panel — lists all saved fields as cards with type badge, condition summary, and required indicator</li>
<li>Right panel — inline create / edit form; clicking a card loads it for editing</li>
<li>Fields are created, updated, and deleted without leaving the page</li>
<li>The form auto-shows/hides the Dropdown Options textarea and Condition Value input based on your selections</li>
</ul>
<h3>Usage</h3>
<ol>
<li>Go to WooCommerce → Checkout Fields.</li>
<li>Click Add New Field.</li>
<li>Fill in:
<ul>
<li>Field ID — a unique slug (lowercase, underscores only), e.g. <code>pan_number</code></li>
<li>Label — what customers see at checkout, e.g. “PAN Number”</li>
<li>Field Type — Text, Textarea, Dropdown, or Checkbox</li>
<li>Dropdown Options — one option per line (only shown when type is Dropdown)</li>
<li>Required — tick to block checkout if the field is left empty</li>
<li>Show When — the condition that must be true for the field to appear</li>
<li>Condition Value — the value for your condition (amount / country code / product ID)</li>
<li>Validation Regex — optional regex for Text and Textarea fields</li>
</ul>
</li>
<li>Click Save Field.</li>
</ol>
The field will appear on the checkout page whenever its condition is met. Submitted values are stored with the order and visible in the admin order screen and in all WooCommerce order emails.
<h3>Condition Examples</h3>
Gift message field for large orders: 
* Type: Text | Show When: Cart total > | Value: 1000
PAN card field for Indian customers only: 
* Type: Text | Show When: Shipping country = | Value: IN 
* Validation Regex: <code>^[A-Z]{5}[0-9]{4}[A-Z]{1}$</code>
Delivery preference for a specific product: 
* Type: Dropdown | Show When: Product ID in cart | Value: 42 
* Options: Morning
Afternoon
Evening
Simple gift wrap option: 
* Type: Checkbox | Show When: Always | Required: No
<h3>Block Checkout Notes</h3>
To use with the WooCommerce Block Checkout:
<ul>
<li>WooCommerce 8.9 or newer is required</li>
<li>Fields are registered in the “Order” section of the block checkout</li>
<li>Conditional display is not supported in block mode — all your fields will always show</li>
<li>Field values are saved and displayed in orders automatically by WooCommerce</li>
</ul>

Mr. J Dev Dynamic Checkout Fields

Add custom fields to the WooCommerce checkout based on cart contents, value, or country. Saves data to order meta and displays it in the admin.

Dennis Buchwald

Flinkform is a form builder that lives entirely inside the WordPress Block Editor. Forms are composed from native blocks (<code>block.json</code> v3), styled through <code>theme.json</code> design tokens, and powered by the Interactivity API — no separate admin UI, no shortcodes, no jQuery.
<h4>How it works</h4>
<ul>
<li>Block Editor native — forms are built with <code>block.json</code> and the Interactivity API, directly inside the editor</li>
<li>theme.json styling — forms inherit your theme’s typography, colours and spacing automatically</li>
<li>Modern stack — WordPress 6.5+, PHP 8.1+, no jQuery, frontend JS under 15 KB gzipped</li>
<li>Multi-step forms — split long forms into steps with a Page Break block, included in the free core</li>
<li>Conditional logic — show/hide fields based on user input, included in the free core</li>
<li>WCAG 2.1 AA — full keyboard navigation, screen-reader compatible, aria-live announcements</li>
<li>Privacy by design — no external services, no tracking cookies, no IP tracking — everything stays on your server</li>
</ul>
<h4>Features (free core)</h4>
Form building 
* 13 field types: Text, Email, Textarea, Number, Date, URL, Phone, Select, Radio, Checkbox, Toggle, Hidden, Section Heading 
* Dedicated Consent field for privacy-policy agreement 
* Multi-step forms with Page Break block, per-step validation and progress indicator (bar, dots or numbers) 
* Conditional logic — show/hide fields, skip steps, gate the submit button 
* Two-column layout with per-field full-width override
Styling 
* Automatic theme.json inheritance (colours, typography, spacing, border radius) 
* Style panel: primary colour, field style (bordered/soft/underline/minimal), label position (above/beside/floating/placeholder), submit button style (fill/outline/ghost)
Notifications 
* Admin notification email on every submission (configurable recipient, merge tags) 
* Optional confirmation email to the submitter 
* Sends through your site’s standard WordPress mail (<code>wp_mail</code>)
Spam protection 
* Always-on honeypot + signed time-based check (zero configuration) 
* Built-in proof-of-work challenge with accessible math fallback for visitors without JavaScript 
* No external service, no API keys, no tracking cookies, 100% GDPR-friendly
After submission 
* Success message or redirect to a custom thank-you URL (with open-redirect protection) 
* Optional submission ID and form ID query parameters for conversion tracking (GA4, Meta Pixel, Plausible, etc.)
Admin 
* Submissions list with search, filter by form, sort, bulk actions 
* Single-submission detail view with all field labels and values 
* Mark as read/unread 
* Per-form data retention with automatic daily purge
<h3>Privacy</h3>
Flinkform is built with privacy by default. Here is what the free core does and does not do:
What the free core stores: 
* Form submissions (the field values visitors enter) in a dedicated database table (<code>{prefix}flinkform_submissions</code>)
What the free core does NOT do: 
* It stores no IP addresses and no browser user-agent strings 
* It sets no tracking, analytics or marketing cookies. Flinkform sets exactly one strictly-necessary cookie — <code>flinkform_flash</code> (lifetime ~60 seconds, httpOnly) — and only when a form submission fails validation, to carry the error message and the visitor’s input across the page reload. Successful submissions set no cookie at all 
* It contacts no external service
Data retention: 
* By default, submissions are retained until you delete them. To comply with the storage-limitation principle (GDPR Art. 5), set a per-form retention period (Form block → Data Retention) and Flinkform deletes older submissions automatically each day 
* Individual submissions can be deleted from the admin submissions screen at any time
Data deletion: 
* All free-core data (the submissions table) is permanently removed when the plugin is uninstalled through the WordPress admin 
* Flinkform integrates with WordPress’s privacy tools (Tools > Export Personal Data / Erase Personal Data) to support data-subject access and erasure requests
<h3>Source Code</h3>
The complete, uncompiled source code (including the <code>src/</code> directory with the 
unminified JavaScript/CSS that compiles into <code>build/</code>) is publicly available at: 
https://github.com/dennisbuchwald/Flinkform
Build instructions (Node.js 18+ and npm required): 
1. Clone the repository: <code>git clone https://github.com/dennisbuchwald/Flinkform.git</code> 
2. Install dependencies: <code>npm install</code> 
3. Build the compiled assets into <code>build/</code>: <code>npm run build</code>
The build is powered by <code>@wordpress/scripts</code> (webpack). The <code>src/</code> sources are 
excluded from the distributed plugin zip to keep it small; this repository is 
the canonical, reviewable source.

Flinkform – Forms for the Block Editor

Block-native form builder for the WordPress Block Editor — theme.json styling, multi-step forms, conditional logic, Interactivity API.

Mr. J Dev Dynamic Checkout Fields vs Flinkform – Forms for the Block Editor