Skip to main content
Best practices

Replace your devices without losing sight of an asset

Everything your team needs to run a replacement wave, and keep every asset visible while it happens. We flag every device well before its end of life, so you have time to organise. The swap itself can only happen when the asset is in front of your team, which is what this guide is about.

Before the new devices arrive

Set your team and plan first

One owner, named

A single person accountable for the wave, plus the users who will physically swap devices and pair them in S-HUB.

A schedule sized to your volume

Three numbers: swaps per week, sites involved, and a named backup for absences. We build it with you on the alignment call.

Someone on site at delivery

Make sure a named person receives the parcel, so swapping can start as soon as assets are at the DC.

Step 1 · when you receive the announcement email

Turn the alert into a working list

Open S-HUB and go to Set up, then filter Device status → Replacement needed to show only the assets concerned. This filtered view is your starting point.

The Device UID column shows the device currently on the asset; Device status shows which ones need replacing. The filter sits top right of the table.

01Sort it so it tells you where to act

  • Sort by Location details to bring up the assets already at your DC, or at whichever site does the swapping.
  • Check Last location date to see how long each one has been sitting there.
  • Any column header can be sorted — build the view you want, then export it.

02Put the list in the hands that need it

  • Share (Actions menu) sends the list to your logistics team — simplest for a small batch, and you can share a different list per site.
  • Export gives you an .xlsx of the filtered view. Better for high volumes: the file becomes the team's day-to-day tracking tool.
Actions › Share, and the export button, top right of the table.

Step 2 · the one rule that decides everything

Swap the moment the asset is in front of you

You never know how long an asset will stay at the DC: it comes back, gets reprocessed and leaves again — sometimes within a day.

An asset flagged for replacement that is physically available gets its device changed the same day. Not batched, not scheduled.

Step 3 · in the warehouse

Never mix old and new

This is where waves go wrong: a new device put back in the return box, or an old one paired to an asset. Everything in the parcel is designed to make the two impossible to confuse.

What you get in the parcel
  • Boxes of new SMADE devices, identified by a green label outside.
  • Identification labels, orange stickers in both cases: “replace device” on kits still to swap, “old device” on devices coming back to us.
  • A return box and a prepaid FedEx label — old devices come back in this box, within two months.
The habit that saves the wave

Label the kit, not just the device. An orange “replace device” sticker on the kit tells whoever handles it next that a swap is still pending — even if they are not on your SAV team, and even three weeks later.

Keep the return box away from the new stock, so an old device can never be paired by mistake.

Step 4 · in S-HUB, right after the swap

Pair the new device

The physical swap is only half of it. Until the new device is paired in S-HUB, the asset stays invisible.

01Open the modal

In Set up, open the kebab menu (the three dots inside the asset's serial-number tag) and choose Change device.

02Select the right device — and double-check it

Search by UID. The UID is printed on the back of the device; the last five digits are enough to find it. Read it off the device in your hand, not from memory.
Type the last digits of the UID and pick the matching device. Confirm that what is on screen is what is in your hand before you validate.

03Confirm the status changed

The asset's Device status should now read All good. If it does, the swap is recorded. It is normal for the asset not to appear on the map straight away: a new device only shows a position after its first transmission.
Paired the wrong device? Tell us the same day
A mispairing means two assets are now reporting each other's location — and nobody downstream can tell. Do not try to fix it by moving devices around: write to mike@smade.io with both serial numbers and we will correct it properly. Fast, if we hear about it early.

Step 5 · staying on top of the wave

Three ways to see what is left

01The counter on your home page

In How is your fleet today?, Devices requiring maintenance is your remaining count. It refreshes every day. Click it to open the list of assets concerned.
Devices requiring maintenance — the number to drive down to zero. The figures shown here are illustrative, from a demonstration workspace.

02The map, when you need to know where

In Locate, open More filters, then Device status → Replacement needed and apply. You now see every asset awaiting a swap plotted on the map — useful to spot the ones parked far from your DC, and the ones about to come home.
Locate › More filters › Device status. Remember to click Apply, then Find assets.

03Regular situation recaps

We send regular recaps of where the wave stands — the list of kits whose device still needs replacing — so you always know what is outstanding without opening anything. Read them and reply if something looks off. That thread is the fastest way to reach us during a wave.

Questions along the way

We are one email away

Any question about the replacement process is worth a message, before it slows your team down.

SubjectContact
Replacements, mispairing, bulk actions, anything odd in S-HUBmike@smade.io
Parcel not received, shipment status, returnsfrida@smade.io
Adding users, access rights, subscriptionsYour account manager

Or simply reply to any of our emails. A question asked on day two costs everyone a lot less than the same question asked in month three.

Keep this playbook handy

Download the original guide to follow it offline or share it with your team.