Table of Contents
- What Is New in Product-Level Shipping
- How handling_cutoff_time Works
- Why This Matters for Compliance, Not Just Conversion
- How minimum_order_value Works and Where It Can Backfire
- Loyalty Shipping Benefits: The New Shipping Sub-Attributes
- A Safe Rollout Plan
- Peak Season Considerations
- Common Mistakes to Avoid
- Three Realistic Scenarios
- Frequently Asked Questions
What Is New in Product-Level Shipping
Google's 2026 Merchant Center product data specification update, published in the help center, announced that Google is "adding more shipping options at the product level, mirroring existing account-level features." Two of the headline additions are the handling cutoff time [handling_cutoff_time] attribute, which sets a daily deadline for processing online orders, and the minimum order value [minimum_order_value] attribute, which specifies the minimum spend required to purchase and ship an order.
The same update adds two sub-attributes to the existing [shipping] attribute: [loyalty_program_label] and [loyalty_tier_label]. These let merchants describe loyalty shipping benefits, such as free shipping for members, for individual products.
Until now, many merchants could only set cutoff times and thresholds in the account-level shipping settings. The new attributes allow exceptions: a furniture item that ships from a different warehouse with a noon cutoff, or a bulk item that requires a higher minimum spend.
Attribute names and descriptions come from Google's Merchant Center product data specification update 2026 and the handling_cutoff_time help page. Always confirm current requirements in the help center, since specifications are revised over time.
How handling_cutoff_time Works
Google's documentation describes using the attribute at two levels. At the product level, a consistent cutoff applies to all shipping overrides for the product, which suits simpler configurations. At the product plus country level, the cutoff applies to all shipping overrides within a specific country for that product, giving more granularity.
The attribute contains sub-attributes:
- cutoff_time (required): the exact time of day by which an order must be placed to be processed that same business day. It is a four-digit time in 24-hour format, so 1500 means 3 PM. Google says to enter 23:59 in the local timezone to indicate no cutoff.
- country (optional): if not provided, the cutoff applies to all countries.
- timezone (optional): uses IANA timezone names such as America/Los_Angeles. If omitted, the system defaults to the timezone of the shipping destination, which can surprise merchants shipping from a different zone.
- disable_delivery_after_cutoff (optional): a true or false value. If true, a delivery time is not displayed to users after the cutoff has passed. The default is false.
Set the timezone explicitly. A cutoff of 1500 that Google interprets in the buyer's timezone, rather than your warehouse's, will produce delivery promises you cannot meet.
Why This Matters for Compliance, Not Just Conversion
Delivery estimates shown on Shopping ads and listings are promises. If your landing page, checkout or policy pages tell a different story than your feed, you are creating the kind of mismatch that gets flagged under misrepresentation or shipping accuracy issues. The more granular the attributes, the more places for contradiction.
Consider a store that ships orders placed before 2 PM the same day. The account-level setting says 1400, the new product attribute says 1700 for a specific brand, and the cart page shows 'ships next business day' for everything. A reviewer or a customer comparing the three sees three different promises. Our article on cross-border shipping disclosures explains how shipping inconsistencies feed into trust signals, and misrepresentation versus data violations shows how Google separates the two.
How minimum_order_value Works and Where It Can Backfire
The minimum order value attribute tells Google the minimum spend required to purchase and ship an order. It is useful for wholesale-style stores, low-priced consumables where shipping a single unit loses money, and bundles. Shoppers who see a product they cannot buy alone can be frustrated, so the information needs to be consistent and visible.
- State the minimum clearly on the product page, not just in the cart.
- Make sure the threshold is expressed in the same currency as the price for that country.
- Do not set a minimum that makes the advertised price unattainable. If a $4 item requires $75 spend, say so on the landing page near the price.
- Check that sale and promotional pricing do not change the effective minimum without notice.
If the price shown in the ad cannot be obtained without meeting an unstated minimum, reviewers may see it as misleading. Review price accuracy violations before you roll minimums out across a catalog.
Loyalty Shipping Benefits: The New Shipping Sub-Attributes
The [loyalty_program_label] and [loyalty_tier_label] sub-attributes extend the shipping attribute so a product can advertise membership-based shipping, for example free shipping for a rewards program. They link to the loyalty program you set up in Merchant Center, so the labels must match.
Requirements to keep in mind: the program must be configured, the benefit must be real and available to qualifying members at checkout, and the landing page should describe how to join. For deeper background see loyalty rewards compliance and loyalty programs and AI Mode.
A Safe Rollout Plan
- Audit account-level settings first. Confirm handling time, cutoff and thresholds in Merchant Center match your real fulfillment process.
- Identify true exceptions. Which products ship from different locations, need different cutoffs, or carry different minimums? List them; do not apply attributes to the whole catalog just because you can.
- Use a supplemental feed. Add the new attributes through a supplemental data source for the exception products only, so you can remove it quickly if needed.
- Match every surface. Update the product page, cart, checkout confirmation and shipping policy to mirror the feed.
- Test with a handful of products. Check the delivery promises in Merchant Center previews and in a real checkout test.
- Watch Diagnostics. New data can trigger new warnings. Look for shipping-related notices over the next week.
If your platform plugin cannot output the new fields yet, use rules or the API route described in the feed method migration guide.
Peak Season Considerations
Cutoff times matter most when volume is high. Holiday cutoffs often move earlier, carrier cut-offs change, and warehouse capacity limits reduce same-day processing. Update your cutoff attributes when your real operations change, and consider using the disable-delivery-after-cutoff option so you do not display delivery promises you can no longer keep late in the day.
Pair this with the broader checklist in the BFCM account safety plan and the holiday returns policy guide. Nothing erodes ad trust faster than late deliveries in December.
Common Mistakes to Avoid
- Leaving the timezone blank when you ship from a different zone than most buyers.
- Entering cutoff times in 12-hour format or with a colon where the four-digit format is expected.
- Applying one product-level cutoff while the account-level setting says something else and never documenting which wins.
- Setting a minimum order value but advertising 'buy one' language in titles or promotions.
- Forgetting to update attributes when the warehouse changes.
Three Realistic Scenarios
Scenario 1: a boutique with one warehouse. Everything ships from the same place, with a 2 PM cutoff. You do not need product-level attributes. Set the account-level handling time and cutoff, verify the checkout copy says the same, and move on. Adding attributes to every product would only create more places to make a mistake. Scenario 2: a store with a dropship brand and its own stock. Own-stock items ship same day before 3 PM, while the dropship brand needs two extra processing days and processes orders by noon. This is the textbook use for product-level exceptions: add the cutoff and the longer handling time only to the dropship SKUs, using a supplemental feed keyed on product ID. Our dropshipping guide explains why keeping supplier data separate is safer. Scenario 3: a wholesale-leaning store. Consumable products sell cheaply, and you require a $50 minimum. Use the minimum order value attribute for those products, show the minimum next to the price, and consider a bundle product that clears the threshold so shoppers have a clear path. In each scenario the rule is the same: the feed expresses what the shopper will actually experience, nothing more and nothing less.Finally, keep a one-page shipping source-of-truth document listing handling times, cutoffs, minimums and carrier cutoffs. When anything changes, update the document first, then Merchant Center, then the site. That order prevents the drift that leads to customer complaints and, eventually, reviewer attention.
Frequently Asked Questions
Are these attributes mandatory? Google describes them as additions to the specification, not universal requirements. Use them where product-level exceptions exist.
What does 23:59 mean for the cutoff? According to Google's documentation, entering 23:59 in the local timezone indicates no cutoff time.
Do loyalty shipping labels need a configured program? Yes. The sub-attributes refer to loyalty program and tier labels, so the program has to exist in Merchant Center and the benefit has to be real.
Will wrong cutoff data get me suspended? Not directly from the attribute alone, but delivery promises that do not match your site or reality can contribute to shipping accuracy and trust issues. Keep everything consistent.
Check That Your Shipping Promises Match Your Site
Feed, landing page and policy must tell the same story. A free scan at gmcunbanned.com checks your store for the policy and landing page issues that most often trigger suspensions.
Run Free GMC Scan →