SleekView for Checkout Field Editor: every custom field as a sortable row
Read Checkout Field Editor's custom-field definitions from wc_fields_* options and join them to the postmeta/wc_orders_meta values customers entered at checkout. Sort by field, filter by value, edit inline.
♾️ Lifetime License available
Stop opening orders to read what customers typed at checkout
Checkout Field Editor adds custom fields to billing, shipping, or additional sections at WooCommerce checkout — gift messages, delivery instructions, VAT IDs, referral sources. The field definitions live in WordPress options (wc_fields_billing, wc_fields_shipping, wc_fields_additional) and the customer-entered values land in order meta as _billing_*, _shipping_*, or arbitrary keys per the field's name.
The default Orders list shows none of these. To read a delivery instruction or a referral source, you open the order and scroll. SleekView exposes each Checkout Field Editor key as a column — picked from the actual definitions in your wc_fields_* options — and surfaces the captured values directly in the orders table. Sort by referral source, filter by VAT-ID present, or build a fulfilment view that shows gift-message text alongside shipping address.
Inline edits write back to the order through WooCommerce CRUD, so corrections to a typo'd VAT ID or a missing tracking note happen without leaving the row. Bulk-set a field across many orders for migrations or cleanup, and the standard order-update hooks fire as if each had been edited by hand.
Workflow
How SleekView reads your Checkout Field Editor data
Point at the field definitions
wc_fields_billing, wc_fields_shipping, and wc_fields_additional in wp_options, listing the fields and their types so the column picker reflects your real configuration.
Compose your column set
Save and scope the view
Edit inline and ship
Sample columns
A typical orders view with custom checkout fields
wc_fields_billing/wc_fields_shipping/wc_fields_additional and joins captured values from order meta.
wp_options (wc_fields_*) + wp_wc_orders_meta
| Order # | Customer | Gift message | Delivery note | Referral | VAT ID |
|---|---|---|---|---|---|
| #10934 | alex@studio.co | Happy birthday Mum | Leave at side gate | Newsletter | — |
| #10932 | ria@design.io | — | Buzzer broken, call | Friend | DE812345678 |
| #10930 | tom@hello.dev | Congratulations | — | — | |
| #10928 | mia@brew.coop | — | Office reception | Podcast | BE0123456789 |
| #10925 | leo@atelier.fr | Pour Maman | Sonner trois fois | FR40123456789 |
Comparison
Default Checkout Field Editor admin vs SleekView
Default Checkout Field Editor
- Custom-field values are only visible inside the per-order screen
- Field definitions live in options arrays edited via the plugin's UI
- No way to filter orders by custom-field value (e.g. "all gift orders")
- Conditional fields exist in definitions but conditions aren't visible elsewhere
- Bulk corrections to a custom field across many orders aren't supported
SleekView
-
Pick custom-field columns from the actual
wc_fields_*definitions - Filter orders by custom-field value, not just by status and date
- Inline-edit any custom-field value through WooCommerce CRUD
- List field definitions and their conditions as their own audit view
- Surface fields from billing, shipping, and additional sections in one row
Features
What SleekView gives you for Checkout Field Editor
Custom-field columns from the real definitions
SleekView reads wc_fields_billing, wc_fields_shipping, and wc_fields_additional directly. Pick a column from the actual list of fields configured in the plugin — no typing meta keys by hand, no guessing names.
Filter on what customers entered
Saved views like "Gift orders this week", "Orders with a VAT ID", or "Referrals from Podcast" become real. Combine custom-field filters with status, date, and total to narrow down to exactly the rows you need.
Edit inline, hooks intact
Fix a typo in a VAT ID, append a fulfilment note, or bulk-clear an obsolete field across migrated orders. Each write goes through CRUD so order-updated hooks, audits, and webhooks fire as expected.
Audience
Who uses SleekView for Checkout Field Editor
Gift-heavy stores
A view filtered to "gift message present" with the message text inline lets fulfilment print enclosure cards in batches. No more opening every order during the holiday rush.
Customer support
When a customer mentions a delivery instruction, search by email and see the captured note alongside the order. Edit it inline if the customer is calling to update it mid-call.
Compliance and finance
B2B stores with VAT-ID capture filter to orders where the field is present, export for invoicing, and audit empty values for follow-up. The same view powers an end-of-month tax reconciliation.
The bigger picture
Why custom-field values belong in the orders list
Checkout Field Editor solved one problem cleanly — capture extra information at checkout without writing a custom plugin — but left another in place. Once the customer types a gift message, a delivery instruction, or a VAT ID, that data lives in order meta, invisible from the orders list, accessible only by opening each order one at a time. Stores that capture lots of custom data feel this most: a gift-heavy retailer printing enclosure cards during the holidays, a B2B shop reconciling VAT IDs at month-end, an agency tagging referral sources for marketing reports.
Each of them ends up exporting CSVs or writing custom queries to do the work the admin doesn't support. SleekView removes that step. It reads the field definitions Checkout Field Editor already maintains, exposes them as columns in the orders table, and makes them filterable, sortable, and inline-editable.
The data was always there — it just wasn't where ops needed it. Pull it into the row and the workflow becomes obvious.
Questions
Common questions about SleekView for Checkout Field Editor
Yes. SleekView scans wc_fields_billing, wc_fields_shipping, and wc_fields_additional options, lists the configured fields, and exposes them as picker entries when you compose a column. You don't have to type meta keys — you pick from the list of fields actually configured in the plugin.
Yes. Custom-field columns are filterable just like core columns. Combine them with status and date for views like "Gift orders processing this week" or "Orders with referral = Podcast in the last 30 days". Saved views persist these filters per role.
Yes. Custom-field values stored in order meta update through WooCommerce CRUD when you edit them inline. Hooks like woocommerce_update_order and any plugin-specific filters still fire — Checkout Field Editor's own logic on save runs as it would from the per-order screen.
Yes. On HPOS, custom-field values move from postmeta to wc_orders_meta. SleekView reads from the active store. The same view config works across HPOS and legacy schemas.
Yes. Build a view sourced from the wc_fields_* options that lists every defined field — label, type, section, required flag, conditions. Useful for auditing checkout copy or finding fields that no longer apply but still display.
The conditions live in the field definition. SleekView exposes the condition rule as a column on the field-definitions view, so you can audit which fields show only for certain shipping countries or product categories. Captured values still surface in the orders view, with a blank where the field didn't apply.
Yes. Filter to the orders you want, select them in the table, and bulk-set a custom-field value. Each write goes through CRUD so hooks fire per row. Useful for cleanup migrations — "clear this deprecated field on all orders before 2024-01" — without writing a one-off SQL script.
SleekView reads any meta key on an order, so values captured by other field plugins surface as columns the same way — you just pick the meta key directly. The picker integration with field definitions is specific to Checkout Field Editor's wc_fields_* options; other plugins work via the generic meta path.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkout