Genius Merchant Sync System Requirements

• A licensed store on a supported nopCommerce version and administrator access to install and configure plugins.
• SQL Server as the nopCommerce database. The application identity must have the normal schema-migration permissions required for plugin installation.
• A stable public HTTPS canonical storefront URL. Google OAuth redirect URIs must exactly match the callback shown by the plugin.
• Outbound HTTPS access to Google OAuth, Google Merchant API, and the documented Genius licensing endpoints. API keys and service-account keys are not used for third-party customer authorization.
• A Google Merchant Center account, the required account permissions, a Google Cloud project with Merchant API enabled, and an OAuth Web Application client when customer-owned OAuth is selected.
• Accurate product identifiers, public product and image URLs, supported language/currency/target-country data, and any required Google Merchant policies.
• Reliable UTC system time and an enabled nopCommerce scheduler. Multi-node stores additionally require one shared nopCommerce database and a persistent protected ASP.NET Core Data Protection key ring readable by every application node.

Google account eligibility, Merchant policies, product approvals, quotas, tax configuration, DNS, TLS, server administration and source-catalog data quality remain the store operator's responsibility.