---
title: "Warehouse vs Store Stock Mismatch: How to Settle It Before Dispatch"
slug: "warehouse-vs-store-stock-mismatch"
published: "2026-08-24"
author: "Ravi Chandel"
---

# Warehouse vs Store Stock Mismatch: How to Settle It Before Dispatch

Your salesperson says stock is available, but your warehouse says otherwise. Resolve the mismatch by checking the same item, unit and supplying store, then reviewing movement/history and confirming the shelf before you promise dispatch.

## Start with the location that must fulfil the order

Use the location that will load the order as the referee. Check its item, unit and recorded balance first; then review the recent stock entries before you promise the retailer a dispatch date.

This sounds simple, but the disagreement usually starts because two people are answering different questions. The salesperson may remember 180 cartons in the business. The warehouse supervisor may have 42 cartons in the branch that must load the vehicle. The owner may be looking at the combined number across the godown, branch and shop. All three numbers can be correct and still produce a wrong customer promise.

For Indian distributors, wholesalers, FMCG stockists and multi-location retailers, the useful question is not only “Do we have this item?” It is “Which store has it, in which unit, and can that store supply this order?” This is the same location check that matters in [wholesale and distributor stock management](/stock-management-software-for-wholesalers-distributors) and [FMCG distributor inventory management](/inventory-management-software-for-fmcg-distributors). Location-wise, store-wise or godown-wise stock becomes useful when everyone checks the same place.

If the mismatch appears only after a sale makes the supplying shop’s balance negative, follow the [negative-stock troubleshooting guide](/blogs/why-stock-goes-negative-after-sale) before promising a transfer or changing the balance.

If the recorded quantity still needs a shelf check, use the [live stock count routine for a shop that stays open](/blogs/how-to-count-stock-without-closing-shop?utm_source=blog&utm_medium=organic&utm_campaign=warehouse-vs-store-stock-mismatch&utm_content=shelf-check-routine) to count one marked area without stopping every sale.

## Why the salesperson and warehouse report different stock

There are four common reasons for the mismatch:

1. **The location is different.** The salesperson remembers stock at the main godown, while the order is being dispatched from a branch or shop.
2. **The unit is different.** One person is talking about pieces, another about boxes, and the purchase team is thinking in cartons.
3. **A recent entry changed the number.** A purchase inward, sales outward, return or transfer was recorded at the location after the last conversation.
4. **Staff cannot see the same stores.** A staff member may work with one store while the owner or salesperson is considering the whole business.

The fix is not a longer argument. It is a short check with a fixed order: item, unit, location, recorded number, recent movement and physical shelf check.

## Quick answers for a warehouse and store stock mismatch

### What should I check first?

Check the exact item and unit at the location that must dispatch the retailer order. Do not start with the combined business total.

### What if another godown has the item?

Treat it as stock at another location. Check that source location’s own requirement and the time needed to move the cartons before you change the dispatch promise.

### What can Stock Register help me see?

Stock Register can show item details by store and the recorded stock movement/history for an item. It can also limit staff access by store. Your team still has to find the carton and decide whether to dispatch or move it.

### What should I tell the retailer?

Give a date and quantity only after the supplying location has enough recorded stock and the godown team confirms the carton or shelf. If stock is at another store, give a realistic transfer or dispatch date instead of saying “available” without a location.

## Use six checks before you promise dispatch

### 1. Name the item the same way

Write the item name, pack size and unit in the retailer order. “Biscuit stock” is not enough. “Parle-G 800 g carton, 30 cartons” gives the salesperson, store staff and godown team one question to answer.

If your team uses pieces, boxes and cartons interchangeably, write the selling unit beside the quantity. A mismatch in unit can look like missing stock even when the recorded entries are correct.

### 2. Name the supplying store

Write Jaipur godown, Kishangarh branch or Ajmer shop—not just Rajasthan or Ajmer district. The supplying store is the location that has to make the order ready. Stock in another godown can help, but it does not make the dispatching store ready today.

### 3. Check the recorded store balance

Open the item details for the supplying store. Compare the recorded quantity with the retailer requirement. This is the first point where [store-wise stock in Stock Register](/features/multi-godown) settles the broad “available or not” argument into a quantity and location.

### 4. Read the recent movement

Look at the item’s recorded movement/history around the date of the disagreement. The [stock tracking and item history page](/features/stock-tracking) explains the recorded entries a merchant can review. A purchase inward may have increased stock at the main godown. A sales outward entry may have reduced the branch balance. A return or internal movement may explain why the salesperson’s older number no longer matches the store view.

Use the history to find the entry that needs checking. A history entry tells you what was recorded; it does not prove that a carton is on the shelf.

### 5. Check staff and store access

