| 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.
...
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.
...
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:
...
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.
...
This implies that if the MAT defined for any store in SFS masters is greater than the total active time of the store from the instant of order placement till the SLA of the order then the Store will not be eligible for the hopping process.
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 but not all the 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.
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 |
|---|
|
...
INCREFF OMS doesn’t need to communicate the acceptance and rejection to the Order sourcechannel.
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 is tried to hop to some other fulfilment fulfillment location.
The Qty remaining that INCREFF OMS is not able to hop in the end is still associated with the original Sub Order and Sub Order remains in UNFULFILLABLE status.
If Sub Order Fulfillment Type is SINGLE_SHIPMENT_PARTIAL, then the Sub Order will be allowed to process and whatever Qty 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 Qty can be manually cancelled by seller from OMS UI if requiredIn 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,
|
...
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.
...
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 Accept/Reject, user can follow below mentioned steps.
Go to Accept Orders under Inventory & Order section in Increff SFS.
User can pply 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 to be Accepted / Rejected for that Store will be displayed with the Order Status next to it.
Click on Accept button which will open a an overlaying screen having +/- Sign buttons and SKU details on right - side of the screen.
Enter the Qty you want to Accept and Click on Accept button at the botttombottom. 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 being rejected in OMS and deallocation happens accordingly.
Following The following cases happen afterwardsafterward:
If OMS is splitting routing source:
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.
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 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 the current Accepted Quantity, Rejected Quantity, Seller Cancelled Quantity, and Customer Cancelled Quantity to CIMS.
...
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
...
Maximum Acceptance Time are listed below
Go to Configurations Screen under Sundry section in SFS.
Navigate to MAT tab.
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
...