Philip R

Thanks very much. In the meantime, I found that rolling back WooCommerce to 10.4.3 restores attribution reporting, until this is resolved.

Someone else has reported this problem, you may wish to follow it.

https://ww.wp.xz.cn/support/topic/from-7th-of-february-order-origins-always-unknown/

Thank you @oalili. I do have twice-daily automatic backups of the database. If you could point me in the right direction for how to access the tables for storing the spam and valid entries , I would appreciate it. I am still troubleshooting the underlying issue and this would help.

@oalili Thank you! I have updated to 1.2.62.

Regarding my site, the only other thing that I can think of that has happened in the time that the problem appeared has been the Cloudflare settings, as well as some work on the WordPress database that my developer colleague made. If you like, I can follow up with you on email to send you those Cloudflare settings, if it would help pinpoint the issue. The information you provided about a small JavaScript snippet on the checkout page to collect metadata possibly being interfered with could be a helpful clue.

@oalili Thank you. We will continue there. For the benefit of others, I have also recently applied the WooCommerce 10.5 update, and I wonder if anyone else has experienced a problem after applying the WooCommerce 10.5 update.

Review submitted!

The following suggestion to insert a guard for WooCommerce Product Vendors appears to work. I offer the solution to @victormonk in the event that you wish to test and merge it into the plugin itself. Please see below…

…

What’s actually breaking

1. Product Vendors has its own email templates

WooCommerce Product Vendors ships its own email templates, including:

• woocommerce-product-vendors/templates/emails/order-email-to-vendor.php
• woocommerce-product-vendors/templates/emails/email-order-details.php
• woocommerce-product-vendors/templates/emails/plain/order-email-details.php (Stack Overflow)

Those templates know how to restrict order items to a single vendor. 2. Kadence globally hijacks all email templates

In the Kadence plugin file
kadence-woocommerce-email-designer/kadence-woocommerce-email-designer.php
there is this method:

function filter_locate_template( $template, $template_name, $template_path ) {
    // Make sure we are working with an email template.
    if ( ! in_array( 'emails', explode( '/', $template_name ) ) ) {
        return $template;
    }

    // ...
}

Inside this function, Kadence ignores where the template actually came from and forces WooCommerce to use its own copy under templates/woo/emails/... for anything that looks like an email template.

That means:

• When Product Vendors tries to load its vendor-specific email-order-details.php,
• Kadence intercepts and instead uses Kadence’s generic templates/woo/emails/email-order-details.php,
• That generic template just calls wc_get_email_order_items( $order, ... ) on the full order, exactly like core WooCommerce.(WooCommerce GitHub)

Result: vendor emails see all order items, not just their own. The simplest safe fix: don’t let Kadence touch Product Vendors templates

We can fix this by slightly changing filter_locate_template() so that it skips templates that belong to WooCommerce Product Vendors and lets that plugin handle its own emails.

Step 1 – Open the Kadence main plugin file

File path:

wp-content/plugins/kadence-woocommerce-email-designer/kadence-woocommerce-email-designer.php

Search inside it for:

function filter_locate_template( $template, $template_name, $template_path ) {

You should see the beginning of the function like this:

function filter_locate_template( $template, $template_name, $template_path ) {
    // Make sure we are working with an email template.
    if ( ! in_array( 'emails', explode( '/', $template_name ) ) ) {
        return $template;
    }

    // clone template.
    $_template = $template;

    // Get the woocommerce template path if empty.
    if ( ! $template_path ) {
        global $woocommerce;
        $template_path = $woocommerce->template_url;
    }

    // Get our template path.
    $plugin_path = KT_WOOMAIL_PATH . 'templates/woo/';

    // ...
}

Step 2 – Insert a guard for WooCommerce Product Vendors

Right after the “Make sure we are working with an email template” check, add this block:

function filter_locate_template( $template, $template_name, $template_path ) {
    // Make sure we are working with an email template.
    if ( ! in_array( 'emails', explode( '/', $template_name ) ) ) {
        return $template;
    }

    // --- BEGIN: do not override WooCommerce Product Vendors templates ---
    // If the resolved template lives inside the WooCommerce Product Vendors plugin,
    // leave it alone so vendors still see their vendor-specific items only.
    if ( $template && false !== strpos( wp_normalize_path( $template ), 'woocommerce-product-vendors/templates/' ) ) {
        return $template;
    }
    // --- END: do not override WooCommerce Product Vendors templates ---

    // clone template.
    $_template = $template;

    // Get the woocommerce template path if empty.
    if ( ! $template_path ) {
        global $woocommerce;
        $template_path = $woocommerce->template_url;
    }

    // Get our template path.
    $plugin_path = KT_WOOMAIL_PATH . 'templates/woo/';

    // ... (rest of the original function remains unchanged)
}

What this does:

• When WooCommerce has already resolved a template path like
  wp-content/plugins/woocommerce-product-vendors/templates/emails/order-email-to-vendor.php,
  Kadence now immediately returns it and does not swap in its own email template.
• So Product Vendors’ own order-email-to-vendor.php and its own email-order-details.php are used again, which correctly limit items to that vendor.

Step 3 – Upload and test

1. Save the file.
2. Clear any opcode cache if your host uses one (optional but helpful).
3. Place a test order with products from multiple vendors.
4. Check vendor emails:
   • Each vendor should again see only their own products.
   • Admin / store owner still sees the full order.

Trade-offs & notes

• Kadence styling won’t apply to Product Vendors’ vendor emails after this change.
  They’ll go back to the Product Vendors default HTML/layout, but they’ll be correct.
• This change is inside the plugin, so:
  • When Kadence WooCommerce Email Designer updates, your edit may be overwritten.
  • Keep a note of this patch so you can re-apply it after updates.
• A more advanced solution would be to:
  • Copy Product Vendors’ order-email-to-vendor.php into your theme, and
  • Manually blend in Kadence’s HTML structure while still using the vendor-specific item logic.
    If you want to go that route, I can sketch that template for you too.

Quick summary

• The bug isn’t in order-email-to-vendor.php itself; it’s Kadence forcing all email templates (including Product Vendors’ ones) through its own generic email-order-details.php.
• By adding a small guard in filter_locate_template() to skip templates from woocommerce-product-vendors/templates/, you restore the proper vendor-only behavior while keeping Kadence for all the core WooCommerce emails.