Ask whether the salesperson, warehouse supervisor and staff member are looking at the same store. [Staff roles and store access](/features/staff-roles) help an owner check which location a staff member can work with, but two staff accounts may not show the same set of stores. Confirm whose view is being used before treating a difference as an error.

### 6. Confirm the shelf before you commit

Ask the godown team to locate the carton, confirm the unit and report whether it can be loaded. A recorded balance is the right starting point for the conversation. It is not a substitute for the last physical check before dispatch.

## Example: one item, three locations and one retailer order

A distributor receives an order for 30 cartons of Parle-G 800 g. The salesperson says, “We have enough.” The Jaipur godown says, “Not here.” The owner checks all three locations:

| Location | Recorded cartons | Retailer order | First decision |
| --- | ---: | ---: | --- |
| Jaipur godown | 180 | 30 | Check the shelf and prepare dispatch. |
| Kishangarh branch | 42 | 30 | Stock exists elsewhere; do not call it Jaipur stock. |
| Ajmer shop | 0 | 30 | Do not promise this shop for the order. |

The combined number is 222 cartons, but the combined number is not the dispatch answer. Jaipur has 180 recorded cartons, so after a 30-carton order the recorded balance would be 150 cartons. Kishangarh has 42 cartons, but those cartons need a separate movement decision if the retailer order must leave Jaipur. Ajmer has none for this order.

The salesperson was broadly right that the business has the item. The warehouse team was right that the item was not available at every location. The correct customer answer comes from the supplying location, not from the broadest number.

## What the example teaches the sales team

Salespeople need a location in the order note. “Available” should become “180 cartons recorded at Jaipur godown” or “42 cartons recorded at Kishangarh branch.” That small change stops the warehouse from receiving an order with a hidden location problem.

It also gives the salesperson a useful next question: “Which store can supply the order, and by when?” If the retailer needs same-day dispatch, stock at another branch may not solve the order. If next-day dispatch is acceptable, the transfer can be discussed with the right people.

## What the example teaches the warehouse team

The warehouse team should answer with the location, item, unit and recorded quantity. “No stock” is incomplete if the godown has 180 cartons but the staff member searched for pieces or a different pack size. “Stock available” is also incomplete if the quantity is at another store.

The best reply is practical: “Parle-G 800 g carton: 180 cartons recorded at Jaipur; 30 requested; shelf confirmation pending.” That gives sales, store staff and the owner the same next step without pretending that software has checked the shelf.

## Use the movement history to find the disagreement

Suppose the salesperson saw 210 cartons at Jaipur on Monday. On Wednesday the store view shows 180 cartons. The first question is not “Which person is wrong?” Check the recorded entries:

- Was there a 30-carton sales outward entry from Jaipur?
- Was the entry made against the right item and unit?
- Did a return or correction change the number?
- Was the movement recorded at Jaipur or another store?
- Does the store staff member have access to the location being discussed?

Stock movement/history gives the team a place to investigate the recorded change. It does not tell the team whether a carton was placed on the wrong shelf, whether a carton is damaged, or whether a physical count should be accepted without a human check.

## Keep the staff view close to the staff job

A store manager at Jaipur needs Jaipur stock and the entries that affect Jaipur work. A person responsible for several godowns may need a wider view. Store-based staff access can help the owner keep location visibility closer to each person’s work.

Before you compare two staff reports, write down:

1. Which staff member is reporting?
2. Which store or stores can that person access?
3. Which item and unit are they using?
4. Which date or recent entry explains the number?

Store access will not fix a wrong entry or a missing carton. It does tell you whether two people are looking at the same set of stores before you compare their numbers.

## Decide what to say before you call the retailer

### Say “ready to dispatch” when

The item and unit match, the supplying location has enough recorded stock, the recent movement does not need clarification, and the warehouse team confirms the carton or shelf.

### Say “we are checking the location” when

The salesperson has a combined number, the branch number is different, the unit is unclear, or a recent entry needs a human check. This is better than committing to a date the warehouse cannot support.

### Say “available from another store” when

The item is recorded at a different godown or branch. Add the expected movement and dispatch date only after the source location’s own requirement and the transfer responsibility are clear.

### Say “not available for this dispatch” when

The supplying store has zero or insufficient recorded stock and another location cannot support the order in time. The retailer can then decide whether to wait, accept a substitute or reduce the order.

Use this short decision table in the order note so sales and the supplying store repeat the same answer:

| Dispatch answer | Use it when | What to tell the retailer |
| --- | --- | --- |
| Ready to dispatch | The supplying store has enough recorded stock and the shelf is confirmed. | Name the store, quantity and dispatch date. |
| Checking the location | The unit, recent entry, store balance or shelf still needs checking. | Say when you will confirm; do not promise from the combined total. |
| Available from another store | The item is recorded at a different branch or godown. | Name the source store and give a date only after movement timing is clear. |
| Not available for this dispatch | The supplying store is short and another location cannot support the order in time. | Offer a later date, a different source or a smaller quantity. |

