For e-commerce operations · readiness-first workflow

Know what's ready, blocked, and waiting for review.

Import a CSV, paste product URLs, or start from your existing catalog. Central maps products and variants, verifies missing facts, and routes everything into operational states — so your team sees what can ship, what's blocked, and what needs a decision.

app.central.to/workflows/spring-catalog
intake audit enrich publish
0% Mapping
workflow://spring-catalog · 1,626 SKUs · CSV + retailer URLs
Mapping 47 columns · 12 suppliers ready
Products 1,626 SKUs · 412 variants parsed
Token reservation 81,300 reserved · cap 90K ok
Field gaps dims · materials · care · 6 more 5,082 closed · 91% coverage 0.94
Conflicts routing to decision queue 87 routed · merchant decides queued
Held claims unsupported / single source 49 hidden until verified held
Channel readiness checking required fields 847 ready · 412 blocked gated
Audit log pending workflow run 1,626 entries · who/what/when written
Ready for
PDP copy Buyer FAQ Schema.org Google MC Custom feed ChatGPT Widget
operations queue · not a pile

Your catalog isn't one pile. It's five operational states.

Most teams stare at thousands of SKUs and can't see what's moving. Imports wait on mapping, variants wait on inheritance, feeds wait on required fields, claims wait on a merchant decision.

Central groups every product by its real state: ready to publish, blocked on a missing field, needs a source, needs a decision, hidden until verified. Throughput becomes visible. Bottlenecks become obvious.

A catalog you can act on. Every blocker has an owner, every decision has a queue.
readiness board · spring-catalog workflow

1,626 SKUs by operational state

1,626total 52%ready
Ready 847 conf ≥ 0.85 · sourced
Smeg TSF01 · Redall required · 0.96
KitchenAid 5KSM150all required · 0.94
Le Creuset 26 cmall required · 0.97
+ 844 more
Blocked 412 missing channel fields
DeLonghi Magnifica SGoogle MC · GTIN missing
Dyson V15 DetectGoogle MC · category
Bosch MUM 6title 168 ch · > 150
+ 409 more
Needs source 231 single source · below floor
Smeg TSF03 · Creamcapacity · 0.71
Magimix 4200XLpower · 1 src
Sage Barista Expressweight · 0.68
+ 228 more
Needs decision 87 sources disagree
Nespresso Vertuo Popwarranty · 1 yr ↔ 2 yr
Philips Series 5000capacity · 1.5 L ↔ 1.7 L
Krups EA8108weight · 8 kg ↔ 8.4 kg
+ 84 more
5operational states 4blockers have a routed owner 52%ready to publish last updated · 4 min ago
Top tasks · 6 of 779 shownowner
Dyson V15 Detect CordlessGoogle MC · category mismatch (8023)ops
Nespresso Vertuo Popwarranty · 3 retailers disagreemerchant
DeLonghi Magnifica SGoogle MC · GTIN missingops
Magimix 4200XLpower rating · single sourceenrich
Philips Series 5000capacity · spec sheet conflicts retailermerchant
Bosch MUM 6 mixertitle 168 ch · Google cap 150ops
how operations work

Map the intake. Show the state. Keep control.

AI drafts the content. Verification decides what ships. Three visible steps from messy intake to a workflow that operations can actually run.

1map the intake

Make every supplier file, CSV, or shop URL trackable product work.

CSV, supplier files, product URLs, shop URLs, or catalog export — Central auto-detects field mappings, clusters variants to their parent, and normalizes units before anything else happens.

$central.workflow('spring-catalog')
sourcesCSV + 4 supplier files + URLs
SKUs1,626 · 412 variants
mapped47 columns✓ ready
2show the state

Every product gets a state. Every state has an owner.

Products and fields move through ready, blocked, needs source, needs merchant decision, hidden until verified, and published. Every status is queryable, filterable, and routable to the right team.

ready847 SKUs · 52%publish
blocked412 · missing fieldsops
source231 · below floorenrich
decision87 · conflictmerchant
hidden49 · unverifiedheld
3keep control

