Versions Compared

Old Version 20

changes.mady.by.user Raghav Mehta

Saved on

compared with

New Version 21

changes.mady.by.user Shivani Verma (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Order Hopping refers to re-splitting and routing the items of a sub-order that a fulfilment location is not able to fulfil due to some reason.

Scope Of Work

  1. Hopping of Orders among Increff-managed Fulfillment Systems (SFS,USP and WMS) for the orders that are routed and Split by Increff Omni.

  2. Capturing and considering the store holidays, opening and closing time in Routing, Splitting and Hopping of Orders. 

  3. Accept / Reject Orders at SKU Qty level in SFS for an Order.

  4. Auto Hopping the orders after a certain time threshold (MAT) for non-responsive stores.

Trigger Points

Following are the trigger points when hopping of an order is expected to happen:

  • Order not getting accepted by the store initially.

  • Rejection during picking/packing in stores.

  • At the scheduled closure of the store.

Terminology

Store Schedule

Store schedule is a predefined time window defined by the Stores in SFS when the Stores are open and operational. Increff SFS always considers the Store schedule before doing the Hopping of a Splitted or routed order to ensure that the Sub Order which needs to hopped should not reach to a non-operational store.

...

  1. If Daily schedule is not defined on any day, the store scheduled is marked as Unscheduled for that day. The Store Schedule needs to be defined by Store initially or else the Ad-Hoc Schedule will also not be considered even if it is defined for that day.

  2. If the Store is marked as Closed in Store schedule screen or if the current time has passed from the Store Closing time defined in store schedule, then the store will be marked as OFFLINE and the store will not be eligible to get new orders.

  3. Ad-Hoc store schedule will take precedence over daily store schedule every time.

...

MAT - Maximum Acceptance Time

MAT is the maximum time that can be taken by a store to Accept / Reject the order, after which Auto-Hopping Logic of a Sub Order will be triggered. 

...

  • The time will be taken in Seconds from SFS UI. 

  • The time will be stored at the Store level masters in SFS as every store can have a different MAT.

MAT consideration on Active time of Stores 

MAT consideration will be on Active time of stores. SFS will be computing that if a store is eligible to fulfil Sub Order or not with help of RequiredBy Time (SLA) of a Sub Order.

...

This implies that if the MAT defined for any store in SFS masters is greater than the total active time of store then the Store will not be eligible for hopping process.

Acceptance Status 

Every Sub Order in OMS will have a new status field known as Acceptance Status. Following can be the possible values of Acceptance Status:

...

Info

  1. For Sub Orders being fulfilled from  WMS, 

    1. Sub Order Acceptance will be AUTO. This means WMS need not give the explicit acceptance for a Sub Order to OMS. 

    2. WMS ORDER_ACK will be treated as an Acceptance by itself in OMS. On ORDER_ACK the Sub Order Accept Status will move to ACCEPTED.

  2. For Sub Orders being fulfilled from SFS, 

    1. Sub Order Acceptance will be MANUAL. This means SFS need to give explicit acceptance/rejection for the Sub Order to OMS within the expected MAT. 

Order Acceptance/Rejection Workflow

Order Acceptance/Rejection when Increff Omni does the Splitting / Routing

When Increff OMS does the Splitting and Routing:

...

Info

In OMS Search Orders Screen,

  • User can view the Hopped Qty in SKU line item details for any order.

  • User can also view the Accept and Reject Qty in Fulfillment Items details for any order.

...

Order Acceptance/Rejection when Channel does the Splitting / Routing

When Channel/Marketplace does the Splitting and Routing:

  • INCREFF OMS needs to communicate the acceptance and rejection to the Order source (Channel/Marketplace).

  • For Sub Orders to be fulfilled by WMS:

    • Acceptance will not be communicated to the Channel/Marketplace.

    • Acceptance between WMS and OMS happens simulatenously during Order ACK

  • For Sub Orders to be fulfilled by Store:

    • Acceptance and Rejection will be communicated to the Channel explicitly through Order Notification API.

    • Acceptance and Rejection will always be communicated to the Channel on the Outward Order level.

Acceptance and Rejection of Sub Orders in SFS

Acceptance and Rejection of a sub-order can happen at 3 places in SFS:

  • Operator checks if the inventory is available or not and Accepts/Rejects the order before picking.

  • During Picking process

  • During Packing process

Acceptance and Rejection Flow before Picking

Below mentioned workflow carries out in SFS.

  1. Outward Order gets created in OMS.

  2. Sub Orders get created in OMS after splitting of Outward Orders.

  3. Sub Orders get synced to SFS.

  4. SFS Accepts / Rejects the Sub Order. In order to Accept/Reject, user can follow below mentioned steps.

    1. Go to Accept Orders under Inventory & Order section in Increff SFS.

    2. User can pply different filters like:

      1. From Date/To Date

      2. Channel

      3. Status (ACCEPTED,REJECTED,PARTIALLY_ACCEPTED)

      4. Sort By (Order ID,ORDER_TIME,REQUIRED_TIME)

      5. Sort Order (Ascending/Descending)

      6. Page Size to check all the orders which needs to be Accepted/Rejected by Store.

    3. All Orders which are eligible to be Accepted / Rejected for that Store will be displayed with the Order Status next to it.

    4. Click on Accept button which will open a overlaying screen having +/- Sign buttons and SKU details on right-side of the screen.

    5. Enter the Qty you want to Accept and Click on Accept button at the botttom. If Qty entered is 0, then the complete order will be considered as Rejected

  5. Available Inventory gets allocated to Sub Order which is Accepted by store in OMS.

  6. QTP is reduced for the Qty being rejected in OMS and deallocation happens accordingly.

  7. Following cases happen afterwards:

    1. If OMS is splitting routing source:

      1. Qty that is getting rejected also gets increased in REJECTED inventory bucket to under-expose the inventory for OMS Hopping logic so that two stores do not get stuck in an infinite loop for hopping the same sub orders again and again.

      2. Seller Cancellation won’t be allowed from OMS UI until the Sub Order is in UNFULFILLABLE status.

      3. Rejection will lead to a hopping trigger but not Auto seller cancellation.

      4. Acceptance and Rejection are not communicated to the channel.

    2. If OMS is not splitting and routing source:

      1. Rejection done by the store will lead to Auto seller cancellation.

      2. Acceptance and Rejection are not communicated to channel.

      3. Seller Cancellation won’t be allowed from OMS UI until the Sub Order is in UNFULFILLABLE status.

      4. Accept/Reject notification trigger should come from the store first before the order has moved to UNFULFILLABLE status.

  8. OMS communicates the current Accepted Quantity, Rejected Quantity, Seller Cancelled Quantity, Customer Cancelled Quantity to CIMS.

Acceptance and Rejection Flow during Picking

During Picking process of Accepted Orders,

  • If the store can fulfil a SKU in an order, the SKU can be picked.

    • Picked SKU’s can be rejected after picking till completing the order.

  • Like wise, if the store can't fulfil a SKU in an order, the SKU can be rejected.

    • Rejected SKU’s cannot be picked if AUTO_HOP flag is ON, since they are hopped to a different store.

    • Rejected SKU’s can be picked if AUTO_HOP flag is OFF before order packing is completed.

  • Virtual Combo’s must be picked/rejected together.

...

Acceptance and Rejection Flow during Packing

During Packing process of Accepted Orders, store can reject the order if store doesn't want to do fulfill the order and the order status will be marked as REJECTED.

Defining MAT (Maximum Acceptance Time) in SFS

In Configurations screen of SFS a new tab MAT is added to define the Maximum Acceptance Time by the store to Accept/Reject any order which is being hopped by Channel or Increff system.

...

  • Warning time is the time which will inform the Store operator that the MAT is about to breach.

  • Once Warning time has crossed, a warning sign will start appearing for the orders in Accept Orders screen of SFS.

...

Steps to be followed to define MAT are listed below

  1. Go to Configurations Screen under Sundry section in SFS.

  2. Navigate to MAT tab.

  3. User can define the values of MAT and Warning time which will be considered for all orders which are in REQUESTED status in Accept Orders screen

Note

  1. Warning time should always be defined less than or equal to MAT

  2. Once MAT is breached, the Order status will be marked as MAT_BREACHED, the same can be checked in Search Order Screen in SFS.

...

Location Level Splitting Configuration in CIMS

In CIMS, for any fulfillment location a user can enable/disable the location to be eligible for
Splitting-Routing of an Outward order by changing Splitting Allowed value in CIMS Client Channel pair for that fulfillment location.

Steps to be followed to Enable/Disable Splitting

  1. Go to View Client/Channel.

  2. Select a channel for which the fulfillment location Splitting Allowed should be changed.

  3. Go to Associated Locations section for this channel.

  4. Select Edit Location button on the right side of any fulfillment location.

  5. Select YES in Splitting Allowed value if the fulfillment location is eligible for Splitting or else select FALSE .

  6. Click on Update to save the changes for that fulfillment location.

Note

If a Fulfillment Location is marked with Splitting allowed as FALSE but there was some free inventory available in the fulfillment location but later on if the Splitting Allowed flag is marked as YES then the Outward Orders needs to be retried manually from Search Orders screen to be marked as ACCEPTED

Things to be noted after Sprint 70 release changes

Note

  • Creation of UOM Definition that contains an SKU which is already a part of Virtual SKU definition will not be supported if any splittable Open Outward order is present in Omni system from Sprint 70 onwards

  • For any Outward Order that needs to be splitted by INCREFF OMS and contains a Virtual Combo SKU whose child SKUs are also part of some UOM definition will move to FAILED order state in CIMS as the case is not supported from Sprint 70 onwards.

...