Bulk Import Catalog-Specific Product Data Overrides (Excel)

• Overview
• Purpose
• Feature Description
• Instructions
• Important Notes

Overview

This feature lets you download and import an Excel file (.xlsx) to define product data in a specific catalog using catalog-specific override data that differs from the product master in product management.

Even for the same product, you can set different prices, delivery dates, SKU variants, etc., for each catalog.

Purpose

Use this feature to manage product information by catalog in one place and control sales conditions and display content for each catalog.

By explicitly managing differences in prices, delivery dates, and SKU variants by business partner and channel, you can also use it to support compliance and control.

Feature Description

Field-Level Overrides and Inheritance from the Product Master

You can create "Override Data" for each catalog separately from the product master.

By creating override data, you can define catalog-specific prices, delivery dates, SKU variants, etc., even for the same product.

For overridable fields, you can manage each field separately by choosing whether to use a catalog-specific value, inherit from the product master, or explicitly clear the value.

For example, even when the same SKU has prices in multiple currencies or transaction terms, you can make only some prices inherit from the product master while keeping other prices and SKUs as catalog-specific values.

*Fields that cannot be overridden, such as product names, continue to refer to the product master.

Even after override data is created, fields that inherit from the product master use the values updated in the product master. Fields overridden with catalog-specific values are not changed by updates in the product master.

Overridable Fields

Currently, the fields for which override values or inheritance from the product master can be specified are as follows.

• Include in Catalog: You can specify whether each SKU is included in the catalog.
• Price: You can set the wholesale price at the SKU level.
• Reference Retail Price: You can set the suggested retail price at the SKU level.
• Is Selectable Delivery Date: You can specify whether to make the delivery date selectable within a range at the Product level.
• Delivery Date: You can specify the estimated delivery date as a range from From (start date) to To (end date) at the Product level.
• Custom Attribute: You can set custom attributes at the Product level and SKU level.

Target Catalog Code for Import

To perform bulk import of catalog-specific product data overrides, a code must be registered in the target catalog.

If the code is not registered, the Catalog Code column of the downloaded XLSX file will be blank. If you run the import while the Catalog Code column is blank, an error will occur.

Before downloading or editing the file, make sure the code has been registered in the target catalog.

The catalog code can be registered from the catalog editing feature. For details, see Edit a Catalog.

Application Logic by Level

• Product-level fields (Delivery Date, Product Custom Attributes)
  The value in the first row of the product in the file (the first SKU row) is referenced and applied uniformly to all SKUs.
• SKU-level fields (Include in Catalog, Price, Reference Retail Price, SKU Custom Attributes, etc.)
  Individual values for each SKU row are applied.

SKU Display Order by Row Order

The display order of SKUs within the catalog is determined by the row order in the file.

Behavior That Varies by Condition

• Deletion of Some SKU Rows (Exclusion from SKU-level field updates)
  If some SKU rows within a product are deleted from the file, the SKU-level fields for the deleted SKU rows are excluded from updates.
• Deletion of All SKU Rows (Exclusion from Product Updates)
  If all rows of a specific product are deleted from the file and imported, the product is treated as "Not subject to update," and the current data and field-level override/inheritance state is kept as is.
  This prevents products from unintentionally entering an override state.

Language Settings

Based on the settings at the time of download, headers and other elements in the file are generated in the corresponding language.

Instructions

The bulk import flow for catalog-specific product data overrides is as follows.

1. Download the XLSX file for catalog-specific product data overrides
2. Edit the XLSX file for catalog-specific product data overrides
3. Upload the XLSX file for catalog-specific product data overrides and perform bulk import

1. Download the XLSX file for catalog-specific product data overrides

Navigate to the XLSX File Download Page

1. Click the Catalogs menu.

2. Click the Detail button of the target catalog from the catalog list.
   The "Catalog Details" page opens.

   You can also narrow down the catalogs by entering criteria in Filter Catalogs.

3. Click Bulk Import for Catalog-Specific Product Data Override in the product list section.
   The "Catalog-Specific Product Data Override" modal opens.

4. Click Download XLSX file.
   The "Download XLSX for Catalog-Specific Product Data Bulk Override" page opens.

Download the XLSX File

1. File Language
   Specify the language for columns and other text in the file from the dropdown menu.

2. Select Target Products
   Select the target products in the catalog.

   • Click Select All to select all products in the catalog.
   • Click Remove All Selections to deselect all selected products.

3. Click the Download button.
   The "XLSX file for catalog-specific product data override" is downloaded.

2. Edit the XLSX file for catalog-specific product data overrides

Product data is prepared based on the products specified in the download settings.

For products without override data, data from the product master is prepared; for products that already have override data, data from the current override data is prepared.
If override data does not exist, data for SKUs that are inactive in the product master is prepared with "Include in Catalog: false".

Open the downloaded "XLSX file for catalog-specific product data override" and edit the values you want to override.

