Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Analysis of Existing Booking CSV files

...

It also covers the concept of a booking which represents an ASN from the client i.e. “we are arranging our own transport, but these Goods are going to arrive at your warehouse on date X”.

Booking Type

why this booking?

ASN

GOODS TRANSFER

SALES ORDER

Booking Type

why this booking?

ASN

GOODS TRANSFER

SALES ORDER

Organisations of Record

Official Who? Consignor / Consignee of record, Client

OPTIONAL

if missing, we must enrich with Consignor, Consignee and also Client, Responsible SEKO Entity

OPTIONAL

if missing, we must enrich with Consignor, Consignee and also Client, Responsible SEKO Entity

OPTIONAL

if missing, we must enrich with Consignor, Consignee and also Client, Responsible SEKO Entity

Goods

what are the goods?

MANDATORY

No children

MANDATORY

No children

MANDATORY

Children may be specified. In the absence of children, we should have logic to decide how to construct the parent SKU based on pre-approved combinations of child SKUs from the Client

Collection Location

from where?

NOT APPLICABLE

OPTIONAL

if missing, we must enrich with normal factory premises for this client, if configured

OPTIONAL

if missing, we will decide which of our warehouses when planning workflow, based on available inventory & destination. We may need to create more than one workflow depending on where the inventory is, to fulfil the order

Collection Time

when goods collected?

NOT APPLICABLE

MANDATORY

OPTIONAL

if missing, we decide when we plan the workflow; however if they require collection directly from their factory then they will likely tell us

Delivery Location

to where?

OPTIONAL

if missing, we must enrich with normal inbound warehouse for this client, if configured

OPTIONAL

if missing, we must enrich with normal inbound warehouse for this client, if configured

MANDATORYclient may optionally define an additional destination which is the final destination, but this is only valid if there is a Handover To Agent

Delivery Window

when goods delivered?

MANDATORY

MANDATORY

MANDATORY

Receive From Agent

handover from who?

MANDATORY

OPTIONAL

if missing, there is no separate agent we are receiving from at origin

OPTIONAL

if missing, there is no separate agent we are receiving from at origin

Handover To Agent

handover to who?

NOT APPLICABLE

OPTIONAL

if missing, there is no separate agent we are handing over to at destination

OPTIONAL

if missing, there is no separate agent we are handing over to at destination

Transport

How? (Mode, Containers etc)

MANDATORY

OPTIONAL

if missing, we decide how to transport (and if present, we may still decide to do it differently when setting up workflow)

OPTIONAL

if missing, we decide how to transport (and if present, we may still decide to do it differently when setting up workflow)

White Glove

installation required?

NOT APPLICABLE

NOT APPLICABLE

OPTIONAL

if missing, there is no White Glove service applicable or required to be managed by us. Must not be present if there is a Handover To Agent

...

  • System should validate the inbound API based on the above mandatory / optional / not applicable

  • System should enrich booking internally when data is missing, based on client-specific configurations (see items in blue). It must also generate our own internal Booking ID as per the existing system

  • System should reply to the sender with the internally-generated Voyager internal Booking ID

  • System could Ideally, the system should also reply with enriched booking details (see items in blue above) in addition to the Internal Booking ID