Token caps, review gates, channel readiness — visible before cost.

Review gates, confidence floors, token caps, and channel readiness rules make automation visible before cost-triggering or publish actions happen. Nothing burns the budget by surprise.

cap90K tokens · workflow scope62%
floorconf ≥ 0.85enforced
gates6 sensitive fields · reviewon
channelsGoogle · Bing · customgated
audit1,626 entries · who/whaton
eight use cases · for operations

Everything Central does between messy intake and channel-ready output.

Field mapping, variant inheritance, conflict routing, token governance, review gates, channel readiness, batch enrichment, and multi-channel publishing — all from a workflow your team can actually run.

01
[ intake ]

Import + field mapping for messy CSVs

Map columns, normalize units, and cluster variants in one pass — across every CSV, supplier file, or catalog export your team brings in.

Pain47 column variations across 12 suppliers, manual mapping eats days every quarter.
ValueAuto-detected mappings with override, variant rows clustered to their parent, units normalized before enrichment.
supplier columns raw
Artikel-Nr.SKU
Gewicht_kgWeight
EAN-CodeGTIN
Farbe / colourColor
AbmessungDimensions
field
mapping
canonical fields normalized
EUR · €Price · EUR
kg · grams · gWeight · g
cm · mm · inDimensions · cm
Color codes · namesColor · enum
Parent + variant rowsVariant tree
02
[ intake ]

Variant inheritance, surfaced

See which fields are inherited from the base product and which are overridden per variant — with confidence on every cell.

Pain5,000 variants × 30 attributes — copying everything by hand isn't possible, but silent overrides cause feed rejections.
ValueVariant matrix shows inherited vs. variant-specific values explicitly. Enrich the base, variants update; override per variant when needed.
Smeg TSF01 Retro 2-Slice Toasterbase product · 33 attributes
8 color variants
attribute TSF01-RED TSF01-CRM TSF01-BLK
Power inherited inherited inherited
Slot width inherited inherited inherited
Color Red Cream Black
GTIN 8017709293895 8017709294595 8017709294601
Weight inherited inherited 1.43 kg
03
[ controls ]

Conflict routing & merchant decisions

When sources disagree, the conflict surfaces as a decision task — keep the owned value, accept the verified value, or hold the claim until verified.

PainThree retailers say three weights. AI picks one without telling anyone, and it lands on every channel.
ValueConflicts surface as routed decision tasks. The owner sees source agreement, picks the answer, and the choice is logged.
3 sources · weight · disagree
Brand spec1.42 kg1.00
MediaMarkt1.40 kg0.82
Coolblue1.50 kg0.78
!
route
to
decision
Decision requiredmerchant · 1 of 87
Keep brand value (1.42 kg)
Accept verified retailer agreement
Hold the claim until a 3rd source
04
[ controls ]

Token caps + cost governance

Reserve tokens before enrichment runs. Cap spend per workflow, per project, per channel scope.

PainOne uncapped run burns the month's budget on a workflow nobody approved.
ValueToken reservations + per-workflow caps gate cost-triggering work before it runs. Reservations are visible to the team that owns the budget.
spring-catalog · token budget90,000 cap
consumed reserved cap
43,200
consumed
37,800
reserved
9,000
remaining
Reservation gate
refuses run if reservation > remaining
on
Per-workflow cap
90K tokens · spring-catalog scope
on
Burst limiter
5K tokens / 5 min · per project
on
05
[ controls ]

Review gates & confidence floors

Decide which fields publish automatically, which need review, and which are held until verified — by field, not by guess.

PainSensitive fields (compatibility, safety claims, warranty) silently land on the page when nobody set a policy.
ValuePer-field review gates + confidence floors enforce policy in workflow. Sensitive fields are routed, not assumed.
T
Title
channel-required · low-risk
floor 0.85 auto-publish ops own
P
Price · currency
factual · imported only
floor 1.00 auto-publish merchant own
W
Warranty
commercial · medium-risk
floor 0.85 review merchant decides
C
Compatibility claim
marketing · high-risk
floor 0.92 hold · until verified legal/ops decide
S
Safety / certification
regulatory · highest-risk
floor 1.00 hold · brand only compliance
06
[ output ]

