Centra

Depict reads your catalog directly from the Centra GraphQL API. You provide your Centra API base URL and a GraphQL access token; Depict imports the full catalog and then keeps it updated from Centra’s event stream.

​

Limits and behavior

• Every permission in the table below is mandatory. The integration cannot run with a subset.
• The token must have an integration name set. Without one the catalog imports once, but updates never arrive.
• Changes propagate through Centra’s event queue, which Depict polls roughly every 5 seconds. A daily reconciliation run compares Depict’s copy against Centra to catch drift.
• Saving the onboarding wizard starts the initial import. The wizard shows its status and offers controls to start or retry that first import when available. For a later full backfill or re-import, contact Depict.
• Depict does not currently send token-expiry or revocation alerts. Record the expiry date and set a renewal reminder, even if Centra’s expiry emails are enabled.
• Depict reads catalog data only. No customer, order, or checkout data leaves Centra through this integration.

​

Setup steps

​

1. Create the Centra token

Open System → API tokens in Centra and create an Integration API token. See Centra’s access-token guide. Confirm with your Centra CSM/PSM that the event system is enabled for the environment you’re connecting; QA and production must be enabled separately.

• Fill Description, Organization name and Email. Use contact details for the organisation responsible for maintaining the integration; Centra requires the organisation name and email.
• Set Integration name to a new name used only by Depict, for example Depict. Create a name rather than selecting one another integration already uses. Tokens with the same name share an event queue, so another consumer can acknowledge updates before Depict receives them.
• Check Expires at before saving. Centra’s access-token guide describes a 30-day default; check the actual date in your form and choose a date your team can renew before. Record it and set a reminder.
• Grant every permission in the checklist below, then save. Copy the generated GraphQL access token: it is the credential used for Centra’s bearer-token authorization, rather than a token identifier or another code.

​

2. Connect through the Depict wizard

Sign in at app.depict.ai and select your merchant, marked Onboarding. If your merchant or account is missing, ask your Depict contact to grant access. On Welcome to Depict, click Get Started and choose Centra.

1. On Connect Centra to Depict, paste your Centra GraphQL endpoint URL (including /graphql) into API URL and the access token into API Key. Paste only the token value, without Bearer. Click Verify; continue when the credentials are valid.
2. On Review markets you want to import, select one Centra store and the markets to import.
3. On Map attributes, choose the attribute type and element key for Color, Gender and Age, and any optional attributes you need. Select one attribute for all products assigns the chosen value to every product; use it when that value applies to your whole catalog.
4. On Complete Centra data integration, click Continue to save the configuration and start the initial import.
5. On Set up site, check First product import. It shows import progress and the product count after success. If offered, use Start ingestion or Retry; contact Depict if the import remains failed or unknown. You can click Complete while the import runs; it returns you to the Dashboard.

Continue with Getting started to install Depict on your storefront. Connecting the catalog does not activate storefront search; your Depict contact confirms search setup separately.

​

Required permissions

Select these individual read permissions and the one event update permission. Leave ALL unselected: it grants access beyond what Depict needs. The object and field names below identify the choices; the API scope is the exact permission Depict checks. Choose each object’s read permission, plus its listed attributes or stock permissions; these are separate choices. Event:write is required because Depict acknowledges consumed events back to Centra.

​

How sync works

• Initial import. Saving the wizard’s configuration starts the full catalog download. Follow its progress under First product import on Set up site; completing onboarding does not mean the import has finished.
• Ongoing updates. Depict polls Centra’s event queue roughly every 5 seconds, so a price, stock, or content change typically reaches Depict within seconds and is live in search within minutes. Incremental updates cover these Centra object types:

• Reconciliation. Once a day Depict compares its copy of the catalog against Centra to detect drift. If you suspect your catalog is out of date, contact Depict, who can run the comparison on demand and re-trigger a full import.

​

What Depict reads

The import fetches your markets (with their warehouses), pricelists, mapped attributes, categories, languages, and the active products’ displays with media, prices, and per-warehouse stock. Attributes come through Centra’s mapped attributes; translations come per language. Centra’s product hierarchy maps onto Depict’s three-level model like this: Note the offset: a “variant” in Depict is your Centra size, and your Centra variant is Depict’s product group.

​

Markets and languages

Markets, pricelists, and languages are imported in full, and each language gets its own search index.

​

If the token stops working

A revoked or expired token stops catalog updates. Depict does not currently send its own expiry or revocation alert. To keep updates running:

• Track the date shown in Expires at and renew the token before it. Centra documents expiry-email notifications, but keep your own reminder rather than relying on their availability.
• If an existing connection needs a replacement token, contact Depict to update it. Depict can audit its permissions and integration name against this checklist.

​

Data scope

The permission list above contains no customer, order, or checkout scope: Depict does not read customer or order data from Centra. Behavioural data (purchases, clicks, search queries) is collected by Depict’s on-site tracking on your storefront — a separate processing activity, not data read from Centra.