Warehouse Fulfillment Lifecycle
The Warehouse Fulfillment Lifecycle BPM illustrates the process of fulfilling an order allocated to a warehouse, followed by synchronizing fulfillment updates to HotWax Commerce.
Last updated
The Warehouse Fulfillment Lifecycle BPM illustrates the process of fulfilling an order allocated to a warehouse, followed by synchronizing fulfillment updates to HotWax Commerce.
Last updated
HotWax Commerce, being as an Order Management System, finds the best location to fulfill an online order from. In the event where an approved order is brokered and allocated to warehouse fulfillment location, HotWax Commerce synchronizes allocation details with the Warehouse Management System (WMS) or ERP systems like NetSuite. Once the order is fulfilled, HotWax Commerce then also synchronizes the fulfillment updates from the WMS or ERP systems.
Items that have been successfully allocated to warehouses have fulfillment status "Reserved" in HotWax Commerce. A scheduled job in HotWax Commerce then synchronizes the allocation details of orders with the ERP or WMS leveraged to fulfill warehouse orders.
Most of our customers use NetSuite ERP to fulfill orders from their warehouses. In this scenario, the order is already present in NetSuite with a status of "Pending Fulfillment" because HotWax Commerce synchronizes orders to NetSuite as soon as they are "Created" in HotWax Commerce.
For orders allocated to warehouses, a scheduled job in HotWax Commerce generates a feed containing order line items with their respective fulfillment locations and synchronizes it with NetSuite. Once NetSuite’s script reads and consumes this feed, the fulfillment location details is updated on the order item.
Learn more about order synchronization from HotWax Commerce to NetSuite
When the warehouse fulfillment team begins the fulfillment process for an order item, an item fulfillment record is automatically generated in NetSuite. Upon picking, packing, and shipping the item, multiple actions take place in NetSuite:
The item fulfillment record is marked as "Shipped".
The initial order status "Pending Fulfillment" is updated to "Pending Billing".
Finally, once the invoice is auto generated, the order status is updated from “Pending Billing” to “Billed”. This marks the completion of the order lifecycle in NetSuite.
In the event where a fulfillment team is unable to find an order item to be fulfilled, they reject that specific order. A scheduled job in HotWax Commerce imports the rejected order item feed from NetSuite. Subsequently, all rejected orders are moved to the rejected queue in HotWax Commerce so that they can be rebrokered and allocated to a new fulfillment location.
A scheduled job in HotWax Commerce synchronizes all the fulfilled order item details from NetSuite and multiple actions take place:
The fulfillment status of the order item is updated from “Reserved” to “Shipped”.
In the event of a partial shipment, the fulfillment status of the shipped items will be updated to "Shipped", while the order itself will remain in the "Approved" status until all items have been shipped.
When the fulfillment status of all items in an order is marked as “Shipped”, the order status is updated from "Approved" to "Completed" in HotWax Commerce.
Once the order is marked as “Completed” in HotWax Commerce, a scheduled job in HotWax Commerce sends the tracking details to eCommerce and marks the orders “Fulfilled”.
If a retailer uses another WMS or ERP to fulfill warehouse orders:
HotWax Commerce will synchronize allocation details with the ERP or WMS in place.
HotWax Commerce will also synchronize fulfillment updates from the ERP or WMS to mark order "Completed" in HotWax Commerce and "Fulfilled" in eCommerce.