Channel readiness gating

Block channel publish until required fields meet each channel's spec — title length, category, GTIN, taxonomy.

Pain"Won't index", "title too long", "category mismatch", "missing GTIN" — feed rejections eat your week.
ValueChannel readiness checks fail-fast against feed requirements before the feed runs. The block surfaces in the queue with a routed owner.
verified record
titleSmeg TSF01 Retro 2-Slice Toaster · Red · 8 colors
gtin8017709293895
categoryToasters > 2-slot
price · EUR179.00
energy labelmissing
GGoogle MC
title 58 / 150 ch · GTIN ok · category 4044 ready
BBing MC
title 78 ch > 70 cap · needs short variant blocked
CFCustom feed
all mapped columns present · UTF-8 ok ready
EUEU energy label feed
energy class missing · required by EPREL blocked
07
[ workflow ]

Batch enrichment with audit log

Run enrichment by product family, supplier, category, or workflow scope. Every change carries who, what, when.

PainPer-SKU clicks don't scale to 5,000 SKUs × 17 attribute gaps. And nobody knows who changed what.
ValueBatch jobs with scoped workflows + an audit log that tells you which fields changed, why, and by whom.
batch job · in flight Q2 catalog refresh · suppliers 1-4
scopesupplier=ACME · category=appliances
SKUs1,238 selected
budget61,900 tokens reserved
workflowFULL · enrichment
974 / 1,238 · 74%est 3 min left
Audit log · most recent9 entries
09:14:22addbattery_life set to 30 h on 412 variants · conf 0.97
09:13:51decideNespresso warranty conflict resolved by m.weber · keep brand value
09:13:09holdIP rating held on 49 SKUs · no merchant source
09:12:30runbatch enrichment started by j.fischer · 1,238 SKUs
08
[ output ]

Multi-channel publishing from one record

Push the same verified record to every surface — PDP, Google MC, Bing, custom feeds, Schema.org, widget, ChatGPT.

PainRe-keying the same SKU for Google, marketplaces, custom feeds, Schema.org, and ChatGPT — every channel demands a different shape.
ValueOne record adapts; Channel Studio shapes the verified data per channel automatically.
verified record
nameSmeg TSF01 Retro Toaster · Red
gtin8017709293895
price · EUR179.00
categoryToasters > 2-slot
adapt
per
channel
GGoogle MC
Smeg TSF01 Retro 2-Slice Toaster, Red, 950 W
ready
BBing MC
Smeg TSF01 Toaster Red 950W 2-slice
ready
CFCustom CSV
sku, name_full, desc_long, price_eur, gtin
ready
JLSchema.org / JSON-LD
Product + FAQPage + AggregateRating
ready
how it fits the product

Three connected systems. One workflow.

The same Central product system that runs enrichment and publishes channels also gives operations its queue, its gates, and its audit log.

01 · Enrichment Engine

Verifies every fact.

Gathers across various sources, scores confidence, and keeps unsupported claims out of publishable copy. Each fact carries a source and a score.

verified
sources scanned15
multi-verified67.6%
held for review3
avg. confidence0.94
/features/enrichment-engine →
02 · Channel Studio

Adapts the record to every channel.

Turns the verified record into Google Shopping fields, custom feeds, page copy, Schema.org / JSON-LD, and AI-readable outputs — gated by channel readiness.

channels · per record
Google Merchanttitle cap
Bing · Perplexityready
custom feedsCSV · XML · JSON
JSON-LDx-central
/features/channel-studio →
03 · Product Widget

Verified data on the page.

FAQs, Smart Negatives, buyer answers — drop one script tag and the widget renders only from the verified record. Nothing ships until readiness allows it.

on-page
hook layerpercentile callout
details layerspecs · FAQ
advisorverified-only
install1 script tag
/features/product-widget →
proof artifact · same catalog

