Table of Contents

CFS operations and scanning

A Container Freight Station (CFS) is a facility where cargo is received, handled and prepared for container transport. For Less-than-Container-Load (LCL) shipments, goods from different shippers are combined into a container rather than each shipment using a complete container. At the destination, the cargo can be separated again for collection or onward transport.

CFS operations cover the physical work around this process. Stuffing means loading cargo into a container; stripping means unloading it. Recording these activities helps the forwarding team distinguish cargo that has arrived at the CFS from cargo that is already loaded or ready for pickup.

In FMS, cargo and equipment events connect this physical progress with the related shipments and Consolidation Documents. The shipment represents the individual cargo movement, while the consolidation brings the cargo together for the shared container movement.

Recording handling progress

The CFS scan functions identify handling units using a voyage call and external handling unit number. Operators can execute equipment/cargo events at the point of work instead of updating each document manually. An undo action allows an incorrectly recorded event to be corrected.

For example, when cargo for several LCL shipments is loaded into one container, the operator records the stuffing events against the relevant cargo and equipment. The forwarding team can then review the recorded handling progress in the related documents.

Configuration hints

  • Set up the relevant equipment/cargo event templates for your shipment and consolidation processes.
  • Configure the scan flow with the required event code, document type, equipment/cargo type and status. Supply the port, container number and handling unit number from the scan session as appropriate.
  • Decide whether the container number is mandatory for each scan action and whether the action executes or undoes an event.
  • Test the flow with a shipment linked to a consolidation and verify the event history before using it operationally.

See also