Ship Logic & Takealot
User guide

The Takealot (TAL) Johannesburg and Cape Town distribution centres (DC) will each be set up as separate hubs (branches) on Ship Logic (SL) for The Courier Guy (TCG). These hubs will be carved out of the normal Johannesburg and Cape Town hubs. 

There will be no drivers allocated to these hubs such that when any collection or delivery address is a TAL DC, no driver will be assigned automatically resulting in shipment statuses of “collection unassigned” or “delivery unassigned”. 

A dummy driver will be set up for each TAL DC. This could be the actual driver of the truck that goes to the DC but it does not have to be a real driver as this driver will not be assigned to an actual driver area (the driver will only be used to indicate that a collection has been processed by TCG).

TAL DC deliveries will use inter-hub manifests and will not appear on a driver trip sheet as out for delivery (these shipments will go from outbound on a manifest directly to delivered). 

Table of Contents

The following information is drawn from the  TAL DC Collection & Delivery process document (Click to view )

Collections from Takealot

A TAL seller will create a shipment as normal on Ship Logic, setting the relevant TAL DC as the collection address (and the TAL seller’s address as the delivery address). The TAL seller can choose from the standard service levels e.g. economy, overnight etc. as required.

A shipment will be unassigned and available in the Ops Dashboard after it has been created by the seller.

Check each unassigned collection’s exception number under Special instructions. Do this by viewing the special instructions column in the Ops Dashboard

  • If an exception number has been provided, assign the Takealot driver to that shipment.
  • The relevant driver will now be assigned to the collection and have it available on his trip sheet. 
  • If an exception number has NOT been provided, tag the shipment with the “Takealot Collection Follow-up” tag
  • Use the search tag function on your shipment page to filter for all relevant tagged shipments afterwards. 
  • You can select all relevant shipments from this view and send bulk communication to the client if required

The driver of the truck to the TAL DC will then take the stack of confirmation papers to determine what needs to be collected from TAL.

Optionally, look at the driver tripsheet, which would also show all the collections assigned to the dummy TAL DC driver. The collections will go to the driver app after it has been assigned.

The driver must then individually scan the shipments as collected with the driver app when at the takealot premises.

Once collected, delivery to the TAL seller will then happen as per the normal delivery process.

Deliveries to Takealot

A TAL seller will create a shipment as normal on SL, setting their address as the collection address and the relevant TAL DC as the delivery address. The TAL seller can choose from the standard service levels e.g. economy, overnight etc. as required. 

A driver will collect the shipment from the TAL seller as normal and it will end up in the designated area of the relevant hub e.g. the Johannesburg hub for the Johannesburg TAL DC.

Operations will manually work through each shipment, checking the PO numbers against the bookings on the TAL portal as normal.

Check PO numbers by info scanning each shipment to open the waybill information. Look for the PO number in the Special instructions 

Shipments can be scanned for delivery once the PO numbers have been confirmed. They will be scanned onto a manifest outbound for TAL DC

An interhub manifest needs to be created for each truck that goes to the TAL DC. 

Shipments will be scanned and palletised using our tagging feature.

There will be a number of predefined reusable shipment tags set up to manage the pallets e.g. TAL-JHB-DC-1 to TAL-JHB-DC-20.

Open the newly created manifest, click on outbound and select a tag (pallet) to add while scanning.

Start by scanning the confirmed waybills to add them to the manifest.

When all shipments are outbound and palletised, check the item limit

If the item limit has not been reached once the pallet is complete, then the manifest will be closed and the TAL delivery confirmation for that pallet will be attached to the pallet.

If the item limit was reached with that pallet then all the parcels for that pallet can be removed in bulk.

Select all the shipments with the relevant tag and remove them in bulk by clicking on the the trash can icon

The truck will deliver the pallets to the TAL DC (all part of the same manifest)

Once delivered, the driver can individually mark/scan each shipment as delivered or more likely, Operations can filter shipments based on the manifest number and bulk edit all the shipments on the manifest to a status of delivered (dealing with any exceptions manually as required)

The typical tracking events for a shipment going to a TAL DC will therefore look as follows:

    1. Submitted
    2. Collection assigned 
    3. Collected 
    4. At hub
    5. In transit (optional)
    6. At hub (optional)
    7. Outbound to Takealot JHB DC
    8. Delivered

There will be no “Out for delivery” tracking event (and therefore no SMS with OTP will be sent).