A catalog rarely lives in just one place. The store wants it in its format; the ERP, in a CSV with the columns it understands; a marketplace, in its own file and with its own length limits. The usual approach is to prepare each one by hand, in a separate spreadsheet. And as soon as you change something in one, the others no longer say the same thing.
One master product record and its outputs
In Noobit, you maintain each product record just once: that's the master product record. Each destination is an output, a template that says which columns the file has and where each one comes from. The record isn't touched for each channel: each output puts it into its own format.
- Columns named the way each destination asks: your ERP's, the ones in Amazon's template or those of any other system.
- Each column comes from a piece of data in the record: name, EAN, price, category, short description, a specific section, the main photo…
- Simple tweaks: strip the HTML, keep plain text or trim to a maximum number of characters.
- If needed, one row per variation, with its own SKU, EAN, price and photo.
The result is a CSV you download; large catalogs are prepared in the background.
Copy or rewrite, column by column
Each column is filled in one of two ways. Most are copied from the record as is: it's exact and costs nothing. When a destination asks for something else — a shorter description, a different tone — the AI rewrites that column from the record, following your instruction. It rewrites, it doesn't invent: it starts from what the record says. Before exporting you see what it will cost, and anything already rewritten isn't charged again as long as nothing changes.
Which products go to each channel
Not everything in the catalog goes everywhere. Each output decides which products it carries: the whole catalog, whatever matches a filter (a brand, a status, a category, only products with an EAN) or a fixed list by EAN or SKU. On each product's record you can see which channels it goes to and which it doesn't.
The exception, product by product
Sometimes a channel needs a product to say something different: a shorter title for the marketplace, a description adapted for the ERP. For that, you set that field by hand from the product record, for that output only, and it stays marked. The other channels keep reading the master product record, and if you change your mind, you go back to the generated text in one click.
The golden rule is the same as always: you change the master product record, and an exception is marked as an exception.