Skip to main content

Publish without rework

See what a channel would reject before you send it

From one golden record, Fuse builds the feed each channel expects and reports the non-conformities, product by product, before publication.

Request a demo

The situation today

What goes wrong today

Every channel has its own categories, field names, allowed values, length limits and mandatory attributes. A missing field or a wrong category means a rejection or a long approval delay, and you find out after the send, when the range was supposed to be live. Keeping one spreadsheet per channel is how teams end up publishing last month's catalogue on the marketplace that matters most.

The mechanism

How it runs in Fuse

You encode each channel's requirements once, as an attribute list plus the rules that go with it. From the golden record, Fuse projects CSV, JSON, XML or REST: fields renamed to the channel's names, categories transformed, units converted, titles cut to the limit, allowed values substituted and non-compliant products excluded from the run. Validator reports what would fail, per product and per rule, before anything leaves the platform.

Product health

Ergonomic office chair

CHAIR-458 GTIN 05400123456789

2/8 fields ready

  • reference CHAIR-458 Ready Matched across all four sources.
  • gtin 05400123456789 Ready Checksum valid.
  • description 48 characters Review Too short for the marketplace minimum of 300.
  • material not set Review Attribute missing. Required by two channels.
  • price 129 EUR / 134 EUR Blocking Two sources disagree. ERP and Supplier B are 5 EUR apart.
  • availability Last seen 14 days ago Blocking Stale. The freshness rule allows 24 hours.
  • image_url v2 asset Review Points at the superseded product version.
  • lead_time not set Review Absent. Blocks the B2B distributor feed.
Illustrative payloads. Field names match the default Fuse model.

Amazon and Google Shopping are examples of attribute lists you configure, not certified connectors. The feed leaves as a file or a REST call. Fuse reports what a channel would reject; it cannot promise that a first submission is accepted.

What changes

What you get

  1. Fewer rejections

    Non-conformities become a report you read before sending, not an email you receive afterwards.

  2. Faster publication

    The correction loop happens inside Fuse, at the speed of a re-run rather than a channel round-trip.

  3. One source, many feeds

    The channel definition changes; the catalogue does not have to move with it.

  4. Quicker reaction to spec changes

    A channel changes a rule, you change one list, and the next run reflects it everywhere.

Indicators to track

How to measure it

Feed acceptance rate

accepted rows per submission

Rejections per channel

rejected products per run

Time to fix a rejection

hours from report to corrected re-send

Products published without manual work

percentage of the run needing no intervention

Next

Related use cases

  • Omnichannel synchronisation

    Validated changes leave Fuse immediately or on a schedule, over files, REST or a connector, with success, error and retry reported per destination.

    Publish without rework

  • Attribute normalisation

    Fuse converts source values into the reference lists your business uses for units, colours, sizes, materials, dimensions and technical characteristics.

    Speak one product language

  • Product golden record

    Fuse reconciles ERP, PIM, supplier and team data, applies the priorities you set, and produces a traceable record every system can read.

    Ingest and reconcile

Bring the channel whose rejections you are absorbing

We encode its attribute list, its allowed values and its limits, then run one of your ranges against them and hand you the report you would have got after the send.

Request a demo

One channel, one range, one pass.