Home arrow Inventory Management arrow Retail Inventory Management arrow Merchandising Structure & Coding
Print

Merchandising Structure & Coding

Merchandising structure
MINDER provides a three-level Merchandising Structure to facilitate ‘top-down’ merchandising management. While individual users can select their preferred terms, those most frequently used are:

  • Department
  • Class(ification)
  • Item or Style

In addition, however, you can optionally have both Class and Items/Styles further sub-divided into colours and sizes, and you can assign Departments ‘Group’ owner codes to facilitate selective reporting.

Trading structure
MINDER provides a Zone facility that enables stores to be logically grouped for reporting and other system purposes.

When Zones are used, each store has an ‘owner’ zone, and standard zone based reporting will report stores accordingly. However, it is also possible to create ‘structured’ Zones to group stores in ways that suit the needs of individual MINDER users, e.g. by state, by size, by the merchandise range that they carry, etc. Provision has been made for the user to be in control of the sequence in which the stores within a ‘structured zone’ print. Rather than simply printing in store number sequence, the stores are printed in the sequence they are set-up in the Zone cross-referencing. For your convenience, you are not restricted to using the term Zone; we can set a parameter for you to change the term to one you may prefer such as Area, State, etc.

Merchandise Coding
Department, Class and Item codes can be up to 14 alpha-numeric characters in length.

ImageWhen colour/size facilities are used, the Item/style component can be up to 8 alpha-numeric characters, and both colour and size codes can be up to three characters in length. The concatenation of a Style code, a colour code, and a size code is referred to as an SKU (i.e. Stock Keeping Unit), and can be up to 14 characters.

The relationship between an Item/Style and a Class, a Class and a Department, a Department and a Group, is an attribute held in the database, and therefore does not have to be embedded in the code identifying an individual item of merchandise.

The advantages of this to users of MINDER include:

  • Merchandise codes are smaller, and therefore more efficient to work with, and allow for the use of more compact price tickets.
  • It is far easier for you to reorganise your merchandising structure, e.g. change the Class an Item belongs to, change the Department it belongs to, etc. It can all be done without having to re-ticket the merchandise.