Build-to-order Odoo module generating Google-compliant Shopping feeds — multi-country, multi-currency, auto-scheduled FTP/SFTP delivery. One-time license from $249.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Build-to-order Odoo module generating Google-compliant Shopping feeds — multi-country, multi-currency, auto-scheduled FTP/SFTP delivery.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Google Merchant Center / Shopping Feed Manager Pro is a build-to-order Odoo module that turns your Odoo product catalog into fully Google-compliant Shopping feeds — without CSV exports, spreadsheet cleanup, or brittle third-party middleware. ECOSIRE designs, builds, installs, and supports this module for your specific catalog and campaign structure; it is NOT an off-the-shelf apps.odoo.com instant download. After purchase we scope your requirements and deliver a production-ready module in roughly 2–4 weeks.
Google-compliant feed generation in both XML (RSS 2.0 with the g: namespace) and delimited TXT formats, rendered via QWeb/templating directly from product.template and product.product records
Manual on-demand generation from a button plus fully scheduled regeneration through ir.cron automated actions (hourly, daily, or custom cadence)
Multiple independent feed instances — one feed per product category, country, language, or e-commerce sales channel — managed from a single product.feed model
Country-specific instances that each carry their own target market, language, pricelist_id and currency, deriving correct per-market prices from existing Odoo pricelists and tax rules
FTP, SFTP and HTTPS auto-upload of generated feeds to Google Merchant Center with credentials stored in Odoo config parameters, not hard-coded
Configurable attribute mapping layer (product.feed.mapping) letting you bind any Odoo field — standard or custom — to each Google attribute: id, title, description, link, image_link, price, availability, condition
At its core the module adds a product.feed model (plus product.feed.mapping and product.feed.run log models) that reads directly from your product.template / product.product records and renders a Google-spec XML (RSS 2.0 with the g: namespace) or delimited TXT feed. Every required Shopping attribute — id, title, description, link, image_link, price, availability, condition, brand, gtin, mpn — is mapped through a configurable attribute-mapping layer so you decide exactly which Odoo field (standard or custom) feeds each Google attribute. Computed fields (@api.depends) keep derived values such as sale price, availability from qty_available, and localized titles always current.
Because Google Shopping is inherently multi-market, the module supports multiple feed instances: one feed per category, country, language, or e-commerce sales channel. Each country-specific instance carries its own target language, pricelist_id, and currency, so a EUR feed for Germany and a GBP feed for the UK derive correct, per-market prices from your existing Odoo pricelists and taxes — no duplicate products required. Feeds regenerate on demand from a button, or automatically on a schedule via ir.cron, and are pushed straight to Merchant Center over FTP, SFTP, or HTTPS with credentials stored securely in Odoo settings. A per-run log records item counts, warnings (missing GTIN, disapproved-risk fields), and transport results so you always know the last successful upload.
Access is locked down with ir.model.access.csv plus record rules (feeds scoped per company / marketing team), views are delivered as clean XML/OWL for Odoo 17, 18 and 19 (Community or Enterprise), and an optional QWeb report gives you a printable feed-health summary. Where you need programmatic control — CI validation, external orchestration — the feed generation and status endpoints are reachable via Odoo's XML-RPC / JSON-RPC API. The result is a single source of truth in Odoo driving your Google Shopping and Performance Max campaigns, with clean, compliant data that reduces product disapprovals and keeps ad spend working.
Runs Google Shopping and Performance Max campaigns and needs clean, always-current product data flowing from Odoo to Merchant Center without manual CSV wrangling. Wants custom labels and per-market feeds to segment bids and cut product disapprovals.
Owns the Odoo website catalog across multiple countries and currencies. Needs each market to advertise the right price, language, and availability, and wants feed generation to just run on a schedule instead of being a weekly chore.
Responsible for the Odoo instance and its integrations. Wants a properly built module — secured with access rules, scheduled via ir.cron, upgrade-safe across 17/18/19, and callable over XML-RPC — rather than fragile spreadsheets or an unmaintained third-party app.
Buy the license on ecosire.com and download the Google Merchant Center / Shopping Feed Manager Pro module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for Google Merchant Center / Shopping Feed Manager Pro, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Reads live data straight from Odoo products (no CSV export step) | Native product.template/product.product read with @api.depends computes | Possible but you build and maintain the ORM logic yourself | Usually yes, but mapping is fixed to the app's assumptions | |
| Multi-country / multi-currency feeds from existing pricelists | One feed instance per market with its own pricelist and currency | Achievable but significant bespoke effort | ||
| Scheduled auto-upload to Merchant Center via FTP/SFTP/HTTPS | Built with ir.cron plus secure transport to your MC account | You must build cron jobs and transport handling | ||
| Fully configurable Odoo-field to Google-attribute mapping | Dedicated mapping layer covering standard and custom fields | Hard-coded unless you build a mapping UI | ||
| Google-spec XML (RSS 2.0 g: namespace) and TXT output | Both formats, validated against current Shopping spec | Depends entirely on your implementation | ||
| Security via ir.model.access.csv and record rules | Role- and company-scoped access to feeds and credentials | Only if you author the ACLs and rules yourself | ||
| Built, installed and supported for your catalog by the vendor | Scoped build, deployment, training, and support window | Your internal team owns all delivery and upkeep | ||
| Guaranteed compatibility across Odoo 17, 18 and 19 | Pinned and version-tested for your series, upgrade path available | You port it forward on each upgrade |
This is a build-to-order module, not an instant download. After purchase we run a short scoping call to confirm your markets, currencies, product fields, and Merchant Center setup, then design, build, and install the module. Typical delivery is 2–4 weeks depending on catalog complexity and the number of country feeds. You get staging access to review before we push the first live feed to production.
Every build includes a post-go-live support window (typically 30 days) with a named ECOSIRE contact for bug fixes and questions. Because we deliver the full source to your Git repository, you own the code. We also offer an optional ongoing maintenance plan that covers Odoo version upgrades (17→18→19), Google Shopping specification changes, and new feature requests as your campaigns grow.
Yes. We build against your specific series — Odoo 17, 18, or 19 — and the module works on both Community and Enterprise editions. The __manifest__.py and views are pinned to your version so upgrades stay predictable, and we can port the module forward under a maintenance plan when you upgrade Odoo.
You create one feed instance per market. Each instance carries its own target language, Odoo pricelist, and currency, so a German EUR feed and a UK GBP feed derive correct per-market prices from your existing pricelists and tax configuration — no duplicated products. The feed reflects Odoo website visibility and availability from stock on hand for each channel.
Generated feeds are automatically uploaded to Merchant Center over FTP, SFTP, or HTTPS, on a schedule you set via Odoo's ir.cron (for example nightly), or on demand from a button. Credentials are stored securely in Odoo configuration parameters. Each run is logged with item counts, validation warnings, and the upload result so you can confirm the latest feed landed.
Yes. A dedicated attribute-mapping layer lets you bind any Odoo field — standard or a custom field — to each Google Shopping attribute (title, description, GTIN, MPN, brand, condition, custom_label_0–4, and more). You can also filter which products enter each feed by category, brand, stock status, or a saved domain, so only eligible, compliant SKUs are exported.
Yes. The generation and status methods are reachable through Odoo's XML-RPC / JSON-RPC API, so external tools or CI pipelines can trigger regeneration, validate feed output, or check the last-run status. This is useful if you orchestrate campaigns or feed QA from outside Odoo.
Build-to-order Odoo module generating Google-compliant Shopping feeds — multi-country, multi-currency, auto-scheduled FTP/SFTP delivery.