The most expensive gap in any bulk commodity operation is not the gap between budgeted and actual demurrage. It is not the gap between forecast and achieved throughput. It is the gap between what the commercial team committed to a customer and what the operations team can actually deliver on the day that commitment comes due. This is the problem that sales operations alignment exists to solve, and in bulk commodity exports, getting it right is the difference between commitments that hold and commitments that quietly bleed margin every quarter.
Everyone who has worked in this industry long enough has seen it. A sales manager, eager to close a renewal, agrees to a lifting schedule that neither the rail operator nor the port has confirmed. A marketing lead, under pressure to hit a quarterly tonnage target, accepts a laycan that squeezes two vessels into a window that can only service one. A customer relationship manager, trying to smooth over a missed shipment, offers a forward concession that the operations team learns about when the vessel nominates.
Each of these moments is survivable on its own. Each is collectively catastrophic. They accumulate into a pattern, a pattern of commitments made in one system, delivered (or not delivered) in another, and reconciled in a third, that erodes margin, exhausts teams, and eventually reaches the customer as inconsistency.
This playbook is about that pattern. Not as a communication problem or a relationship problem, although it manifests as both, but as a structural problem with a structural solution. We will look at why sales operations alignment is the default casualty in most bulk commodity exporters, what the commercial-operational divide costs in ways that never make the P&L, and how to start closing it, not with a full sales and operations planning overhaul, but with something smaller and more achievable: one shared handover record.
In most bulk commodity exporters, commercial and operational functions evolved from different starting points and respond to different logics.
Commercial teams grew out of the customer relationship. Their tools, CRM systems, contract management platforms, and pricing models are built around deals, accounts, and forward obligations. Their horizon is months to years. Their success metric is the quality and duration of customer relationships, measured by renewals of offtake contracts and price realisations. When a commercial manager looks at the business, they see a portfolio of commitments stretching into the future.
Operational teams grew out of the asset. Their tools, mine planning systems, stockpile management, rail scheduling software, port terminal platforms, and shipping management are built around throughput, capacity, and flow. Their horizon is days to weeks. Their success metric is tonnes moved, uptime achieved, and costs controlled. When an operations manager looks at the business, they see a network of constraints that must be optimised within tight windows.
Both views are correct. Neither is complete. And the handover point between them, where a commercial commitment becomes an operational obligation, is the most consequential interface in the business.
In most organisations, that handover is a meeting, an email chain, and an assumption. The commercial team forwards the confirmed sale. Operations acknowledges receipt. The nomination follows. Everyone proceeds.
What is missing is the thing that would make this handover actually load-bearing: a single authoritative record of the commitment that both teams can see, query, and update in real time. A record that ties the contractual obligation to the operational plan surfaces conflicts before they become crises and maintains a version history that both functions trust.
Without that record, each team builds its own version of reality. The commercial team’s spreadsheet says the customer will receive 180,000 tonnes in June. The operations team’s plan states that volume is achievable only if two specific rail slots are available and the port does not have a scheduled maintenance window. Neither team knows the other’s caveats. Both proceed as if their view is the view.
The gap opens at that moment. It just does not become visible until the vessel is at anchor and someone asks why the cargo is not ready.
The commercial-operational divide creates a category of cost that is structurally invisible. Not hidden, the events show up in financial statements, but they’re disaggregated across so many line items and framed as so many one-off occurrences that the pattern never coalesces into a single number someone can point to.
Consider what appears on the ledger when sales and operations are out of sync.
Demurrage is an unexpected expense. When the commitment made to the customer cannot be met within the agreed window, vessels wait. The demurrage line absorbs it. For a detailed breakdown of why demurrage is a symptom rather than a cause, see our piece on why demurrage isn’t the real problem.
Freight concessions and commercial adjustments. When the commercial team, aware that operations cannot deliver cleanly, pre-empts the customer complaint by offering a rebate or discounted forward pricing, the concession hits revenue, not the coordination budget.
Rework the cost on shipments. When cargo is loaded against the wrong specification, because the quality commitment in the contract was not visible to the loading team, downstream costs include re-blending, vessel repositioning, or customer penalty claims.
Air freight for samples and documentation. When the handover is messy, documentation often arrives late. Customers chase samples. Samples get flown. Logistics budget absorbs it.
Accelerated labour costs. When operations discover a commitment they did not plan for, teams work harder to catch up. The overtime appears under payroll. No one connects it back to the sales call that created the commitment without checking.
Lost throughput. When the network has to absorb an unplanned obligation, other movements slide. The tonnage lost to rescheduling rarely makes a report because it is lost to a future that was never measured.
None of these costs is small. Taken together over a year, they routinely amount to a single-digit percentage of revenue, which, for a bulk-commodity exporter, is a very large number. And they compound. Because each coordination failure consumes management attention, the organisation’s capacity to improve shrinks. Teams spend their time firefighting, not rebuilding.
There is a second category of cost, harder to quantify but more damaging in the long run. When sales promises outpace operational reality often enough, customers stop trusting the sales conversation. They start negotiating with operations directly. They build buffers into their own planning. They begin shopping for alternatives, not because a competitor offered a better price, but because they cannot run their business on commitments that do not hold.
That is the point at which weak sales operations alignment stops being an internal efficiency problem and becomes a customer retention problem. By then, the cost is on a different line item entirely — the one labelled “lost renewal.”
The divide rarely presents itself as an abstract strategic issue. It presents as specific incidents that people work around, one at a time, until the cumulative drag becomes impossible to ignore.
A commercial manager confirms a February laycan with a long-standing Japanese customer. The customer’s mill has a planned outage, and this is the only window that suits their turnaround. The commercial manager, who has worked the account for six years, remembers that February has typically been a flexible month operationally. She confirms the window by email. The operations team sees the confirmation late on a Friday. By then, two rail slots that would have served the nomination had been reallocated to a different customer, whose February window had been confirmed two weeks earlier through a different channel. The conflict was discovered on Monday. Both customers receive different versions of “we’re working to confirm.”
An operations planner is building the April schedule. She sees on her plan that a 170,000-tonne shipment is pencilled in for the second week. She does not see that the commercial team has already agreed to an upgrade in quality specification for that customer — they renegotiated on a call two weeks prior and the contract annex has not yet been uploaded. The shipment loads to the original specification. The customer rejects the documentation on arrival. A three-way argument begins about who said what and when.
A marketing lead is preparing the quarterly forecast for the executive committee. He pulls tonnage numbers from the CRM, where commercial commitments are logged. He pulls capacity numbers from the ops system, where the plan is built. The two numbers do not match, not because anyone is lying, but because the CRM records the sold volume at the agreement date and the ops plan records the expected achievable volume at the execution date, and in between, weather, equipment, and grade availability have shifted things. He picks one number. The executive committee proceeds on the basis of a picture that is, at best, only partially true.
A customer relationship manager is handling a complaint. The customer’s plant manager points to a shipment that arrived two days late and says the contract specifies liquidated damages. The relationship manager looks at the contract. It does specify a delivery window. It also specifies a force majeure clause that may or may not apply to the event that caused the delay. She does not have the operational evidence in front of her, the weather data, the vessel movements, the port queue, because that lives in three different systems and none of them are wired into her workspace. She has to choose between a quick concession (which sets a precedent) and a lengthy investigation (which frustrates the customer). She concedes.
Every one of these moments is recoverable in isolation. Every one of them represents a small, preventable leak. And every one of them happens because the commercial and operational views of reality have not been reconciled.
When companies recognise the divide, the instinctive response is to add a meeting. A weekly commercial-operational alignment meeting. A monthly S&OP review. A quarterly planning session.
These help. They also routinely fail to close the gap for three structural reasons.
Meetings update people, not systems. The alignment achieved in a meeting lives in the minds of the attendees and, optimistically, in a set of meeting notes that one person writes up and circulates. Everyone who was not in the room has to be updated through a second communication, which is often delayed, often lossy, and often never happens. The system of record, the CRM, the ops plan, and the contract remain unchanged unless someone deliberately takes an additional step to update them.
Meetings produce decisions, not constraints. A good alignment meeting can resolve a conflict. What it cannot do is prevent the next conflict from being created between meetings. If the commercial team takes a new commitment on Tuesday and the operations team schedules around an old assumption on Wednesday, the next meeting will surface the conflict, but in the meantime, both teams have proceeded on incompatible plans.
Meetings reward presence, not accuracy. In any organisation that runs on regular alignment meetings, a culture develops where being in the room and having an opinion matter more than having the underlying data right. The person with the clearest voice often wins the commitment, not necessarily the person whose system actually reflects what can be delivered.
The second common response is to invest in a full sales and operations planning (S&OP) process. Done well, S&OP is genuinely powerful. Done as most organisations do it, an overlay process running on top of disconnected systems, it creates an additional layer of reconciliation work without removing the original fragmentation. Sales operations alignment does not improve. It just gets narrated more formally.
The third response, the one most visible in bulk commodity exporters over the past decade, is to implement integrated planning Software. Some of this Software is excellent. Some of it is shelfware because it was designed for consumer goods manufacturers, fast-moving goods distributors, or industrial supply chains that do not align with mine-to-port-to-vessel flows. The Software solves the wrong problem and gets blamed for the unchanged outcome.
None of these responses is wrong in principle. All of them tend to underinvest in the simple, structural piece that actually closes the gap: a single shared handover record that both functions trust and update.
Start with the simplest version of the idea. Every commitment made to a customer that has operational consequences, lifting volume, laycan, quality specification, loading port, vessel nomination window — lives in one place that both the commercial and operations teams can see, edit, and question.
This is not a CRM. A CRM is optimised for the relationship and the deal. It does not naturally surface the operational constraints that make a commitment deliverable or undeliverable.
It is not an ops system. An ops system is optimised for throughput and flow. It does not naturally surface the contractual terms and customer expectations that sit behind a volume number.
It is the handover layer between them. A structured record that answers, for any given commitment: what was promised, in contractual terms; what is the operational plan to deliver it; what are the current risks to that delivery; who is responsible on each side; and what has changed since the commitment was made, and by whom.
When this record exists and is actually used, several things start to happen.
A commercial manager contemplating a new commitment can see the operational picture before making a commitment. Not through a separate system, not through an email to operations, but as an integrated view at the point of decision. The confirmation happens against reality, not against optimism.
An operations planner building the schedule can see the commercial context behind every number. Not as a line item, but with the commitment terms, the customer’s flexibility, the precedent, and the stakes. Scheduling decisions can be made with commercial awareness, not in isolation.
A marketing lead producing the forecast can pull from one source, not two. The forecast reflects both the commercial commitment and the operational deliverability. Variance between them is visible, not hidden, which means it can be discussed, not argued about.
A customer relationship manager handling a complaint can pull up a single record that shows what was promised, what happened, and why. The conversation with the customer becomes evidence-based. The internal conversation about accountability becomes data-based. The emotional temperature drops.
None of this requires rebuilding the underlying commercial and operational systems. Those systems remain the systems of record for their respective domains. The shared handover record is the thin integration layer that ties them together at the points that matter, and it is the foundation on which durable sales operations alignment is built.
Most exporters who try to close the commercial-operational divide try to do too much, too soon. They procure enterprise Software. They consult external integrators. They launch transformation programmes that collapse under their own weight long before they deliver value.
The alternative is to start with a minimum viable handover record, narrow in scope, fast to stand up, deliberately imperfect, but real enough to change behaviour.
At a minimum, the handover record contains:
A commitment header for every confirmed commercial agreement with operational implications, the customer, the volume, the window, the quality specification, the loading port, the commercial owner on the sales side, and the operational owner on the delivery side.
A plan link pointing to the current operational plan is intended to provide the commitment, scheduled rail movements, stockpile allocation, and vessel nomination or nomination window.
A risk register that captures known threats to delivery, a maintenance window that falls within the laycan, a grade availability concern, a forecast weather event, and a rail slot that has not yet been confirmed. Each risk has an owner and a status.
A change log that records, in plain language, every material change to the commitment or plan, when it happened, who made it, and the rationale. This is the single most important feature and the most commonly neglected one.
A customer communication record that captures the last substantive conversation with the customer about the commitment, who spoke, what was said, and what was agreed.
This is not conceptually complex. It can live in a shared system as straightforward as a well-designed spreadsheet with disciplined usage, although at scale it naturally wants to live in something more robust. The complexity is not in the tool. It is in the discipline of keeping it current.
The shared handover record is only as useful as the behaviour around it. That behaviour has to be designed, not hoped for.
Update on commitment, not after. The commercial team must be required to update the handover record at the moment of commitment, not at the next weekly meeting. This is non-negotiable. If a commitment is made and the record does not reflect it, the operations team is entitled to treat it as provisional. The incentive structure aligns quickly.
Operational sign-off before confirmation. For material commitments above a volume threshold, within a tight window, and involving a non-standard specification, commercial confirmation requires an operational acknowledgement on the record. This is not bureaucracy. This is the structure that prevents the sales-confirms-then-ops-finds-out pattern.
Daily five-minute check, not a weekly hour. The handover record is reviewed by both teams at the start of every day, what has changed, what is at risk, and what needs attention. Five focused minutes beat a weekly hour because it catches issues when they are still small.
One source of truth for the forecast. The quarterly forecast, the board report, and the commercial review all draw from the handover record. This eliminates the two-number problem and forces the teams to resolve variance at the source, rather than in the forecast.
Visible change log. Every change is visible to both teams. No private updates, no quiet edits. The change log is the audit trail that makes the record trustworthy over time.
Each of these behaviours is simple. Their cumulative effect is profound. They transform the handover from a failure point into a strength.
Alignment is not a vibe. It is measurable, and the measures matter because they turn a soft-sounding initiative into a concrete operational programme.
Commitment-to-plan variance. For every commitment entered, what is the delta between the commercial commitment (volume, window, specification) and the operational plan to deliver it? A healthy variance is small and trending down. A variance that stays large, or grows, tells you the handover record is being used as a post-hoc record, not a pre-commitment tool.
Time-to-acknowledgement. From the moment a commercial commitment is made until operations formally acknowledge it in the record. Hours are good. Days are a problem. The longer the lag, the more decisions both teams make on incompatible pictures.
Change log density. How many changes to a commitment occur between confirmation and execution? Too few suggest the plan was never stress-tested. Too many suggest the original commitment was made without sufficient operational input.
Exception escalation rate. How often does an issue escalate to senior management because commercial and operational teams cannot agree on a path forward? A well-functioning handover produces few of these. Most are resolved at the handover layer.
Customer-surprise events. How often does a customer learn about a problem from operations or from the vessel agent, rather than through a proactive commercial touchpoint? This is the ultimate external measure of whether the internal alignment is working. A deeper discussion of this is in our piece on proactive customer calls, the practice that turns internal alignment into visible commercial reliability.
These five metrics, tracked month over month, tell a more honest story about sales operations alignment than any qualitative review.
The handover record does not exist in isolation. Its real power comes from how it connects to other operating disciplines.
It connects to quality assurance. When the continuous quality thread from mine to vessel is live, the specification in the handover record is tied back to the grade availability and blending plan, and the match between what is sold and what can be delivered becomes visible before loading, not after.
It connects to shipment transparency. When the handover record feeds a real-time shipment visibility layer that customers can see, the commitment and its current status travel together. The customer does not have to chase; the commercial team does not have to interpret.
It connects to board-level reporting. When the board-level shipping performance framework reports against the handover record, the KPIs the board sees are the ones that actually govern the commercial-operational relationship, not a set of proxies assembled in the week before the meeting.
It connects to the offtake protection. When the offtake renewal case is being built, the handover record is the evidence base, the clearest single demonstration that commitments made are commitments kept.
None of these programmes works as well in isolation as they do together. The handover record is the backbone that lets each of them operate on shared data, shared assumptions, and shared accountability.
Closing the commercial-operational divide is not a multi-year transformation. It is a twelve-week discipline-building exercise, with one caveat: the first four weeks are the hardest, and most initiatives die before they finish them.
Weeks one to four: establish the record. Build the minimum viable handover record — spreadsheet, shared workspace, purpose-built module in an existing tool, whichever fits your environment. Populate it with the current commitments book. Reconcile against the CRM and the ops plan. Expect to find variance. Work through it.
Weeks five to eight: enforce the discipline. Commercial updates on commitment. Operational acknowledgement before confirmation. Daily five-minute check. Visible change log. Expect resistance. The resistance is the point; it tells you where the old informal patterns are strongest, and those are the patterns that have been costing you money.
Weeks nine to twelve: measure and tune. Start reporting on the five metrics. Commitment-to-plan variance. Time-to-acknowledgement. Change log density. Exception escalation. Customer-surprise events. Use the first month of data as the baseline. Identify the one or two patterns most responsible for the variance. Target them specifically.
By week twelve, the organisation has shifted from having two reconciled-at-meetings views of commercial and operational reality to a single shared record that drives behaviour. The metrics are not yet world-class. The discipline is not yet automatic. But the structural change is in place.
From there, the real work begins: deepening the integration, connecting to upstream and downstream systems, extending the record to cover more categories of commitment. But none of that later work pays off if the foundation is not laid. And the foundation is not a platform. It is a record and a set of behaviours around it.
The shared handover record is not a CRM replacement. CRMs remain the right tool for relationship management, pipeline tracking, and contract management.
It is not an ops system replacement. Mine planning, rail scheduling, stockpile management, port operations, and shipping all remain where they are.
It is not a heavyweight S&OP process. S&OP may be the right destination; the handover record is the foundation that makes S&OP actually work, rather than being a performance of planning.
It is not a consultant-led transformation. Consultants can help; the discipline has to be owned by the operating teams, or it will not stick after the consultants leave.
What it is is a structural answer to a structural problem. Sales operations alignment fails by default because two legitimate views of reality have been allowed to live in separate systems, with meetings and emails as the only bridge between them. The handover record builds the bridge into the system itself.
The commercial-operational divide has always been expensive. What has changed is the cost of leaving it unaddressed.
Customers are more demanding about transparency. The expectation of transparency that used to be a nice-to-have is now a procurement requirement. When a customer asks for real-time shipment status and the commercial team cannot provide it without calling operations, the gap becomes visible externally as well as internally.
Regulators are more demanding about evidence. Scope 3 emissions reporting, CSRD compliance, and traceability requirements: the evidence trail runs from mine through port to vessel, and it requires the commercial and operational records to align. If they do not, the regulator’s question cannot be answered with confidence. See our piece on scope 3 emissions as a competitive edge for more on this.
Competitors are moving faster. Exporters investing in integrated commercial and operational capabilities are setting expectations in the market. Customers who experience that capability elsewhere bring it back to their other suppliers as a baseline. Exporters who have not closed the divide will find themselves explaining why, not demonstrating what.
Capital is more scrutinised. When weak sales operations alignment costs several per cent of revenue, and capital is priced tightly, that gap is no longer absorbable as the cost of doing business. Boards are asking where the operating leverage will come from. The answer, for most exporters, is here.
If you take one thing from this playbook, let it be this: the gap between what sales promises and operations delivers is not a communication problem. It is a structural problem, and it has a structural answer. Sales operations alignment is built, not declared.
You do not need a new system. You do not need a transformation programme. You need one shared record of every commitment made to a customer, a discipline of updating it at the moment of commitment, and a measurement framework that tells you honestly whether the divide is closing.
Most of the organisations that will be commercially strong in bulk commodity export over the next decade are the ones that get this right. The brand promise, reliability, quality, relationship, lives or dies at the handover between commercial and operations. Everything else is theatre over a structural reality that customers eventually see through.
Start small. Start now. One shared handover record. Three disciplines. Five metrics. Twelve weeks.
If you would like to talk through how this looks in Practise for your operation, or see how SCIAR’s platform supports the integrated commercial-operational view, get in touch with the team. The gap costing you the most is the one you can close the fastest.
Nick Ogle has over 30 years of experience in Enterprise IT, spanning engineering, sales, and marketing roles across Australia, the USA, and APJ for various IT vendors.
Nick is passionate about entrepreneurship and Software innovation that drives positive change. Currently, he is the Sales & Marketing Manager at SCIAR Systems, a Newcastle-based SAAS startup, where he is helping commercialise their groundbreaking Bulk Commodity Logistics solutions.
For more information on Nick and to find articles that have been written on the IT sector in the past, feel free to look at his LinkedIn profile or browse some of the additional articles Nick has written for SCIAR.