Checkout Field Editor stores its custom field definitions in the thwcfe_sections option, with each field's key, type, and conditional rules. Captured values land in wp_postmeta against the order with the field key as the meta key. Standard fields keep their normal Woo keys (_billing_first_name, etc.), but new fields use whatever key the merchant chose (_gift_wrap_type, _company_vat, _delivery_window, etc.).

SleekPixel reads the field definitions from the Checkout Field Editor option, then maps a chosen subset onto the receipt card. The template editor exposes each custom field as a variable with the field's label as a hint, so a gift-wrap field can be rendered with a wrapped-gift icon, a delivery-window field can be rendered as a time badge, and a company VAT field can be rendered as a B2B identifier.

The card renders on woocommerce_order_status_processing and on woocommerce_order_status_completed, depending on which status the merchant prefers to use as the trigger. Refunds and manual order edits regenerate the card automatically so the values shown always reflect the current state of the order.

Checkout Field Editor is one of the most-installed checkout customization plugins for WooCommerce, used by stores that need fields beyond the default address set. Gift orders capture a gift_wrap type and a message. B2B orders capture a company VAT number and a purchase order reference.

Subscription stores capture a preferred delivery day. Bakery stores capture allergen notes. Every one of those fields is the actual purpose of installing Checkout Field Editor in the first place.

Yet none of them show on the order's OG image, because the default OG image on every Woo order page is the storefront's homepage logo. A gift order looks identical to a standard order in previews. SleekPixel changes that by treating each order's custom fields as social content.

The card surfaces the chosen subset of fields, with their labels and styled badges, then ships as a real PNG attached to the order. When the order URL is shared in a confirmation email, in a support ticket, or in an ops channel, the preview reflects the checkout context that made this order different from the next.