موجودی روی سیستم، هنوز قول تحویل نیست

When a customer asks about delivery timing, the sales response is often shaped by a quick look at the inventory figure in the system: is the item there or not? But that question is not enough for making a promise. The number on the screen may include material already set aside for another order, material awaiting quality control, material that has not yet been cut, or stock that does not actually match the new order’s specifications. Inventory may exist, but it is not necessarily available to promise.

This is not merely a warehouse error; it is a customer communication issue. Customers do not treat the difference between “the item is recorded in the system” and “the item will be delivered on the agreed date” as an internal business detail. They hear a promise and plan around it. When that promise is not fulfilled, trust in the entire sales process is damaged, even when the reason for the shortage appears reasonable inside the organization.

This piece addresses one simple principle: sales should not sell inventory; it should sell the organization’s real capacity to fulfill a commitment. To get there, sales, warehousing, and planning need a shared definition of sellable inventory, one that means the same thing to everyone regardless of individual guesswork or experience.

The first layer is physical inventory: what is actually located in the warehouse, yard, preparation line, or storage area. This layer is essential for operational control, but it is not a sales answer on its own. Material that physically exists may still be unavailable for allocation because of damage, specification mismatch, missing documentation, or an unclear status.

The second layer is reserved inventory. It needs to be visible separately from free inventory, rather than surviving only as a note in colleagues’ minds. A reservation may relate to a confirmed order, a valid quotation, a contractual commitment, replacement material for a defective item, or a priority the organization has accepted. If reservations are invisible to sales, the same unit of inventory may be promised to multiple customers.

The third layer is inventory in preparation, such as material that must be cut, packed, tested, labeled, or transferred from another location. This inventory is not necessarily unavailable, but its readiness time is part of the delivery promise. Presenting it as ready stock hides the true operational lead time and creates conflict when the customer expects loading to begin.

The fourth layer is inventory awaiting a decision. A newly arrived shipment may not yet have been accepted, or its specifications may require approval. Material may be recorded in the system while a final decision on quality, ownership, pricing, or substitution is still pending. This category should not automatically enter the pool of sales options.

The fifth layer is available-to-promise inventory. This is the quantity and specification that can be allocated to a customer with confidence after reservations are deducted, preparation status is considered, quality constraints are checked, and the real dispatch timing is calculated. This definition must be clear, visible, and shared, rather than dependent on a salesperson’s guess or a verbal warehouse response.

For every item, sales needs clear answers: how much is free? How much is already reserved? How much needs an operational step? What is the earliest readiness date? And does the material match the customer’s request? If these answers are not available through a clear path, sales response time may seem fast, but the risk of a broken promise rises as well.

The answer is not to make the sales process unnecessarily complicated. The answer is to design an internal rule for promise-making authority. Sales should know when it can confirm a delivery date immediately, when it should provide only a delivery window, and when it must obtain confirmation from operations or planning before responding. This rule must be simpler than the shortcuts people might otherwise take around it.

In a purely hypothetical example, imagine a salesperson receiving a request for material with a particular specification. The system shows sufficient quantity, but part of it is reserved for another confirmed order and the rest requires cutting. The professional response is not to declare the entire quantity ready. The appropriate response can state the allocable quantity and the confirmed preparation time, while proposing a separate date for the remaining quantity after capacity has been reviewed.

This difference in language matters greatly. The phrase “we have it in stock” is usually translated in the customer’s mind as “you can deliver it.” If an operational step or approval is still required, sales language needs to be more precise: “part of the quantity is ready for allocation,” or “part will be ready after planning confirmation.” Clarity at this stage is not a sign of weakness; it is evidence of control over the commitment.

To make this approach operational, the organization needs a shared inventory view, even if that view is initially built with simpler tools. Every item should have an understandable status: free, reserved, in preparation, awaiting approval, blocked, or available to promise. More important than the appearance of the dashboard are ownership and regular updating of these statuses.

Defining statuses is not enough; each status needs an owner and a clear triggering event for change. For example, a reservation should become active when an order is recorded or a decision is approved, not through scattered messages. A reservation release should be recorded after cancellation, expiry, or a change in commitment. Entry into preparation should also show a start time, estimated completion time, and any likely constraint. Without this discipline, the system is simply a tidier version of uncertainty.

A clear boundary is also needed between an inquiry and a reservation. A customer may ask for pricing and availability while exploring options, but that inquiry should not unnecessarily remove material from the reach of other confirmed orders. Conversely, if the organization decides to hold stock temporarily for a sales opportunity, the validity period and the person responsible for extending or releasing it must be clear from the start.

One common mistake is for sales to obtain a verbal answer from the warehouse in order to preserve speed and then pass it on to the customer. A verbal response can be useful for an initial review, but it should not replace a recorded status. Any promise built on an exception must become a traceable decision; otherwise, it can easily be forgotten when shifts change, material moves, or a new order arrives.

Another sensitive point is substitute material. A warehouse may have inventory, but not in the same grade, dimensions, coating, certification, or conditions expected by the customer. Sales should not treat visual similarity as delivery suitability. A substitution is professional only when its differences are stated clearly and the customer’s approval is recorded before allocation. Otherwise, inventory that seems available becomes a post-delivery dispute.

Coordination meetings are useful only when they turn into a list of decisions rather than a reporting exercise. The team can focus on orders close to their due date, ambiguous reservations, material in preparation, and important requests that are not yet available to promise. The meeting output should make clear who will update which status or delivery time, and by when.

The important measure in this area is not simply the number of orders delivered. The organization should examine how many promises were made before operational confirmation, how many reservations conflicted, which statuses remain in preparation longer than expected, and why dates change. The purpose of this visibility is not to find someone to blame; it is to identify the point where sales language separates from operational reality.

Customer trust is not built by answering every question quickly. It is built by answers the organization can stand behind. When sellable inventory, rather than raw inventory, becomes the basis of the conversation, sales can promise with greater confidence, the warehouse faces fewer sudden priority changes, and planning has more room to manage real capacity. A delivery promise does not begin when stock appears in the system; it begins when the organization can truly fulfill it.