Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
The client uses the “Load Sales Orders” service. This action immediately creates Sales Orders with a status of “Create”. The client can initiate this service at any time.
No dispatches are created for these Sales Orders right away. Instead, they are placed in a queue.
These queued Sales Orders are processed during scheduled runs, which are all in UTC, depending on the “Hold Time” Option for each Client.
If all items on a Sales Order are in stock, the status of the Sales Order changes to “Commit”. A Dispatch is then created for all the items.
If a Sales Order has multiple items and only some of them can be fulfilled, and the Hold Hours have not yet expired, the order is returned to the queue.
If a Sales Order has multiple items and only some of them can be fulfilled, and the Hold Hours have expired, the status of the Sales Order changes to “Commit”. A dispatch is created for the fulfilled items. The Sales Order is marked as a “Back Order”. As soon as the remaining items in a Back Order are available in stock, another dispatch is created.
If a Sales Order has one line or one SKU but multiple quantities and only some of them can be fulfilled, the order remains in the queue until all quantities can be fulfilled.
...
Back Order Cancellation
Orders that have been pushed to Seko360, where no dispatch has been created yet, can be deleted through the iHub using the “Load Sales Order Cancel” and “Load Sales Order Cancellations” services. These orders can also be cancelled using the order cancellation process in the front end.
If there are lines on an order that have not been fulfilled (known as back order lines), these can be cancelled as well. However, it’s important to note that you cannot specify which lines to cancel. Instead, an order cancellation request will mark the sales order as partially cancelled and any back order lines will no longer be processed.
In the case of a back order existing for a dispatch, the client needs to call the iHub “Load Dispatch Cancellation” service and provide the “Dispatch ID” and Reason Code. To obtain the “dispatch Id”, the client should call the “Retrieve Sales Order Status” service and provide the Sales Order Number. This process ensures that even partially fulfilled orders can be managed effectively.
...
Back
...
Business Intelligence → DC Reports → Outbound Reports → Backordering
https://seko.atlassian.net/wiki/spaces/SMAN/pages/2842955470/WMS+-+Outbound+Reports#Backordering
Order List
Log In to WMS Client Interface
Navigate to Sales Channels -> Back Orders -> Back Order List
Shows back orders in queue (what lines have been fulfilled, what lines have not been fulfilled, current available qty etc)
This section displays Sales Orders currently in the Order Processing Queue with a status of Partially Processed.
For lines where the Requested Quantity exceeds the Available Quantity, the Available Quantity will be highlighted in red, making it easy to identify which lines cannot be fulfilled.
Once a Sales Order is fully processed or its back order lines are canceled, it will be removed from this list.
Note that changes may not be immediate; users might need to wait for the next scheduled run of the Order Processor for updates to take effect.
The Order Processor handles the processing of these queued orders.
...
Back Order Schedule
Log In to WMS Client Interface
Navigate to Sales Channels -> Back Orders -> Back Order Schedule
Shows all scheduled times of the Order Processer per DC so clients can see when the next run will take place as well as future runs for the day
Reports - Back Orders
Business Intelligence → DC Reports → Outbound Reports → Backordering
https://seko.atlassian.net/wiki/spaces/SMAN/pages/2842955470/WMS+-+Outbound+Reports#Backordering