Manual Feeds for Peptide Catalogues: When to Stop Relying on the App Sync

What is a manual feed, and when should a peptide store use one?

A manual feed is a Merchant Center primary data source that you build and maintain yourself — a scheduled file, a Google Sheet or a Merchant API integration — instead of an ecommerce app sync. A peptide store should consider one when the app keeps pushing product data it cannot control, such as full descriptions containing claims or products it does not want on Google. It is not a way to show Google something different from the website: Merchant Center checks feed data against your landing pages, and the two must match.

Most peptide stores start with the platform app — Shopify’s Google & YouTube channel or a WooCommerce extension — because it is free and fast. The app is not the problem in itself. The problem is that it maps store fields to feed attributes in a fixed way, and peptide catalogues are exactly the kind of catalogue where a few fields decide whether an item is approved.

What are the ways to get products into Merchant Center?

Google’s documentation, read on 23 September 2026, describes these options:

Method	How it updates	Control	Good fit for
Platform app sync	Continuous, driven by the app	Limited to what the app exposes	Small, low-risk catalogues where store copy is already compliant
File (primary)	Manual upload, scheduled fetch, SFTP or Google Cloud Storage; XML, CSV, TSV or TXT	Full, per attribute	Stores with an export they can transform
Google Sheets (primary)	Syncs on a schedule; default every 24 hours	Full, per attribute	Catalogues small enough to maintain by hand
Merchant API (primary)	Programmatic, near real time	Full	Large or fast-changing catalogues with developer support
Supplemental data source	Overrides or adds attributes to an existing primary source	Per attribute, not per product list	Fixing titles, categories or labels without replacing the app
Attribute rules	Transforms data inside Merchant Center	Conditional, per attribute	Systematic clean-up (formerly “feed rules”)

Two constraints from Google matter here. Primary data sources are the only type that can add or remove products; a supplemental source can only add to or update items that already exist. And both supplemental sources and attribute rules require the “Advanced data source management” add-on, enabled under Settings > Add-ons.

Why does the app sync cause problems for peptide catalogues?

Shopify’s help centre states that when the Google & YouTube channel is first set up, all products available to the online store are automatically synced to Merchant Center, and you narrow the selection afterwards. That default is reasonable for a clothing store. For a peptide store it creates predictable friction:

• Everything goes by default. Bundles, calculators, bacteriostatic water, ancillary supplies and discontinued items can all reach Google unless you remove them. Some of those items attract more scrutiny than the core catalogue.
• Descriptions carry the whole page. The description attribute is usually filled from the product body. If that body contains research summaries, dosing tables or “studied for” language, the feed repeats it verbatim.
• Variants multiply issues. Each size or strength becomes a separate item, so a single copy problem shows up as dozens of disapprovals.
• Fields you cannot see. Category, product type and identifier handling are mapped by the app. When they are wrong, you find out from disapprovals rather than from the data.

None of this means an app sync cannot work. It means the app is making editorial decisions on your behalf, and in a category where wording decides eligibility, those are decisions you usually want to make yourself.

When should you switch to a manual feed?

Consider a manual primary feed when two or more of these are true:

1. You repeatedly fix titles or descriptions in the store and the same disapprovals return after the next sync.
2. The app sends products you never intended to advertise, and removing them through the app is unreliable or manual.
3. You need per-item control over google_product_category, product_type, identifier_exists or excluded_destination that the app does not expose.
4. Your store copy is written for customers and your feed needs to be shorter and more neutral — while still describing the same product as the page.
5. You are rebuilding after a suspension and want a small, deliberately curated catalogue in Merchant Center while the full store stays online.

A curated feed is legitimate. Advertising only part of your catalogue is normal. What is not legitimate is a feed that describes products differently from how the website presents them. Google’s common causes of disapproval include “inaccurate product descriptions” and “mismatched categories between your website and product data.”

When should you not switch?

• When the problem is the website. If the notice names Misrepresentation, the healthcare policy or unapproved substances at account level, the fix is on the site. Start with the remediation checklist.
• When you are mid-warning. We could not find a Google statement on whether replacing the data source in an established account triggers a fresh full review. Plan the switch outside a warning period rather than inside it.
• When nobody owns it. A manual feed that is not updated drifts from the site, and drift in price or availability is what triggers preemptive item disapprovals. If you cannot commit to keeping it current, a supplemental source over the app is safer.

What changed with the Content API for Shopping in 2026?

Google’s developer documentation states that the Content API for Shopping reached its sunset date on 18 August 2026. From 1 September 2026, requests from projects without an approved extension began failing intermittently with HTTP 410 Gone, and Google plans full decommissioning in early 2027. The Merchant API is the replacement.

What this means in practice:

• If you use a platform app, Google says the platform partner manages the migration; no action is required from you.
• If you built a custom script or use an older third-party feed tool that calls the Content API directly, it must move to the Merchant API. Intermittent 410 errors look like random sync failures — check for them before blaming Merchant Center.
• If you need more time, Google offers an extension request form linked from its sunset guide.

How do you move from an app sync to a manual feed safely?

1. Export what Merchant Center has now. Download the product list and the affected-items CSV from the Needs attention tab. This is your baseline.
2. Decide the catalogue. List the products you will advertise and the ones you will not. Anything that cannot be presented compliantly should come off the website as well as the feed.
3. Build the primary source. Google Sheets is the simplest start: Merchant Center generates a template; delete the example rows before use and set the sync schedule.
4. Keep product IDs stable. Reusing the IDs the app used keeps products matched to existing Google Ads reporting and campaign subdivisions.
5. Match the pages. Check price, sale price, availability and title against each landing page. Add product structured data so Google’s automatic updates can correct small gaps.
6. Switch over cleanly. Disable the app’s product sync, then activate the manual source with the correct target country and language.
7. Watch Needs attention for a week. Expect items to show as pending while processed. Fix issues in the source, not with one-off edits in the interface.

What should each attribute contain on a peptide product?

Attribute	Google constraint	Peptide-specific guidance
title	Max 150 characters	Compound name, form and quantity. No benefit, outcome or dosing words.
description	Max 5,000 characters	A neutral summary of what the product is, consistent with the page. Not the full page body.
link	Must reach the product page	No age gate or bot wall that stops Google’s crawler; no redirect to a collection.
image_link	No promotional overlays	Clean product image. Avoid imagery of syringes or administration.
price / availability	Must match the landing page	Update on every price or stock change; mismatch triggers preemptive disapproval.
gtin / mpn / brand	Unique identifiers where they exist	If the product genuinely has no GTIN, say so with identifier_exists. Never invent one.
google_product_category / product_type	Should match the website’s categorisation	Choose what the product is, consistently with how the site presents it.
excluded_destination	Keeps items out of named destinations	Use for items you sell but choose not to advertise. It is not a compliance fix.

For how feed design connects to Shopping campaign structure, see peptide Google Shopping. If your items are already disapproved, start with product disapproval vs account suspension to confirm what you are fixing. To check the rest of your setup, try the Google Ads Readiness Score or book a strategy call.

Sources

• Google Merchant Center Help — Create a product data source (primary vs supplemental sources)
• Google Merchant Center Help — Add products to Merchant Center using Google Sheets
• Google Merchant Center Help — Set up your attribute rules
• Google Merchant Center Help — Issues in Merchant Center (common causes of disapproval, PID)
• Google Merchant Center Help — Product data specification
• Google for Developers — Content API for Shopping: deprecation and sunset
• Shopify Help Center — Syncing your products (Google & YouTube channel; read via search excerpt, direct fetch blocked)

Checked 23 September 2026. Merchant Center menus and add-on names change frequently.

Frequently asked