Define, relabel and reorder checkout fields as a schema — live checkout wiring lands in a coming release.
Stores a checkout field schema as JSON in the add-on settings. Each entry carries an id, section, label, type, required flag, position, optional options list, placeholder and a removed flag. GET and POST /ambikly-pro/v1/checkout-fields read and write the schema, gated on the view-store and manage-store capabilities, and every label, placeholder and option is sanitized before saving. The ambikly_checkout_fields filter merges entries over a default field list, relabelling, reordering by position, adding and removing fields, and ambikly_order_meta_keys registers custom ids. In the current release the core checkout does not apply either filter, so a saved schema has no visible effect on the live checkout until that wiring lands.
Built on the same Addon SDK as every other Pro add-on — extend it instead of replacing it.
GET /ambikly-pro/v1/checkout-fieldsPOST /ambikly-pro/v1/checkout-fieldsambikly_checkout_fieldsambikly_order_meta_keysrest_api_initA wholesale supplier plans to collect a company name and VAT number. It defines both fields in the schema now, with required flags and positions, so the moment the core checkout consumes the schema the fields appear without further configuration work.
A store selling only downloads intends to drop the postal address fields. Marking them removed in the schema documents the intended checkout shape for its developers and for the future core renderer, in one place rather than scattered notes.
An agency building a custom checkout template reads the schema over GET /ambikly-pro/v1/checkout-fields and applies the ambikly_checkout_fields filter in its own code, using the add-on as the single source of truth for field definitions across environments.
Ambikly → Add-ons → Checkout Field Editor → toggle on. Pro must be active; nothing else to install.
Open its settings panel and set: field schema (JSON array of field entries).
The storefront surfaces, admin screens and settings it adds are listed under “Where it shows up” above; nothing needs placing by hand unless a shortcode is named there.
Disable the add-on from the same screen. Its settings and data stay in place, and a lapsed license pauses it the same way — the store keeps running.
Not yet. The core checkout form and validation do not call ambikly_checkout_fields or ambikly_order_meta_keys in the current release, so the schema is stored and available to code but nothing renders it. This page will be updated when the core wiring lands.
Reading requires the ambikly_view_store capability and saving requires ambikly_manage_store, or manage_options for either. Because Store Managers can save, every label, placeholder and option is passed through sanitize_text_field and ids and types through sanitize_key.
A JSON object with id, section (defaults to shipping), label, type (defaults to text), required, position (defaults to 99), an optional options array, placeholder and a removed flag. Entries with removed set to true delete the matching default field when the filter runs.
In the schema, yes: an id that does not match a default field is appended with the values you supply, and its id is registered through the order-meta filter. Storing the submitted value against the order is not implemented in the current release.
Cart and checkout combined onto a single page for faster conversion.
CheckoutOne-click upsell offer shown on the order confirmation page.
CheckoutRecurring billing for memberships, SaaS, and subscription boxes. Customers self-manage from their account.
CheckoutPro is $199 a year or $549 once, for all 35 add-ons. Enable this one from the same admin the day you need it.