Perishable Item Processing on First Cry

This document describes the mechanism of exposing the perishable items on FirstCry using Increff Omni.

Details Required

These details are required for all the brands that are going live on first cry. 

1. SKU

2. Category

3. Expiry Date

4. Manufacturing Date

5. Shelf Life in Days (Expiry - Mfg Date)

6. Sellabe percentage Shelf Life

Sellabe Percentage Shelf Life 

A category Level value. 

Which tells how much % of shelf life should be consumed after which this product will become unavailable in First Cry. 

Ie. if the value is 90%. Then this means that once a product crosses its 90% shelf life, it will become unavailable.

We will take minimum of all the categories and define a MinSellableShelfLife

MinShelf Life (in Days) 

Using the data from the above table, we can compute a minimum number value for shelf life across all categories and skus. Let's call it minShelfLife.

SKU Level Tolerance

This denotes that when only X days are remaining, make the product batch unavailable. And Start sending the next batch inventory update. 

Tolerance in days  =   ( expiry date - mfg date ) * (1 - sellable percent of shelf life / 100 ) 

For every SKU client will define a SKU level tolerance based on actual “sellable % shelf life” of that SKU

Implementation Logic in Increff Omni Integration Module 

Proxy will have a hardcoded value set for MinSellableShelfLife and minShelfLife.

CIMS will send expiry date, and using expiry date, MinSellableShelfLife and minShelfLife proxy will compute a manufacturing date and pass on to First cry.

This will ensure whatever products’s inventory update we are sending, will always be sellable on Firstcry.

Once the product actually crosses the SKU wise tolerance, CIMS will stop sending its update and start sending the next batch information to the proxy.