How to Set Up Multi-Location DME Inventory Management

Growth scatters your inventory. One warehouse becomes two, then a branch opens across town, then delivery trucks become rolling storerooms, and units are scattered across hundreds of patient homes. Each of those is a place a serial number can live, and each is a place it can get lost.

The failure mode is predictable. Every site keeps its own spreadsheet, nobody trusts the other site's numbers, and a unit that sits idle in Branch B is invisible to the dispatcher at Branch A who just turned away a rental. Multi-location inventory management is about making every unit visible from one place no matter where it physically sits.

The locations a DME unit moves through

Before you can track units across sites, you need to name the kinds of places they live:

• Warehouses. Your main stock and reprocessing operations.
• Branches. Smaller satellite sites with their own working inventory.
• Trucks. Mobile inventory in transit, often holding units for the day's deliveries and picking up returns.
• Patient homes. Every unit currently out on rental is a location too, even if it is one bed in one house.

A unit is always in exactly one of these at any moment. The job of your system is to know which one, and to record every move between them.

Why per-site spreadsheets fail

Separate spreadsheets feel organized until a unit crosses a boundary. The moment a concentrator moves from the main warehouse to a branch, two files have to be edited by two people who may never talk. One of them forgets. Now the warehouse thinks it still has the unit and the branch does not know it arrived.

Multiply that across trucks and daily transfers and you get drift. Within a month your spreadsheets disagree, nobody knows the true count, and you are back to re-buying equipment you already own. Spreadsheets also cannot tell you a unit's live status, only where someone last wrote it down.

A single cloud source of truth

The fix is one shared record that every site reads from and writes to in real time. With cloud inventory management, a scan at the branch updates the same record the warehouse manager is looking at. There is no reconciliation between files because there is only one file.

This matters most for serialized asset tracking. Each unit has a unique serial, and the cloud record holds its current location, status, and full move history. A dispatcher anywhere can ask "do we have a wheelchair available, and where is it" and get one true answer covering every site at once.

The payoff is fleet-wide visibility. Idle stock at one branch becomes usable to fill demand at another, instead of triggering an unnecessary purchase.

Handling transfers between locations

Transfers are where multi-location setups live or die. A clean transfer has two halves: the unit leaves one location and arrives at another, and both halves are logged.

1. Check out from the source. Scan the unit out of the warehouse, marking it in transit.
2. Assign it to a destination. Note which branch or truck it is headed to.
3. Check in at the destination. Scan it on arrival so the receiving site confirms it landed.

The in transit status in the middle is what keeps a unit from looking lost while it is on the road. If a transfer never gets checked in at the destination, that is a flag worth chasing the same day, because a unit stuck in transit for a week is a unit nobody is watching.

Dispatch and delivery considerations

Dispatch is the daily heartbeat of a multi-location operation. Each morning, trucks load units for deliveries and head out to drop equipment and collect returns. Every one of those movements is a location change.

Give your drivers the same scanning ability as the warehouse. When a driver delivers a bed to a patient home, a scan checks it out to that patient. When they pick up a return, a scan brings it back into the system as in transit, then awaiting reprocessing once it reaches the warehouse. Without that, the truck becomes a black hole where units disappear for hours.

Getting this running does not require a long rollout. The same fast deployment described in the live this afternoon playbook applies whether you have one site or six.

Tying it back to stock health

Multi-location visibility makes your other inventory practices work. You cannot set a meaningful par level per site if you do not know what each site actually holds, and you cannot rebalance idle stock you cannot see. We cover the math in setting par levels and reorder points, and the foundations in what is DME inventory management.

How TrackDME handles it

TrackDME keeps one live record for every serialized unit across every warehouse, branch, truck, and patient home. Transfers are a scan out and a scan in, with an in transit status covering the gap. Your team scans from a phone in the field exactly as they do at the dock, so the source of truth stays current no matter how many locations you run. One dashboard, every unit, wherever it sits.