وقتی سیستم موجودی را نشان می‌دهد اما کالا قابل‌تحویل نیست: پاسخ به اعتراض مشتری بدون وعده تازه

The objection usually begins with one simple sentence: “Then why did you say it was in stock?” At that moment, the salesperson is not merely facing a technical discrepancy; they are facing a gap in trust. The customer made a decision based on information received from the business and now wants to know whether the next piece of information can be trusted. A rushed response, even when intended to calm the customer, can widen that gap.

A distinction is needed between “recorded inventory” and “deliverable inventory.” A product may appear in the system while also being reserved for another order, in transfer, held for quality control, awaiting cutting or preparation, or unavailable for allocation to this order because of its specification or quantity. An inventory number alone is not authorization to promise delivery.

This distinction is sharper in steel and industrial distribution. Actual weight, grade, thickness, certificate status, storage location, cutting capacity, loading feasibility, and allocation priority can all affect deliverability. A salesperson should therefore not infer from a number on a system screen that the material is ready to leave the site.

The central mistake occurs when a business substitutes a technical explanation for a clear answer in order to defend itself. Phrases such as “the system showed it incorrectly,” “the warehouse has not responded,” or “my colleague did not enter it” may explain an internal cause, but they do not tell the customer what is genuinely reliable. Blaming someone in front of the customer neither finds the material nor restores trust.

The purpose of the first call or message is not to solve every part of the issue. It is to ensure that the customer clearly understands which part of the earlier statement was wrong or incomplete, what is now confirmed, what remains unknown, and who will verify it by when. The conversation can be managed in three stages: separate facts from system data, state the unknowns plainly, and assign a follow-up action to a specific owner.

In the first stage, state the fact briefly and directly. Rather than saying, “We have stock, but something has come up,” say: “The inventory was recorded in the system, but its availability for allocation and delivery has not yet been confirmed in the initial review. Therefore, our earlier information was not sufficient to make a delivery commitment.” This is not defensive, but it also does not hide responsibility for the quality of the earlier information.

There is no need to expose every internal detail in the first response. The customer usually does not need the warehouse user’s name, conflicting reports, or the path of a software error. What must be clear is the commercial effect: can the requested material be committed with the same specifications or not? And if the answer is not yet final, why is it incomplete? Share details that improve the customer’s decision, not details that merely display internal disorder.

Before making contact, the salesperson should create a verifiable review instead of asking the broad question, “Do we have this item?” Product code, agreed specifications, quantity, physical location, reservation status, quality-control status, processing requirements, preparation capacity, and loading feasibility should be checked separately. If any one of these remains unclear, the final status remains unclear, even when the inventory number is positive.

To reduce ambiguity, separate the statuses in sales language. “Recorded in the system” means data exists. “Physically confirmed” means its location and quantity have been checked. “Allocatable” means it has not been set aside for another order or another restriction. “Ready for delivery” means the necessary controls, preparation, and ability to release it have been established. Sales should communicate only a status supported by evidence.

The second stage is stating precisely what is still unknown. This can be difficult because a salesperson may fear that admitting uncertainty will look weak. Yet an uncertainty stated plainly and within clear limits is more trustworthy than artificial confidence. A suitable phrase is: “At this point, I cannot confirm a delivery date or a substitute because allocation and preparation have not yet been verified.”

At this stage, avoid three types of statements: invented dates, selling probability, and vague conditional promises. “It will probably be sorted by tomorrow,” “I do not think there will be a problem,” and “If the warehouse confirms it, we will ship quickly” can easily become promises in the customer’s mind. If the condition, decision owner, and review time are not clear, such statements only create hidden commitments.

The third stage turns follow-up into visible work. Good follow-up has three parts: a specific action, a specific owner, and a specific time for returning with a result. For example: “The allocation owner will check the physical inventory and reservation status by 3:00 p.m. today. I will remain your order contact and report the confirmed or unconfirmed result through this channel by 3:30 p.m. today.” The time for reporting a result differs from the delivery date and should not be presented as the same thing.

The owner of the follow-up should be one person or one accountable role, not the vague phrase “the relevant department.” The customer should not have to navigate your internal structure. The salesperson can remain the accountable contact even when the review is performed by warehouse, planning, quality control, or sourcing. What matters is that the customer knows which channel will provide the next answer and what review it will be based on.

The verification time must also be realistic. Setting an overly short window merely to calm the customer, when a review cannot actually be completed within it, is simply another new promise. It is better to provide a defined time for reporting the result, such as “by [specific time] today” or “by [specific time] on the next business day.” If the review encounters an obstacle, update the customer before that time arrives rather than remaining silent while waiting for a complete answer.

A practical response can sound like this: “Our earlier information was based on recorded inventory, but its availability for allocation and delivery has not yet been confirmed. We are now reviewing the physical status, reservation, and preparation requirements. By [specific time], I will give you the result of that review, not an unconfirmed delivery date. After confirmation, I will clearly present the workable options.” This framework accepts responsibility while controlling the scope of the promise.

Once the facts are confirmed, present options in order of practical feasibility. The same material may be deliverable, only part of the quantity may be allocatable, an alternative specification may require customer approval, or no option may be available. Never treat a substitute as equivalent to the original item by default; differences in grade, dimensions, certification, preparation time, or cost must be clear before the customer decides.

If the outcome is negative, a professional response means stating the limitation clearly, not extending hope. You can say: “This quantity with these specifications cannot currently be committed.” Then present only options that can actually be examined: a lower quantity, an alternative specification, sourcing through another route, or pausing the order until the matter is resolved. The final choice should be based on the customer’s need, not merely on the seller’s need to close the conversation quickly.

After the individual case is resolved, every discrepancy should become an input for process correction. Record which status was communicated incorrectly: system data, reservation, specifications, quality control, processing, loading, or sales rules. Also identify the point at which sales turned the phrase “in stock” into “deliverable” without sufficient evidence. The purpose is not to blame an individual; it is to close the same gap next time.

Consider a fully hypothetical example: a salesperson sees positive inventory for a sheet order and tells the customer it is available. A later review shows that part of the quantity is reserved and the rest requires specification checks before dispatch. The right response is not for the salesperson to say, “The load will arrive tomorrow.” The right response is to explain the difference between system records and deliverability, assign a review owner, and return with a result at the stated time.

This approach may not look as attractive in the moment as a quick promise, but it takes the conversation out of guessing and self-defense. In this situation, trust is not built by making the first response complete; it is built by correctly drawing the boundary between what is known, what is unknown, and what will happen next. This article was prepared under an AI author identity, and its recommendations are a general operational framework, not a personal-experience narrative or a claim about a real case.