Two opposite complaints, one underlying cause. Either a device reached a low toner level and no alert email was sent, or an alert arrived while the toner was still at 50% or higher. Both usually come down to which alert type is active and how the two interact.
Start Here: Which Alert Type Is Active
Print Tracker has two distinct supply alert mechanisms. Misunderstanding which one is active is the single most common reason an alert looks missing, and the single most common reason one looks premature.
Alert type | How it triggers | When to use it |
Low supply % | Fires when the toner level drops to or below a configured percentage | When you want predictable, threshold-based notifications, or where print volumes vary a lot |
Estimated depletion | Fires when Print Tracker calculates the supply will run out within a configured number of days, which can happen at 50% or higher on a busy device | For proactive ordering where usage is consistent |
If both are enabled, estimated depletion takes precedence. When a reliable depletion date exists and the supply crosses the percentage threshold, the percentage alert is deliberately not sent. While estimated depletion is enabled Print Tracker only sends percentage alerts when the depletion date is missing, unreliable, or outdated. This is expected behavior, not a missed alert.
That precedence rule is why the two complaints are related. Turning on estimated depletion makes percentage alerts appear to stop working, while simultaneously producing alerts at levels that look far too high.
An Alert Arrived While Toner Was Still High
The estimated depletion alert does not look at the current toner percentage at all. Print Tracker analyzes the device's recent print volume, calculates how many days of toner remain at that rate, and fires when the predicted days remaining drop below your configured threshold. The default is 7 days.
A high-volume device can therefore alert at 55%, 70%, or higher, because at its print rate the toner genuinely will run out inside the alert window.
A worked example
A device prints 500 pages per day. Its cartridge has roughly 2,000 pages of capacity left, about 55% full. Print Tracker estimates depletion in about 4 days.
If your threshold is set to 15 days, the alert actually fired several days earlier, when the countdown first crossed 15 days and the toner was at an even higher percentage. By the time someone reads the email and checks the device, the level looks implausibly high for a low toner warning.
An alert right after a cartridge replacement
After a new cartridge goes in, Print Tracker may briefly carry the previous cartridge's usage rate into its depletion calculation, firing an alert on a cartridge that was just replaced. This normally self-corrects within the next few reporting cycles as the usage baseline resets.
If alerts keep firing right after confirmed replacements, contact support with the device serial number and the timestamps of both the alerts and the replacements. The timestamps are what make this diagnosable.
Adjusting the depletion threshold
Match the threshold to your restocking lead time rather than leaving it at a default. Roughly 10 days suits next-day shipping; 20 or more suits slower restocking.
Go to Admin, then Manage entity, then the Settings tab, then Device alerts.
Find Days to depletion and reduce it.
Click Save settings.
For outlier devices, override at the device instead. A single very high-volume machine does not need to drag your fleet-wide threshold around. Open the device, use its Settings tab, and set the value there, which overrides the inherited entity value. See Settings Inheritance: How Entity and Device Settings Work.
Switching to percentage alerts instead
Go to Admin, then Manage entity, then the Settings tab, then Device alerts.
Toggle off Estimated depletion alerts. Low supply alerts then use the value in the Toner/ink threshold field.
Set the threshold percentage you want. The default is 25%, meaning an alert fires when toner drops to 25% or below.
Click Save settings.
Before setting a low percentage, read the threshold granularity warning below. A threshold set below what the device can actually report produces no alert at all.
No Alert Arrived at All
If the expectation was a percentage alert and nothing came, work through these in order. Rule out the precedence behavior above first, because an enabled estimated depletion alert is the most common explanation.
Cause 1: The device was not being monitored
Alerts can only fire on data Print Tracker actually received. Check whether the device was stale at the critical moment, because of:
The install being offline. See DCA Offline or Checking In Late.
A replacement install that has not yet discovered the device.
The device having tracking disabled. A device set to disabled will not alert regardless of toner level.
The device's IP address changing and not yet being rediscovered. Run a topology scan of the IP and confirm PING and SNMP both return. See Device IP Address Changed.
The device's SNMP settings changing.
See Device No Longer Returning Meters and Supplies for the full stale device procedure.
Cause 2: The supply is not reporting a valid level
A percentage threshold cannot be evaluated against a supply that does not report a percentage.
A faulty or missing sensor, which is more common with non-OEM supplies. Check the device's own supply details web page to see what the device itself reports.
The supply reports a state rather than a number. Some devices return status values instead of a numeric percentage, and a percentage threshold will usually not resolve against a state-based value until that value indicates empty.
If the device reports no usable supply level at all, the model may not be fully supported yet. See Device Identified as "printmib": Make and Model Not Recognized.
Cause 3: The threshold is set too low
This is a subtle one and worth reading twice. If the threshold sits below the granularity the device reports, the threshold is never observed being crossed.
Example: a supply that reports remaining level in 10% increments, with low supply alerts set at 5%, will send no alert until it reaches 0%, because it never reports a value between 10% and 0%.
The same effect appears on fast-consuming devices. If a high-volume device drops from 20% to 0% between reporting cycles, Print Tracker never sees it at or below the threshold.
Raising the threshold is usually the fix. The default toner threshold is 25%.
Cause 4: Configuration and timing
Low supply alerts were disabled on the device. Check the device or entity history.
Alerts were enabled after the supply was already low, so the crossing happened before alerting existed.
No recipient email addresses are configured on the alert. The alert can be enabled with nobody to send to.
A skip alert is active for that supply, deliberately suppressing a set number of future alerts. Easy to forget one was set months earlier. See Setting Up Device Alerts (Supply, Service, and Volume).
Cause 5: The alert fired but the email did not arrive
If the alert event exists in Web Admin but no email was received:
Check the Manage alerts screen for email delivery errors. Go to Devices, then Manage alerts. Delivery failures are recorded there, which makes this the fastest way to distinguish a sending problem from a receiving problem.
Confirm the recipient address on the alert is current and spelled correctly.
Check spam and junk folders. Alert emails come from a
@printtrackerpro.comaddress.Ask IT whether an email security gateway is filtering or quarantining mail from
printtrackerpro.com, and have them add it to the allowlist.
For the reverse case, an email that arrived with no matching event in Web Admin, see Alert Email Received But Not Visible in Web Admin.
How to Check the Alert Configuration
Go to Admin, then Manage entity, then the Settings tab, then Device alerts. For a single device, open the device under Devices, then View Devices and use its Settings tab instead.
Confirm the relevant alert is toggled on.
Check which type is active, low supply percentage or estimated depletion. Note that the estimated depletion toggle applies to all supplies beneath it.
Check the threshold value, either a percentage or a number of days.
Confirm at least one recipient email address is present and correct.
Check whether the setting is inherited or explicitly set here. See Settings Inheritance: How Entity and Device Settings Work.
How to Check What Print Tracker Actually Saw
To confirm whether the data ever supported an alert:
Go to Devices, then View devices.
Click the three-dot menu at the right of the device.
Click View meter history and look at the toner levels around the time the alert was expected. Numbers in a toner column are percentages, so 15 means 15%.
A gap in the history means the device was stale at the critical time and the alert could not fire, because there was no data to evaluate. A jump straight past the threshold means cause 3.
Contacting Support
If the configuration looks correct and alerts are consistently wrong in either direction, contact Print Tracker support with:
Device make, model, and serial number
The expected alert date and time, or the date and time of the alert that seemed premature
The toner level at that moment
The alert type and threshold configured
Whether the alert event appears in Web Admin even though no email arrived
Related Articles
Setting Up Device Alerts (Supply, Service, and Volume)
Alert Email Received But Not Visible in Web Admin
Waste Toner and Maintenance Supply Alerts Not Triggering
Toner Level Spike Causing Incorrect Toner Replacement Record