'Cartonisation' refers to the division of an 'outer' or 'parent' consignment (e.g. a pallet), into 'inner' or 'child' consignments (e.g. cartons), that are then linked to the 'parent' for tracking purposes. it can be used for both Direct Injection and Ship to Store.
The default setup is Direct Injection, where the retailer property
directinjection.enabled is set. This means that the status(es) of the parent is not applied to the child/children, which keep their own individual statuses. If you wish to use the Ship to Store/'Click and Collect' model instead, and have the status(es) of the parent applied to all the children, contact Support.
Regardless of setup, a child, 'inner' consignment can only ever have one parent, 'outer' consignment.
You can track each 'inner' carton/package as part of a linked relationship to the 'outer' pallet/large box, via the
outerParcelCode data in the child's Parcels Array. You can interrogate this data using findConsignmentByConsignmentCode, findConsignmentsByCartonId and findConsignmentsByOrderReference.
'Cartonisation' allows labels and manifests to be generated for two independent legs of a journey, for separate carriers that have no relationship, and for the consignments to be tracked over both legs (see below).
This process refers to the direct injection of packages into a carrier network in another country.
The 'parent' consignment is created and processed in the warehouse in the host country, where it is also 'cartonised' into the child consignments. In order to prepare these consignments for direct injection, the paperwork is generated ready for immediate use within the destination country.
The first leg of the journey is the delivery, by a line haul carrier, of the parent and child consignments to the hub of the chosen carrier in the destination country.
The second leg is the tracked transit of the 'child' consignments to the local depots of the chosen carrier, for onward 'final mile' delivery to the consumers.
Let us say that you are shipping goods from the UK to Germany. You have already created the consignments with printed German address labels, and you already have an account for DHL Paket in Germany, who will undertake the 'final mile' delivery to the German consumers. However, you need a pallet to move the consignment to Germany in the first place. So, you create a parent consignment for the pallet and link the 'inner' consignments to it.
You then engage a line haul carrier such as UPS to collect the full pallet from the UK warehouse and deliver it to the DHL hub in Germany (this is the first leg, following which the role of the 'parent' pallet is complete).
DHL then 'inject' the child packages from the pallet into their local network, and the local DHL depots fulfil the 'final mile' delivery of the packages to your German consumers.
By using parent/child linking, you obtain full tracking from the UK to Germany. Without it, you would only be able to track the children from the point that DHL received the parcel in Germany.
This process allows sellers to use stock from different sources to fulfil their orders, which are then picked up by consumers from their nearest store.
The parent consignment is created in the warehouse, where it is also 'cartonised' into the child consignments, and all the associated paperwork is generated.
The first leg of the journey is the delivery of the parent and child consignments to the seller's central distribution centre by a carrier or retailer fleet vehicle,
The second leg is the tracked transit of the child consignments to local stores, and 'delivery' is the consumer collection.
The parent/child linking means that a store receipt for the parent, and its subsequent 'cartonisation', can be used as events to trigger e-mails for all the children, so that the associated consumers are notified when their packages can be picked up.
The sequence of events is as follows:
Create the parent record for the pallet/large box by using createConsignments.
Store the automatically generated Consignment Code (starting with DMC).
Create and allocate the child record for each 'inner' package using, for example despatchConsignmentWithBookingCode, despatchConsignment or createAndAllocateConsignmentsWithBookingCode. You should specify the same carrier service code for each package (this should be the one for the carrier in the destination country if using Direct Injection).
Store each Consignment Code.
Generate the paperwork for each child consignment.
If you used despatchConsignmentWithBookingCode or despatchConsignment, the paperwork will have been generated as part of the call. If you used createAndAllocateConsignmentsWithBookingCode, then you need to use one of the following: createPaperworkForConsignments, createPaperworkForCarton or createPaperworkForParcel.
Use addInnerToOuter to link each child to the parent as it is being packed. You do this using the parent/child Consignment Codes and parcel numbers (e.g. link parcel 1 of the child consignment to parcel 1 of the parent consignment).
Update the parent consignment with the additional weights and dimensions resulting from the packing in the previous step. You can use either update to modify particular fields, or updateConsignments to modify the entire consignment.
The updating must be carried out prior to allocation.
Allocate the parent consignment to a carrier service using allocateConsignmentsWithBookingCode.
Associate all the consignments (parent and child) with the same Manifest Group Code, so that they all go on the same trailer for the first leg of the journey (refer to Scan to Trailer).
Mark all the consignments (both 'inner' and 'outer') as ready to manifest.