To fix missing prices, incorrect availability or shipping errors in Google Merchant Center, start with the affected product in Products → Needs attention, inspect its final attributes, and compare them with the exact product variant displayed on your website and at checkout. Correct the underlying catalogue or shipping configuration, resynchronise the product data, and check the issue again after Google processes the changes. Uploading the same broken feed repeatedly will not solve a mismatch.
For Nigerian merchants, there is an important country-specific distinction. Google lists Nigeria as a beta country for Shopping ads and free listings, with participation and visibility limitations. Google does not list Nigeria among the countries where shipping costs are universally mandatory for those formats, although an account can still display shipping issues based on its targets, configurations or other requirements. See Google's supported-country list and shipping attribute rules .
This practical guide covers the reasons product listings fail, the checks that separate a bad feed from an inaccurate landing page, and ways to stop the errors returning. Research verified 4 November 2026.
First: find the real error in Merchant Center
Open Google Merchant Center , select Products, then Needs attention. Google's diagnostics guide says this area lists product and account problems, affected items and recommended fixes. Filter by the issue and export the affected-products CSV when several items are involved. Individual products may have an issue-details page showing what is wrong and the relevant attribute.
Do not assume every warning means the entire account is suspended. Google distinguishes warnings, limited eligibility, item-level disapprovals and account-level problems. An item might also be eligible for one marketing method or country but not another. Confirm the actual impact before deciding what to repair first.
| Message or symptom | Likely area to inspect | First action |
|---|---|---|
Missing value [price] | Feed or uploaded product record lacks a valid price | Inspect the product's final price attribute and source mapping |
| Mismatched price (page crawl) | Submitted price differs from landing page or checkout | Compare the same SKU and sale price across every surface |
Missing value [availability] | Stock attribute absent or malformed | Supply an accepted availability value for each offer |
| Mismatched availability | Website and submitted stock state disagree | Check inventory events, cached pages and variants |
| Missing shipping costs | Missing shipping policy or item override where required | Verify target country, coverage and shipping rules |
| Inaccurate shipping costs | Merchant settings do not match customer charges | Reproduce the checkout for the same address and item |
| Merchant listings markup warning | Structured data on product page is incomplete | Run Google's Rich Results Test and inspect Product/Offer |
A feed-processing error, a Merchant Center item disapproval and a Search Console Merchant listings report warning are related but not identical. Search Console checks whether page markup qualifies for certain Search enhancements; Merchant Center also evaluates feed content, country settings and policies. Use the report that actually raised the issue.
1. How to fix missing Google Merchant Center prices
For ordinary online product offers, Google's Product Data Specification requires a usable price attribute. A blank field, wrong mapping, unparseable amount or missing currency can prevent the product from being processed correctly.
The price for a Nigerian-naira offer may look like 45000.00 NGN in a text data source. It should represent the genuine purchasable price of the specified item; never replace a missing value with a fictitious zero or an outdated promotional amount just to clear the error.
Check the attribute at three locations
- Source catalogue: Does this SKU or variant actually have a valid current selling price? Check database or commerce-platform values and whether discounts are active.
- Submitted product source: Open the feed row or integration mapping. Verify
priceis populated, formatted correctly and uses the appropriate currency. - Final attributes: Inspect the product in Merchant Center. A manual edit, supplemental source or rule may override the value in your primary feed. Google's Needs attention documentation warns that some edits can take precedence over later file updates.
For example, imagine a retailer's internal price is ₦45,000 but the exported record contains an empty price because the exporter reads a retired database column. Updating the product page alone will not fix the missing feed field. Correct the export mapping, regenerate the data source and confirm that 45000.00 NGN appears in Merchant Center's final record.
2. How to fix price mismatches between the feed and website
A price can be present but still wrong. Google compares submitted product data with landing-page information; discrepancies may lead to automatic corrections, limited visibility or disapprovals. Google's price attribute guidance requires the listed amount to match what the customer can actually buy.
Common causes include a stale daily feed after a flash sale; a currency conversion; a hidden discount; a default variant showing instead of the submitted size or colour; different prices on mobile and desktop; and caches that serve old HTML to Google's crawler.
Use a same-product, same-variant comparison
| Source | Illustrative price | Diagnosis |
|---|---|---|
| Primary feed for SKU SHOE-43 | ₦45,000 | Old amount |
| Merchant Center final attribute | ₦45,000 | No overriding correction |
| Product page, navy size 43 | ₦49,500 | Live price changed |
| Checkout, same variant | ₦49,500 plus stated delivery | Confirms current sale price |
Fix: Update the feed to the genuine ₦49,500 price, keep page markup consistent, and send an updated product source promptly. If the ₦45,000 amount is a valid current sale price, ensure the sale-price fields, effective dates and customer-visible page reflect it correctly. Do not disguise a mandatory product surcharge as “shipping” to create a misleading lower product price.
When prices vary by visitor location, login state or device, check Google's structured-data restrictions before submitting that page. Google cautions against landing-page values that change according to customer information such as IP address or browser type.
3. How to fix missing or incorrect availability
For the ordinary Merchant Center product data source, availability is required. Google's availability rules accept four main values:
| Feed value | Meaning | Extra requirement |
|---|---|---|
in_stock | Accepting orders and able to fulfil promptly | Must be consistent with actual purchasability |
out_of_stock | Not accepting orders or product unavailable | Do not show as immediately purchasable |
preorder | Accepting orders before initial release | Provide applicable availability_date visible on page |
backorder | Temporarily unavailable but orders accepted | Provide applicable availability_date visible on page |
Do not use the word “available” as a custom value or automatically mark every published product in_stock. A product can be published in your catalogue but have zero sellable inventory. Equally, a backorder is not identical to an unreleased preorder.
Why Google may say an item is out of stock when your system says otherwise
Check whether the exact variant is selected on the linked page. A T-shirt's large size might be unavailable even though the medium size is in stock. Confirm whether warehouse quantities are reserved by pending orders, whether stock is scoped to the delivery location, and whether cached product pages or stale Offer.availability markup contradict the live inventory.
Google's availability mismatch walkthrough advises comparing the product's final attributes against the same variant on its landing page. Repair the inventory-to-feed mapping, regenerate the offer record and, if necessary, clear stale public caches. Avoid promising fulfilment when stock is not actually available.
4. How to fix missing shipping details
Shipping is not one universal global rule. Google lists countries where shipping costs are mandatory for Shopping ads and free listings; Nigeria is not included in that general mandatory-country list as of this review. However, a merchant targeting one of the listed countries, using a configuration that requires shipping, or receiving a specific shipping diagnostic must address the applicable requirement. Do not assume every Nigeria-only offer is disapproved solely because its feed lacks a shipping column.
When Google flags missing shipping costs, its official repair procedure recommends defining a shipping policy at the account level and, where needed, supplying an offer-specific override through shipping.
- Open Merchant Center, then Products & store → Shipping and returns.
- Create or inspect the shipping policy for the actual country or countries of sale.
- Define which products and delivery areas the policy covers, the relevant charges and realistic delivery times.
- Save and verify that each affected offer is covered. For unusually heavy, bulky or fragile items, check whether an item-level override is needed.
- Make the store's visible delivery policy and checkout charges consistent with the settings; reprocess affected items.
Google states shipping-setting changes may need 24–72 hours to appear in the account. This is guidance, not an assurance that every case will be cleared within that time.
5. Fix shipping costs that do not match checkout
A configured shipping policy can still be wrong. Consider a hypothetical Nigerian store charging ₦2,500 for delivery within one city but ₦6,000 for an order to another supported destination. If the product listing incorrectly implies the first rate for both addresses, buyers may see misleading costs.
Use representative delivery addresses within every supported zone and confirm what the customer actually pays. Check minimum-order thresholds, free-shipping promotions, package weight, dimensions, handling fees and whether the chosen service applies to that product. Make sure checkout does not introduce a mandatory delivery-related amount that the declared rate ignores.
Google's shipping specification describes shipping as including relevant delivery, handling, carrier and logistics charges, plus specified associated insurance charges. It also distinguishes handling time from transit time. Do not promise next-day arrival if the warehouse normally needs two working days before dispatch.
For growing stores, start with a small number of maintainable shipping policies rather than dozens of contradictory item overrides. Where account-level settings and item-level attributes both exist, test which value Google uses for the affected offer.
6. Check Product and Offer structured data on every affected page
Price and availability issues sometimes originate in the website's structured data rather than the feed. Google's merchant listing documentation explains how Product and Offer markup describe the offer being purchased.
For a fictional product costing ₦49,500 and genuinely in stock, the relevant portion of a JSON-LD Offer object may be:
{ "@type": "Offer", "url": "https://shop.example.com/products/shoe-43", "price": 49500, "priceCurrency": "NGN", "availability": "https://schema.org/InStock", "itemCondition": "https://schema.org/NewCondition"
}This fragment belongs inside a valid Product structured-data object and is illustrative, not a complete copy-and-paste production schema. The URL is an example, not a live merchant. If the product is sold out, the page and structured data must reflect that instead of leaving an old InStock value.
Run the exact product URL through Google's Rich Results Test , then inspect its rendered structured data. Confirm that JavaScript, caching and variant selection are not producing different offer values. Google advises including product structured data in the initial HTML when practical because JavaScript-generated markup can make shopping crawls less reliable for frequently changing prices and stock.
7. Understand why automatic item updates may not fix the problem
Merchant Center can use machine-readable page data to help correct certain mismatches when automatic item updates are enabled. But Google's structured-data guidance says these corrections are not a replacement for regular product-data updates.
If Google's crawls repeatedly find major discrepancies, automatic price or availability updates may stop working. Google specifically warns that large-scale mismatches can increase the risk of disapproval or account suspension. Even when Google changes the visible item value automatically, the store's underlying catalogue is still incorrect.
Repair the primary source—whether it is Shopify, WooCommerce, a custom Laravel application, an XML file or a database export—then publish consistent values to the website, feed and any relevant API. Re-enable or rely on automatic updates only as a supplementary safety measure, not as the core inventory management system.
8. Check WooCommerce, Shopify and custom platform integrations
When an integration manages the product source, do not assume a manual edit in Merchant Center will permanently fix the record. Review the data path from the store to Google and find the authoritative value.
| Store setup | Common cause | Useful check |
|---|---|---|
| WooCommerce | Variable-product stock or price not mapped per variation | Inspect child variants and the plugin's generated offer data |
| Shopify | App sync delay, market pricing or wrong variant URL | Compare the selected market and current variant with Google data |
| Custom Laravel or other backend | Stale cache, failed queue job or retired price column | Inspect export logs, job failures, database version and cache |
| Spreadsheet or scheduled feed | Old file published, incorrect column mapping or unsuccessful fetch | Confirm the latest successful upload and final product attributes |
| API integration | Partial update, duplicate records or outdated integration | Check API errors, stable IDs and actual final values |
Google has sunset the old Content API for Shopping in favour of the Merchant API . Developers should avoid new work on legacy endpoints and check the latest migration guidance for existing connections.
Whatever the platform, do not edit one product in four different places and hope the systems converge. Decide which system owns the stock and price, record updates centrally, and make downstream synchronisation observable.
9. How to verify a fix and request review
After correcting the actual source, submit or resynchronise data. Reopen the affected offer and confirm its final attributes; check its public page, selected variant, structured data and checkout. Then look again in Needs attention.
Google's review guidance explains that some issues clear after data reprocessing, while others allow a review or website check. Use the review control when it is offered and after the underlying problem has genuinely been resolved. Repeated appeals without correcting product data can waste time and leave eligibility unchanged.
Keep a small incident log: affected SKU, issue type, first detected time, feed value, live-page value, root cause, corrective change, upload timestamp and eventual Google status. A warning that persists briefly after a genuine fix does not necessarily mean the repair failed; allow normal processing and investigate if it remains.
10. Prevent repeat errors with automated checks
For a store with hundreds or thousands of listings, prevention is better than repairing each row manually. A reliable product-data workflow should:
- Validate that every active sellable offer has a stable ID, positive applicable price and accepted availability state.
- Map each variant to the correct product URL and image, not merely the parent product's default selection.
- Reconcile sale-price rules, tax treatment and currency with the actual checkout.
- Generate and publish feeds atomically so Google never fetches a partially written file.
- Update product records soon after stock, price or sale changes; use a scheduled full reconciliation as a backup.
- Test representative destination addresses against shipping rules and delivery promises.
- Keep product page markup and Merchant Center attributes in sync.
- Alert staff when exports fail, disapprovals rise or Google reports systemic mismatches.
For broader store design context, FlyingEze has reviewed e-commerce landing-page tools . Good page design may help shoppers, but Merchant Center needs accurate live offer data and a usable purchase experience as well.
Frequently asked questions
Why does Merchant Center say my price is missing when I can see it on the website?
The required price might be absent from the submitted product record, malformed, overwritten by a rule or missing from the exact variant Google is assessing. Compare the feed, final attributes and that variant's landing page.
Is shipping mandatory for Google Merchant Center in Nigeria?
Google's general list of countries where shipping costs are mandatory does not include Nigeria as of 4 November 2026. That does not remove the need for honest delivery charges or eliminate shipping issues caused by other target countries, account configurations or specific requirements.
What availability value should I use for a sold-out item?
Use out_of_stock when the product is unavailable or not accepting orders. If legitimate preorders or backorders are accepted, follow Google's applicable availability_date requirements.
Can Search Console fix Merchant Center disapprovals?
No. Search Console can help identify structured-data problems on your website, but feed and account problems must be corrected in the product source, Merchant Center or store configuration as appropriate.
How long does a correction take to show?
Timing varies by issue and processing cycle. Google's missing-shipping-cost guidance says some changes can take 24–72 hours to appear. There is no guaranteed universal deadline for approval or renewed visibility.
Will correct prices and shipping guarantee Shopping traffic in Nigeria?
No. Nigeria is a beta target country with participation and visibility limitations. Accurate data improves eligibility, but Google does not guarantee listings, impressions, clicks or sales.
Conclusion: Fix the source, not just the warning
Google Merchant Center errors usually reveal a broken connection between store data, the submitted offer, a product landing page or delivery settings. The durable solution is to identify the exact affected variant, inspect its final attributes, and make the source catalogue, feed, markup and checkout agree.
For Nigerian e-commerce businesses, prioritise truthful NGN prices, stock values that reflect real fulfilment, and shipping details appropriate to each supported target market. Review Google's diagnostics after each correction and automate consistency checks as the catalogue grows. That is more sustainable than repeatedly submitting files or relying on automatic fixes to conceal inaccurate product information.
