トラック 04 · モジュール 03 / 4
Content maintenance: the Maintenance Hub, bulk exports, and exception lists
Maintain many supplier item records consistently — the Maintenance Hub export/edit/import loop, choosing a reliable match key, separating missing records from mismatches, and producing an exception list someone can act on.
読了目安 4 分
このモジュールで学ぶこと
- ✓Use the Maintenance Hub to export, edit, and re-import product content in bulk.
- ✓Choose a reliable record-matching key and check it for missing or duplicated values first.
- ✓Separate missing records from mismatched values when comparing sources.
- ✓Produce an exception list with current value, intended value, and source.
Find mismatches without losing the thread.
A structured comparison lets you maintain hundreds of item records consistently. Match records by a reliable identifier, compare like-for-like fields, and keep a clear exception list — a lookup result is only as reliable as the key and source behind it.
The Maintenance Hub loop
Supplier One's Maintenance Hub covers changes to items that already exist. For bulk content work, export a maintenance spreadsheet of the items you need — Product Content & Site Experience for online content — up to 5,000 items at a time, edit the attributes in Excel, and re-import. The Activity Monitor reports the result per item. Keep the untouched export as your before-snapshot, and change only the columns you intend to change.
Match key
Every comparison between your source and Walmart's export needs a key that exists in both and is unique in each: usually the GTIN or the Walmart item number. Before comparing anything, check the key itself — are any values missing on either side, and are any duplicated? A duplicated key returns a match that may be the wrong row; a missing key returns nothing, which is not the same as "no difference".
Comparison
Compare like for like: the same attribute, the same unit, the same packaging level. Convert units before comparing (mL to mL, inches to inches) and keep the conversion visible. Sort the results into three buckets:
- Match — no action.
- Mismatch — both sides have a value and they differ.
- Missing — one side has no record or no value.
Buckets two and three need different actions: a mismatch is a correction, a missing record is an investigation.
Exceptions
The output of maintenance work is an exception list: one row per difference with the item reference, the field, the current value, the intended value, and the source that supports the change. It feeds the next import directly, and it is the record you show a merchant or support when a value is disputed. A vague "some capacities are wrong" is not an exception list.
ポイント
A lookup result is only as reliable as the identifier and source data behind it. Check the key before trusting the match.
実践してみる
シナリオ
You compare a fictional master sheet with a Maintenance Hub export. One item's GTIN is missing from the export; another GTIN appears twice in the export with different capacities.
演習
- Flag the missing record separately from value differences.
- Investigate the duplicated GTIN before relying on any lookup against it.
- Prepare a clean comparison and exception list once the keys are dependable.
推奨アプローチを表示
Do not treat the missing lookup as a confirmed value or as a mismatch — investigate why the item is absent from the export (not set up, wrong supplier number, filtered out). Resolve the duplicated GTIN first: two records with different capacities means either a data error or a genuine second item mislabeled with the same code. Compare only the validated matches, and record each difference with current value, intended value, and source.
理解度チェック
公式情報を見る
このモジュールに関するマーケットプレイスの公式ドキュメント。