No. SleekPixel only generates the OG image attached to the order URL and the invoice page in the browser. The actual PDF generated by WP Overnight is unchanged. The two systems run in parallel, both reading the same order data.

Yes. SleekPixel reads the order entity through the WooCommerce CRUD layer, which abstracts whether the underlying storage is the legacy wp_posts rows or the HPOS wp_wc_orders table. The same template works with both.

Only if you choose to include it on the template. The order URL is typically private (signed or accessed by logged-in customers), but the OG image itself can be cached by social platforms. Many stores show the document number and status but omit the total for privacy.

SleekPixel regenerates the image on status change. The og:image meta points to the same URL but with a new file, and a cache-busting query string ensures the social platforms re-fetch. Old shares pasted into chat clients still resolve to the latest image.

Yes. WP Overnight stores the formatted number in _wcpdf_invoice_number_data as serialized data, and SleekPixel can either read the formatted value directly or recompose it using your prefix/suffix template.

Yes. The template supports conditional rendering on order status. A paid order can show a green badge, an unpaid one a yellow one, a refunded one a strike-through total. All conditions live in the template, not in code.

Image generation runs after the order save completes and takes a few hundred milliseconds. Bulk regeneration after a template change runs in the background via Action Scheduler and does not block the admin.

Yes. Credit notes have their own meta keys (_wcpdf_credit_note_number, etc.), and SleekPixel can use a different template variant for credit-note URLs. Refund flows and credit notes can each have a distinct visual treatment.