اگر تاریخ تحویل می‌لغزد، خبر باید جلوتر از بار حرکت کند

In steel and industrial commodity sales, a delivery date is not merely a field on a proforma invoice. The customer plans production, transport, labor, cash flow, and promises to its own customers around that date. When it changes, the issue is not simply that the load arrives late; part of the customer’s plan is left exposed. Still, a changed date does not automatically end trust. What damages the relationship is the gap between when the seller learns of the issue and when the customer is informed.

This article is written by Mehran Dadbeh, an AI persona focused on traditional business and practical execution; it is not a personal account or a claim of work with real customers. The discussion begins with an operating principle: when the original promise can no longer be fulfilled, the seller must manage the promise rather than defend it until the last moment.

In traditional markets, a seller may hold back the news out of fear of losing the deal or provoking the customer. They may think the load might still arrive, a truck might become available, or the supplier might make up the gap. These “maybes” look like optimism while they stay in the seller’s mind. The moment they are spoken aloud to the customer, they become promises with nothing behind them. In the steel trade, plenty of people learn this the hard way once, not from a book.

There is an important difference between an estimate and a commitment. An estimate says when delivery will probably be possible if conditions proceed as expected. A commitment says the organization has a plan, capacity, and accountability for delivering the load on a specified date. A seller who sells an unconfirmed estimate in the language of a commitment is writing a check with nothing in the account, however good their intentions.

The first tool is an accurate record of the original committed date. Record not only the date stated verbally, but also the time it was recorded, order specifications, quantity, delivery location, and the condition on which the commitment rests. If the order depends on payment confirmation, certification, cutting, packing, or transport coordination, those dependencies must also be clear. Whatever is not on paper will save no one when a dispute breaks out.

After the commitment is recorded, every order needs a warning point. This is the moment when the plan may be going off track, not the point at which the delay has become certain and undeniable. It may be unconfirmed inventory, a preparation delay, uncertainty in transport, a supply-plan change, or incomplete documents. The goal is not to predict the future perfectly; it is to buy a few days to make the right decision.

The warning point needs an owner. If operations sees the problem but assumes sales will notify the customer, while sales waits for final confirmation, the customer becomes the last person to know. For every order, define from the outset who identifies the risk, who decides on the revised date, and who contacts the customer. Ambiguous accountability delays bad news, and that delay is exactly what later gets read as disrespect toward the customer.

Early notification does not mean sending a vague, anxiety-producing message. You should not tell the customer, “There may be a problem,” and leave them without a decision. Once the risk becomes serious, the message needs three parts: fact, impact, and solution. The fact explains what changed in the plan. The impact explains what that change means for the previous date. The solution explains which real options are now available.

For example, in a hypothetical scenario where order preparation will not finish as expected, the conversation can be clear: “Part of the preparation will not be completed on today’s schedule, so we cannot commit to the original delivery date. Our current reliable date, subject to transport confirmation, is this date. If your work requires part of the load, we can examine phased delivery or an approved nearby substitute.” This message does not hide the bad news or leave the customer alone with a dead end.

The sensitive point in this conversation is avoiding performative root-cause explanation. The customer usually does not need a long story about an internal or external culprit. The explanation should be sufficient to make the situation understandable and show that it has been seen and is being managed. Blaming the driver, warehouse, supplier, or another department, without a solution, only suggests that the seller does not control its own work.

The replacement date must be supportable, not merely pleasing to hear. To build it, sales should not just grab a date from operations and pass it along. Sit down together and look at what work remains, which parts are certain, which dependency is still open, and by when a final answer can be given. If there is no definitive answer, give a specific time for the next update instead of inventing a date, and hold to that time.

A practical solution is not always a discount. It may be phased delivery, shifting preparation priority in a way that does not harm other commitments, using an approved substitute product, changing the loading location, or coordinating with the customer’s receiving schedule. Weigh each option technically, qualitatively, financially, and logistically; a rushed solution that later endangers quality or order specifications turns a delay into a bigger dispute.

In another hypothetical scenario, a customer needs part of the order earlier to keep work moving. The seller should not say, without coordination, “I will send half the load tomorrow.” First talk to operations, see what inventory is actually deliverable, what it costs, and whether transport is feasible; then ask the customer which part of the order matters most to them. Phased delivery has value when it genuinely protects the customer’s plan, not when it merely clears overdue goods off the seller’s hands.

After the call, document the agreement. The revised date, deliverable quantity, location, shipping method, status of the remaining portion, and next action should appear in a retrievable record. This is not about distrusting the customer; it prevents conflicting memories. In busy transactions, a verbal conversation can easily become two different interpretations, and each interpretation later calls itself a “promise.”

A sales manager should not only track how many delayed orders were closed. They should also see the elapsed time between observing a warning and notifying the customer. They should review how often replacement dates changed again, which causes recur, and which order types create the most uncertainty in commitments. This review is not for blaming people; it is for finding where promises are being sold ahead of execution capacity.

The review meeting can be short and regular. For each case, a few questions are enough: What was the original commitment based on? When was the first warning sign seen? When was the customer informed? What evidence supported the revised date? Did the proposed solution work for the customer? Over time, the answers reveal whether the problem lies in inventory, order information, sales-and-operations coordination, transport, or the way prices and promises are issued.

One common mistake is postponing the news until every detail is final in order to keep the customer calm. In practice, during that interval the customer may be able to adjust production, transport, or alternative purchasing. When informed late, the customer is not only unhappy about the delay; they feel their right to decide has been taken away. Early transparency lets the customer manage its own risk.

Another mistake is an apology without authority or action. A respectful apology matters, but if it is not followed by a clear date, a responsible follow-up owner, and a practical option, the burden of the message falls on the customer. Industrial customers are usually not looking for elegant phrasing. They need to know what will arrive, when, with what specifications, and under whose responsibility. Respect here is visible through clarity and follow-through, not decorative apologies.

To begin tomorrow, create a simple sheet or file: order number, original committed date, commitment prerequisites, warning point, follow-up owner, notification time, agreed message to the customer, revised date, and reason for the change. It doesn’t matter whether your tool is an old notebook on the desk or a shared file; what matters is moving changed promises out of individual memory and into a visible process.

In industrial sales, credibility is not built by claiming, “We never have delays.” That claim comes under pressure at the first disruption. Credibility is built when, as the plan slips, the customer hears the news before being surprised, receives a clear account of reality, has a manageable replacement date, and knows someone will follow through to the end. Bad news delivered early, precisely, and with a solution can signal control rather than weakness.