Updating Article Master

• Login to Omni System and navigate to OMS.

• Click on Products.

• Click on Product in Product Setting if you want to upload new SKUs.

• Select a client.

• Click on Download Template. 

• Fill the CSV file and click  on UPLOAD

While creating file template for new SKU upload, please do following basic checks before uploading

• Populate data for all new SKUs

• There should be no duplication of any SKU in the file

• Ensure that if the Client SKU ID is a scannable field on the product, then barcode should have the same value, otherwise different value. Barcode should be a scannable field as GRN happens on barcode. Once uploaded, the barcode cannot be updated.
• SKU already present in Omni OMS should not be added to this file
• All mandatory fields must have values for all new SKU rows
• Image url is not mandatory field, however it is very important for item QC at the time of GRN and order processing
• Image url should be absolute url where respective image is hosted
• axRule should be as per Taxation Rules. 
• Upload limit is 50,000 rows per file.

Note – Row 2 in the screenshot below just describes each field. Please remove this row from the final template you are about to upload.

Template 1

Template 2

Note: If the client does not use UOM, the bulkBreakThreshold column is to be left empty.

Once the file is ready to be uploaded,

1. Select the Client against whom this update is needed.
2. Choose the file in CSV File.
3. Click Submit.

Edit Existing SKUs

• CSV template for updating the existing SKUs will be different. Only the selected
   attributes will be processed in the CSV file.

• The user can download the template file from the same screen after selecting the upload type as Update. 

• You have to populate the data only those fields to be updated, the rest of the fields can be left blank.

Do refer to the links below to do the basic checks while uploading the file.

Update existing article master data in Omni

Master - Products if Expiry feature is enabled

      Product Masters in OMS will have an identifier (is_perishable) which is true for perishable products and          false otherwise.

Product Master Creation of Perishable SKUs

      Following are the steps for creating the Product masters of perishable SKUs:

1. Go to the Products screen in OMS.

2. In the New tab, select Type as Product Master.

3. Select a Client from the list of clients in the dropdown.

4. Download the CSV template.

5. If the expiry feature is enabled for the selected client, the downloaded CSV template will have an additional column is_Perishable.

6. The accepted values for this field are true / false.

7. If is_Perishable is set as true, then the corresponding Client SKU ID will be created as a perishable SKU in the system.

Mark SKUs as Perishable

To mark SKUs as Perishable -  Select the client and upload the CSV file with all the SKUs that needs to be marked Perishable.

Updating the flag for virtual and perishable SKUs

Changing Virtual SKU Flag

Note: Since this is a data updating to be done in backend with help of queries we should avoid doing it frequently. Refer the above guidelines hence before uploading these flags for master data.

Feasible Cases: If below-mentioned case conditions are verified then we can update the Virtual definition for an SKU in the system.

Case 1: Changing the Virtual Flag from True to False

1. No orders should be present in the system for the SKU.
2. No inventory for parent virtual SKU in system.
3. No virtual SKU definition exists for SKU.

 Case 2: Changing the Virtual flag from False to True:

1.  No orders should be present in the system for that SKU.
2.  No inventory for that SKU should be present in the system.

Unfeasible Cases: Below Mentioned are the cases in which we cannot change the Virtual SKU definition in the system.

• Orders are present in our system in any state (Unfulfillable, Fulfillable, Processing, Completed)

• Inventory is present for SKU in system

  • Virtual SKU inventory if SKU is defined as Virtual

  •  Available Inventory if SKU is defined as non-virtual

• Returns are created for the orders which are already processed from the system.

Architectural Challenge

It is not possible to maintain two different states of the same SKU for different Orders. One SKU can either be virtual or non-virtual at a time. If an order is dispatched with Virtual SKU true and we change its flag back to false, we cannot process returns based on it. 

Also, Inventory will move to Incorrect state as during Inventory exposure inventory of an SKU say A defined as A=B+C was exposed as cumulative inventory of B and C but during returns A is just expected to be A.

Returns is just one aspect; a system cannot be designed keeping in consideration the different nature of the same SKU at different points of time.

For Example:

For SKU A defined as A=B+C, and inventory of A is 10 in the system, now If we want to make virtual flag for A as false, the inventory of A should be zero in the system and so does the exposure to marketplaces which is not possible for us to do as it might lead to inventory inconsistency which is an activity which we cannot do (Manually Updating the inventory for SKU listings in the system).

Changing SKUs to Perishable or Non- Perishable.

Note: Since this is a data updating to be done in backend with help of queries we should avoid doing it frequently. Refer the above guidelines hence before uploading these flags for master data.

Feasible Cases

If below mentioned case conditions are verified then we can update the Perishable definition for an SKU in system.

Case 1

Changing the  from Perishable True to False

• No orders should be present in the system for the SKU.

• No inventory for parent virtual SKU in system.

• No virtual SKU definition exists for SKU.

Case 2

Changing the Perishable  from False to True:

•  No orders should be present in the system for that SKU.

•  No inventory for that SKU should be present in the system.

Unfeasible Cases

 Below Mentioned are the cases in which we cannot change the Perishable SKU definition in the system.

• Orders are present in our system in any state (Unfulfillable, Fulfillable, Processing, Completed)

• Inventory is present for SKU in system

  • Perishable SKU inventory if SKU is defined as True

  •  Available Inventory if SKU is defined as False

• Returns are created for the orders which are already processed from the system.

Edge case

If a failed order comes in CIMS for one of the SKUs and the order is not synced in OMS even after retrying the order, then it is likely because the minimum expiry was not marked as null.