TikTok for WooCommerce, distributed by TikTok for Business, handles the catalog sync to TikTok Shop, the TikTok Pixel events through both the browser and the Events API, and the merchant onboarding for Shop ads. It reads from WooCommerce's product post type and meta like _regular_price, _sale_price, and the product image. Inside TikTok, the product feed and Shop ads carry the product image and price correctly. Outside TikTok, the same product URL still previews with whatever default og:image the theme uses, usually a single store logo across the entire catalog.

SleekPixel reads the same Woo postmeta the TikTok integration is already syncing and composites a per-product OG card. The card carries the product image, name, price, sale state, and stock status. The og:image meta tag writes on save into the post head. When a TikTok shopper copies a product URL out of the app and into a group chat, the reshare preview now matches the product feed visual instead of falling back to the store logo. Both plugins share Woo as a data source, but operate on independent channels.

For TikTok's Spark Ads and Shop Ads driving traffic to product landing pages, the card stays aligned with whatever canonical the ad URL points at, so reshared URLs from organic and paid behave the same way.

TikTok for WooCommerce solves the TikTok side of the catalog problem cleanly: products in TikTok Shop, the TikTok Pixel firing browser and server events, Shop ads driving traffic to landing pages. The gap that remains is the moment a TikTok shopper takes the URL out of the app. A copy-and-paste from a TikTok product into a friend's iMessage thread or a group Slack channel breaks the visual coherence the brand spent ad spend building, because the og:image on most Woo stores is the site logo, not the product.

SleekPixel closes that gap by reading the same Woo postmeta the TikTok plugin already syncs and composing a per-product card with the product image, name, price, sale and stock state, and brand mark. The card lives in your WordPress uploads, the meta tag writes on save, and the TikTok Pixel and Events API streams stay completely untouched. The two systems share a data source, WooCommerce, and a goal, getting product URLs to convert at the moment of share, but they operate on independent channels.

That separation is what makes the pairing reliable: nothing in SleekPixel can break TikTok event dedup, and nothing in the TikTok plugin can invalidate a card cache.