Item

An item is managed with the dimensions size range, size, and color. This makes it easier to work with matrix representations. An item can have multiple colors, size ranges, and sizes.

Item Card

Item Number (1 & 2)

The item numbers can be alphanumeric, max. 20 digits. A different number series can be stored for each product group. Useful when using items as ingredients.

Item number 2 can be used as an additional key for the item, e.g. for descriptive item numbers or for item numbers from legacy systems.

Item Colors

Colors are managed in the ERP. Various colors can be assigned to an item.

Valid seasons can be assigned to the item colors. When a new item color is created, a season color is automatically created with the season of the item card. If a color is transferred to another season, the season must be entered manually for the corresponding colors.

No seasonal colors need to be maintained for NOS colors.

Properties of the Item Color

The NOS markings on the item are used as a maintenance aid; they are transferred to the colors and can be adjusted there.

• NOS (Yes / No)
• Resorting via (target stock, sell-off)

Seasonal Colors/Seasonal Collections

Each item is initially assigned to exactly one collection and season (in which it was created). Multiple seasons can be assigned to the item colors. A collection belongs to one season.

Identification of the Item Variant

The selection of the active sizes from the respective size range is done by setting up the variants. For each item color, the active sizes of the size range must be selected - not all sizes of the size range have to be used. Each item variant uniquely identifies an item in a color, a size range, and a size.

The items can be identified in the following ways (Identification Number Type field):

• Standard (item number)
• EAN (item variant)
• Group identification number (lot numbers)
• Single identification numbers (serial numbers)

Assortment/Lot

The BE-Fashion standard offers the option to define one or more lots per item. Lots are used to represent cross-docking processes and to represent packaging units in the warehouse. They are supported in purchasing and sales.

Lots can be single-color or multi-color lots. They can be used as entry aids on documents. A lot consists of different variants of an item. The corresponding quantities are predefined for each size-color combination. A lot thus forms a pre-packed grab unit. A separate EAN/GTIN can be created for identification for each lot.

Inventory tracking is carried out at the item variant level.

Prices

Several different conditions can be maintained per customer. The conditions are related to the order type, e.g. for differentiated discounts.

When changes are made to the customer, e.g. payment terms/shipment terms, orders already entered remain unaffected. The change then applies to new entries. An exception is the blocked flag.

Purchase Prices

Purchase prices can be stored on the item per vendor, currency, and start/end date. Prices can be maintained down to the variant level. The purchase price is written to a price table manually, via order, or from EDI. It can subsequently change.

A history of the purchase price on the item is provided by giving existing price lines an end date and creating new price lines.

Sales Prices

On the item, prices are maintained with a start and end date and a reference to the customer price group. These prices can be entered in € or other currencies (per line). A distinction is made between item prices and variant prices - meaning that if color prices are used, all variants must be created with a separate price (variant prices).

For each price line, it can be decided whether it applies to one customer, all customers, or a customer price group. An RRP (recommended retail price) can be created per sales price line.

Conditions

Several conditions can be assigned to the customer and displayed in an overview on the customer. These are defined by season and order type and include value date days, start date, as well as a deviating payment term, payment method, deliverer, and discounts. Up to 5 discounts can be specified, along with control over whether the discounts apply in a chain or as an addition.

Each customer can have a default condition stored, which is automatically applied to the sales order. The condition can be changed manually per sales order. The total discount of the condition (as a sum or chain) is applied to the order header as a single value. All lines subsequently entered receive this discount as a percentage value on the line. A subsequent change per line is possible. The line discount can be posted as an amount, according to setup, to a separate discount account.

If the conditions for the customer change, the existing conditions can be overwritten, or new conditions can be created.

In addition to the conditions (discounts), which are order-relevant, there are further discounts that are not order-related. These can relate to a pre-order phase and thus several orders, and are, for example, subsequent bonuses at the end of the season.

Document Texts (Formerly Text Modules)

In BE-Fashion, any document texts in any language can be maintained for the item. These multi-line texts can be inherited by documents and, depending on the content, printed in the header, in the line, or in the footer of the document.

As of Version 26.4

There was previously a dual use of the term Text Module in German-language Fashion. This term originally comes from the BC standard and refers to text sections that can be automatically transferred to the lines of purchase, sales, or service documents.

In Fashion, “text modules” also existed, whose function is, however, more far-reaching than the standard feature. The so-called “Extended Text Management” can be used in a time- and language-controlled way to insert additional texts in the printed documents of purchasing and sales - without increasing the document lines themselves. Texts can be transferred as header, item, and line texts within the lines.

To avoid confusion when using the feature, the Fashion text modules are now found on all pages as Document Texts as of Release 26.4. Both functions (text modules and document texts) can be used in parallel.

For the application in BE-Fashion, see order entry, Text Management section.

Notes on Fields