A pile becomes a queue you can run.

The same 1,626 SKUs — invisible on the left, operational on the right. Every blocker has an owner. Every decision has a queue. Every claim has a state.

catalog-export-2026-Q2.xlsx · 1,626 rows before
Spring catalog · 1,626 SKUs
12 SUPPLIERS · 47 COLUMN VARIATIONS
State per SKUunknown
Blocker ownerunrouted
Conflictsunsurfaced
Token spenduncapped
Review policyin memory
Channel readinesschecked at publish
Audit logmissing
Variant inheritancesilent
1,626SKUs ?blockers ?decisions
Central
routes
app.central.to / workflows / spring-catalog after · live
Spring catalog · 1,626 SKUs
5 STATES · 4 ROUTED OWNERS · TOKEN-CAPPED
847Ready
412Blocked
231Source
87Decision
Smeg TSF01 · 8 variants · Google MC readyReady
KitchenAid 5KSM150 · all required · 0.94Ready
Nespresso Vertuo Pop · warranty conflictMerchant
Magimix 4200XL · power · single srcEnrich
Le Creuset 26 cm · all requiredReady
Philips Series 5000 · capacity disagreesMerchant
52%ready to publish 1,626audit entries 0silent overwrites
governance · review gates · token caps

Automation with the guardrails operations actually need.

Central treats token caps, review gates, and confidence floors as product controls — not billing surprises. Operations sees the budget, the policy, and the audit log before anything ships.

spring-catalog · workflow governance

last check · 3 min ago
token cap 90,000 tokens · workflow scope 48% consumed · 42% reserved · 9K remaining enforced
confidence floor 0.85 default · 1.00 for safety below-floor values held for review until 2nd source enforced
review gates 6 sensitive fields gated warranty · compat. · safety · claims · pricing · taxonomy enforced
audit log 1,626 entries · who/what/when add · decide · hold · run · publish — every event on
Recent events3 routed to ops
cap Burst limiter paused a 1,200-SKU sub-batch · 5K tokens / 5 min cap hit 4 min ago
review Compatibility claim on 49 SKUs held — no merchant source · routed to legal 11 min ago
hold Nespresso Vertuo Pop · warranty conflict · 3 retailers disagree · routed to merchant 17 min ago

Frequently asked

Does Central publish without review?

+

Workflow rules decide. Verified, sourced fields above the confidence floor can publish automatically; sensitive or uncertain fields are routed through review gates before they ship. The default floor is 0.85 — you set the bar per field.

How does Central handle messy CSVs and field mapping?

+

Central auto-detects field mappings across supplier CSVs, normalizes units (kg/g, cm/in, EUR/USD), clusters variant rows to their parent, and lets ops override the mapping before enrichment runs. Mapping state is visible per intake.

Can ops teams control token spend?

+

Yes. Token caps are per workflow, per project, and per channel scope. Token reservations are visible before enrichment runs. Burst limits prevent a single run from consuming the month's budget.

Can Central handle variants?

+

Variants inherit base-product fields by default and override per variant where needed. Central shows the variant matrix — which fields are inherited, which are variant-specific — with confidence per cell.

What happens when sources disagree?

+

Conflicts surface as decision tasks, routed to the owner (merchant, legal, compliance). The decision options are: keep the owned value, accept the source-backed update, or hold the claim until a third source. Every decision is logged.

Will Central publish uncertain claims?

+

No. Unsupported, conflicting, or below-floor claims stay hidden or marked for review until evidence or a merchant decision supports them.

Can the same record power pages, feeds, widgets, and AI-readable data?

+

Yes. Central enriches the canonical product record once, then adapts the verified fields into storefront copy, Google MC, Bing MC, custom feeds, Schema.org, JSON-LD, the product widget, and AI shopping surfaces — without re-keying.

Is the audit log queryable?

+

Yes. Every event — add, decide, hold, run, publish — records who acted, what changed, and when. The log is queryable per SKU, per field, per workflow.