Stopped Assets

Stopped assets are assets that have been marked so they can be returned from customers and scanned in branch transfers, but not scanned for delivery to a customer.

There are four Use States (statuses) that indicate an asset is “Stopped”:

Recall — Recall stops are useful in cases such as Lot/Batch recalls where assets may be spread across your organization and out to customers. Assets set to Recall can come back from customers as a return but are prevented from being used in most other actions. When a driver scans an asset in a "Recall" status, they are alerted that the asset should go straight to maintenance. An asset can be set to Recall through:

Complaint (Empty) — Complaint (Empty) stops are set when an issue is found with an empty asset and it must be sent to maintenance. An asset can be set to Complaint (empty) through:

Complaint (Full) — Complaint (Full) stops are set when an issue is found with an full asset and it must be sent to maintenance. An asset can be set to Complaint (empty) through:

Block — Block stops are used if an asset needs to be stopped for a reason other than a recall or complaint. An asset can be tagged as blocked through:

Stopped assets can be returned to circulation with Clear Complaint/Clear Block in the Maintenance action in TrackAbout Mobile 6 and TrackAbout Mobile 7.

Loading Blocked Assets through Integration

This feature is available to clients using basic delivery and not Delivery with Integrated Order Sync. To use this feature, expose an API endpoint to manage this data. (You need to be signed in to TrackAbout to access API endpoint information) Once TrackAbout has the blocked assets list, operators will not be able to add those assets to the delivery record. The operator will get a pop up message advising that the assets are blocked.