## What Stock Register helps you check

For the record side of this check, Stock Register gives you three places to look:

For the product workflow behind this check, see [location-wise stock management for stores and godowns](/location-wise-stock-management). It shows how to find the supplying location, record a stock move and review what changed before the customer gets an answer.

- **Store-wise item details:** see where the item is recorded across shops, branches and godowns.
- **Stock movement/history:** review the recorded stock entries that changed an item’s number.
- **Staff/store access:** keep staff access connected to the stores they work with.

These records narrow down the disagreement. Your team still needs to search the shelf, check the carton condition, confirm loading and make the final customer promise. Stock Register does not reconcile the record with the shelf, reserve cartons, show in-transit status or approve a transfer.

## Common mistakes that create this mismatch

### Using the combined total for a dispatch promise

The business may have 222 cartons, but the supplying branch may have 0. Always name the dispatching store.

### Asking for “stock” without the unit

Pieces, boxes and cartons can create different answers. Put the unit in the order note and in the store conversation.

### Treating another store’s balance as ready stock

Another location can be a source for a transfer. It is not the same as stock already ready at the dispatching godown.

### Ignoring recent movement

If the salesperson’s number is from Monday and the store view is from Wednesday, check the entries between those conversations.

### Giving every staff member a business-wide answer

Staff may have access to selected stores. Ask which locations their view includes before comparing their numbers.

### Treating the software number as a physical count

Recorded stock helps the team choose what to check. It does not remove the need to locate the carton before a time-sensitive dispatch.

## A five-minute daily stock conversation

For each urgent retailer order, ask the team to answer five lines:

1. Item and unit:
2. Retailer quantity:
3. Supplying store:
4. Recorded quantity and last relevant movement:
5. Shelf confirmation and dispatch answer:

Keep that small conversation consistent across the main godown, branches and shops. You do not need a large report for every order; you need a quick answer to what can leave which store, and when.

## When the same item keeps causing calls

If the same item creates a new argument every few days, look for the repeated hand-off rather than blaming the latest person who reported a number. Ask the salesperson to include the pack size and supplying store when the order is taken. Ask the warehouse lead to reply with the recorded quantity, the recent movement and the shelf-check status. Ask the store manager to say whether the cartons are ready for loading, held for another customer or still being located.

For a distributor with a main godown, several branches and retail counters, this gives each person a job-sized answer. Sales needs a promise it can repeat to the retailer. The warehouse needs a location and quantity it can check. The owner needs enough history to see whether the difference came from a late entry, a different unit, another store or a physical count that still needs attention.

Do not turn every disagreement into a long meeting. Put the five-line daily check beside the order or in the team message. If the same item still appears with different units or locations, correct the way the item is named and recorded. If the recorded movement looks right but the shelf is short, keep that as a warehouse follow-up instead of changing the customer promise from memory.

Everyone does not need the same screen. They do need to agree on the store being checked, the number recorded there and the step that must happen before the retailer gets a dispatch promise.

## A weekly review for owners and warehouse leads

Once a week, choose the items that caused the most calls, substitutions or delayed dispatches. Compare the salesperson’s order note, the supplying store’s recorded balance, the recent movement/history and the staff access involved.

Look for patterns:

- the same item is entered in two units;
- one branch is repeatedly treated as part of the main godown;
- sales outward is recorded late or at the wrong store;
- staff cannot see the store they are asked to report on;
- the combined total is healthy while one route location is short.

Use that review to fix the next order note, location name or staff-view question before it causes another call.

## Stock mismatch questions for Indian multi-location businesses

### How do distributors check stock before promising a retailer order?

They check the exact item, unit and supplying godown, review the recent recorded movement, and ask the warehouse to confirm the shelf before giving a dispatch date.

### Why is warehouse stock different from store stock?

The warehouse and store may be different locations, use different units, have different recent entries, or be viewed by staff with different store access.

### Can Stock Register show stock by store?

Yes. Store-wise item details help a merchant compare the same item across shops, branches and godowns.

### Can Stock Register show why the stock number changed?

The recorded stock movement/history can show the entries connected to an item’s change. The team still needs to investigate any physical or entry mistake.

### Can staff see every store?

Not necessarily. Staff access can be set by store, so confirm which locations the staff member can view before comparing their report.

### Does Stock Register automatically reconcile warehouse and physical stock?

No. Stock Register helps you inspect recorded store-wise stock and movement/history. Your team still has to check the physical stock, find the cause and decide what to do next.

## The answer to keep with every order

When the salesperson says available and the warehouse says no, do not choose a person to believe first. Choose one item, one unit and one supplying store. Check its recorded number, review the recent movement, confirm the staff view and ask for the shelf check. Then give the retailer a dispatch answer that names the location and date.