Introduction
There are three main types of order to organise freight activities in AgriChain. This article explains what type of order a site (bulk handlers) should create under what circumstances.
To learn more about the different types of orders, please refer to the article [Refer Article]
What Order should I create?
To determine which type of order you should create, you need to consider two key pieces of information: whether you know the freight provider, and whether you have the pickup and delivery site details.
When to create a Call on Grain (COG Order):
If you do not know the freight provider, but have the pickup and delivery site details, you should create a Call on Grain (COG) order and provide the order number to your counterparty so that they can arrange freight provider to load against it.
To learn more about the COG orders, please refer to the article [Refer Article]
When to create a Freight Order (FO):
However, if you know the freight provider and have the pickup and delivery site details, you may create a Freight Order (FO) with the customer on whoever has the delivery onus.
To learn more about the COG orders, please refer to the article [Refer Article]
The advantage of creating a FO and a COG Order is that they can be created against a contract, and that all information will be prefiled for you. Moreover, you can effectively draw down the tonnage of your contractual obligations while reducing any complexities of applying an order to a contract.
To easily differentiate a COG Order and FO, you may see their identifier/order number.
A COG Order typically starts with a letter G followed by a date and its corresponding number (e.g. Gxxxxxx).
On the other hand, an FO typically starts with a letter F followed by a date and its corresponding number (e.g. Fxxxxxx).When to create a Request Order:
On the other hand, if you do not know the freight provider and do not have either the pickup site or delivery site details, you may create a Request Order.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article