WPRobo Checkout URL Bridge for Meta Shops

Your normal checkout page, e.g. https://yourstore.com/checkout/. Enter it in Commerce Manager under your shop's Settings → Checkout method → "Checkout on another website". You never build the product part of the URL yourself — Meta appends ?products=...&coupon=... automatically when a buyer checks out, and the plugin detects that parameter on any front-end URL.

From your product catalog, not from the checkout URL. Every item you sync to Meta carries a "retailer ID": the Meta for WooCommerce extension uses wc_post_id_123 (your real product ID), data feeds use whatever their id column contains (usually your SKU), and some feeds produce SKU_123 composites. When a buyer checks out, Meta builds the checkout URL from those retailer IDs — and this plugin translates every one of those formats back to the correct WooCommerce product or variation.

No. The plugin resolves whatever retailer IDs your existing catalog already sends, as long as they trace back to your store's product IDs or SKUs. Only catalogs whose IDs match nothing in WooCommerce (e.g. IDs from a previous shop platform) cannot be resolved automatically.

Almost always page caching. Exclude your checkout page (and any URL with a products query parameter) from caching in LiteSpeed Cache, WP Rocket, SG Optimizer, or your host's server-level cache. Most caching plugins exclude /checkout/ by default — verify it.

Yes — pass the variation ID or the variation's SKU and the correct variation is added with its attributes.

Yes. That extension syncs your catalog with wc_post_id_ retailer IDs, which this plugin resolves natively.