ERPNext Google Shopping & Merchant Center Connector

ECOSIRE builds a proper Frappe app — its own module, DocTypes, and permissions — that treats Google Merchant Center as a first-class integration inside ERPNext. A Google Merchant Settings single DocType holds your Merchant Center account ID, OAuth service-account credentials, target country/language/currency, and default attribute mappings. A Google Shopping Feed Item DocType (or child mapping on Website Item/Item) captures per-product overrides — GTIN, MPN, brand, google_product_category, custom labels, and sale-price windows. We map ERPNext Item, Item Price, Item Group, UOM, and stock (get_stock_qty/Bin) onto the Content API for Shopping product schema, resolving the availability and price fields Google actually validates against.

The sync runs on two paths. hooks.py doc events (on_update on Item/Item Price, and stock ledger updates) enqueue a background job so a price or availability change propagates to Merchant Center within minutes instead of waiting for the daily crawl — this is what clears "price mismatch" disapprovals. A scheduler_events hourly/daily job performs a full reconciliation and re-submits the batch, so nothing silently drifts. All Google calls go through the Content API with proper batching and exponential backoff; results (accepted, warning, disapproved with reason) are written back to each product record and surfaced in a feed-status report and dashboard, so your team sees exactly which SKUs are live and why others were rejected. Whitelisted methods expose manual "push now" and "validate feed" actions from the ERPNext UI and the Frappe REST API, gated by a dedicated role profile.

Because Google Shopping is multi-market, the app supports multiple target feeds — country/currency/language combinations — each with its own price list and shipping/tax mapping, plus a promotions/sale-price feed that reads a sale price and effective date range from ERPNext pricing rules. GTIN/MPN and brand are validated before submission so invalid identifiers are caught in ERPNext rather than bounced back from Merchant Center days later.

This is build-to-order: ECOSIRE scopes it against your exact ERPNext version (v15 or v16), your catalog structure, your price lists, and your target Google markets, then builds, installs, and supports it. There is no instant download — after a short scoping call we confirm scope in writing, and typical delivery is 2–4 weeks from confirmed scope. You receive the installable source, documentation, a training session, and a post-go-live support window.