DocsDocsIntegrations

Brink Commerce

Connect Enad catalog data to Brink Commerce.

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.

Brink Commerce connects Enad to one or more Brink store groups. It is useful when Brink is the commerce destination for catalog data managed in Enad.

Requirements

Required connection details:

  • Brink OAuth 2 URL and API base URL.
  • Client ID and client secret.
  • API key.
  • Enad store groups included in the integration.

Configuration

Configuration follows the common integration setup and includes the Brink connection details and store groups selected for sync.

The following choices change how Enad prepares data:

  • Display name setup controls which product or variant name is used.
  • Include product attributes includes Enad product attributes.
  • Use IDs uses identifiers where supported instead of display values.
  • Use parent display names applies parent-level display names.
  • Group tags changes how tags are grouped.
  • Rate limit limits requests sent to Brink.

An optional Merchant Portal URL adds a quick button to the product page. The button opens the matching product in Brink.

Enad appends products/ and the product SKU to the configured Brink merchant portal base URL:

https://merchant-portal.EXAMPLE.brinkcommerce.io/products/SKU-123

For example, the integration setting contains https://merchant-portal.EXAMPLE.brinkcommerce.io/. The product SKU is added automatically.

Sync data

The Sync tab supports all or selected records for:

  • Products, variants, categories, collections, and brands.
  • Images, videos, attributes, and tags.
  • Markets, store groups, and tax groups.

Connection checks are available under Status → Integration validation. The refresh control runs the checks again.

Brink Commerce

# Brink Commerce > 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. Brink Commerce connects Enad to one or more Brink store groups. It is useful when Brink is the commerce destination for catalog data managed in Enad. ## Requirements Required connection details: - Brink OAuth 2 URL and API base URL. - Client ID and client secret. - API key. - Enad store groups included in the integration. ## Configuration Configuration follows the [common integration setup](/integrations#integration-setup) and includes the Brink connection details and store groups selected for sync. The following choices change how Enad prepares data: - Display name setup controls which product or variant name is used. - Include product attributes includes Enad product attributes. - Use IDs uses identifiers where supported instead of display values. - Use parent display names applies parent-level display names. - Group tags changes how tags are grouped. - Rate limit limits requests sent to Brink. An optional Merchant Portal URL adds a quick button to the product page. The button opens the matching product in Brink. Enad appends `products/` and the product SKU to the configured Brink merchant portal base URL: ```text https://merchant-portal.EXAMPLE.brinkcommerce.io/products/SKU-123 ``` For example, the integration setting contains `https://merchant-portal.EXAMPLE.brinkcommerce.io/`. The product SKU is added automatically. ## Sync data The Sync tab supports all or selected records for: - Products, variants, categories, collections, and brands. - Images, videos, attributes, and tags. - Markets, store groups, and tax groups. Connection checks are available under Status → Integration validation. The refresh control runs the checks again. ## Related - [Store groups and markets](/start/concepts/store-groups-and-markets). - [Attributes](/start/concepts/attributes).