Skip to main content

Bulk Import Catalog-specific Product Data Overrides (Excel)

Overview​

This feature allows you to define product data within a specific catalog with unique override data that differs from the product master in product management, by downloading and importing an Excel file (.xlsx) for import.

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

Purpose​

The purpose of this feature is to centrally manage product information by catalog and to control sales conditions and display content for each catalog.

By explicitly managing differences in prices, delivery dates, and SKU variants according to customers and channels, it can also be utilized to ensure compliance and control.

Feature Description​

Item-specific Overrides and Product Master Following​

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

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

For overridable items, you can manage each item separately by choosing whether to use a catalog-specific value, follow the product master, or explicitly clear the value.

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

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

Even after override data is created, items that follow the product master reference the values updated on the product master side. Items overridden with catalog-specific values are not changed by updates on the product master side.

Overridable Items​

Currently, the items for which override values or product master following can be specified are as follows.

  • Include in Catalog: You can specify whether to include a product in the catalog at the SKU level.
  • 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 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.

Application Logic by Hierarchy​

  • Product level items (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 items (Include in Catalog, Price, Reference Retail Price, SKU Custom Attributes, etc.)
    Individual values for each SKU row are applied.

Reordering of SKUs by Row Order​

The display order of SKUs within the catalog is defined according to the row order in the file.

Variable Elements Based on Conditions​

  • Deletion of Some SKU Rows (Exclusion from SKU level item updates)
    If some SKU rows within a product are deleted from the file, the SKU level items for the deleted SKU rows are treated as not subject to update.
  • 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 item-specific override/product master following state are maintained as they are.
    This prevents products from unintentionally entering an override state.

Language Settings​

Based on the settings at the time of download, header items and other elements in the file will be generated in the corresponding language.

Instructions​

Bulk importing of catalog-specific product data overrides is performed according to the following flow.

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

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

Move to the XLSX File Download Page​

  1. Click the Catalogs menu.

  2. Click the Detail button of the target catalog from the catalog list.
    You will be transitioned to the "Catalog Details" page.

    You can also narrow down the catalogs by entering conditions in the 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.
    You will be transitioned to the "Download XLSX for Catalog-Specific Product Data Bulk Override" page.

Download the XLSX File​

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

  2. Select Target Products
    Check 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" will be downloaded.

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

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

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

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

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

Input contentHandling after import
BlankFollow the product master
Value enteredOverride with a catalog-specific value
__CLEAR__Explicitly clear the value (create override data in an empty state)

Description of Each Item​

The presence of columns and item names for prices, custom attributes, etc., vary depending on the maker and brand environment. Please edit according to your company's environment.

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

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

  • Model Number (Cannot be changed)
    Refers to the "Model Number" of the product.

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

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

  • Include in Catalog (Target for override)
    This is an input item 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 item at the SKU level.

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

    • Examples of transaction conditions: 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 item at the SKU level.

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

  • Is Selectable Delivery Date (Target for override)
    This is an input item 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 item 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 item 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 item 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 item 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 functions remain in the XLSX file, an error will occur during import. Therefore, please save after pasting as "Copy > Paste Special > Values".

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

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

Move to the XLSX File Upload Page​

  1. Click the Catalogs menu.

  2. Click the Detail button of the target catalog from the catalog list.
    You will be transitioned to the "Catalog Details" page.

    You can also narrow down the catalogs by entering conditions in the 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, product master following, catalog-specific overrides, and explicit clearing are reflected by item based on the input in the XLSX file.

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

Important Notes​

Item-specific Product Master Following​

Even for products for which override data exists, items that follow the product master reference the values updated on the product master side.

Items for which catalog-specific values are entered will not reflect updates made on the product master side in the catalog. To make each item 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 an instruction to follow the product master, not as an instruction to clear the value.

Application Priority of Data (Product Level)​

Even if different values or __CLEAR__ are entered for each SKU row for Product level items (Delivery Date, Product Custom Attributes), the system will adopt only the value in the "first row of the product" as correct and ignore 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 items for the deleted SKU rows are treated as not subject to update.

If all product rows for a specific product are deleted from the file, the product is merely excluded from the update, and deregistration from the catalog itself (deletion of the product) is not executed.

Maintenance of File Structure (Header Identifier and Key Information)​

  • Cell A1 of the file contains an identification code for system verification; changing or deleting it will cause the import process to fail.
  • System matching keys (Catalog Code, Model Number, SKU Number, SKU display name) used to identify update targets cannot be edited or changed in order to maintain data integrity.