Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.getclaro.ai/llms.txt

Use this file to discover all available pages before exploring further.

Distribute is the last mile: getting catalogue data out of Claro and into the systems that use it. Two surfaces:
  • Unified Catalog — a denormalized, query-ready view of the catalogue.
  • Sync & Export — connectors to Shopify, Amazon, BigQuery, Google Sheets, Webhooks, and S3.

​
Unified Catalog

A read-optimized view that flattens references and joins multiple catalogues into a single shape ready for consumers.

​
What it produces

  • Denormalized records — Product joined to Supplier, Category, Variants, etc., with chosen fields inlined.
  • A read API — paginated, filterable, with the same auth as the rest of your workspace.
  • Exports — CSV, JSONL, Parquet — generated on schedule or on demand.
  • Versioned snapshots — each export is tagged so downstream consumers can pin to a specific snapshot.

​
Configuration

  • Source catalogues — which catalogues feed the unified view.
  • Field selection and renaming — pick the attributes to expose, alias them to consumer-friendly names.
  • Filter — only rows that satisfy a predicate (e.g. published == true).
  • Refresh — live (always current) or scheduled.
  • Access control — per-consumer API keys with field-level permissions.

​
When to use

  • A search index or recommendation system that needs a flat, denormalized feed.
  • Analytics consumers who need a stable, versioned snapshot.
  • Internal tools that want one endpoint instead of joining multiple catalogues themselves.

​
Sync & Export

Outbound connectors that push records (and updates) into external systems.

​
Built-in connectors

ConnectorModes
ShopifyCreate/update products, variants, metafields, images.
AmazonPush listings via SP-API; manage feed types and processing reports.
BigQueryAppend or replace tables; partition and clustering supported.
Google SheetsBi-directional sync with named ranges.
WebhooksPOST per change, batch, or on schedule; signed payloads.
S3Periodic dumps, with optional encryption.
Supabase / PostgresInsert/update via SQL or REST.
SlackNotification deliveries (not record sync).
Each connector has its own:
  • Mapping — catalogue attributes to platform fields, with type coercion.
  • Schedule — real-time, hourly, daily.
  • Conflict policy — how to resolve if the downstream system has a value that conflicts.
  • Filter — a subset predicate so you can sync only published, only specific categories, etc.
  • Retry and backoff — configurable per connector.

​
Push & Sync (Beta)

The Push & Sync operation on a catalogue runs an immediate push for the records in scope. It honors the connector’s mapping and conflict policy, and produces a run with success/failure counts and per-record errors. Use Push & Sync for:
  • One-off backfills or migrations.
  • Re-syncing after a large bulk update.
  • Triggered pushes from a chained pipeline.

​
Custom connectors

For systems not listed, two paths:
  • Webhooks — receive every change (or a batch) at your endpoint with a signed payload.
  • Custom connector (Dedicated plans) — Claro’s success team builds a connector against your system’s API.

​
Inbound vs. outbound

Distribute handles outbound only. Inbound connectors (file upload, scheduled scrapes, HTTPS pulls, Supabase/BigQuery/Postgres reads, Supplier Portal, email-as-source) live on each catalogue’s Data Source tab — see Data Import & Ingestion.