CEDX Catalog · Commerce & Retail
CEDX Catalog is the product-information console: products, variants, categories and attributes with a completeness score on every row, a channel-readiness board that says what is blocked and why, and a drift count for rows where the live channel copy no longer matches the master.
The readiness board does not say content needs work. It says 178 products fail the marketplace channel's required-attribute checks, and names a shoe blocked by one missing GTIN. That is a work list, not a mood.
Runs on demo data. Northline Outfitters is the software's demo workspace, not a customer.
What it is
The products table carries a completeness bar, variant count, media count and primary channel on every row — a merino tee at 100% with 16 variants and 8 media reads next to drafts still under 80%, and 279 products sit in the enrichment queue.
420 variant rows with parent, option, family, price, stock and barcode — options like XS / Black on the row. The barcode column either has the GTIN or admits it does not: 156 rows are empty, and that is its own filter chip.
48 categories, 8 roots, 1,165 product links — with each category's channels, its mapped state and its status on the row. Ten categories are unmapped with no channel map, and the table says so in a column instead of letting it surface at publish time.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/catalog.
01 — Overview
The cards read 320 products, 420 variants, 65.1% master complete against the 90% target, 36.3% channel-ready, 279 products at incomplete risk with 129 critical, and 318 rows in sync drift. The readiness board breaks it by channel: 178 blocked from the marketplace, 68 from POS, 59 from wholesale.
02 — Products
Every product row shows how complete it is, how many variants and media it has, and which channel is primary. The under-80% card — 279 products — is the enrichment queue, one click from the table.
03 — Variants
The variant table is where identity lives: option, price, stock and GTIN per SKU row. The missing-barcode chip cuts the table to the 156 rows that cannot list on a channel requiring a GTIN.
04 — Categories
The category tree with product counts, channel coverage and mapped state per node. Roots, leaves and unmapped are chips, so the ten categories with no channel map are a filter away rather than a report.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Works the 279-product enrichment queue — a draft submitted with zero media gets sent back, and the board says which.
enrichment queue · 279
Owns identity attributes: 156 variants with an empty GTIN are their list, and the barcode column says so plainly.
missing GTIN · 156
Watches readiness per channel — 68 blocked from POS, 178 from the marketplace — and the 318 rows drifting off the master.
drift rows · 318The shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Products gather attributes, media and variants until the completeness bar moves — the demo average sits at 65.1% against a 90% target.
GTINs and identity attributes go on the variant rows; 156 are still empty, and the marketplace channel blocks for exactly that.
Categories attach to channel trees — 1,165 product links, 10 categories still unmapped — so each channel knows its assortment.
Ready rows publish per channel; the drift counter then flags the 318 rows where live copy has moved off the master.
One record
The same product rows show up as Store's trading table, the register's price book and the marketplace's listing checks. Master data lives here once.
Store's product table — price, stock, promo depth — is the trading view of the rows this catalog keeps complete.
CEDX MarketplaceThe attribute checks blocking 178 products here are the same completeness rules the marketplace console applies to seller listings.
CEDX POSThe POS price-book refresh annotated on this console's chart is the register pulling its price file from the master.
CEDX OrdersOrders links back to this catalog from its own console; line-item identity starts here.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your products, your channels
Catalog with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/catalog. It runs on demo data, which the workspace banner makes plain.
A product passes the channel's required-attribute and mapping checks. The board shows the ready share per channel with the blocked count next to it — 178 blocked from the marketplace, 68 from POS, 59 from wholesale in the demo.
Rows where the live channel copy no longer matches the master's price, title or media. The demo flags 318 rows at a drift score of 40 or more, so republishing is a list, not an audit.
Because channels require them. 156 demo variants have an empty barcode, and the Overview traces a blocked listing to one missing GTIN — identity attributes are the difference between complete and publishable.
No. The console scores completeness, checks channel requirements and counts drift — the writing and the photography stay with your team, as the limits section states.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. The readiness board is on the first screen.