/ Introduction

There are many installations with a very large product catalogue and only a little fragment is used. 

For that reason, there should be created a Product archive for inactive products.

An inactive product is a product which is not assigned to anything like a display of v4k etc.

/ Active product

A product is considered active if assigned to a display, a vision or a vision4k.

/ Inactive product

An inactive product will not have any audit

No product template, product schedule will be saved

It is not possible to set position on an inactive product

Inactive products will not be included in recalculation jobs

Only Product number, reorder code, description and product references will be saved on an inactive product.

Manual fields will still work on an inactive product


/ Archive routine

A routine job will run every night to archive products in active product catalog which is no longer active.

An active product will be moved to inactive when it have not been active for 14 days

Archive mean move the active product to inactive product.

When a product being archived the audit trail will be removed.


/ Deactivation of product archive

It will be possible on installation and groups with product catalog to disable product archive. If product archive is disabled, all products will be treated as active. This is useful when using a price checker or similar on installation.


/ Configuration and functions

From GUI it would be possible to deactivate the product archive for an installation or group

It should be possible to start activation of all products in catalog, so the products will be available for for example an initial installation assign

Add action to inactive product list to activate selected product


/ Activation of archived product

Import server will handle the retrieve data step, at the moment this is activation of an inactive product.

Flow is:

  • Retrieve product to activate from worker table
  • Attempt to retrieve the product and data from the product archive
  • Use the data in product archive to get the product object which can be saved to active product catalog. Same routine as when a product is imported
  • Update worker table with success (product found) or failure (product not found)

Later, we might be able to add logic to retrieve the product data from external sources.


/ Import flow

When a file is retrieved for import, we will quickly mark which product is active and which is inactive.

Active products will be imported as today

Inactive products will need the product number, reorder code, description, product references and then it will be stored in the product archive with the raw data.

No further processing or audit will be stored.

Inactive products would still need to take merge variables into account