Configure Inventory Allocation Rule Application Conditions

info

This page describes procedures for environments using Inventory Management (New Method).

If your screen layout differs from the one shown on this page, refer to the Inventory Management (Conventional Method) manuals.

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

Overview

This section explains how to configure the conditions that determine which targets an inventory allocation rule applies to during inventory allocation.

Application conditions are configured for each brand, targeting catalogs, SKUs, buyers, or globally.

Purpose

The main purpose of configuring allocation rule application conditions is to define the rules referenced during inventory allocation for each target and standardize the criteria for inventory allocation.

By specifying application targets at granularities such as catalogs, SKUs, and buyers, you can ensure that the same allocation rule is applied under the same conditions. Since the precedence when multiple conditions match is also defined, it is useful for avoiding rule applications that differ from expectations.

Feature Description

Types and Precedence of Application Conditions

In application condition settings, you can configure conditions to apply allocation rules to specific catalogs, SKUs, buyers, or globally.

The hierarchy of conditions represents the granularity at which the assignment target is specified. When multiple application conditions match a single order line during inventory allocation, more specific application conditions take precedence.

The precedence, from highest to lowest, is as follows:

1. Catalog × SKU × Buyer

   Conditions specified by combining catalogs, SKUs, and buyers.

2. SKU × Buyer

   Conditions specified by combining SKUs and buyers.

3. Catalog × Buyer

   Conditions specified by combining catalogs and buyers.

4. By SKU

   Conditions that specify a SKU.

5. By buyer

   Conditions that specify a buyer.

6. By catalog

   Conditions that specify a catalog.

7. Apply to all (global)

   Conditions applied globally. Catalogs, SKUs, buyers, and other targets are not selected individually for this condition.

Application Condition Status

Application conditions have statuses that represent registration states and update schedules.

Status	Description
UNREGISTERED	A state where it has not been registered as an application condition yet.
DRAFT	An application condition that is not yet reflected in inventory allocation.
ACTIVE	An application condition referenced during inventory allocation.
DELETE PLANNED	An application condition scheduled to be deleted or archived during updates.
No change	A scheduled state that will not change the current state even after updates.
DISABLED	A state where Apply to all (global) is not applied.

Information Available in the Condition List

In the condition list, you can check the Current status, Change details, and target columns.

Target columns are displayed combining Catalog, Product/SKU, and Buyer depending on the condition type.

Instructions

Navigating to the Application Condition Settings Page

1. Click the Inventory menu.
2. Click the Settings tab.
3. Click Allocation rules.
4. Click the Details button for the allocation rule you want to configure.
5. Click the Application condition settings button.
   The "Application condition settings" page opens.

Adding and Changing Application Conditions

Application conditions can be broadly divided into combined conditions and individual conditions. In either case, targets are added in units of catalogs, products/SKUs, or buyers for the configured condition type.

Basic Operation Method

1. Click the Bulk add/remove conditions button.
   The "Bulk condition operation" modal opens.
2. Select the targets to include in the conditions.
   • Catalog
   • Product/SKU
   • Buyer
3. Click the Add conditions button to add application conditions.

Catalog Configuration Method

Catalog configuration is performed for the following condition types:

• Catalog × SKU × Buyer: Open the modal with the Add/remove conditions button.
• Catalog × Buyer: Open the modal with the Add/remove conditions button.
• By catalog: Open the modal with the Select catalogs button.

1. Select the checkboxes for the target catalogs in the modal.
2. Click the Select button. The selected catalogs become the target of the conditions.

SKU Configuration Method

SKU configuration is performed for the following condition types:

• Catalog × SKU × Buyer
• SKU × Buyer
• By SKU

1. Open the modal with the Add/remove conditions button.
2. Click the Select products button.
3. Select the checkboxes for the target products.
4. Click the Select button. All SKUs related to the selected products become the target of the conditions.
5. To configure SKUs individually, subsequently click the Select SKUs button for each product.
6. Select/deselect the checkboxes of the target SKUs to configure them.
7. Click the Select button. The target SKUs are updated.

