Multi-Warehouse Inventory Management: A Practical Guide to Branch Stock Control
Practical multi-warehouse inventory guide covering branch balances, item locations, transfers, counts, returns and sellable stock. Learn the workflow with Rigi24.

Practical foundation for multi-warehouse control in Rigi24

Multi-warehouse management is not simply a larger version of single-location stock keeping. It is a discipline for keeping the right item, in the right condition, at the right place, with a traceable reason for every movement. In Rigi24, the Inventory module gives you the structure needed to manage warehouses, internal storage locations, items, movements, stock counts, and condition-based classifications such as damaged, repair, and scrap. Used well, this structure reduces avoidable searching, mispicks, silent losses, and the common confusion between what is physically present and what can actually be sold or issued.
The real operational challenge is not counting boxes. It is making decisions fast enough to protect cash flow and service levels. If a branch in another city can see only a vague total instead of location-specific stock, staff may promise customers items that are not genuinely ready to ship. If receiving teams do not separate inspected stock from quarantined stock, “inventory” becomes an illusion. The goal of the following chapters is to turn that confusion into a controlled process with clear responsibilities, explicit stock states, and practical location logic.
1. Executive summary: what multi-warehouse management solves

Multi-warehouse management solves five recurring business problems: stock visibility, allocation discipline, transfer control, condition tracking, and replenishment planning. When these are weak, businesses commonly experience overbuying in one location while another location runs short, repeated emergency transfers, and time wasted reconciling spreadsheets with actual shelves.
In a small business, these failures often look minor. A branch may “have stock somewhere,” but staff spend 20 minutes searching. In a larger operation, that same weakness becomes lost sales, expensive expediting, and stock disputes between teams. Rigi24 is most useful when each movement reflects a real operational event: receiving, put-away, internal relocation, damage write-off, repair return, or stock count adjustment.
What good control should answer instantly
- Which warehouse physically holds the item?
- Is it sellable, damaged, under repair, quarantined, or reserved for a planned purpose?
- Is the quantity in the system aligned with the count in the location?
- Which branch should receive the next replenishment first?
Decision criterion: if a manager cannot answer these questions without asking three people and checking two files, the inventory model is too loose for operational use.
2. Business example: central warehouse in Tbilisi and satellite branch in Kutaisi
Consider an illustrative business with a central warehouse in Tbilisi and a retail-and-service branch in Kutaisi. Tbilisi receives supplier deliveries, stores reserve stock, and prepares transfers. Kutaisi holds a smaller selling range and a limited repair bench. This arrangement works only if the two sites are treated as separate operational nodes, not as one blended stock pool.
Example: Tbilisi receives 120 units of a router model. Forty are intended for immediate branch demand, sixty remain as buffer, and twenty are held for service replacement. If Kutaisi sells seven units in a day, the branch should not “borrow” from the central reserve by informal promise alone. Instead, there should be a defined transfer movement so the system and the shelf match. Without that discipline, the business will show 113 units in one file, 104 on the rack, and a service team waiting for goods that were already promised elsewhere.
Useful rule: central stock should not be treated as a universal safety net unless replenishment timing, transport timing, and branch demand are actually measured. Otherwise, the central warehouse becomes a hidden source of overcommitment.
3. Master data: SKU, variants, units, supplier references and naming
Master data is the language of inventory. If names are inconsistent, stock movements become ambiguous even when the physical handling is correct. Each item should have one primary identity, clear variants where needed, and a stable supplier reference map. In practice, the same device may be sold in black and white, or in 64 GB and 128 GB variants. Those are not cosmetic differences; they are separate inventory identities if customer demand, pricing, or replenishment differs.
A practical naming structure should include a product family, meaningful variant, and unit logic. For example, “Wireless router, dual-band, black” is more useful than “Router A” because staff can recognize the item without consulting extra notes. Supplier references should be recorded as cross-references, not replacements for the internal item identity. That way, if one vendor labels the same item differently, receiving can still map it correctly.
Actionable naming discipline
- Assign one internal item name and keep it stable.
- Separate variant-defining attributes from marketing text.
- Define the stock unit clearly: piece, set, box, or pack.
- Record supplier article codes and GTIN where available.
- Avoid duplicate items created only because a description was typed differently.
Pitfall: mixing “box” and “piece” as if they are interchangeable. If one box contains 10 units, receiving 5 boxes is not the same as receiving 5 pieces. The unit must be explicit at the item setup stage, not discovered during reconciliation.
4. Physical structure: warehouse, zone, aisle, shelf, bin and unique locations
A strong warehouse layout starts with a location hierarchy that mirrors how staff actually search. The simplest useful model is warehouse → zone → aisle → shelf → bin. The purpose is not bureaucratic detail; it is to ensure every stock unit can be placed and found without guesswork. Rigi24’s internal storage locations should be set up to reflect this real structure, not a vague naming scheme like “back room” repeated across departments.
Each location must be unique. If two shelves are both called “A1,” staff will eventually create contradictions during stock counts and put-away. Use a naming convention that allows fast human recognition and machine clarity. For example, TBS-MAIN-Z1-A03-S2-B04 is not elegant, but it is unambiguous. Simpler conventions can work too, provided they never overlap.
| Level | Purpose | Example |
|---|---|---|
| Warehouse | Site-level ownership | Tbilisi main store |
| Zone | Functional area | Fast movers, quarantine, service |
| Aisle | Walking and picking path | A03 |
| Shelf | Vertical storage level | S2 |
| Bin | Exact pick or storage point | B04 |
Decision criterion: if two workers would interpret the same location code differently, the structure is too weak and must be redesigned before scaling.
5. Stock states: sellable, damaged, repair, quarantined, reserved
Stock state management protects margin and service quality. A physical item is not automatically available for sale simply because it exists. It may be damaged, awaiting inspection, reserved for a customer order, or held for repair. Rigi24 supports stock classifications such as damaged, repair, and scrap, so the business should define how each state is used operationally and who may move stock between them.
Sellable stock should be clean, counted, and fit for immediate issue. Damaged stock should be separated at once, not left on a shelf where it can be re-picked by mistake. Repair stock should move into a distinct area with a clear return path. Quarantined stock is especially important when incoming items need review before being released into normal circulation. Reserved stock should be treated carefully in planning, even when the system configuration is simple: a reserved unit is not the same as free stock available for the next order.
Example of a practical state flow
- Received item is checked and placed in quarantine.
- After inspection, acceptable units move to sellable stock.
- Units with a fault move to repair.
- Units beyond economical repair move to scrap or damaged write-off status.
Pitfall: storing repair and sellable items in the same location because space is tight. This saves square meters but creates expensive mistakes later.
6. Receiving: purchase order, inspection, partial receipt and discrepancies
Receiving should begin with a comparison between what was ordered and what physically arrived. The purchase order is the expectation; the shipment is the evidence. Staff must inspect quantity, visible condition, packaging integrity, and item identity before stock becomes operationally usable. If the business accepts everything blindly, later discrepancies become difficult to prove or correct.
Partial receipt is common and should be managed deliberately. Suppose 100 units were ordered, but only 92 arrived. The receipt should record the accepted 92 units, note the missing 8, and preserve the discrepancy for follow-up. If 3 units are dented and 89 are acceptable, those 3 should be separated immediately rather than silently blended into normal stock. This keeps the warehouse record honest and gives purchasing a factual basis for supplier claims.
Receiving procedure
- Match the delivery note to the purchase order.
- Count cartons and, where necessary, open and verify contents.
- Check for visible damage, wrong model, or missing accessories.
- Record accepted quantity and discrepancy reason.
- Move accepted goods to the correct temporary state or location.
Decision criterion: when discrepancies recur with the same supplier, the issue is not just “bad luck”; it is a purchasing control problem that should influence vendor selection and receiving rules.
7. Put-away and slotting: fast movers, heavy boxes, fragile devices
Put-away is the moment when inventory either becomes efficient or becomes hard to find. Slotting means placing goods where they are easiest and safest to handle based on demand, weight, fragility, and turnover. Fast movers should be stored close to the dispatch or picking path. Heavy boxes belong at lower levels to reduce injury and damage. Fragile devices should avoid high-traffic areas and unstable stacking.
Illustrative case: if a small accessory sells 30 times a week, but it is stored in the farthest aisle, staff will waste time on every pick. By contrast, a heavy printer stored on an upper shelf creates lifting risk and a greater chance of damage during retrieval. The best location is not the emptiest one; it is the one that minimizes total handling cost.
Slotting rules that work in practice
- Place fast movers nearest to the main pick route.
- Keep heavy items low and stable.
- Use protected locations for fragile or high-value devices.
- Do not mix unusual shapes with standard cartons unless the bin is clearly marked.
Pitfall: slotting by arrival order instead of demand. Warehouses often become chaotic because the newest receipt is stored wherever there is space, not where future picks will be fastest.
8. Inventory visibility and definitions of physical versus available stock
Visibility means more than seeing a total quantity on screen. The business must distinguish physical stock from available stock. Physical stock is everything physically present in the warehouse or branch, regardless of condition. Available stock is the portion that can actually be sold, transferred, or issued under current rules and practical constraints. A damaged item may be physical stock but not available stock. A quarantined item may be visible but not usable. A reserved item may be physically present yet already assigned to a future demand.
In a disciplined model, inventory visibility should answer not just “how much do we have?” but “how much can we use now, and where is it located?” Example: Tbilisi may physically hold 50 units, but only 38 are sellable because 7 are quarantined and 5 are in repair. Kutaisi may show 12 physical units, but 4 are reserved for a customer installation tomorrow. That distinction prevents false confidence in branch replenishment.
| Quantity type | Meaning | Operational use |
|---|---|---|
| Physical stock | Items present in locations | Counting, storage, reconciliation |
| Available stock | Usable for sale or issue | Promises, replenishment, dispatch |
| Reserved stock | Assigned to a planned demand | Order planning, allocation control |
Final decision rule for this stage: if physical stock and available stock are not separated in daily thinking, the warehouse will appear healthier than it really is. That illusion is one of the most expensive errors in multi-location operations.
Warehouse-to-warehouse transfers and handover checkpoints
A transfer between warehouses is not a simple movement of boxes. It is a controlled change of custody, location, and stock responsibility. In Rigi24, the practical goal is to make the movement visible in Inventory without losing traceability between the sending side and the receiving side. The safest process is to treat every transfer as two linked events: a dispatch record and a receipt record, each checked against the same item list.
What must be agreed before departure
- Source warehouse and destination warehouse names exactly as used in Rigi24.
- List of items, quantities, and, if relevant, batch or serial references.
- Packaging method: loose units, cartons, pallets, or mixed load.
- Who may release the goods and who may confirm receipt.
- Whether damaged, scrap, or repair units may travel on the same shipment.
Handover checkpoints that prevent disputes
- Pick verification: compare physical units with the prepared transfer list.
- Pack verification: confirm count after cartons or pallets are closed.
- Dispatch checkpoint: record what actually left the source warehouse.
- Arrival checkpoint: inspect seals, cartons, and obvious shortages before opening.
- Receipt checkpoint: count and post the received quantity only after checking the contents.
Practical decision rule: if the value or risk is high, do not rely on one count. Count at least twice, once at packing and once at receiving. If the goods are low value and mixed in bulk, a single count may be acceptable, but only if the packer and receiver are different people.
A full example transfer of 12 items with short shipment
Assume Warehouse A sends 12 units of item SKU-A17 to Warehouse B. The dispatch note lists 12 units in one carton. On arrival, Warehouse B opens the carton and finds only 10 units. This is a short shipment, and the record must show the gap clearly instead of forcing the books to match the plan.
| Step | Planned | Actual | Action |
|---|---|---|---|
| Prepared for transfer | 12 | 12 packed | Create the movement with expected quantity |
| Received at destination | 12 | 10 found | Post receipt of 10 only |
| Exception review | 2 missing | 2 short | Investigate packing error, loss, or damage in transit |
How to handle the shortage correctly
- Do not change the original expected quantity after the fact.
- Record the received quantity as 10.
- Document the shortage reason as “short shipment under review” or a similar internal note.
- Check whether the source warehouse still shows 12 dispatched units or whether the discrepancy came from packing.
- If the missing 2 units are later found, add them through a separate correction movement, not by silently editing the first record.
The business question is not only “What arrived?” but “Where did the variance occur?” If the source warehouse consistently shows full dispatch and the destination consistently receives less, the problem may be loading or transport. If the shortfall appears before departure, the problem is packing discipline or count control.
Cycle counting versus annual stocktake and variance investigation
Cycle counting is the steady, targeted check of selected items or locations during normal operations. Annual stocktake is the broader full inventory pause, usually used as a complete review point. They serve different purposes and should not be treated as substitutes.
When cycle counting is the better choice
- High-value items with frequent movement.
- Locations with recurring errors.
- Fast-moving stock where small variances can accumulate quickly.
- Items with a history of picking or receiving mistakes.
When annual stocktake is necessary
- To verify the overall balance of the warehouse.
- To reset confidence after a year of operational changes.
- To review all stock classes, including slow-moving and dormant items.
- To support year-end financial control.
Best practice is to use cycle counts to correct problems early and annual stocktake to confirm the larger picture. If you wait for one yearly event, the cause of a variance may be impossible to trace. If you count continuously without any full review, hidden structure issues may remain unnoticed.
Variance investigation method
- Confirm the physical count again.
- Check whether a pending movement was open at the time of counting.
- Review recent receipts, transfers, returns, and scrap postings for the item.
- Compare the counted location with the recorded location.
- Identify whether the error is in quantity, unit of measure, or wrong item selection.
Illustrative case: if item B22 shows a system balance of 48 and physical count of 45, the three-unit variance may come from a missed return, an unposted transfer, or a picking mistake. The correct response is not a blind correction. The correct response is to find the operational cause, then post a controlled adjustment only after the root issue is understood.
Returns from sales: complete return, partial line, damaged units
Returns must be handled with more precision than outgoing sales because they often mix good stock, defective stock, and uncertain condition. In an inventory system, the key decision is whether the returned goods can be restored to usable stock, must be marked damaged, or should move to scrap or repair status.
Complete return
A complete return means the customer sends back the full sold quantity. If 8 units were sold and 8 units come back in acceptable condition, the goods may return to available stock after inspection. The important control is that the return is not automatically treated as saleable before a person checks condition, packaging, and identification.
Partial line return
A partial line return means only some units from the original line come back. Example: 10 units were sold, 3 are returned. The returned 3 should be received as a separate quantity linked to the original sale line where possible. The remaining 7 stay sold. Avoid rewriting the original sale as if only 7 had ever been sold; that erases history and complicates reconciliation.
Damaged units
If the returned items are damaged, do not put them back into normal stock just because they physically re-entered the warehouse. Classify them according to actual state, for example damaged, repair, or scrap, depending on internal rules. The decision should depend on whether the item can still be sold, repaired economically, or must be removed from usable inventory.
A useful rule: every return needs two decisions, not one. First, does the quantity belong back in inventory? Second, in what condition class does it belong? Mixing these decisions leads to false available stock.
How sales orders, invoice issue and delivery must avoid double deduction
A common operational failure is deducting stock more than once across the sales flow. The risk appears when sales order creation, invoice issue, and physical delivery are all treated as separate stock-consuming events. The business must decide at which stage inventory is reserved, at which stage it is reduced, and which document is only financial.
Control principle
Only one event should reduce on-hand stock for a single sale. The other documents should reference the same transaction without causing a second movement. If your process deducts at order stage and again at invoice stage, shortages will appear even when the warehouse shipped exactly what was sold.
Safe process design
- Sales order: record demand and, if configured, set aside stock logically without posting a second deduction later.
- Picking or delivery: confirm the physical issue of goods.
- Invoice: issue the financial document without duplicating stock removal.
- Exception handling: if quantity changes, correct the sale line and linked movement together.
Illustrative example: a customer orders 5 units, the warehouse ships 5 units, and the invoice is issued for 5 units. If the system already reduced stock when the order was confirmed, then delivery must not reduce stock again. Otherwise the warehouse will show 10 units less than reality after only one physical shipment.
Online store stock reservation and overselling prevention
Online selling requires a separate discipline from warehouse stock visibility. The main risk is overselling: the store accepts orders based on stock that has already been promised elsewhere or is still moving through a transfer, return, or count adjustment. The solution is not simply “show stock online.” The solution is to define what quantity is truly available to sell.
Practical reservation logic
- On-hand stock: what is physically present.
- Committed stock: what is already linked to orders or internal allocation.
- Available stock: what remains after commitments and safety margin.
Where exact reservation behavior is not formally configured, the safe business rule is to sell from a conservative available figure, not from raw on-hand quantity. For example, if the warehouse holds 20 units, 8 are already committed, and 2 are held as safety buffer, the online store should not expose 20 as sellable quantity.
Overselling prevention checklist
- Refresh stock visibility frequently enough for your sales speed.
- Exclude quarantined, damaged, and transfer-in-transit stock from online sale.
- Set a safety reserve for fast movers.
- Review items with repeated stockouts and tighten their sellable quantity.
The decision criterion is commercial stability. A small amount of conservative under-selling is usually better than frequent cancellations, customer complaints, and emergency stock corrections.
Using barcodes and QR safely: scans identify items, not automatically post stock
Barcode or QR scanning is an identification tool, not a substitute for inventory control. A scan can confirm that the person is looking at the right item, location, or logistic unit, but the system should not assume that a scan itself means stock has moved. Physical action must still be verified.
Why this matters
If a scan automatically posts movement, a misread label or accidental scan can create an incorrect transaction. Good practice is to use scanning as the input to a controlled step, such as pick confirmation, receipt verification, or location matching, rather than as the final act by itself.
Safe scanning workflow
- Scan the label.
- System shows the referenced item, location, or package.
- Operator confirms the physical situation.
- Only then is the stock movement posted by the proper transaction step.
Example: scanning a carton label may show 24 units of SKU C09. That confirms identity, not quantity in stock. The carton may still be sealed, partially empty, or already counted elsewhere. Scan data should support the count, not replace it.
GS1 identifiers: GTIN products, GLN locations and SSCC logistic units
GS1 identifiers improve precision when used correctly. GTIN identifies the product, GLN identifies the location, and SSCC identifies a logistic unit such as a pallet or shipment unit. These codes help reduce ambiguity, especially when goods move between warehouses, transport partners, or mixed packaging levels.
How each identifier supports operations
| Identifier | Used for | Operational benefit |
|---|---|---|
| GTIN | Product identity | Reduces confusion between similar items |
| GLN | Location identity | Clarifies which warehouse, dock, or site is involved |
| SSCC | Logistic unit identity | Tracks pallet or shipment unit as a single object |
How to apply them without overcomplicating the process
Use GTIN where product identity must be exact, especially in receiving and transfer documentation. Use GLN where the same company operates multiple sites or storage points and the written warehouse name may be too vague. Use SSCC when one pallet, cage, or mixed shipment unit needs its own unique reference from dispatch to receipt.
Important caution: identifiers do not replace stock logic. A pallet may have a valid SSCC and still contain the wrong quantity, a damaged product mix, or an incorrectly labeled item. Treat the code as a reference that supports control, not as proof that the physical contents are correct.
For Rigi24 operations, the best approach is to keep product, location, and movement references consistent across documents, then use counting and inspection to verify reality. That combination is what prevents most warehouse errors: clear identities, disciplined handovers, and no assumption that a label alone makes stock true.
Governance, controls, and disciplined execution
Once warehouse structure, transfers, counting, sales flow, and item identification are in place, the next task is not more complexity. It is control. A small inventory error can travel through purchasing, pricing, and customer promises within a single week. The practical goal is to make every movement explainable, every exception visible, and every correction attributable to a person, a time, and a reason.
1. Staff access rules, audit history, and separation of duties
Access should follow responsibility, not convenience. The person who receives goods should not be the only person allowed to edit the same stock record later. The person who counts stock should not also be the one approving write-offs without review. In a disciplined setup, each user has a defined scope: who may create items, who may post movements, who may enter counts, and who may approve adjustments. If your organization uses Rigi24’s Inventory module, treat these permissions as a configuration question and verify the exact rights available in your environment rather than assuming a default model.
Audit history matters because inventory disputes are rarely about the latest transaction alone. They are about the chain of events. A useful audit record shows what changed, when it changed, who changed it, and the stated reason. If a count was corrected from 18 to 12, the history should show whether the cause was damaged goods, prior mis-posting, or an unresolved transfer. Without this trail, the warehouse becomes a debate rather than a system.
- Assign each user to one primary role: receiver, storekeeper, branch manager, or reviewer.
- Limit the ability to edit posted documents to a small number of trusted supervisors.
- Require a reason field for all manual adjustments and scrap postings.
- Review change history weekly for unusual reversals, repeated edits, or after-hours activity.
- For high-value items, separate physical handling from record approval.
Decision criterion: if one employee can receive, count, correct, and approve the same stock line alone, the control design is too weak. Even a small branch should keep at least one second-person check on corrections above a chosen threshold, such as items valued above 500 or movements above 20 units.
2. Operating across distant cities, connectivity interruptions, and sync review
Multi-city operations fail when each branch assumes the system “must be correct” and stops reconciling locally. Distance increases risk because errors remain hidden longer. If locations use Rigi24 across several cities, the operating rule should be simple: each branch is responsible for its own local discipline, and headquarters is responsible for reconciling the exceptions. If connectivity is interrupted, the branch should continue physical control procedures and record what occurred so entries can be reviewed later. Do not leave goods moving without a written local log just because the digital entry is delayed.
When links are unstable, the branch manager should maintain a short exception register: time of interruption, documents affected, items received or issued during the gap, and the expected reconciliation step. The purpose is not bureaucracy. It is to stop “temporary” problems from becoming permanent invisible stock drift.
| Situation | Operational risk | Required local action | Review action |
|---|---|---|---|
| Connection loss during receiving | Goods arrive without immediate posting | Use a paper or local log, mark cartons, note supplier and time | Compare log to posted receipt before end of day |
| Connection loss during transfer | Both sites may believe they own the stock | Record dispatch and receiving time separately | Match both sides and resolve timing gaps |
| Delayed count entry | Count result may be overwritten by later movement | Freeze count area if possible | Review any movement during count window |
3. Useful metrics: available-to-sell, stock accuracy, shrinkage, and lead time
Metrics should answer operational questions, not decorate reports. Available-to-sell is the quantity you can promise safely after excluding damaged, blocked, or reserved stock according to your business rules. If you hold 120 units of a router, but 18 are under repair and 7 are visually damaged, your practical available stock is not 120. A manager who sees only the gross number will overpromise.
Stock accuracy compares system quantity with verified physical quantity. If the system shows 500 units and the count confirms 485, accuracy for that item is 97 percent. That sounds good until you notice that the missing 15 units are the exact fast movers needed for a weekend sale. Accuracy should be tracked by item class, not only overall average.
Shrinkage is the unexplained reduction between expected and physical stock after legitimate issues are already recorded. A monthly shrinkage of 2 units on a low-value cable line may be acceptable noise; the same pattern on a high-value switch may indicate process failure. Lead time measures how long it takes to replenish from order to usable stock on the shelf. If replenishment takes 9 days but your fast-selling item sells out every 6 days, your reorder rule is already too late.
- Track available-to-sell by item and by warehouse, not only at company level.
- Review stock accuracy after counts, transfers, and major receiving days.
- Separate shrinkage caused by damage, repair, and scrap from unexplained loss.
- Measure lead time by supplier and by route, because one city lane can be slower than another.
4. Stock replenishment: reorder point, lead time, and safety-stock intuition
Replenishment should be formula-driven, but the formula must be understandable to the team. A simple reorder point uses expected daily demand multiplied by lead time, plus a buffer for uncertainty. If a networking cable sells 12 units per day, supplier lead time is 5 days, and you want a 3-day cushion, the reorder point is 12 × 5 + 12 × 3 = 96 units. That means you place the order before stock falls below 96, not when it reaches zero.
Safety stock is not a luxury. It is insurance against late trucks, sudden promotions, and count errors. But too much safety stock creates slow-moving inventory and ties up cash. The right buffer depends on demand volatility, lead time reliability, and item criticality. A critical switch model with erratic supply deserves more safety stock than a low-value patch cord with daily replenishment.
- Classify items into fast, medium, and slow movers.
- Estimate average daily usage from recent actual issues, not from hope.
- Measure realistic lead time from confirmed order to saleable receipt.
- Add a safety buffer larger for volatile or critical items.
- Review reorder points monthly and after supplier changes.
Pitfall: using one universal reorder point for all branches. A central warehouse with daily deliveries and a remote branch with weekly courier service cannot use the same replenishment logic. Reorder rules must reflect location, route, and customer pattern.
5. Worked scenario: computer network equipment distributor with 3 warehouses
Consider a distributor with three warehouses: City A as the central hub, City B as a sales branch, and City C near a major project customer. The company stocks routers, switches, access points, patch panels, and spare power supplies. The hub receives imports, City B handles same-day orders, and City C stores project reserve stock.
Problem 1: City B frequently shows enough routers in the system, but customer orders are delayed because some units are already damaged or awaiting check. The practical fix is to classify those units separately and calculate available-to-sell by status, not by raw quantity. If 40 routers are on hand, 6 are damaged, and 4 are under verification, the branch should communicate 30 saleable units, not 40.
Problem 2: City C is ten days from the main supplier, but project demand is irregular. The branch should keep higher safety stock on project-critical items and lower stock on generic accessories. For example, 50 spare power supplies may be justified if one contract depends on immediate replacement, while patch cords can be replenished more frequently from City A.
Problem 3: transfers between City A and City B are often delayed in recording. The remedy is a daily transfer closing routine: dispatches recorded before truck departure, receipts confirmed on arrival, and unmatched lines reviewed before the next day starts. If one transfer line remains open for two days, management should ask whether the issue is transport delay, missing paperwork, or actual loss.
6. Daily and weekly checklists for owner, storekeeper, and branch manager
Checklists work because they convert memory into routine. They should be short enough to be used and strict enough to matter.
| Role | Daily checklist | Weekly checklist |
|---|---|---|
| Owner | Review exceptions, stock shortages, unresolved adjustments | Check shrinkage trend, high-value movements, slow movers, branch discrepancies |
| Storekeeper | Post receipts, issue goods correctly, label damaged items, close open receiving tasks | Count fast movers, inspect location order, verify pending transfers |
| Branch manager | Approve urgent corrections, confirm customer-priority stock, review late postings | Analyze stock accuracy, lead-time delays, repeated errors, staff discipline issues |
Checklist rule: if a task is repeated every week with no recorded outcome, it is not a control. Add a result field such as “no differences,” “difference corrected,” or “supplier claim opened.”
7. Mistakes that create phantom inventory and their remedies
Phantom inventory appears when the system says stock exists, but the shelf does not. The most common causes are simple: goods received but not posted, issued items not deducted, transfers partly recorded, damaged stock left in active inventory, and manual edits made to solve a short-term shortage. One hidden error can cascade into pricing, purchasing, and customer trust problems.
- Receiving without posting: remedy by matching every truck or carton to a receipt record the same day.
- Issue without deduction: remedy by closing pick and issue tasks before shift end.
- Wrong location: remedy by enforcing a physical bin check before posting a move.
- Unrecorded scrap or repair: remedy by moving damaged stock to its own status immediately.
- Copying quantities from memory: remedy by requiring a visible count source or second-person verification.
When phantom stock is found, do not only correct the number. Trace the cause. If 15 units are missing every month from the same fast-moving item, the remedy is not a larger safety stock. It is a process fix, possibly tighter receiving, bin discipline, or better separation of damaged goods.
8. Practical rollout plan: map, pilot, reconcile, train, monitor
A controlled rollout prevents the system from becoming a pile of half-finished records. Start by mapping actual processes: who receives, who stores, who transfers, who counts, and where the exceptions happen. Then pilot one warehouse or one product family first. Do not launch every location at once unless the team already has disciplined stock habits.
- Map: document current locations, item groups, and problem points.
- Pilot: activate one warehouse or one branch with a limited set of items.
- Reconcile: compare physical stock to system stock before expansion.
- Train: teach the exact sequence for receiving, moving, and counting.
- Monitor: review errors daily for the first weeks and weekly after stabilization.
Do not mistake software launch for operational adoption. Real adoption is visible when staff stop keeping parallel notebooks for the same stock and when managers trust the exception log enough to act on it.
9. Limitations and honest distinction: best practice versus verified Rigi24 features
It is important to separate what the business should do from what the product is verified to do. Rigi24’s Inventory module includes warehouses, internal storage locations, items, movements, stock counts, and damaged, repair, and scrap classifications. That is enough to build a serious stock-control process. However, unless you verify a feature in your own environment, do not assume automatic reservation logic, universal permission depth, offline synchronization, scanning hardware support, or built-in analytics.
Best practice may require configuration, procedure, or external discipline even when the software supports the record structure. For example, separation of duties can be enforced by company policy even if the platform provides only basic access settings. Similarly, a synchronization review routine can be a manual managerial check even if the system does not automatically flag every mismatch.
10. Decision checklist, common questions, and actionable conclusion
Before rollout or process redesign, ask five questions: Do we know which items are critical? Do we have one owner for exceptions? Are damaged and repair stock clearly separated? Can we explain every transfer gap? Are we counting the same way in every branch? If the answer to any of these is “not yet,” fix the process before asking the system to solve it.
Common question: should every branch keep the same reorder rule? No. Use the same logic, not the same number. Common question: should stock adjustments be frequent if the business is busy? No. Frequent adjustments are usually a sign that the process is too loose. Common question: should the owner check every movement? Not necessary. The owner should check the exceptions, trends, and high-risk items, while the team executes the routine controls.
Actionable conclusion: control inventory by design, not by heroics. Define access, reconcile daily, count strategically, classify damaged stock properly, and keep a realistic replenishment model. If you use Rigi24 as the record system, make it the disciplined source of truth for defined workflows, while remembering that the quality of inventory depends far more on operating habits than on software alone.
\nRelated Rigi24 resources
GS1 warehouse management · GS1 location identification (GLN) · GS1 SSCC

Frequently asked questions
Can one business track warehouses in different cities?
Yes. Treat each location as a separate warehouse and record stock in the correct location; confirm relevant features in your Rigi24 setup.
Does the presence of stock in another branch mean it is available here?
No. Physical availability and transport time must be checked separately.
What is sellable stock?
Stock physically on hand minus damaged, reserved or otherwise unavailable units, according to the approved business rules.
Should a barcode scan automatically deduct stock?
No. Scanning should identify an item; an authorized inventory movement should determine quantity changes.
How are damaged returns handled?
Inspect the units and record them separately from sellable goods until an approved disposition is decided.
How often should stock counts be performed?
Use risk-based cycle counts for high-value items and a periodic full count when appropriate.
How do invoices affect stock?
Define precisely which sales or delivery event updates stock, and prevent duplicate posting.
Is an offline feature guaranteed?
No. Offline operations must be confirmed in the specific deployment rather than assumed.



