Products

OrderFlow can support numerous products types, and can be configured to process certain product types differently. Some product types currently supported by OrderFlow are:

Type	Description
Default	The default product type. Typically these are physical products that can be stored, and go through all of the standard fulfilment processes.
Batch Tracked	Associated product lot references, useful if there is requirement to identify source batches for products received or despatched.
Bundle	A grouping of individual physical products (SKUs) which can be sold and despatched as a logical unit.
Composite	Created or assembled using one or more non-sellable constituent raw component products.
Free Gifts	Does not require picking, but can be scanned to pack and will appear on customer paperwork.
Insert	Does not require picking, but can be scanned to pack and will not appear on customer paperwork.
Packaging	A stockable packaging product, for example, a jiffy bag or cardboard box.
Raw Component	A non-sellable component which forms part of a composite product, for example via a kitting or assembly process.
Virtual	Usually a product with no physical form that does not participate in stock management operations, for example a downloadable application.

We need to know the type of every product that you intend to despatch from your warehouse, and any workflow requirements associated with these types.

In the most simple cases, your warehouse will be storing and despatching default products using 'standard' fulfilment processes.

Some further aspects to consider:

Do all of your sales channels use the same product code to identify an individual product?
Do any of your products require an element of personalisation?
Are datasheets (product-specific printable documents) required for any of the products you ship?
Are products with the same SKU interchangeable, or are there factors such as remaining shelf life, condition or size which mean that interchangeability cannot be guaranteed?
What is the threshold level that should trigger the re-ordering of a product?
Do you wish to use product attributes - such as those listed in the Integration chapter - to determine your courier selection script?
Do you wish to use product attributes to determine your target putaway locations?
If the answer to the previous two questions is yes, please consider if those product attributes should be made mandatory, and where OrderFlow should get these attributes from (for example, the eCommerce system, or via an uploadable product catalogue spreadheet)

You should also consider how you would like to identify your products.

Do you wish to relabel products using your own barcodes, or rely on barcodes provided by customers?
If so, do you have any special requirements on what information appears on your product labels?