Retail Express inbound sync
Retail Express inbound sync
Open Settings → Integrations → Retail Express → View. A Twelfth managed
connection imports Rex data read-only. Twelfth scopes, builds and runs the
pipeline; workspace members do not configure its extraction credentials,
endpoints or schedule here.
This import reads products, outlets, suppliers, stock positions, sales,
purchase orders, receipts and product price history. Twelfth maps the data into
your workspace and publishes the tables used by the pipeline,
Performance and other workspace views. To change Rex products, configure the
separate writeback connection.
Update health
Update health opens first. The current managed nightly runs from 04:00
and usually finishes by about 05:30, Melbourne time (AEST/AEDT). The
panel shows the next run and the last 14 nights, including partial and failed
updates.
The latest run has three steps:
- Pulled from Retail Express — source tables were read.
- Prepared for Twelfth — the data was mapped into serving tables.
- Available in Twelfth — the workspace import completed. No new data
means the import found no new snapshot to apply.
The connection summary shows Data current to, the latest successful
snapshot’s date, and Last refreshed, when the last successful refresh
completed. A recent refresh and recent source data are different: a table can
be pulled successfully while its source has stopped changing.
Needs attention
Each item says whether the issue is on your Retail Express sync or
Twelfth’s side.
- If the pull, preparation or workspace import fails, Twelfth is alerted
automatically. Your workspace keeps the last successful update. - If only some tables arrive, those that missed the run retain their previous
data. The panel names the missing tables. - If Twelfth is pulling a table every night but its newest records are old,
check the sync that copies Rex into your own database, where your managed
connection uses one. This is different from Twelfth failing to pull it.
Use Contact Twelfth on the connection page for a freshness issue or to
request a field or mapping change.
Source tables
Every table the managed pipeline reads from Retail Express is listed under its
own name (retailexpress_orders, retailexpress_productdetailslog and so on),
with a plain-language label and:
- Status: Synced (read every night), Backfilling (history still
loading), Planned (access agreed, sync not yet switched on) or Retired
(superseded by another table and no longer read). - Rows: how many rows the warehouse holds for it.
- Data from … to …: the span of the table’s watermark, from the earliest
to the latest change the warehouse has seen. A table with only a “to” date is a
current-state table, not a history. - Watermark: the Retail Express column the nightly filters on, so you can
tell which changes a refresh picks up (acreated_onlog is append-only; a
coalesce(modified_on, created_on)table also carries edits). - In the sync since: the date the table joined the nightly, shown for
tables added after the connection first went live. - Unlocks: what having the table makes possible in Twelfth, for example
your own price history from the product change log, or supplier lead times
from purchase-order receipts.
Twelfth publishes this list from the pipeline itself, so it describes what is
actually read rather than what was planned. Planned and retired tables show no
rows or dates: they are declarations, not measurements.
What we sync
The connection page lists every table the managed pipeline publishes to your
workspace, with:
- Status: Synced (in the latest refresh), Not published yet (an
optional table the pipeline does not produce for your workspace yet), or
Pending first sync. - Rows: how many rows the latest refresh carried.
- Source updated: when that table last changed at the source, so a stale
table stands out even when the refresh itself succeeded.
Tables marked optional are extensions (for example buyer remits or
recommendation rationale) that a pipeline may publish later; their absence
never blocks a refresh.
The two lists describe different stages: Source tables is what the pipeline
reads from Rex; What we sync is what it publishes into Twelfth. Source
coverage does not mean every source column is available in a workspace view.