Product data is a machine-readable promise. If the feed says a blue medium item is in stock for $28 but the page opens a red small item for $34, Google and the shopper see different offers. Dropship stores face this mismatch often because a supplier can change variants, stock, price, and shipping without editing your store.
Build the feed from verified store offers and keep it synchronized with the page and checkout. Every submitted item should lead to the exact purchasable variant at the stated price and availability. Update or pause an offer when the supplier facts no longer support it.
This is part three of the Merchant Center Dropshipping Guide. First check store eligibility and product pages and policies. This article focuses on the data layer that connects those pages to Google.
Use the current specification as the contract
Google’s product data specification defines required and conditional attributes for the target country and program. At a minimum, understand the rules for a stable item ID, title, description, landing-page link, image, price, availability, condition, identifiers where applicable, and shipping or return data. Apparel, custom products, bundles, subscriptions, and other categories can need additional attributes.
Do not build a permanent feed from a dated example without checking the current specification. Google updates its requirements, and availability or shipping rules can differ by country. Keep a dated mapping document for your store: source field, Google attribute, transformation, update frequency, and owner. A mapping makes it possible to identify whether a bad value came from the supplier, your catalog, or the feed export.
Start with a handful of sample products and inspect the processed result in Merchant Center. A technically valid file can still contain the wrong variant, unsupported claim, or stale price. The buyer-facing page remains the decisive comparison.
Give each real offer a stable ID
Use a stable ID for the same product variant across updates. Do not reuse an ID for a substantially different item because a supplier replaced the original. If the size, color, material, or bundle changes what a buyer receives, represent it correctly as a distinct variant under the current specification. Keep your internal product ID separate from a supplier’s changing marketplace URL or listing number.
Maintain an identity record: product name, approved supplier and variant, your SKU, sample date, catalog version, and URL. When a supplier silently swaps a batch, compare it with the approved sample before continuing to use the old data. A feed cannot make an unverified physical item consistent.
For product identifiers, follow Google’s unique product identifier guidance. Use a real manufacturer-assigned GTIN when applicable; do not invent a barcode or put your store’s SKU in the GTIN field. Use brand and MPN only when they truthfully identify the product under the applicable rules. If a product lacks assigned identifiers, follow Google’s instructions for that situation rather than borrowing another product’s codes.
Write titles and descriptions from the tested item
The feed title should describe the item a buyer can purchase, with useful verified attributes such as type, brand when authentic, size, color, material, or quantity. Do not stuff it with unrelated search phrases. The landing page title and visible product information should support the same offer. A product sourced from AliExpress is not automatically a branded item because the supplier put a logo in a thumbnail.
Use a description that distinguishes the product and answers real buyer questions. Record dimensions and contents from a sample when possible. Remove claims about safety, durability, compatibility, or certification that lack evidence. The AliExpress listing guide gives a claim inventory for this work.
Use an image you have rights to use and that represents the exact variant. A photo of a larger bundle or different finish can mislead even when the feed text is correct. Check the landing page’s selected variant and image from a normal browser session, because a supplier-linked catalog plugin may default to another option.
Keep price aligned at all three points
The feed price, landing-page price, and checkout price for the target shopper must agree. Google’s specification explicitly requires price and currency to match the landing page and checkout. Audit sale prices, currency conversion, variant surcharges, mandatory add-ons, and checkout discounts. If a low price applies only after a code or membership, use the supported attribute and presentation for that offer rather than pretending every shopper can get it.
Supplier prices are inputs to your retail pricing, not feed prices. When a supplier raises its price, choose whether to absorb the change, update your store price and feed together, or pause the item. Do not let a supplier sync overwrite the store price at one layer while the feed remains stale. Record the last successful comparison between source, store, and Google.
Google may use page information to help correct some temporary mismatches through automatic product updates. That feature is a safety net, not a replacement for maintaining the underlying catalog. If your page markup is also stale or wrong, automation can reproduce the same error. Resolve the source of the mismatch.
Define availability from fulfillable stock
Google’s specification says availability must match the landing page, checkout, and structured data. A dropship store must decide what “in stock” means when it does not hold the item. It should mean the exact variant can be ordered and fulfilled under the promised terms, based on current supplier evidence. A week-old marketplace buy button is not enough for a fast-changing item.
Create a stock-confidence process. A direct supplier may provide a reliable inventory feed or reserved stock. A marketplace seller may require more frequent manual checks and a smaller catalog. Set a maximum age for stock evidence according to how quickly the item changes. When the source becomes uncertain, stop accepting new orders or mark the product unavailable in all connected surfaces.
Use preorder or backorder only when the offer genuinely has that status and the required date and buyer explanation are available. Do not select a different status simply to avoid a disapproval. If the product is out of stock, follow the current specification for displaying price and availability on the landing page while preventing an impossible purchase.
Keep shipping facts current
Google requires shipping information in many target countries, including the United States, under the conditions described in the product data specification. The account’s shipping services, product-level attributes, and website should agree about cost, speed, and eligible locations. A supplier offering several routes does not mean every buyer gets the fastest route at the lowest price.
Use a tested handling time and a current transit estimate for the supported region. If a product is unusually large, fragile, or shipped from a different country, give it the appropriate shipping rule rather than the store’s cheapest default. The Shipping Profit Guide shows how to form a delivery promise from the actual parcel and destination.
When supplier shipping changes, update the store’s delivery policy and Merchant Center settings together. If your website promises free shipping but the account reports a charge, or the account reports free shipping while checkout charges the buyer, resolve the discrepancy before increasing traffic.
Add truthful Product and Offer structured data
Google Search Central’s merchant listing structured-data guide explains how Product and Offer markup can describe price, availability, shipping, and return information on a purchase page. Structured data should describe the visible offer, not a second, more attractive version of it. A page with variant choices needs markup that corresponds to the actual selected or represented offer under Google’s current guidance.
Test markup on a small set of pages and inspect what Google sees. Confirm that price currency, availability, and condition reflect the page. Markup can improve machine understanding and support automatic updates, but it does not guarantee a rich result or compensate for an inaccurate listing. Do not add invented ratings or reviews to make a sparse product page appear established.
If your platform automatically generates schema, inspect its output after changing variants, sale prices, or inventory. A plugin can leave InStock in JSON-LD after checkout blocks the item. Treat that as a catalog synchronization bug, not merely a search enhancement issue.
Choose an update rhythm that matches the risk
Google provides scheduled data-source updates and other ways to submit product changes. The right frequency depends on how quickly your price and availability change and on the technology you use. A daily file may be adequate for stable reserved stock; a volatile marketplace product can change between updates. In that case, a smaller catalog and pre-order availability check may be safer than a large stale feed.
Monitor the time from source change to storefront change to feed processing. If you cannot guarantee consistency, pause the affected item during the gap. Do not rely on an arbitrary refresh schedule without measuring whether it catches supplier changes before shoppers click.
Keep a change log for price, availability, URL, image, and shipping rules. When Merchant Center reports a mismatch, the log helps identify whether the error began in supplier data, your catalog, the page template, or Google processing. It also prevents the team from “fixing” a feed while leaving checkout wrong.
Test the final buyer experience
Choose one submitted item from each major product profile. Open the URL Google has for it, confirm the exact variant, compare price and availability, and proceed to checkout in a supported region. Check the page’s structured data and account shipping configuration. Repeat after a supplier or store-platform change.
The success condition is simple: the machine-readable product and the human-readable purchase experience describe the same current offer. The next article explains how to use diagnostics to find the specific layer that broke when they do not.