$cart_items = WC()->cart->get_cart();
    foreach ( $cart_items as $cart_key => $item )
        {
            //custom code
        }

When the cart include products from different shops ( within the MultiSite Network ), the same code can be used. Still, a switch to the product shop is required, for the inner code to be able to correctly retrieve the data. The easiest approach will be to add 2 actions as the example:

    $cart_items = WC()->cart->get_cart();
    foreach ( $cart_items as $cart_key => $item )
        {
            do_action( 'woocommerce/cart_loop/start', $item );
            
            //custom code
            
            do_action( 'woocommerce/cart_loop/end', $item );
        }

There are a few steps required to make the preparation and actual domain assignment:

1. Domain Purchase. A domain is required. If not owned, this can be purchased through any registrar provider. A domain can be anything and can use any available extension.
2. Domain DNS Setup. A Domain Name System (DNS) is required to be set for the new domain name. This is a way to make a virtual link for the domain to actual data storage( server ). Generally, basic DNS management is available at the domain registrar. You need to use the DNS details you received from your hosting provider. A DNS update/change can take up to 24 hours to become available to all networks. You should wait before the domain becomes available through your browser before continuing.
3. Add Domain to Host. The domain needs to be assigned to your host. Presuming the management interface is a cPanel (which is what most servers use) the Addon Domains area should be used. As Document Root the exact path of the current stand-alone WordPress instance ( where WPCommerce MultoDomain is deployed ) must be provided. This is the same path as the main domain through which the site can be accessed. So you don’t need a new WordPress install. Using the same path ensure that accessing the new domain goes to the same WordPress instance.
4. Assign the Domain to your site. Within the WordPress Dashboard, at WooMultoDomain, use Add Domain. Through the interface, provide the Site Address ( the new Domain ), a title, a description. Once created, access Edit ( within All Domains interface) for further adjustments.

    

   

5. The configuration is completed, the new shop should be available for access through the New Domain. Depending on the browser, a cookie and cache data clear might be required. Also, a browser restart, to ensure new cookies will be used. The new shop, with a different domain, is ready to use all plugin features.

When using WPCommerce MultiDomain, by default, all domains share the same options. Some exceptions apply, to ensure each shop uses its own:

• Blog name
• Blog Description
• Active theme
• Widgets
• Menus
• WooCommerce settings
• etc.

This is enough for the majority of the sites, as provides enough flexibility to customize each of the domain. If necessary, include more options in the ignore list is possible.
The proper way to add options in the ignore list is through a WordPress filter woomd/ignore_options. The filter needs inserted through a custom file on /wp-contet/mu-plugins/.

Through the filter, an exact option name can be provided, or if needed to match a group of options, the % char match any substring:
theme_logo
plugin_options
credits_page
divi_% ( this match any option name that starts with divi_ followed by any string combination )

For example, if multiple domains use the same theme, that requires to show differently from a domain to another. Presuming the theme use theme_option to store the settings, the following code provides the ignoring function, so allows customization of the theme on each of the domains, using individual options:

    add_filter ( 'woomd/ignore_options' , '__woomd_ignore_options' );
    function __woomd_ignore_options( $ignore_options )
        {
            if ( is_array ( $ignore_options ) )
                {
                    $ignore_options[]  =   'theme_option';
                }
            return $ignore_options;
        }

Benefits of the Feature:

• Targeted Marketing
  With the capability to hide certain product categories on specific domains, businesses can fine-tune their marketing efforts. By displaying relevant products tailored to each domain’s demographic or geographic audience, conversion rates can soar.

• Streamlined User Experience
  Eliminate clutter and streamline navigation by hiding irrelevant product categories. Customers browsing a domain dedicated to a particular niche or region will appreciate a cleaner interface showcasing products pertinent to their interests.

• Flexible Branding
  Maintain brand consistency across domains by curating product offerings to align with each site’s unique branding and messaging. Whether promoting seasonal specials or exclusive collections, this feature empowers brands to convey a cohesive identity tailored to diverse audiences.

• Enhanced SEO Performance
  Leveraging the 404 error page strategically can bolster SEO efforts. By directing users to a customized error page rather than simply displaying “product not found,” businesses can maintain user engagement and potentially reduce bounce rates, positively impacting search engine rankings.

• Granular Control
  The integration of hide/show attributes within the WordPress Product Category interface affords administrators granular control over product visibility. Easily toggle categories on or off across domains with a few simple clicks, ensuring precise targeting without the need for complex coding or third-party solutions.

• Promotion and Exclusivity
  Drive excitement and exclusivity by selectively hiding premium or limited-edition product categories on specific domains. Create buzz and incentivize customers to explore different domains for unique offerings, fostering a sense of anticipation and discovery.

The Hide attribute for the categories can be managed through the default WooCommerce Categories interface:

1. Navigate to the default WooCommerce Categories interface in your WordPress dashboard.
2. Locate the desired product category you wish to hide on specific domains.
3. Within the category settings, you’ll find a new option labeled “Category Visibility.”
4. Select the domains where you want the category to be visible or hidden by toggling the visibility options accordingly.
5. Save your changes to update the category settings.
6. Repeat these steps for each product category you wish to customize visibility for across different domains.

The implementation of the WooCommerce Multi-Domain plugin’s feature to hide specific product categories across domains presents a significant advancement in e-commerce customization. By strategically leveraging this functionality, businesses can optimize their overall efforts by tailoring product visibility to match the interests and preferences of each domain’s audience. This granular control not only enhances user experience but also boosts brand consistency and search engine rankings. Embracing this innovative feature empowers businesses to maximize their online presence, drive engagement, and ultimately increase conversions across diverse online platforms.

If you use the WPCommerce WooMultiDomain solution, the blog_id becomes meaningful: it holds the product’s origin blog/site ID inside the multisite or multi-domain network. That means every order line can carry a direct reference to the exact site where the product record lives, which simplifies reconciliation, inventory tracing, and any cross-site fulfillment logic.

Be mindful that blog_id is an internal identifier: it’s best used in administrative views and developer tools rather than shown to customers. When monitoring multi-domain stores, keeping the blog_id visible in admin order items speeds debugging and makes multi-site commerce workflows much easier to manage.

To hide the blog_id meta field, a custom code can be used. The following code example can be added within theme functions.php or a custom file in /mu-plugins/ folder.

    /**
    * Remove 'blog_id' from formatted order item meta shown in admin/emails/frontend.
    *
    * @param array            $formatted_meta Array of formatted meta objects/arrays.
    * @param WC_Abstract_Item $item           The order item object.
    * @return array Modified $formatted_meta without 'blog_id' entries.
    */
    function hide_order_item_blog_id_meta( $formatted_meta, $item ) 
        {
            foreach ( $formatted_meta as $index => $meta ) 
                {
                    // Support both object and array shaped meta entries (defensive)
                    if ( is_object( $meta ) ) {
                        $key = isset( $meta->key ) ? $meta->key : ( isset( $meta->display_key ) ? $meta->display_key : '' );
                    } elseif ( is_array( $meta ) ) {
                        $key = isset( $meta['key'] ) ? $meta['key'] : ( isset( $meta['display_key'] ) ? $meta['display_key'] : '' );
                    } else {
                        $key = '';
                    }

                    if ( '' !== $key && strtolower( $key ) === 'blog_id' ) {
                        unset( $formatted_meta[ $index ] );
                    }
                }

            // Reindex numeric keys and return
            return array_values( $formatted_meta );
        }
    add_filter( 'woocommerce_order_item_get_formatted_meta_data', 'hide_order_item_blog_id_meta', 10, 2 );