Using XML Feed and API Together in Magento 2 (Google Shopping)

The Offer ID is the unique identifier that links your Magento products to Google Merchant Center listings. It's the key that allows both Feed and API to update the same product.

Format in Magento: Typically your product SKU or entity ID Example: ABC-12345 or 24-MB01

When you send product data to Google (via Feed or API), the Offer ID tells Google: "This is product ABC-12345, update its data."

Example: Product with SKU "ABC-12345"

1. XML Feed sends product data with offerId: ABC-12345
2. API Module sends product data with offerId: ABC-12345
3. Google sees the same Offer ID and updates the same product

Both methods update the same product in Google because they use the same Offer ID.

Important: The Offer ID configured in the Feed module must match the Offer ID used by the API module. By default, both use the same source (configured in Feed module settings), so this happens automatically.

• Type: Scheduled fetch or SFTP upload
• Contains: Complete product catalog
• Updates: On your configured schedule

• Type: Merchant API
• Contains: Individual product updates
• Updates: Real-time when products change

Google can combine data from multiple sources for the same product:

1. Primary source provides the base product data
2. Supplemental sources can add or override specific fields

When using Feed + API together, you have two options:

Option A: Separate Data Sources (Recommended)

• Feed uploads to File data source
• API updates to Merchant API data source
• Google merges both, with most recent data taking precedence

Option B: API as Primary

• API module handles all product data
• Feed serves as backup/verification only

1. Keep your existing Feed setup (SFTP or scheduled fetch)

   • Runs daily or hourly
   • Ensures complete catalog is always in Google

2. Add the API module for real-time updates

   • Pushes changes immediately when products are saved
   • Handles price and stock updates between feed runs

1. Feed Module

   • Attribute mapping configured
   • Offer ID field set (usually SKU)
   • SFTP or scheduled fetch active

2. API Module

   • Same store view as Feed
   • Merchant API data source created
   • Auto Sync enabled

3. Verify Offer ID Match

   • The "id" field in Feed module settings
   • Should match what API module sends as offerId
   • Check a synced product in both to confirm

The Offer ID is configured in the Feed module under attribute mapping:

Stores > Configuration > Magmodules > Google Shopping - Feed > Attribute Mapping

Look for the id field mapping. Common options:

• SKU (recommended) - Unique, human-readable
• Entity ID - Magento's internal ID (numeric)
• Custom attribute - If you have a dedicated identifier

1. Use SKU if your SKUs are unique and stable
2. Never change the Offer ID of existing products - Google treats it as a new product
3. Keep it consistent across all stores/feeds for the same product
4. Alphanumeric characters only - avoid special characters

If Feed sends offerId: SKU123 and API sends offerId: 456:

• Google sees these as two different products
• You'll have duplicates in Merchant Center
• Changes via API won't affect the Feed product

When both Feed and API send data for the same product, Google uses the most recent data for each field.

Example scenario:

1. 08:00 - Feed runs, sends price: €50
2. 10:00 - You change price to €45 in Magento
3. 10:01 - API sends price: €45
4. Google now shows: €45 (most recent)

If Feed and API show different prices:

1. Check timestamp of last Feed run
2. Check API sync status for the product
3. The most recent update should be in Google

If a product is in Feed but not syncing via API:

1. Check if product passes Feed module filters
2. Check API module product grid for errors
3. Verify product was initialized in API module

If you see duplicates in Merchant Center:

1. Check Offer ID in Feed export
2. Check Offer ID in API sync log
3. Ensure both use the same identifier

• Check generated XML for correct Offer IDs
• Monitor SFTP upload logs
• Review Merchant Center processing reports

• Check Products grid for sync status
• Verify Offer ID matches Feed
• Monitor error rates

• Products > Diagnostics for issues
• Check "Data sources" for last update times
• Verify product count matches expectations

Yes, if using both modules. Each module needs its own data source type in Merchant Center.

No. Google Shopping charges are based on clicks, not on how many times you upload product data.

Technically yes, but not recommended. The Feed serves as a safety net ensuring all products remain in Google even if API sync has issues.

The API module supports inventory-only sync. Full product data comes from Feed, real-time price/stock from API.

1. Note a product's SKU in Magento
2. Find it in Feed XML export - check the <g:id> value
3. Find it in API sync log - check the offerId
4. Find it in Merchant Center - check the Offer ID
5. All three should match