Xentral

Documentation Index

Fetch the complete documentation index at: https://docs.frontic.com/llms.txt

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

​

What you get

​

Connection settings

The settings panel shows a Connection Status indicator. When the connection is broken it surfaces the reason returned by the Xentral API — so you can tell whether the token is invalid, expired, or the Xentral instance is unreachable. Update credentials here and re-test after the issue is fixed.

​

Channels

A Xentral channel in Frontic has a selection of currencies available. Translations are populated from the translations Xentral exposes per locale.

​

Data Feeds

The Xentral connector exposes two feed types: The standard Settings → Updates → Schema setup wizard applies — see Data Feeds in the overview. For Xentral specifically:

• Updates step — Polling is supported. On the first run (or after a manual refresh), all records are fetched regardless of timestamp.
• Manual refresh — every Xentral feed exposes a Refresh action that re-runs the feed against the source in full. Use it when something changed on the Xentral side that didn’t reach Frontic during a scheduled poll, or to recover after a polling gap.

​

What the data looks like

​

Variants

Xentral distinguishes between matrix products (configurable products with variants) and simple products (no variant axis). The connector handles both:

• Matrix products — the matrix product record becomes the parent, each variant becomes a separate record with parentId pointing back to the matrix product.
• Simple products — emitted as a self-parented record using the same source ID on both sides. See Product Models for how this shape composes at the API layer.

​

Currency-resolved prices

For products, the connector pre-filters sales prices to the currencies declared on the channel. Only prices valid on the current date that apply to all customers (no customer-specific or customer-group-specific pricing) are included. Map them into the Price composite in the Value Composer — no per-region price-picking logic needed.

​

Translations

Product texts are fetched per locale. The connector resolves the localized text values (name, description, and other translatable fields from Xentral’s API) for every locale on the channel.

​

Attributes split into options and properties

The connector’s attribute extractor separates variant-defining options from descriptive properties and stamps them onto the feed record under the reserved $-prefix namespace:

• $options — the selectedOptions from variant records, normalized into a flat list per record. Drives variant selectors (size, colour, etc.).
• $properties — product property values with their property name, value, and unit. Descriptive attributes that don’t drive variant selection.

Map either list into your storage with the Option composite in the Value Composer, rather than deriving them from Xentral’s raw structures.

​

Additional data pre-loaded

Each product record also carries:

• $medias — product media items (images, documents).
• $stocks — stock levels per warehouse location.
• $crossSellings — cross-selling product references.

​

Category relations

The connector adds a flat list of category IDs onto each product record under $rel.categoryIds, derived from the product’s categories association. Category-link blocks and syncs that need only the IDs can map this directly in the Value Composer.

​

Auto-delete reconciliation

When a feed runs in full (manual refresh), the connector diffs Xentral’s current record set against what Frontic holds and emits deletes for products or categories that have disappeared on the Xentral side. Your storage doesn’t accumulate orphan records when items are removed in Xentral.

​

Good to know

• Read-only. The Xentral connector pulls from Xentral; it doesn’t push back. Catalog edits happen in Xentral.
• Incremental polling. Scheduled polls fetch only products updated since the last successful poll — keeping regular syncs fast on large catalogs. Categories are always fetched in full on each poll.
• Reserved $-prefix keys. The connector emits $options, $properties, $medias, $stocks, and $crossSellings on every product record. Don’t use $-prefixed keys for your own custom attributes — Frontic reserves that namespace for connector-side normalization.

​

Related