Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Free shipping threshold is mistakenly synced as minimum spending threshold #2469

Open
eason9487 opened this issue Jul 15, 2024 · 3 comments
Open
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc.

Comments

@eason9487
Copy link
Member

Describe the bug:

If there is a minimum order amount to get free shipping, it will be mistakenly synced to Google Merchant Center as a minimum spending threshold.

This issue occurs with shipping data obtained from WooCommerce core or set in this extension.

Steps to reproduce:

Using WooCommerce core shipping data

  1. Go to WooCommerce > Settings > Shipping > Shipping zones and set up a zone with free shipping and minimum order amount.
    image
  2. Go to edit free listings.
  3. Select the Recommended: Automatically sync my store’s shipping settings to Google option for the shipping rates setting.
  4. Add the above configured zone to the Audience setting.
  5. Save changes.
  6. Wait a moment for the settings to sync to Google Merchant Center.
  7. Go to Google Merchant Center and navigate to Shipping and returns page.
  8. Expand the corresponding shipping policy.
    • The above minimum order amount of free shipping is set as the No shipping under amount.
    • The Free shipping over amount is empty

1

Using extension shipping data

  1. Go to edit free listings.
  2. Select the My shipping settings are simple. I can manually estimate flat shipping rates option for the shipping rates setting.
  3. Add a free shipping threshold.
    image
  4. Save changes.
  5. Go to Google Merchant Center and navigate to Shipping and returns page to see the incorrect synchronization.

1

Expected behavior:

The minimum order amount to get free shipping should be synced to Google Merchant Center as the Free shipping over amount.

Actual behavior:

The minimum order amount to get free shipping is synced to Google Merchant Center as the No shipping under amount.

Additional details:

Related codes:

The minimumOrderValue field in Content API for Shopping document:

https://developers.google.com/shopping-content/reference/rest/v2.1/shippingsettings#service

Minimum order value for this service. If set, indicates that customers will have to spend at least this amount.

@eason9487 eason9487 added type: bug The issue is a confirmed bug. impact: high This issue impacts a lot of users as reported by our Happiness Engineers. priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. and removed impact: high This issue impacts a lot of users as reported by our Happiness Engineers. labels Jul 15, 2024
@tomalec
Copy link
Member

tomalec commented Dec 29, 2024

I'd like to question the severity of this issue. As if I understand correctly, we indeed use the x free shipping threshold as the "No shipping under" instead of "Free shipping over," but we do so for the shipping group with cost == 0. So logically, it means zero-cost for orders over x.

So, instead of, creating one shipping group:

  • "Shipping rate 99.00, free shipping for orders over 987.00"
    We create two
  • "Shipping rate 0, for orders over 987"
  • "Shipping rate 99.00, for all"

So, both, IMHO, describe more-or-less the same thing. I agree that they are not precisely the same, and it would be better for the merchant experience to create n/2 groups and use that field.

Another thing is that, in API docs, I didn't find a way to specify a free shipping threshold :/

@puntope puntope added priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. product sync and removed priority: high The issue/PR is high priority—it affects lots of customers substantially, but not critically. type: bug The issue is a confirmed bug. labels Jan 2, 2025
@puntope
Copy link
Contributor

puntope commented Jan 2, 2025

I agree with @tomalec here. Google Service does create a single group for each threshold that is equivalent to the expected behaviour. So I'm setting this as low for now. Feel free @eason9487 to revert this if I'm missing something about the issue that makes it a High Prio Bug.

@puntope
Copy link
Contributor

puntope commented Jan 2, 2025

Tested this a bit more... When I enter in MC and edit the Shipping I cannot set Excluded Value as 0 anymore 😕

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc.
Projects
None yet
Development

No branches or pull requests

3 participants