| Table of Contents |
|---|
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
Hopping of Orders among Increff-managed Fulfillment Systems (SFS,USP and WMS) for the orders that are routed and Split by Increff Omni.
Capturing and considering the store holidays, opening and closing time in Routing, Splitting and Hopping of Orders.
Accept / Reject Orders at SKU Qty level in SFS for an Order.
Auto Hopping the orders after a certain time threshold Maximum Acceptance Time(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.
...
Daily Store Schedule- This Store Schedule will be defined with the Opening and Closing time of the store for all 7 days of the week.
For example:
...
Day of the Week
...
Opening Time
...
Closing Time
...
1
...
10:00
...
19:00
...
2
...
10:00
...
19:00
...
4
...
10:00
...
19:00
...
7
...
00:00
...
00:00
Ad-Hoc Store Schedule- This Store Schedule will be defined with the Opening and Closing of the store for the occasions like National holidays or Extended Store Operation time due to some festive season.
For example:
Date | Opening Time | Closing Time |
|---|---|---|
26-01-2023 | 10:00 | 19:00 |
15-08-2023 | 10:00 | 19:00 |
31-12-2023 | 00:00 | 00:00 |
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note:
|
...
|
...
|
...
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.
Note:
The time will be taken in Seconds hours from SFS UI.
The time will be stored at the Store level masters in SFS as every store can have a different MAT.
...
Maximum Acceptance Time 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.
Please keep note of below mentioned things related to Order allocation to a Store location and Hopping process to other store
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Note: Active Hrs and Store Allocation
|
...
|
...
|
...
|
This implies that if the MAT defined for any store in SFS masters will be greater than the total active time of store then the Store will not be eligible for hopping process.
...
Order Hopping will Happen in below cases
|
Acceptance Status
Every Sub Order in OMS will have a new status field known as Accept Acceptance Status. Following can be the possible values of Accept Acceptance Status:
REQUESTED - The location has been requested to fulfill the sub-order.
ACCEPTED - The location has ACCEPTED to fulfill the entire sub-order. In the case of WMS, an order moves to this status on ORDER_ACK.
REJECTED - The location has REJECTED to fulfill the entire order
PARTIALLY_ACCEPTED - The location has accepted to fulfill one or more qty Qty but not all the qty Qty of the SKU line item of sub-order.
AUTO_REJECTED - The store did not accept to fulfill the sub-order within the MAT time and sub-order got auto-hopped by OMS.
...
.
Spit Threshold Breached Status
In Outward Orders section, there is a new status SPLIT_THRESHOLD_BREACHED added.
If an Outward order is retried 20 times to be hopped to various fulfillment locations but either all locations are disabled or all stores are not eligible for hopping(due to MAT breach or store being non-operational) with Splitting Allowed in CIMS, then the status of Outward Order will be marked as SPLIT_THRESHOLD_BREACHED.
| Info |
|---|
|
...
|
...
|
Order Acceptance/Rejection Workflow
Order Acceptance/Rejection when Increff Omni does the Splitting / Routing
When Increff OMS does the Splitting and Routing:
INCREFF OMS doesn’t need to communicate the acceptance and rejection to the Order sourcechannel.
If Accept Acceptance Status is PARTIALLY_REJECTED/REJECTED when:
If The Sub Order Fulfillment Type is BLOCK_COMPLETE, the Sub Order moves to the is in the UNFULFILLABLE state on rejection.
The Sub Order will be is tried to hop to some other fulfilment fulfillment location.
The qty’s Qty remaining that INCREFF OMS is not able to hop at in the end is still is associated with the original Sub Order and Sub Order remains in UNFULFILLABLE status.
If Sub Order Fulfillment Type is SINGLE_SHIPMENT_PARTIAL, the Sub Order will be allowed to process and whatever is not fulfilled from location gets Seller cancelled automatically as per the usual workflow.
Auto Seller cancellation does not happen in this case and in the case of Unfulfillable quantity of order line item even after hopping, the quantity can be seller cancelled from OMS UI if required manually.In this scenario, automatic seller cancellation does not occur. Additionally, even after hopping, if the quantity of an order line item remains unfulfillable, the seller can manually cancel the quantity from the OMS UI if necessary.
| Info |
|---|
In OMS Search Orders Screen,
|
...
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 implicitly 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 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 checks if the inventory is available or not and accepts or rejects Accepts/Rejects the order before picking.
During Picking process
Process steps and screenshots required
During Packing process
...
Acceptance and Rejection Flow before Picking
Below mentioned workflow carries out in SFS.
Outward Order gets created in OMS.
Sub Orders get created in OMS after splitting of Outward Orders.
Sub Orders get synced to SFS.
SFS Accepts / Rejects the Sub Order. In order to acceptAccept/rejectReject, user can follow below mentioned steps.
Go to Accept Orders under Inventory & Order section in Increff SFS. (Screenshot of Accept orders screen is required)
User can apply different filters like:
From Date
/To Date
Channel
Status (ACCEPTED, REJECTED, PARTIALLY_ACCEPTED
)
Sort By (Order ID, ORDER_TIME,REQUIRED_TIME)
Sort Order (Ascending/Descending)
Page Size to check all the orders which needs to be Accepted/Rejected by Store.
All Orders which are eligible for Acceptance / Rejectance to be Accepted / Rejected for that Store will be displayed with the Order Status next to it.
Click on Accept button which will displayopen an overlaying screen having +/- Sign buttons at top right of the screen and Accept button at bottom of and SKU details on right side of the screen.
Enter the Qty you want to Accept and Click on Accept button at botttomthe bottom. If Qty entered is 0, then the complete order will be considered as Rejected
Available Inventory gets allocated to Sub Order which is Accepted by store in OMS.
QTP is reduced for the qty’s Qty being rejected in OMS and deallocation happens accordingly.
Following The following cases happen afterwardsafterward:
If OMS is splitting routing source source:
Quantity Qty that is getting rejected also gets increased in REJECTED inventory bucket to underexpose 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.
Seller Cancellation won’t be allowed from OMS UI until the Sub Order is in UNFULFILLABLE status.
Rejection will lead to a hopping trigger , but not auto Auto seller cancellation.
Acceptance and Rejection are not communicated to the channel.
If OMS is not splitting and routing source:
Rejection done by the store will lead to Auto seller cancellation.
Acceptance and Rejection are not communicated to channel.
Seller Cancellation won’t be allowed from OMS UI until the Sub Order is in UNFULFILLABLE status.
Accept/Reject notification trigger should come from the store first before the order has moved to UNFULFILLABLE status.
OMS communicates to CIMS the current Accepted Quantity, Rejected Quantity, Seller Cancelled Quantity, and Customer Cancelled Quantity to CIMS.
.png?version=1&modificationDate=1681309934721&cacheVersion=1&api=v2&width=680)
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.
Steps and Screenshots required
Acceptance and Rejection Flow during Packing
Steps and Screenshots required
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 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 (Screenshot required).
...
Steps to be followed to define
...
Maximum Acceptance Time are listed below
Go to Configurations Screen under Sundry section in SFS.
Navigate to MAT tab (Screenshot required).
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
| Infonote |
|---|
|
...
Location Level Splitting
...
Configuration in CIMS
In CIMS, Now 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 any that fulfillment location.
Steps to be followed to Enable/Disable Splitting
Go to View Client/Channel.
Select a channel for which the fulfillment location Splitting Allowed should be changed.
Go to Associated Locations section for this channel (Screenshot required).
Select Edit Location button on the right side of any fulfillment location (Screenshot required).
Select YES in Splitting Allowed value if the fulfillment location is eligible for Splitting or else select FALSE (Screenshot required).
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 |
|---|
|