Completeness per Sales Channel
Product Data shows for every listing how complete its attributes are on its marketplace – per sales channel and per language of the channel. The worklist Completeness per Sales Channel lists every listing with its score, shows what is missing, and closes the gaps straight from the selection: with the bulk tool, through Excel or with AI suggestions.
You reach the worklist from the Product Data Dashboard (tile Completeness, action group Completeness), through search, and from the FactBoxes on the item card, the item list and the Marketplace Item List.
Prerequisites
- Product Data is switched on and has a license or a running demo (see Setup). Without one, you can look at the stored scores but not recalculate them; the nightly run then does nothing.
- The marketplaces have their attribute mappings and – where the connector delivers one – their attribute schema in merchantCENTRAL. Completeness judges exactly what merchantCENTRAL checks when sending; it has no rules of its own.
What counts
Per listing and language, Product Data resolves the attributes the way merchantCENTRAL would send them: category, schema, approved mapping, value, translation, allowed values. Of these, the following count:
| Required (counts fully) | Recommended (counts half) | |
|---|---|---|
| Marketplace | Mandatory attributes of the marketplace. If the marketplace category is missing where the marketplace requires one, that counts as one missing mandatory attribute | Optional attributes of the marketplace with an approved mapping |
| Item category | Attributes an attribute rule marks as Required, inherited ones included | Attributes an attribute rule names without requiring them |
- An attribute is OK if merchantCENTRAL can send it as it is: with a value, translated into the language of the channel (or language-neutral, or through a value mapping) and allowed by the marketplace. For an attribute only the item category names, what counts is whether there is a value – for variants their own value first, otherwise the item's.
- A mandatory attribute without a mapping counts as missing.
- Optional marketplace attributes without a mapping and those whose mapping has the source type Not Sent do not count. Most marketplaces have dozens of them; they would push every score down without anybody wanting to fill them.
- An attribute both the marketplace and the item category name counts once. If the attribute rule requires it, it counts as required, even if the marketplace lists it as optional only.
- A marketplace without a schema sends what its approved mappings name. These attributes then count as recommended; only the attribute rules of the item category are required.
The score
Completeness % = 100 × (Required OK + 0.5 × Recommended OK) / (Required + 0.5 × Recommended)
- Rounded down: 100 % really means complete; 199 of 200 mandatory attributes are 99 %.
- 100 % if nothing counts for the listing.
- A blocked listing has 99 % at most – what is not sent is not complete.
- Colours: red below 60 % or blocked, yellow below 100 %, green at 100 %.
Next to it, every line shows:
| Column | Meaning |
|---|---|
| Blocked | merchantCENTRAL does not send the listing in this language, because a mandatory attribute or the category is missing or an attribute rule with Block Listing applies |
| Missing Required | Required attributes that cannot be sent: no value, no mapping, no translation or a value the marketplace does not allow |
| Untranslated | Counted attributes with a value that has no translation into the language of the sales channel |
| Invalid Values | Counted attributes with a value the marketplace does not allow – not in its list, too long or out of range |
| Required, Required OK, Recommended, Recommended OK | The figures the score is made of |
| Item Category Code | The item category at the time of the calculation; its rules have a say |
| Calculated At | When the line was last calculated |
Choosing Missing Required, Untranslated or Invalid Values opens the Completeness Details of the line, filtered on exactly these attributes.
A line stands for a listing in one language of its sales channel; a channel with three languages has three lines per listing. An empty language is the language of the item texts.
Calculating
The scores are stored, not calculated when the page opens. The worklist therefore opens at once, even with many thousands of listings.
- Calculate Completeness calculates every listing within the filters of the header (marketplace, sales channel, item category, item no.). Listings never calculated before appear only after this. A run you wait for takes 1,000 listings at most. With more, the page offers to calculate every listing once in the background through the job queue.
- Recalculate calculates the selected lines – after you closed gaps, for example.
- Recalculate Completeness Nightly in the Product Data Settings creates a job queue entry that calculates every listing each night between 1 and 5 a.m. Switching it off removes the entry. The run writes one transaction per listing; a listing that fails keeps its old scores. The result is in the merchantCENTRAL activity log.
Every calculation first runs merchantCENTRAL's attribute check for the listing. The Attribute Status of the marketplace item and the Attribute Issues are thus as current as the calculation. Lines of listings that no longer exist are removed by the next calculation within its filters, or by the next nightly run.
Changes to attribute values, mappings or attribute rules show with the next calculation.
The worklist
Filters in the header: marketplace, sales channel, item category, item no. (also as a filter such as 1896-S|1900-S) and Show:
| Show | Lines |
|---|---|
| All | Every calculated line |
| With Gaps | Below 100 % |
| Incomplete | Sent, but below 100 % |
| Blocked | Not sent |
| Complete | 100 % |
The filters apply to what is shown and – except Show – to Calculate Completeness.
FactBox Per Sales Channel. Per marketplace and sales channel the average, the blocked, the incomplete and all calculated listings. A click opens the worklist on this channel. Blocked, incomplete and complete do not overlap – a blocked listing counts as blocked only.
FactBox Attributes in the Channel Language. The attributes of the current listing, resolved live as in the Attributes FactBox of the marketplace items – always in the first language of the sales channel.
Completeness Details (action Details). Every attribute that counts for the line – required or recommended, OK or not, with a hint on what is missing and what to do. The details are worked out when they open and may differ from the stored figures until the next calculation. Unlike the attribute issues, they also show missing recommended attributes.
Close gaps
The actions under Close Gaps work on the items of the selected lines:
| Action | Effect |
|---|---|
| Fill with Bulk Tool | Opens Replace Item Attribute Values with these items |
| Export to Excel | Opens the Excel export with these items |
| Suggest with AI | Starts the AI suggestions for these items (50 at most per run) |
If the item numbers do not fit into a filter, the page says so instead of opening without a filter. Then Recalculate the selected lines, and the new score is in the list.
Navigate
| Action | Opens |
|---|---|
| Details | The completeness details of the line |
| Attribute Issues | The issues merchantCENTRAL's attribute check found for the listing and language |
| Listing | The marketplace item card |
| Item Card | The item card |
On item and listing
- Item card and item list: FactBox Completeness per Marketplace with one line per marketplace and sales channel – the lowest score across variants and languages and the number of blocked lines. A click opens the worklist for this item and channel.
- Marketplace Item List: FactBox Completeness with the stored score per language of the listing.
Both FactBoxes appear only while Product Data is switched on.
On the dashboard
The dashboard shows three completeness elements:
- Tile Completeness: the average of all calculated lines (listing per language) and how many of them are complete; Not calculated before the first calculation.
- Card Listings by Completeness: complete, incomplete, blocked – three groups without overlap. Each segment opens the worklist on exactly the lines it counts.
- Card Completeness Calculation: how many listings are calculated (of all marketplace items), when the oldest stored calculation ran (yellow if older than two days) and whether the nightly recalculation is on.
Typical cases
See Troubleshooting: the worklist is empty, the scores are stale, a listing is blocked, or the score stays below 100 % although every mandatory attribute is filled.