| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Organisation Actors
Summary | Description |
Shipper
The manufacturer & supplier of goods to their clients
Vendor
For the purposes of SEKO, synonymous with the Shipper
Consignor
The organisation equivalent to, or an affiliate of, the Shipper / Vendor, to appear on all official documents in relation to a shipment
Shipper's Client
The client of the Shipper, to whom the Shipper is ultimately supplying the goods (but need SEKO to manage the collection & delivery of those goods)
Consignee
The organisation equivalent to, or an affiliate of, the Shipper's Client, to appear on all official documents in relation to a shipment. Alternatively it may be a Sales Office of the Consignor, acting on behalf of the Shipper’s Client.
Branch
A SEKO organisation that is part of the SEKO group, typically distinguished by origin country (for the Shipper) and destination country (the Shipper's Client)
Client
A client of SEKO. This could be the Shipper requiring SEKO's freight forwarding services (the client of the SEKO Branch at origin country), and/or the Shipper's Client (the client of the SEKO Branch at destination country, or the Shipper's Client wishing to use SEKO's systems for PO / DCM management)
Supplier
A supplier of shipment / freight services (e.g., Carrier, co-loader, partner Agent). Note that where a SEKO Branch itself performs activities as part of a Shipment, that SEKO Branch is a special form of Supplier in this context.
For the purposes of this document, it should be remembered that the term ‘Supplier’ is meant from SEKO’s perspective i.e., a supplier of services allowing SEKO to effectively manage the end-to-end processes of a Shipment. It should not be confused with the concept of ‘the supplier of goods’, for which the terms ‘Shipper / Vendor / Consignor’ are reserved.
Agent
A partner Freight Forwarding or Carrier company to whom SEKO subcontracts its services. It is a special form of Supplier in the context of Shipments management
Customs Broker
The Supplier who performs the function of ensuring that import & export compliance processes and documentation is correctly and fully carried out. This is a special type of Supplier, which could also be a SEKO Branch at origin or destination
Key Business Terms
Term
Description
SEKO 360 DCM (Demand Chain Management) | Offers a comprehensive solution for managing your supply chain from Purchase Order to Final Delivery. | |
Cargowise (CW1) | Global logistics platform/International Forwarding services which Integrates data to Seko360 DCM from Vendor Booking to Delivery | |
Client | Seko 360 Customer responsible for Creating Purchase Order, Authorizing Shipments and Managing final delivery | |
Vendor | Supplier of the Client who manufactures the goods and responsible for Arranging Booking of goods. Also acts a the “ Shipper” | |
Origin Agent | Seko360 Agent who arranges shipments from Vendor/factory to arrive at the Origin Port and Destination Port | |
Destination Agent | Seko360 Agent who is responsible for managing shipments from Destination Port to Final Delivery. | |
Branch | SEKO local Origin office | |
Shipper/Consignor | Sender of the shipment to appear in the Shipping documents | |
Consignee | Recipient of the shipment to appear in the Shipping documents |
Key Business Terms
Term | Description |
Purchase Order (PO) | is a document issued by a buyer to a supplier, detailing the specific goods or services to be purchased. It outlines the terms and conditions of the transaction, including quantities, prices, delivery dates, and payment terms. |
Booking | An instruction or request received by a SEKO |
origin from Vendor, requesting |
movement of goods | |
Shipment | A sequence of operational activities that SEKO branches need to manage and oversee, in moving goods and fulfilling client Bookings, on behalf of a given Consignor / Consignee |
Shipping Instruction (SI) | This is an instruction sent by |
Back-to-Back
Destination
Vendor includes Shipping details, documents and Final Packing | |
FCL | Full Container Load. Goods within an individual Shipment for a given consignor/consignee take up all the space in a Container. This term is officially applied to Sea and Rail shipments, although the concept also exists for Air freight |
LCL
Less Than Container Load. Goods within an individual Shipment for a given consignor/consignee would not be enough to fill a whole Container. Rather than consignor or consignee bearing the cost of an entire Container, they expect SEKO to consolidate more than one shipment (either from the same consignor, or from multiple consignors) into a single Container to obtain better costs efficiency. This term is officially applied to Sea and Rail shipments, although the concept also exists for Air freight.
FTL
Full Truck Load - the equivalent of FCL, but for Road freight. In this case the truck is fully loaded at the Shipper's factory and makes the entire road journey for one official Shipment to one Consignee's warehouse
LTL
Less Than Truck Load - the equivalent of LCL, but for Road freight. A Road Shipment does not have enough goods to fill a trailer on the truck. In this case, rather than there being consolidation into Containers at a freight station (as for Sea / Rail / Air), the 'consolidation' is typically handled by the Supplier (Carrier) who may either do a 'milk run' between multiple origin factories (either for the same Shipper, or for different Shippers), or may wait until several different Shipments at the Shipper's factory are all ready for collection and then turn up to collect. In either case, the single truck would then be effectively carrying multiple Shipments. The carrier may then need to do multiple delivery drops at the Destination end, if the Shipments cover multiple Consignees or multiple warehouses for a given Consignee.
Container
For Sea / Rail, this will be an official solid box of several different shapes and sizes, with tracked serial numbers and identifiers as part of Supplier Instructions, to be loaded onto the Vessel or the goods train. For Air, this will be an official box called a 'ULD' (Universal Load Device), shaped specifically for cargo holds of aircraft, with its own serial numbers and identifiers, and can only be loaded by approved Agents at a freight station.
For Road transport, the trailer containing the goods is not typically deemed a 'container'; instead, the general information about the truck itself (e.g., registration numbers) is captured as part of Supplier Instructions.
SOP
Standard Operations Procedure... usually set up as part of client onboarding and standard processes. These will also be used to further inform how Shipments and Suppliers are set up once Client Bookings have been received (note that Bookings may only contain minimal information and therefore Shipment setups need to also be informed by the defined SOP).
Consolidation
Processing and loading of goods from multiple Shipments into one Container or trailer for the purposes of a Consol
Consol
This is another kind of Shipment, representing Goods from more than one LCL or LTL Shipment consolidated into a single container (or truck). Activities within a Consol are then booked in external Supplier Instructions e.g., a Sea / Rail / Air / Road Carrier for the main transit phase between origin and destination
Buyer's Consol
The SOP for a given Vendor / Shipper may require that where their Shipments are LCL, more than one of them are to be consolidated into full containers comprising a mix of goods, but all for that one Shipper; therefore, the cost of the entire container is borne by that Shipper or their Shipper's Client (depending on incoterms)
Agent's Consol
The Agent (SEKO) looks for opportunities to consolidate multiple LCL Shipments, regardless of their Shippers, into full containers. The cost of the entire container is then allocated to each Shipper or Shipper's Client (depending on incoterms) based on the proportion of the space each Shipment is using inside the Container
Origin
A term representing a very broad location of activities, geographically located at or near the Shipper's factory with the freight stations, container yards and ports, in the Shipper's country
Container | Shipping containers are large, strongly built metal boxes that are used to transport goods over long distances. |
Consolidation | Processing and loading of goods from multiple Shipments from different Suppliers/Vendor into one Container |
Origin | A term representing a very broad location of activities, geographically located at or near the Shipper's factory with the freight stations, container yards and ports, in the Shipper's country |
Destination | A term representing a very broad location of activities, geographically located at or near the Consignee's delivery warehouses with the freight stations, container yards and ports, in the Consignee's country |
FCL | Full Container load |
LCL | Less Than Container Load |
CY/CY | (container yard to container yard) or Vendor Load shipment is an FCL shipment where the packed containerised cargo gets collected at the container yard of one origin port and is delivered to the container yard of the destination port. |
CFS | (Consolidation and Forwarding Station) A shipment, where the goods are delivered at CFS for grouping (consolidating) them together for a specific destination. |
MSDS | Material Safety Data Sheet is a document that contains information about the potential hazards of a product and how to safely handle, store, and dispose of it. |
iHub Services & CargoWise Integration
SERVICE NAME | MEANING | USAGE |
|---|---|---|
Load PO | Load Purchase Order | Create new or update Purchase Order Load via iHub. View PO List in DCM Interface |
Load All PO | Load All Purchase Order | Load all open purchase orders by bulk. If a PO line is excluded in the next upload=delete in Seko360 DCM |
Push XUS | Push XML Universal Shipment | XUS Push is sent when a Shipment is created from a Booking for a Client that has subscribed to the ‘Push XUS’ service. DCM data to Cargowise |
Load XUS | Load XML Universal Shipment | Used to load CargoWise Shipment data into DCM
|
Load XUE | Load XML Universal Event | Load CargoWise Container events into DCM |
Push SDS | Push Shipment Details Service | Pushed from multiple places (Approval, COB, Delivery Booking…) Push ‘Draft’ from Shipment Push List and ‘Final’ from COB if Shipment is created from a booking for a Client that has subscribed to the ‘Push SDS’ service. |
Load SI | Load Shipment Instruction | Used to create a Shipment Instruction (SI), update the SI data and pack the lines into Containers. Created via iHub Generic services |
Load Booking | Used to create Booking and new PO Lines Data into DCM. Created via iHub FTP or REST note: custom conditions are set for specific clients | |
Load DI Booking | Load Document Identifier | Client will upload “Document Identifier” for the booking from XML files to an FTP directory. Done after Load Booking service |
Push SOC | Push Shipping order confirmation | note: custom conditions are set for specific clients |
Push SOCFCR | Push Shipping Order Freight Cargo Receipt | note: custom conditions are set for specific clients |
Push SWB | Push Sea Waybill | note: custom conditions are set for specific clients |
NOTIFICATIONS
Emails sent to Users / User groups if the Notification has been SET for the client
Notification NAME | Trigger | Send From-->TO |
|---|---|---|
Shipment Requiring Authorisation | when a shipment is submitted and is awaiting for approval | origin agent -> client |
Shipment Instruction (SI) Approval Request | When the SI has been submitted | vendor -> operations team/Branch |
Booking Cancellation Request | when the Vendor requests a booking cancellation | vendor -> operations team/Branch |
Booking Cancellation Confirmation | when the Origin Agent approves/rejects the booking cancellation request | origin agent -> supplier (supplier email stated in the booking) |
Shipment Routing | when Origin Agent amends the routing | origin agent -> client |
Delivery Confirmed | when the delivery booking has been confirmed | destination agent -> client |
Delivery Confirmation Declined | when the delivery booking confirmation has been declined | destination agent -> client |
Delivery Amend Confirmed | when the delivery booking amendment has been confirmed | destination agent -> client |
Delivery Amend Declined | when the delivery booking amendment has been declined | destination agent -> client |
Delivery Cancel Confirmed | when the delivery booking cancellation has been confirmed | destination agent -> client |
Delivery To Confirm | when the delivery booking is awaiting confirmation | client -> destination agent |
Delivery Planned Amended | when the delivery booking amendment is awaiting confirmation | client -> destination agent |
Delivery Planned Cancelled | when the delivery booking is cancelled | client -> destination agent |