Cocoa Arrivals Targets: How to Calculate the Weekly Pace Needed
5 min read · Public
Turn a cumulative cocoa-arrivals target into a weekly research benchmark. Work through the maths, test alternative delivery paces and understand why an arrivals shortfall is not automatically a production loss.
A cocoa arrivals target becomes more useful when you turn it into a weekly requirement. Instead of asking whether the latest delivery number looks large or small, ask how much must arrive during the remaining reporting window to reach a clearly defined target.
The calculation is simple. Choosing compatible inputs is the important part. The examples below are entirely illustrative: the 900,000-tonne target is a scenario, not a current forecast or market consensus.
The three inputs you need
Record cumulative arrivals at a specific cutoff, a target cumulative total covering the same season and geography, and the complete reporting weeks remaining after that cutoff. Keep a source and publication date for any externally supplied target. If you selected the target yourself, label it as your scenario.
Weekly arrivals and cumulative arrivals are different measures. A cumulative figure already includes deliveries within its stated coverage. Do not add the latest weekly figure again if that week is already included.
The required-pace calculation
Assume 240,000 tonnes have arrived toward a 900,000-tonne target, with eight complete reporting weeks remaining.
Required average = 660,000 ÷ 8 = 82,500 tonnes per week.
This is an average requirement. It does not imply that every week must deliver exactly 82,500 tonnes, or that the physical system can achieve that pace. If the target has already been reached, the remaining requirement is zero.
Using the same hypothetical starting total and eight-week window:
Constant weekly pace
Additional arrivals
Ending cumulative total
Difference from target
60,000 tonnes
480,000 tonnes
720,000 tonnes
180,000 below
70,000 tonnes
560,000 tonnes
800,000 tonnes
100,000 below
82,500 tonnes
660,000 tonnes
900,000 tonnes
Target reached
90,000 tonnes
720,000 tonnes
960,000 tonnes
60,000 above
These are constant-pace scenarios, not probabilities. A catch-up in deliveries could produce a different path from a steady weekly rate. The table makes the size of the required catch-up visible without pretending to forecast it.
Recalculate when the next report arrives
Suppose the following week's verified cumulative total becomes 310,000 tonnes. Seven weeks then remain. Against the unchanged illustrative 900,000-tonne target, the new requirement is 590,000 ÷ 7, approximately 84,286 tonnes per week.
The requirement has increased because that week's 70,000 tonnes was below the previous required average. That arithmetic describes progress against the selected target. It does not establish why deliveries were lower or whether the target remains credible.
Use the newly reported cumulative figure rather than automatically adding a headline weekly number. Revisions, coverage differences or rounding can make those two methods disagree. Investigate the discrepancy instead of silently forcing them to match.
What a shortfall does and does not mean
Port arrivals measure reported deliveries within a specified system. They are not the same as harvested national production, exports loaded onto vessels, or global cocoa supply. Logistics, delivery timing and selling decisions are possible explanations for a difference; none should be treated as established without evidence.
A below-target path becomes more informative when it persists across comparable reports and independent crop or export evidence supports it. Conversely, a strong catch-up week can narrow the delivery gap without resolving weather risks later in the season. Avoid attaching an automatic bullish or bearish price label to the calculator result.
The ICCO statistical overview ↗ treats production, grindings and trade as distinct parts of the cocoa balance. That distinction is useful when moving from a delivery observation to a broader market assessment.
Build a repeatable monday check
Begin with the source date and coverage on the Côte d'Ivoire arrivals page ↗. Compare like-for-like periods with the arrivals comparison tool ↗, then use the target calculator to test the remaining requirement. Finally, check inventories ↗ for independent destination-side context.
If a deadline includes a partial reporting week, model that part separately. Do not round it into a full week and hide the assumption. Retain the original target and any later revisions so the analysis remains reproducible.
The arrivals page also links to the free database preview for readers who want to bring those observations into one research workspace.
Method and sources
Checked 13 November 2026, 18:55 UTC. Original Cocoa Market Hub educational analysis assembled with automated research assistance. This is a transparent arithmetic method using illustrative figures, not a newly reported crop estimate. Consult the linked source and data-page definitions before using real observations. No price reaction or causal market claim is inferred.
Additional reading context
Educational explanation added to help interpret this article. It is not a new market update or a revision to the original dated figures.
Putting the guide into practice
Choose one dated observation relevant to this guide and trace it back to the original source. Record the benchmark, unit and reporting period before comparing it with another figure. This turns the explanation into a repeatable research process: establish what is measured, check what changed and identify what the observation cannot tell you.
Use the database to check the neighbouring evidence. A price observation can be compared with physical availability and positioning; an inventory or arrivals observation can be checked against compatible history and demand reporting. Agreement between several observations can strengthen a hypothesis, while disagreement highlights the next question to investigate. Neither outcome removes the need to check timing and definitions.
Applying this topic
For crop and arrivals research, distinguish a delivery report from a full-season production estimate. Compare equivalent reporting periods and keep the estimate date visible. A delayed delivery pattern may change weekly arrivals without establishing the final crop outcome. Weather reporting is most useful when the affected region, timing and crop stage are known; a forecast concern needs subsequent observations before it can be treated as confirmed production damage.
Published research and personal commentary, not personalised investment advice. Trade ideas can fail; evaluate the assumptions and dated follow-ups. The original published post is preserved.