Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Life of 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 a billing reference in CargoWise (a shipping/logistics/financials system used by SEKO)

  • Send Sales Order to Warehouse

  • Update Purchase Order for work costs associated with the Sales Order

  • Warehouse picks, packs and dispatches information

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

  • Process Dispatched Notification

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

      • packaging details

      • confirmation of Purchase Order

    • Send “Pre-Alert” email to Final Mile Facility, which is known as a “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

    • White Glove Partner to complete the work and give information on extra costs incurred

    • Send a revised Purchase Order for complete work

Sales Order Quantities

A booking can be made up of a set of parents each with or without child records, as shown below.

SKU Structure (ROOM Specific - SKU structure 1st generation)

Parent & Child

  • 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 White Glove system incorporates both the ROOM specific SKU structures with parent/child SKUs and the standard SKU structures with parent only SKUs (which have no concept of child SKUs).

Sending Quantities to the Warehouse

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

  • No labels