Yes. The agent UI scans wc_orders_meta (or postmeta on legacy) and lists meta keys actually present in your store. Checkout Manager fields appear under their configured meta key, so you pick from real keys instead of guessing names.

Yes. Writes go directly to wc_orders_meta using the order's CRUD layer where the value is a known meta key. For values that need additional validation (a date format, a country code), the column can be configured to enforce that validation in the inline editor.

Standard order-status edits route through WooCommerce CRUD so woocommerce_order_status_changed and related hooks fire. Custom-field edits trigger the standard updated_post_meta hook on legacy, or the equivalent meta-update hook on HPOS. Any Checkout Manager listener attached to those hooks will run.

Yes. Filters support "is empty" and "is not empty" on any meta-derived column. Useful for finding orders missing a required VAT number, an age confirmation, or a gift-message that should have been entered.

Yes. Conditional fields still write to the same wc_orders_meta keys when the condition is met. SleekView shows the value when present and blank otherwise. You can filter to "orders where the conditional field has a value" to see which orders triggered the condition.

Yes. Any saved view exports to CSV with the active columns including custom-field columns. Useful for sharing a delivery-window queue with the warehouse or a VAT report with the accountant. GDPR data-export tooling continues to work as before.

Each view picks its own columns, so you don't show all fields at once. Fulfillment views show delivery and gift fields, finance views show VAT and tax fields, support views show contact fields. Saved views per role keep things focused per team.

Yes. wc_orders_meta on HPOS works the same way postmeta does on legacy for SleekView's purposes. The same Checkout Manager field configuration produces the same column on either schema, and SleekView detects which path is active.