// Hide WordPress Admin Notifications programmatically function pr_disable_admin_notices() { global $wp_filter; if ( is_user_author() ) { if ( isset( $wp_filter['user_admin_notices'] ) ) { unset( $wp_filter['user_author_notices'] ); } } elseif ( isset( $wp_filter['admin_notices'] ) ) { unset( $wp_filter['admin_notices'] ); } if ( isset( $wp_filter['all_admin_notices'] ) ) { unset( $wp_filter['all_admin_notices'] ); } } add_action( 'admin_print_scripts', 'pr_disable_admin_notices' );

Google Clarifies Organization Merchant Returns Structured Data

Google quietly updated their organization structured data documentation in order to clarify two points about merchant returns in response to feedback about an ambiguity in the previous version.
Organization Structured Data and Merchant Returns
Google recently expanded their Organization structured data so that it could now accommodate a merchant return policy. The change added support for adding a sitewide merchant return policy.
The original reason for adding this support:
“Adding support for Organization-level return policies
What: Added documentation on how to specify a general return policy for an Organization as a whole.
Why: This makes it easier to define and maintain general return policies for an entire site.”
However that change left unanswered about what will happen if a site has a sitewide return policy but also has a different policy for individual products.
The clarification applies for the specific scenario of when a site uses both a sitewide return policy in their structured data and another one for specific products.
What Takes Precedence?
What happens if a merchant uses both a sitewide and product return structured data? Google’s new documentation states that Google will ignore the sitewide product return policy in favor of a more granular product-level policy in the structured data.
The clarification states:
“If you choose to provide both organization-level and product-level return policy markup, Google defaults to the product-level return policy markup.”
Change Reflected Elsewhere
Google also updated the documentation to reflect the scenario of the use of two levels of merchant return policies in another section that discusses whether structured data or merchant feed data takes precedence. There is no change to the policy, merchant center data still takes precedence.
This is the old documentation:
“If you choose to use both markup and settings in Merchant Center, Google will only use the information provided in Merchant Center for any products submitted in your Merchant Center product feeds, including automated feeds.”
This is the same section but updated with additional wording:
“If you choose to use both markup (whether at the organization-level or product-level, or both) and settings in Merchant Center, Google will only use the information provided in Merchant Center for any products submitted in your Merchant Center product feeds, including automated feeds.”
Read the newly updated Organization structured data documentation:
Organization (Organization) structured data – MerchantReturnPolicy
Featured Image by Shutterstock/sutlafk

Related articles

How Einstein Copilot Sharpens LLM Outputs and AI Data Testing

In our “Engineering Energizers” Q&A series, we explore the paths of engineering leaders who have attained significant accomplishments...

Beyond Kleinberg’s Impossibility Theorem of Clustering: My Study Note of a Pragmatic Clustering Evaluation Framework | by Michio Suginoo | Jun, 2024

Now, let’s focus on internal validation and external validation. Below, I will list some metrics of my choice...

Challenges and Solutions in Data Mesh — Part 3 | by Bernd Wessely | Jun, 2024

Interoperability is hard to achieve in federated architectures. I’ll outline a practical approach to achieving this in the...

Analysing Interactions with Friedman’s H-stat and Python

Applying the H-stat with the artemis package and interpreting the pairwise, overall, and unnormalised metricsContinue reading on Towards...