Skip to main content

Pre-orders and backorders on Google Shopping: the ship date

A pre-order or backorder needs a ship date on the product page and in [availability_date], and the same status in your product data and on the page. Use preorder only for products not yet released; a restock is a backorder. “Coming soon” with no date is how a pre-order turns into a month of chasing emails.

Major4 min read

Why this matters

Google’s “Availability [availability]” page defines both states and gives each the same duty. Preorder: “You’re accepting orders for this product, but it’s not been released for sale.” Backorder: “The product isn't available at the moment, but you’re accepting orders and it will be shipped when it's available again.” For both, you must send the [availability_date] attribute, and “The availability date should be visible on the landing page.” It also draws the line between them: “The preorder [preorder] value should only be used for new products that haven’t been released yet.” A sold-out product you are restocking is a backorder.

The “About landing page requirements” page says the same from the page side: “If the product is available for preorder or backorder, the page should also show the expected date when the product will be shipped.” The “Availability date [availability_date]” page explains what kind of date: the date “should also be added to the product’s landing page and be clear to your customers”, and “If an exact date can’t be provided, you can use an estimated date”, such as a month. In the data itself it asks for a single date rather than a range, and “Google recommends adding an estimated date (up to 1 year in the future) and updating the value as soon as the expected date the product can be shipped to the consumer is confirmed.”

Status has to agree everywhere too. The availability page asks you to “Show a consistent availability across the landing page, structured data (if available), checkout page, and your data source”. A page taking pre-orders while the product data says in_stock is a mismatch, and the Misrepresentation policy lists “Promoting products that aren't stocked” under “Unavailable offers”. In structured data, PreOrder or PreSale maps to preorder and BackOrder to backorder. For the wider rules on stock status see availability in Merchant Center; for the delivery promise on the rest of your range, handling time vs transit time.

The free scan reports as a failure a product page whose structured data and visible stock status contradict each other, and flags product markup that declares no availability at all. The dates in your product data are outside the scan; compare them with the page by hand. The misrepresentation checker lists every stock check in one place.

Typical evidence

“Pre-order” owes the shopper a date

A product marked orderable while quietly weeks from shipping misrepresents availability. The compliant pattern has two halves that must agree: a real date beside the CTA, and a matching availability date in the feed.

Product pageno date
Pre-order now
Shopper expects this week. It ships in six.
Product pagedated
Pre-order now
Ships on or before 15 July 2026
feed: availability = preorder · date 2026-07-15
Hide the wait and you misrepresent it to Google; promise a date you’ll miss and you misrepresent it to the customer. One honest date satisfies both.

The public signals this check looks for:

  1. A “Pre-order” or “Coming soon” button with no ship date anywhere on the page

    A “Pre-order” or “Coming soon” button with no ship date anywhere on the page.

  2. A sold-out product that is being restocked is marked preorder instead of backorder

    A sold-out product that is being restocked is marked preorder instead of backorder.

  3. The page takes pre-orders while the product data still says in_stock

    The page takes pre-orders while the product data still says in_stock.

  4. The page shows standard delivery times beside a pre-order button, so the shopper expects t…

    The page shows standard delivery times beside a pre-order button, so the shopper expects the usual wait.

  5. The date on the page was the supplier’s first guess and has already passed

    The date on the page was the supplier’s first guess and has already passed.

What it looks like once it is right

“Pre-order: ships on or before 14 November 2026. You will be charged when your order ships.” The product data says preorder with an [availability_date] of 14 November, and the structured data says PreOrder.

Common mistakes

Common mistake

A product page says “Coming soon – order now!” beside “Delivery in 2–3 days”. There is no date, the structured data says InStock, and the product data says in_stock. Orders sit for six weeks.

Fix checklist

Give the shopper a date they can use

Hiding the wait or promising a date you cannot meet both create a misleading public claim. Keep one honest date consistent across the page and any submitted product data.

Pre-order now
no date — needs review
Ships in days!
optimistic date you miss
Ships ≤ 15 Jul
honest date — page = feed

Questions merchants ask

Do I need to show a date for pre-orders on Google Shopping?

Yes. Google's availability page requires the [availability_date] attribute for preorder and backorder items and says the date should be visible on the landing page. An estimated date, such as a month, is acceptable when you do not have an exact one.

What is the difference between preorder and backorder in Merchant Center?

Preorder is for new products that have not been released yet. Backorder is for existing products that are out of stock and will be back, where you are still taking orders. Google's availability page says the preorder value should only be used for new products that haven't been released yet.

Can I use a date range for the availability date?

Not in the product data. Google's availability date page advises against date ranges and recommends an estimated date, updated as soon as the real ship date is confirmed. On the page you can give the month if that is all you know.

Remediation

Risk signal

Pre-orders are a promise with a date in it. Put the date on the page, send the same date in [availability_date], mark new releases and restocks correctly, and move all of it together when the supplier slips.
PriorityAddress and document this finding as part of the store’s remediation work.
EvidenceRecord the current state before each change, apply the fix, then capture the corrected state so every change is evidenced.

Similar cases

Sources

  1. Availability [availability] — in stock, out of stock, preorder, backorderGoogle Merchant Center Help — support.google.com
  2. Availability date [availability_date] — preorder and backorder ship datesGoogle Merchant Center Help — support.google.com
  3. About landing page requirementsGoogle Merchant Center Help — support.google.com

Last reviewed 23 Sep 2026.

That is one issue. The library documents 134.

The free scan lists what it finds on your store. The paid report adds the affected pages, captured evidence and step-by-step fixes. Start free, with no account needed.