DocsDocsIntegrations

Google Retailer

Connect an Enad market and warehouse to a Google retail catalog.

This guide preserves published Enad setup and compatibility guidance. Enad app is authoritative for current controls. Use generated API/OpenAPI reference and the Event catalog for exact fields, payloads, authentication, and delivery behavior; examples and operational limits below are compatibility guidance until attached to those contracts.

The Google Retailer integration connects Enad catalog data to a Google Cloud retail catalog and branch.

Requirements

The Enad market and online warehouse must exist before configuration. Required Google Cloud values:

  • Project.
  • Location.
  • Catalog.
  • Branch.
  • Service-account security key as a JSON object.

Configuration

Configuration follows the common integration setup. The selected Enad market and online warehouse define the scope of the connection.

The security-key JSON is a secret and must not appear in support messages, logs, or documentation.

Validation and sync

Connection checks are available under Status → Integration validation. The refresh control runs the checks again. The Sync tab supports resending all or selected catalog records.

Google Retailer

# Google Retailer > This guide preserves published Enad setup and compatibility guidance. Enad app is authoritative for current controls. Use generated API/OpenAPI reference and the Event catalog for exact fields, payloads, authentication, and delivery behavior; examples and operational limits below are compatibility guidance until attached to those contracts. The Google Retailer integration connects Enad catalog data to a Google Cloud retail catalog and branch. ## Requirements The Enad market and online warehouse must exist before configuration. Required Google Cloud values: - Project. - Location. - Catalog. - Branch. - Service-account security key as a JSON object. ## Configuration Configuration follows the [common integration setup](/integrations#integration-setup). The selected Enad market and online warehouse define the scope of the connection. The security-key JSON is a secret and must not appear in support messages, logs, or documentation. ## Validation and sync Connection checks are available under Status → Integration validation. The refresh control runs the checks again. The Sync tab supports resending all or selected catalog records. ## Related - [Store groups and markets](/start/concepts/store-groups-and-markets). - [Stocks](/events).