What is a Sales Order

...

A Sales Order is sent in the form of an Outbound booking by the client, on behalf of their customer, to SEKO. The sales order then takes the following journey:

• Create Sales Order in White Glove System (WGS)

• WGS creates a billing reference in CargoWise (a shipping/logistics/financials system used by SEKO)

• Send WGS update costs associated with the Sales Order to WarehouseUpdate produce a Purchase Order for work costs associated with the Sales Order

• Warehouse picks, packs and dispatches information

• WGS records scheduled work date for customer of SEKO Client

• WGS send Sales Order to Warehouse

• SEKO 360 Warehouse pick, pack and dispatch goods

• SEKO 360 Warehouse Dispatch Sales Order and send Push Notification to White Glove system

• WGS Process Dispatched Dispatch Notification

  • Some information has to be entered manually onto White Glove system including

    • packaging details

    • confirmation of Purchase Order

    • confirmation that expected costs have been added

• WGS Send “Pre-Alert” email to Final Mile Facility, which is

  known as a “White Glove Partner”

  also the White Glove Partner. This includes

  • Information on the goods being received

  • Booking confirmation URL for White Glove Partner to schedule the work with the end customer

  • Purchase Order based on known information about the job

• WGS records arrival of goods at Final Mile Facility

• White Glove Partner

  to complete

  completes the work and give information on extra costs incurred

• WGS records completion status of job (completed successfully / with issues / aborted)

• WGS update actual costs based on completed work

• WGS Send a revised Purchase Order for

  complete work

  completed work to Final Mile Facility / WG Partner

• White Glove Partner sends invoice

• WGS charges SEKO Client through CargoWise (CW1)

• WGS receives payment from SEKO Client through CargoWise (CW1)

• WGS pays invoice through CargoWise (CW1)

Sales Order Quantities

A booking can be made up of a set of parents each with or without child records, as shown below. Where there is a parent/child relationship the parent becomes a grouping mechanism for the child SKUs and is representative of what will be built. There is no tanglible process for those SKUs and the warehouse does not know what they are.

...

• Parent SKU100 x 2 (2 meeting rooms)

  • Child SKU1 x 8 (4 walls each meeting room, 8 walls total)

  • Child SKU2 x 2 (1 roof each meeting room, 2 rooves total)

  • Child SKU3 x 12 (6 chairs each meeting room, 12 chairs total)

SKU Structure (Standard structure including ROOM 2nd generation)

Parent Only

• Parent SKU3 x 3 (3 chairs)

White Glove SKU Processing

...

The warehouse has no concept of parent and child SKUs and only allows one of each SKU line and quantity. Duplicate SKUs are not allowed in a sales order so the quantities have to be consolidated across all the SKUs. Given the example in the booking structure above, the quantities sent to the warehouse should be as follows where the SKUs to be sent to the warehouse are shown in red:

• 8 x SKU1

• 2 x SKU2

• 15 x SKU3