For cells that can be overridden, the handling after import differs depending on the input.

Input content	Handling after import
Blank	Follow the product master
Value entered	Override with a catalog-specific value
__CLEAR__	Explicitly clear the value (create override data in an empty state)

Description of Each Field

The available columns and field names for prices, custom attributes, etc., vary depending on the maker and brand environment. Edit the file according to your company's environment.

Do not rewrite the column names.
Rewriting column names will cause import errors.

• Catalog Code (Cannot be changed)
  Indicates the target catalog for which the product data override is performed.

• Model Number (Cannot be changed)
  Indicates the product's "Model Number".

• SKU Number (Cannot be changed)
  Indicates the SKU number of the SKU.

• SKU (Cannot be changed)
  Indicates the display name of the SKU.

• Include in Catalog (Target for override)
  This is an input field at the SKU level.

  To create override data, enter true or false.

  • true : The target SKU will be displayed in the Buyer App and can be ordered.
  • false: The target SKU will be hidden in the Buyer App.

• Price (Target for override)
  This is an input field at the SKU level.

  To create override data, enter the override "Wholesale Price" for each combination of transaction term and currency.

  • Examples of transaction terms: wholesale rate-based pricing, FOB, EXW, etc.
  • Examples of currencies: JPY, USD, CNY, etc.

  In the case of wholesale rate–based pricing, enter the retail price for the override.

• Reference Retail Price (Target for override)
  This is an input field at the SKU level.

  To create override data, enter the override "Reference Retail Price" for each currency.

• Is Selectable Delivery Date (Target for override)
  This is an input field at the Product level.

  Enter true to enable or false to disable.
  When enabled, buyers will be able to specify the delivery date at the time of order.

  The delivery date can be any date within the period from Delivery Date (From) to Delivery Date (To).

• Delivery Date1 (From) (Target for override)
  This is an input field at the Product level.

  Enter the "Delivery Date (From)" for the override in yyyy-MM-dd format.

  Example: 2026-01-01

• Delivery Date2 (To) (Target for override)
  This is an input field at the Product level.

  Enter the "Delivery Date (To)" for the override in yyyy-MM-dd format.

  Example: 2026-01-31

• Custom Attribute (Product level) (Target for override)
  This is an input field at the Product level for custom attributes registered in the master in advance.

  To create override data, enter the value.

• Custom Attribute (SKU level) (Target for override)
  This is an input field at the SKU level for custom attributes registered in the master in advance.

  To create override data, enter the value.

Saving the XLSX File

Once data entry is complete, save and close the XLSX file.

Note that if formulas remain in the XLSX file, an error will occur during import. Therefore, save after pasting as "Copy > Paste Special > Values".

3. Upload the XLSX file for catalog-specific product data overrides and perform bulk import

Once the file editing is complete, upload it to DEXTRE.

Navigate to the XLSX File Upload Page

1. Click the Catalogs menu.

2. Click the Detail button of the target catalog from the catalog list.
   The "Catalog Details" page opens.

   You can also narrow down the catalogs by entering criteria in Filter Catalogs.

3. Click Bulk Import for Catalog-Specific Product Data Override in the product list section.
   The "Catalog-Specific Product Data Override" modal opens.

Execute Bulk Import of the XLSX File

1. Click Select File.

2. Select the edited "XLSX file for catalog-specific product data override".

3. Click the Import button.

   If the import is successful, inheritance from the product master, catalog-specific overrides, and explicit clearing are reflected for each field based on the values in the XLSX file.

   If there is a problem with the file contents, the import will fail and an error message will be displayed.

Important Notes

Following the Product Master by Field

Even for products for which override data exists, fields that follow the product master use the values updated in the product master.

Fields for which catalog-specific values are entered will not reflect updates made in the product master in the catalog. To make each field follow the product master, leave the target cell blank in the XLSX file and import it.

To explicitly clear a value, enter __CLEAR__ in the target cell. A blank cell is treated as a request to follow the product master, not as a request to clear the value.

Data Application Priority (Product Level)

Even if different values or __CLEAR__ are entered for each SKU row for Product level fields (Delivery Date, Product Custom Attributes), the system uses only the value in the product's first row and ignores the input values in the second and subsequent rows (following SKU rows).

Behavior when SKU Rows Are Deleted

If some SKU rows within a product are deleted from the file, the SKU-level fields for the deleted SKU rows are excluded from updates.

If all product rows for a specific product are deleted from the file, the product is only excluded from the update, and the product is not removed from the catalog.

Parts of the XLSX File That Cannot Be Changed

Do not change or delete the contents of cell A1 of the file. If you change the contents of cell A1, the import process will fail.

Also, Catalog Code, Model Number, SKU Number, and SKU cannot be changed. Changing them will cause inconsistencies between the values entered for overridable fields and the target product and SKU.