Buyer Configuration Method

Buyer configuration is performed for the following condition types:

• Catalog × SKU × Buyer: Open the modal with the Add/remove conditions button.
• SKU × Buyer: Open the modal with the Add/remove conditions button.
• Catalog × Buyer: Open the modal with the Add/remove conditions button.
• By buyer: Open the modal with the Select buyers button.

1. Select the checkboxes for the target buyers in the modal.
2. Click the Select button. The selected buyers become the target of the conditions.

Configuring Change Details of Application Conditions

For application conditions, change details are configured for each row of the list.

Available operations vary depending on the status of each row or the target of the conditions.

• Activate after update: Selecting the checkbox activates the conditions of the corresponding row when updating the application conditions. Clearing it keeps it as a draft. When the Current status is ACTIVE, it cannot be returned to a DRAFT.
• Remove application condition: Directly deletes rows that are UNREGISTERED in the application conditions.
• Mark for deletion: Deletes the conditions of the corresponding row when updating the application conditions. This targets rows already registered in the application conditions.
• Undo deletion plan: Restores rows planned for deletion.
• Change: Changes the target (catalog, product/SKU, buyer) of the corresponding row. This operation is possible only when the Current status is UNREGISTERED or DRAFT.

Also, by selecting each row with checkboxes and choosing an operation from the Bulk action dropdown, you can operate on multiple rows at once. There are three options for bulk actions:

• Activate selected application conditions: Activates the selected rows all at once.
• Draft selected application conditions: Makes the selected rows drafts all at once. If rows with a Current status of ACTIVE are selected, the Draft selected application conditions operation cannot be performed.
• Mark selected for deletion or exclude: Among the selected rows, those already registered in the application conditions are set as planned for deletion. Those unregistered are removed.

Configuring Apply to All (Global)

Unlike catalogs, SKUs, and buyers, the Apply to all (global) condition does not have a setting to select the target of the condition.

1. Check the Current status.
2. Specify the status After update with radio buttons.
   • DISABLED: Disables the condition.
   • DRAFT: Makes the condition a draft. When the Current status is ACTIVE, it cannot be returned to a DRAFT.
   • ACTIVE: Enables the condition.

Reviewing the Impact

1. Once the input for each condition is complete, click the Review impact button.
   The "Review impact" modal opens.
2. Check the list of conditions that become active and conditions that become inactive due to the changes. Conditions that become a DRAFT after the update are not displayed.
3. Once the confirmation is complete, close the modal.

Saving Application Condition Settings

After reviewing the impact, click the Update button.

Upon successful processing, the application condition settings are saved.

Important Notes

Configuring Application Conditions for Each Brand

Application condition settings must be configured separately for each brand.

When operating allocation rules across multiple brands, review the application conditions for each target brand.

Application Condition Settings Cannot Be Displayed Without Permissions

If you do not have read permissions for catalogs, products, and buyers, the application condition settings cannot be displayed.

If they cannot be displayed, No Permission and the required permissions are displayed.

Application Conditions with the Same Content Can Be Configured for Only One Allocation Rule

Within the same brand, application conditions with the same condition type and target combination cannot be configured for multiple allocation rules.

If another allocation rule has an ACTIVE or DRAFT application condition with the same content, saving may fail.

Operations That Cannot Be Configured Depending on the State of Allocation Rules

Depending on the state of allocation rules or application conditions, there are operations that cannot be executed.

• When the allocation rule is a DRAFT, operations to make application conditions ACTIVE cannot be performed.
• ACTIVE application conditions cannot be returned to a DRAFT.
• Application conditions cannot be assigned to archived allocation rules.

Settings Cannot Be Saved If Inputs or Selections Are Incomplete

Update can be executed when there are changes.

If there are duplicate targets, unselected targets, or changes that cannot be made with the selected status, the settings cannot be saved.

Checking the Save Status When There Are Unsaved Changes

If you leave the screen with unsaved changes, you must confirm that there are unsaved changes.