Improve markup for e-commerce shipping options #2506
Assignees
Labels
no-issue-activity
Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
Comments
|
For additional context on what we've done at Google so far:
|
|
Having 'shipping location' as a concept might also be useful. An understanding of where items are being shipped from is often an influence on purchasing decisions. |
|
Richard,
Do you mean “made in Chile” and shipped from a warehouse in Atlanta? Where
something is shipping from is not always the same as where it comes from.
Your comment at first read seems to conflate these concepts. Is that your
intent?
…On Tue, Mar 24, 2020 at 5:20 PM Richard Wallis ***@***.***> wrote:
Having 'shipping location' as a concept might also be useful. An
understanding of where items are being shipped from is often an influence
on purchasing decisions.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2506 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAJ2JT5KRDOOT2IPLOKVVLRJDMT7ANCNFSM4LSXFWDA>
.
|
|
I mean shipped from a supplier somewhere. Example scenario 1: Example 2: In both cases knowing the location from whence the product is shipped would be helpful in deciding who to purchase from, and the risk to a safe and timely arrival. |
|
@RichardWallis @HughP - thanks. We may come back to these but my colleagues tell me there are some complexities. We can revisit "ships from" later if there are use cases. |
danbri
added a commit
that referenced
this issue
Apr 21, 2020
35 tasks
|
I do not understand the utility of Additionally (and I think relevant to the point above) this needs examples, especially as understanding how to mark up |
danbri
added a commit
that referenced
this issue
Jun 19, 2020
|
Stale issue message |
github-actions
bot
added
the
no-issue-activity
|
Following the source link (#2506) from https://schema.org/PostalCodeRangeSpecification: https://schema.org/PostalCodeRangeSpecification appears to be US-centric. Many countries use alpha-numeric postal codes. Would the following be considered OK for postal codes H2* and V2X 6E3 to V2X 6S4? Is "postalCodeEnd" optional? Logically, it should be to allow for everything that matches "postalCodeBegin"... |
|
@danbri Can the product schema examples be updated to reflect changes? |
I don't get at all why we would mark up shipping destination at all? If a company sells internationally, the options could be endless! Google can access other linked data to calculate shipping based on browser location and shipper ( USPS, UPS, FedEx, etc all ). I don't see examples that require a certain amount to be spent to qualify for free shipping, either. |
|
@danbri Not sure if this is the right place to ask and suggest, but it seems like it. If I got this right the minimum for ShippingDeliveryTime is 1 day. No way to specify same day delivery for local delivery with average delivery time for a given Product, right? We could specify 0 days but I am not sure how that will be handled and some categories like food delivery usually is faster than retail delivery and I see no way to specify this food product = 40min and retail product = 1hour30min. Is this planned as the hyper local delivery business is growing and becoming more popular? Suggestion if introducing minutes isn't feasible would be a new tag for samedaydelivery: |
|
List of postalcodes Hello, Question Is it possible to define a list of postalcodes instead of a range? From the documentation its not clear what the cardinality is for each attribute like for "postalcode". https://schema.org/DefinedRegion Something like:
Or is the example in this link valid having multiple ranges where postalcodeEnd is optional? If its optional we could simply define Workaround Else it seems we have to repeat the whole OfferShippingDetails for each postalcode which increases the json size massive. |
FYI, you should use an @graph block, and use Schema type blocks within the @graph with unique @id's. Then each property that needs to be repeated, just use the @id to refer to the appropriate block, that way you don't repeat big blocks of data. In case you use WordPress and WooCommerce, have a look at the WPSSO plugin (and its WCSDT add-on https://wordpress.org/plugins/wpsso-wc-shipping-delivery-time/), which optimizes the @graph markup in this way. js. |
|
Thanks for your reply and i think i understand the concept to reference a @graph by @id. But is this a wordpress or woocommerce related thing or is it from schema.org? We develop our own shop system. Quick test: https://search.google.com/test/rich-results/result?id=1tRokUQnsIScCDCIkUzmgw Google and schema.org testing tools dont complain if attribute postalcode is an array it seems. I will try this out in production and see if google merchant center will respect it. |
|
I went with the array solution but have not yet seen confirmation that it is accepted by Google. They do provide examples of addressRegion as an array. I also have addressCountry as an array. It would be nice if this is clarified. |
It's a Schema markup thing - here's a pretty extensive example from one of our test sites. :) |
|
@jsmoriss Thats a great example and interesting use case with the references using @id. I tested with
Maybe i will remove the shipping data markup and keep it settings in the merchant center. |
|
@djmj I believe the merchant centre takes priority. It may be worth keeping it in for other possible consumers. |
|
@jsmoriss I am impressed with the complexity of your example. I have a question that your example does not cover, and wonder if you have an example that helps me get my product correctly defined. We have a business that can only ship certain products within California. I am trying to create a shippingDetails/shippingDestination that defines the region where doesNotShip is true (all states except California), and a region where doesNotShip is false. I tried using an array of shippingDetails with defined regions within it. Your example shows me where my DefinedRegions are incorrectly defined. I'm stuck on whether or not I need multiple offers, each covering the ship/does not ship, or an array of shippingDetails. Thanks in advance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(this is a proposal from Google based on our experience using schema.org Product markup)
Motivation: When users search for and browse different products across the web, they often want to understand what kinds of shipping options might be available to them. It would be useful for Schema.org to have expressivity that allowed various merchants to describe their shipping policies, including cost and estimated delivery times according to delivery location. As always there are various levels of detail that might be made explicit.
Our suggestion is to start with something like the following:
Main concepts:
Plus these as "useful to have":
This initial version may not support dynamic pricing based on other dimensions, such as the item price or weight or dynamic carrier rates. These are consequently difficult here because of the vast number of potential edge cases, but more potentially could be supported in the future.
The text was updated successfully, but these errors were encountered: