Volusion Google Merchant Center Suspended: What to Fix
Volusion has been around since 1999, which means a lot of merchants on this platform have older store configurations that were never updated for modern Google Shopping requirements. If your Volusion store just got suspended, you are likely dealing with a combination of feed attribute gaps, policy page deficiencies, and possibly misrepresentation triggered by price or availability inconsistencies. Here is what to fix and in what order.
Volusion's Feed Export: What Google Requires vs. What You Get
Volusion's native Google Shopping feed export covers the basics but often misses required fields that Google now treats as mandatory for all merchants. In 2024 and 2025, Google tightened its requirements around GTINs, condition disclosure, and availability accuracy. Volusion's older feed templates were designed before some of these requirements existed.
The result: merchants who set up their Google Shopping integration years ago and never touched it may now have a feed that is technically submitting but violating current policy on every product row. Google's crawler has become more aggressive about checking feed data against live landing pages, and the gap between what a Volusion feed sends and what the live page shows is the number one suspension trigger for this platform.
1. Missing or Incorrect Product Attributes
Google now requires, at minimum: id, title, description, link, image_link, price, availability, condition, and either gtin, mpn, or brand with identifier_exists=false for custom products. Volusion's default export frequently omits condition (new vs. used vs. refurbished), sends incorrect availability values (Volusion uses "Y/N" internally but GMC needs "in stock" or "out of stock"), and skips GTIN for products where it is available but not entered in the product database.
Fix: Audit your Volusion product database and add GTINs for all branded products. Set the condition field explicitly for every product. Check that your availability mapping converts Volusion's internal stock flags to GMC-accepted values. If Volusion's export cannot handle this mapping, use DataFeedWatch or Channable with a direct API connection to Volusion.
2. Price Discrepancies Between Feed and Live Pages
Volusion's feed caches product data and does not always refresh in real time. If you run sales, use tiered pricing, or have automatic discounts that apply at cart level, the price in your feed may not match what a customer sees on the product page or at checkout. Google's crawler checks prices at the landing page level, and any mismatch (even a few cents due to currency rounding) triggers a misrepresentation flag.
Fix: Set your GMC feed to refresh every 24 hours minimum. If you run frequent promotions, set up GMC Promotions separately rather than changing product prices in your feed. For tiered or customer-group pricing in Volusion, make sure your feed reflects the default (logged-out visitor) price, since that is what Google compares against.
3. Incomplete Policy Pages
Many Volusion stores from the V1 era have generic policy pages that were auto-generated during store setup. These pages often lack specific details that Google now requires: an exact return window (number of days), whether the customer or merchant pays return shipping, and what happens to non-returnable items. Shipping policy pages often just say "we ship via UPS" without mentioning delivery timeframes or cost calculation methods.
Fix: Edit your Returns page to include the full return window (e.g., "30 days from delivery date"), your refund method (original payment method, store credit, or exchange), return shipping responsibility, and any product categories excluded from returns. Edit your Shipping page to include specific carriers, estimated delivery windows by region, and how shipping costs are calculated. Link both pages in your Volusion footer.
4. Checkout Flow and HTTPS Issues
Older Volusion stores sometimes use the secure.volusion.com subdomain for checkout, or have HTTPS certificates that are not applied consistently across all pages. Google's automated verification of the checkout flow may flag a transition from your main domain to a different subdomain as a trust issue, especially if the certificate does not cover both domains properly.
Fix: Verify that your entire site, including product pages, cart, and checkout, runs on HTTPS with your own domain. If your checkout runs on a Volusion subdomain, configure SSL to cover both domains or contact Volusion support to migrate checkout to your primary domain. Run a full SSL check using SSL Labs to confirm there are no certificate warnings anywhere in the checkout flow.
5. Business Identity and Trust Signals
Volusion stores, particularly those using template designs without customization, often lack the trust signals Google's reviewer looks for when processing a reinstatement appeal: a visible business address, a real phone number, an About Us page with business history, and a business name that matches the GMC account registration. Template stores sometimes display the Volusion default "Your Company Name" placeholder in some locations, which immediately signals an unverified or inattentive merchant.
Fix: Search your entire Volusion store for any placeholder text and replace it with real business information. Add your physical business address and phone number to the Contact page and footer. Create or update your About Us page. Cross-check that the business name in your GMC account settings matches your website and legal business registration exactly.
Run a Free GMC Audit in 60 Seconds
The GMCSuspension tool scans your store against 52+ Google Merchant Center policy requirements and shows you exactly what to fix before you appeal.
Run Free AuditAppealing Your Volusion GMC Suspension
The appeal form in GMC asks you to describe what you changed. Be specific. For each of the issues above that applied to your store, write one or two sentences explaining what was wrong and what you did to fix it. Include dates. If you made feed changes, mention the specific attributes you corrected and when you pushed the updated feed. If you updated policy pages, link to them in your appeal text.
Vague appeals ("we reviewed our store and fixed any issues") almost always result in denial. Specific appeals ("we corrected our availability attribute mapping to use 'in stock' and 'out of stock' values, regenerated our feed on June 20, and confirmed via GMC diagnostics that all 847 products now show green status") get reinstated much faster.
Use our GMC appeal process guide for the full structure. If your issue was specifically misrepresentation, our misrepresentation fix guide has additional documentation requirements. For a full pre-appeal checklist, see our suspension checklist. If your appeal was already denied, check the reinstatement denied guide for next steps.
FAQ: Volusion and Google Merchant Center Suspension
Why did my Volusion store get suspended on Google Merchant Center?
Volusion suspensions typically result from outdated feed configurations, missing required product attributes like GTIN and condition, incomplete policy pages, or misrepresentation caused by price discrepancies between the feed and live product pages.
Does Volusion V2 fix the Google Shopping feed problems from V1?
Volusion V2 has an improved feed export, but it still requires manual configuration to include all required GMC attributes. Merchants who migrated from V1 to V2 sometimes carry over feed errors. Regenerate your feed from scratch in V2 and validate it in GMC's diagnostics before connecting.
How do I set up a compliant product feed in Volusion?
In Volusion, go to Inventory, then Import/Export, and use the Google Shopping feed export. Map all required fields: id, title, description, link, image_link, price, availability, condition, brand, and gtin or mpn. Use a feed management tool like DataFeedWatch if Volusion's native export does not cover all required fields.
Volusion uses a subdomain for checkout. Does that cause GMC issues?
It can. If your Volusion checkout moves to a secure.volusion.com subdomain and your SSL certificate or checkout redirect is not configured properly, Google may flag the checkout experience as inconsistent. Verify your checkout URL uses your custom domain and HTTPS throughout.
How long does Volusion GMC reinstatement take after appeal?
Standard policy violation appeals typically resolve within 3 to 7 business days. Misrepresentation appeals can take up to 3 weeks. If your appeal is denied, you must wait the required cool-down period before resubmitting.
Run a Free GMC Audit in 60 Seconds
The GMCSuspension tool scans your store against 52+ Google Merchant Center policy requirements and shows you exactly what to fix before you appeal.
Run Free Audit