Skip to content

FAQ

No. It is an add-on for the free Pair plugin and requires it to be installed and active (version 0.1.0 or later). Without the free plugin, Pair Pro does not boot and displays an admin notice instead.

Where does the “frequently bought together” data come from?

Section titled “Where does the “frequently bought together” data come from?”

From your own store’s completed and processing orders. Pair Pro scans the most recent paid orders (150 by default, configurable from 20 to 1000), keeps the ones that contain the product being viewed and counts the other products bought alongside it. Nothing is guessed from categories and no data leaves your site.

Why is the block not showing on some products?

Section titled “Why is the block not showing on some products?”

The block hides itself when there is no co-purchase data for that product: no recent paid order contains it together with other products, or every co-purchased product is filtered out (out of stock with In stock only on, unpublished, or hidden from the catalog).

Results are cached for 12 hours per product in a transient. New orders influence the block after the cache expires. The cache stores the full ranked list (up to 12 products), so changing the product count does not trigger a new scan.

Yes. Order lines are attributed to their parent product, so variations of the same product collapse into a single recommendation.

It is a plain POST form with a nonce, no JavaScript. Pair Pro adds each product from the block to the cart, skips anything not purchasable or out of stock, shows the standard WooCommerce message and redirects back to the product page.

Is it compatible with WooCommerce HPOS and Blocks?

Section titled “Is it compatible with WooCommerce HPOS and Blocks?”

Yes. Pair Pro declares compatibility with High-Performance Order Storage (Custom Order Tables) and the Cart/Checkout Blocks, and reads orders through the WooCommerce order API, which is HPOS-safe.

Where do I buy Pair Pro and how much is it?

Section titled “Where do I buy Pair Pro and how much is it?”

Pair Pro is sold and delivered through Freemius at https://plogins.com/plogins-pair-pro/. Annual licenses cost EUR 29 for 1 site, EUR 59 for 5 sites and EUR 99 for unlimited sites. It is not available in the WordPress.org plugin directory.

Through the Freemius SDK bundled with the plugin, using your license.

Yes. With manual curation on, the product editor gets a Pair recommendations meta box. Pick the products for that specific product and choose whether your picks lead the automatic ones (prepend) or replace them entirely (replace).

They express “when the product is in category A, recommend products from category B”. You define up to six rules globally, and they lead the automatic picks on the product page. Useful when a category sells another one and no order history says so yet.

Set a percentage and it applies once the whole “frequently bought together” set is in the cart, added through the add-all-to-cart button. It is a negative cart fee, so it shows as its own line in the totals. Remove any product from the set and the discount disappears at the next recalculation.

On the order-received page (on by default) and after the checkout form (off by default), plus anywhere you place the Pair Recommendations block in the block editor or an FSE template. All of them reuse the free plugin’s markup, so they inherit your theme’s product cards.

Turn A/B testing on and pick the strategy for variant B. Each visitor is assigned A or B at random, kept in a cookie for 30 days. Variant A keeps your configured product-page strategy, variant B uses the alternative, and the analytics screen reports the two as separate rows so you can compare impressions, clicks and click-attributed add-to-cart events.

Impressions and clicks are counted directly. Conversions are click-attributed: if a shopper clicks a recommendation and later adds that product to the cart, the add-to-cart is credited to the recommendation. That is approximate by design, a directional signal about which placement earns attention rather than revenue accounting.

Yes, one: {prefix}pair_pro_stats, the aggregated analytics table, dropped again when you delete the plugin. It counts impressions, clicks and click-attributed conversions per day, placement and product, aggregated on write so it stays small. Settings live in WordPress options and co-purchase results in transients.

Everything Pair Pro created goes: the pair_pro_settings, pair_pro_version, pair_pro_activated_at and pair_pro_db_version options, every cached pair_pro_fbt_* transient, the _pair_manual_recommendations product meta and the {prefix}pair_pro_stats analytics table, once per site on a network. Deactivating changes nothing; only deleting the plugin triggers it. If you would rather keep the analytics history and your hand-picked sets, return false from the pair-pro/uninstall/delete_data filter. The free Pair plugin and its settings are untouched either way.