The following page describes the logic of sending data from a White Glove Outbound (Sales Order) Booking to the WMS as a Sales Order.
Refer to the source booking data Booking Domain Model in conjunction with the WMS documentation for sending a Sales Order : Load Sales Orders
Load Sales Order API Call
The following tables show the different sections of the Load Sales Order API call to the WMS, and how to populate them, based on the White Glove Booking Domain Model items. Note that only the fields within the WMS Load Sales Order API call are listed here; all other fields are optional and must not be populated in this implementation.
Sales Order Main Section
WMS API field | From White Glove Booking Model |
|---|---|
Sales Order Number | Booking. Booking Ref |
Sales Order Reference | Booking. External System Source. Source Ref |
On Hold | FALSE |
Courier Name | Booking. Handover Organisation. Code for the instance of Handover Organisation where its Role = HANDOVER TO CARRIER |
Notes | Concatenate the following Information fields if they are present in the White Glove booking: Booking. Collection. Additional Info Booking. Delivery. Additional Info Booking. Handover Organisation. Additional Info for the instance of Handover Organisation where its Role = HANDOVER TO CARRIER Booking. Transit Additional Info |
Special Instructions | Concatenate the following Information fields if they are present in the White Glove booking: Booking. Collection. Additional Info Booking. Delivery. Additional Info Booking. Handover Organisation. Additional Info for the instance of Handover Organisation where its Role = HANDOVER TO CARRIER Booking. Transit Additional Info Booking. Change Additional Info |
Order Type | “Wholesale” |
Scheduled Ship Date | For phase 1, this value must be populated from the value provided manually by the SEKO operator as part of workflow planning (although such value will be defaulted from Booking. Collection. Latest By) |
Sales Order Header Section
WMS API field | From White Glove Booking Model |
|---|---|
DC Code | Booking. Collection. Location. Location Code (note: this should be the Warehouse code provided in the Sales Order booking) |
Ship To Company Section
WMS API field | From White Glove Booking Model |
|---|---|
Company Code | The Code of the White Glove Partner selected as the “Supplier” of the outbound sales order (i.e. the supplier of White Glove services). This will be manually selected by the SEKO operator on the front-end, as part of confirmation of sending the WMS Sales Order. |
Company Description | This description will be populated from the corresponding lookup against the select Company Code above, from static data, by accessing the fully Company Name |
Delivery Details Section
WMS API field | From White Glove Booking Model |
|---|---|
Line1 | The address line 1 for the selected Final Mile Facility address. This will be manually selected by the SEKO operator on the front-end, by selecting a location of type “Final Mile Facility” associated with the selected Company Code above, as part of confirmation of sending the WMS Sales Order. |
Line2 | As above; populated from the selected Final Mile Facility location |
Line3 | As above; populated from the selected Final Mile Facility location |
Line4 | As above; populated from the selected Final Mile Facility location |
City | As above; populated from the selected Final Mile Facility location |
County | As above; populated from the selected Final Mile Facility location |
Postcode Zip | As above; populated from the selected Final Mile Facility location |
Country Code | As above; populated from the selected Final Mile Facility location |
Sales Order Line Item Section
This section is repeated as a list for each Booking. Goods instance in the sales order booking
WMS API field | From White Glove Booking Model |
|---|---|
Line Number | Incrementing integer, starting from 1 (see ‘n' below) |
Product Code | Booking. Booking Goods(n). SKU |
Quantity | Booking. Booking Goods(n). Quantity. Quantity |
ASN Number | If this sales order booking has an ‘allocated goods from’ reference pointing to an inbound Transfer Order or ASN booking from the client, use Booking. Booking(allocate from). Booking Ref |