Google Merchant API vs Direct Feed Submission in Magento 2

1. Extension generates XML feed file
2. Cron job uploads file to Google SFTP server
3. Google processes the file (usually within hours)
4. Products appear in Merchant Center

Simple Setup

• Just SFTP credentials from Merchant Center
• No OAuth configuration
• No API quotas to worry about

Reliable

• Mature, well-tested approach
• Works with any catalog size
• Easy to debug (you can inspect the XML file)

Automated

• Cron handles everything
• Set it and forget it
• Multiple feed types supported

No API Deprecation Concerns

• Feed format rarely changes
• Not affected by API version updates

Location: Magmodules → Google Shopping - Feed → SFTP Upload

1. Log into Google Merchant Center
2. Go to Settings → SFTP
3. Generate SFTP credentials
4. Copy username and password to extension config

1. Extension authenticates with Google API
2. Products sent individually or in batches
3. Google processes immediately
4. Near real-time updates possible

Faster Updates

• Changes reflect within minutes
• No waiting for file processing
• Better for high-frequency changes

Granular Control

• Update individual products
• Delete specific items
• Immediate feedback on errors

Advanced Features

• Inventory updates
• Price updates
• Supplemental feeds

Google launched the Merchant API as the successor to the Content API for Shopping.

• You need updates faster than hourly
• You have complex inventory management
• You're building custom integrations
• You need programmatic control over products

1. Open Google Merchant Center
2. Navigate to Settings (gear icon)
3. Select SFTP from the menu
4. Click Generate to create credentials
5. Save the username and password

1. Go to Magmodules → Google Shopping - Feed → SFTP Upload
2. Enable SFTP Upload: Yes
3. Enter SFTP credentials
4. Set upload schedule via cron

1. Generate feed via CLI: bin/magento googleshopping:feed:create
2. Check Merchant Center for new products
3. Verify no upload errors in logs

No. The SFTP feed method continues to work and is not deprecated. Only the Content API for Shopping is being deprecated (August 2026).

Keep using it. There's no reason to switch unless you need faster updates.

Yes, for individual product updates. But for full catalog syncs, the difference is minimal because feed processing is quite fast.

Technically yes, but it's not recommended. Pick one method to avoid confusion and potential conflicts.

Both methods support supplemental feeds. SFTP is often easier for supplemental data.