If you have not done so already, please check the overview on Onforwarder Addresses here: Onforwarder Addresses
This guide goes into details of how to configure Onforwarders, through the use of Carriers, Delivery Runs, Address to Delivery Run Mapping (A2DR) and Delivery Address to Onforwarder Address Mapping (A2A) to match your business processes, and automate onforwarder allocations.
There are two ways in which Onforwarders operate with regards to billing, and this affects how they should be configured within CartonCloud:
- Scenario A - You don't manage or charge your customer for the work performed by the Onforwarder (The onforwarder already has a relationship with your customer, and charges them directly), so you're responsibility ends when you deliver to the Onforwarder, and you only charge the customer for local delivery.
- Scenario B - You manage, and charge the customer for all of the work performed, and also pay the onforwarder directly. You're responsible for the consignment all the way to the final delivery destination and must receive back a signed POD from the onforwarder.
Scenario A - Your responsibility ends when once the onforwarder takes possession of the goods
In this case, you simply charge the customer for local delivery (if delivering to the onforwarder), or for a local pickup (if the onforwarder picks up from you).
Within this, there are two options for managing the delivery runs and allocations, and this really depends on volume and internal processes:
- If you have a large number of consignments which go to a specific onforwarder (completely fills a vehicle, or nearly fills a vehicle), the easiest way to manage them is to create a Delivery Run specifically for each Onforwarder (and give it the name of the onforwarder). That way, it's very easy to allocate all of the consignments going to one onforwarder in one go, from one page - and it makes it very clear on your run sheets when you ask "Who is taking the stock to Max Transport?"
See our guide on how to set this up: Onforwarder - Use Case 1
- If you have few consignments going to the onforwarder, and want to allocate the jobs to one of your regular runs (for example, North Run, which would mostly contain direct delivery consignments that are not being onforwarded), then you would not want to create Onforwarder runs, but instead use A2A mapping to automatically insert the Onforwarder Address.
See our guide on how to set this up: Onforwarder - Use Case 2
Scenario B - Your responsibility ends when the consignment is delivered to the final delivery location. (And therefore responsible for the POD)
In this case, you charge your customer for delivering all the way to the end location and pay the onforwarder directly for handling the onforwarded component.
To handle this scenario, you will make use of CartonCloud's Multi-Carrier functionality, creating a new Carrier for your onforwarder so you can accurately track costs associated with the onforwarder (and optionally, create bills so you can reconcile to the invoices the onforwarder sends to you). You'll then use an onforwarder-specific Delivery Run which is linked to this carrier so all allocations to that run are immediately attributed with your carrier.
Note: If you want to track expenditure with an onforwarder, you must create a new Carrier for them, and a new Delivery Run which is linked to that Carrier. You cannot use your standard Delivery Runs as you'll be unable to differentiate which items were sent with the onforwarder.
See our guide on how to set this up: Onforwarder - Use Case 3