Planning Inter-Store Transfers in Excel: Where It Breaks Down
What Excel does well for inter-store transfer planning, the eight points where it gets stuck, and eight signs that it is time to move to software.

Excel can plan inter-store transfers for a small chain with a short product list and a weekly rhythm. It gets stuck when the number of store, product and size combinations outgrows what a planner can review, when the data is already old by the time the list is ready, and when nobody can say afterwards why a move was made.
What Excel does well
A spreadsheet is a reasonable first tool. It costs nothing extra, the planner controls every formula, and a rule can be changed in a minute. For a chain with a few stores and a stable assortment, a weekly export of sales and stock, a pivot table and a sorted list of gaps will find the obvious moves. Many transfer rules that later run in software were first worked out this way.
Where it gets stuck
| Sticking point | What it looks like | What it costs |
|---|---|---|
| Size of the problem | Every store paired with every other store, for every product and size; the file slows down and the planner reviews only the top rows | Most opportunities are never looked at |
| Data age | Export, clean, calculate, check, send: the list reflects stock from days ago | Stores are asked to send units they have already sold |
| Stock in transit | Units already on their way to a store are not in the export | The same gap is filled twice |
| Size logic | Rules work on totals per product, because size-level formulas are too heavy | Transfers break size runs in the sending store |
| Conflict with replenishment | The warehouse team ships to a store the same week a transfer arrives | Overstock in the receiving store |
| One owner | One person understands the file | Holidays and resignations stop the process |
| No memory | Each week's file replaces the last | Nobody can check whether past moves sold |
| Re-keying | The list is typed into the ERP as transfer documents by hand | Errors, and a day lost before stores see it |
None of these is a fault in Excel. They are the point at which a calculation tool is being used as a decision system.
Eight signs it is time to move to software
- Building the weekly list takes more than a working day.
- The planner reviews one product group per week and never reaches the rest.
- Stores regularly report that the requested units are no longer there.
- The same product travels back and forth between two stores in one season.
- Transfers are decided on product totals, and stores complain about leftover sizes.
- Nobody can state what last month's transfers sold.
- The process stops when one person is away.
- Store count or assortment has grown since the file was designed, and the review rhythm has slowed down.
Two or three of these signs are normal friction. Five or more mean the spreadsheet is setting the limit on how well stock is balanced.
What changes with software, and what does not
It helps to separate two layers. The record system, usually the ERP, creates the transfer document and updates stock in both stores. The decision layer chooses which transfers are worth making. Excel has been doing the second job. Replacing it does not mean replacing the ERP.
| Step | With a spreadsheet | With a decision layer |
|---|---|---|
| Data | Manual export | Read from the ERP and POS on a schedule |
| Coverage | Top rows of a sorted list | Every store, product and size |
| Rules | Formulas known to one person | Shared settings: minimums, core sizes, last transfer dates |
| Review | Planner builds the list | Planner approves or rejects recommendations |
| Execution | Re-keyed into the ERP | The approved list goes to the ERP for execution |
| Follow-up | Rarely done | Results of past moves are kept and compared |
What does not change is the planner's judgment. The rules in the spreadsheet (which stores never send, which products are excluded, how much stock a display needs) are the starting configuration of any software. A team that has run transfers in Excel arrives with those rules already tested.
How Klibre fits
Klibre, the retail planning platform from RNV Analytics, is a decision layer of this kind. Its in-season module recommends inter-store transfers based on sales performance. RNV states that recommendations follow product segmentation and size curves, that they are explainable, and that they are approved in one click, so the team keeps control of what is executed.
Klibre is designed to work with a retailer's existing ERP, POS and inventory systems, including Nebim V3, Odoo, Microsoft Dynamics (including Navision), SAP, Logo and Hitit. A ready connector is available for Nebim V3. RNV states four weeks from integration to go-live.
In RNV's Yargıcı case study, the fashion retailer implemented Klibre's inter-store transfer module, and RNV reports an increase of up to 300% in sales of transferred products. This is RNV's reported result, not an independent measurement.
The method that the software applies is explained in what in-season inventory rebalancing is.
FAQ
Can a small chain plan transfers in Excel?
Yes. With a few stores and a stable assortment, a weekly spreadsheet review finds the main imbalances. The limits appear as stores, products and sizes multiply.
Does the ERP's transfer screen replace Excel?
No. The ERP records and executes a transfer. It does not compare stores and choose which transfers are worth making. That choice is what the spreadsheet has been providing.
What should be prepared before moving from Excel to software?
The rules already in use, written down: exclusions, display minimums, store groups, cut-off dates. Also a check that stock records in the ERP match what is on the shelves.
Will planners lose control?
They should not. The planner's work shifts from building lists to approving recommendations and adjusting rules. A system that cannot show the reason for a move makes that harder, so explainability is worth asking about.
Is Excel still useful afterwards?
For one-off analysis, yes. The weekly decision moves out of it; ad hoc questions stay.