INVENTORY THRESHOLD DEFINITION
A percentage needs a reference quantity.
Identify the stock being counted before approving the alert.
Introduction
A public smart fridge listing says that an email can be sent when stock falls below a preset value, giving 50% as an example. That sounds straightforward until a buying team tries to use the percentage to plan replenishment. The missing question is simple: fifty percent of which quantity, and across which products?
The WEIMI single-door AI fridge page supports the existence of a stock-email feature and a preset-value example. It does not define the denominator, establish 50% as the default or prove that the trigger is available separately for each product. These details belong in a configuration discussion and an acceptance example.
This guide focuses on the meaning of a percentage threshold. It uses three real public WEIMI products as a procurement shortlist, not an independent software test. No alert latency, delivery reliability, automatic ordering or stockout-prevention result is verified here.
Quick Answer
Ask the supplier to write the percentage as a fraction. Identify the quantity in the numerator, the reference quantity in the denominator and the products or compartments included. Then ask how those quantities are entered, updated and displayed in the offered configuration.
The reference might be described in several ways during a buying conversation, such as a configured quantity or an agreed loading baseline. Those are possible definitions to clarify, not verified descriptions of WEIMI software. Do not choose one on the supplier’s behalf.
Use a small worked example with known quantities and a documented threshold condition. Clarify whether the condition is strictly “below” the value, how displayed percentages are rounded and which event is expected to generate the email. Request evidence for the actual configuration rather than assuming the wording answers these questions.
Comparison Table
| Question |
Why it matters |
Evidence to request |
| What is being counted? |
Units and product scope define the numerator |
Written inventory definition |
| What is the reference quantity? |
The same remaining units can yield different percentages |
Documented denominator and update method |
| Where does the rule apply? |
Whole cabinet and individual products are different scopes |
Configuration showing supported scope |
| What does below mean? |
Equality and rounding can affect interpretation |
Worked boundary example |
| What happens after a refill? |
The reference may need review |
Documented refill and configuration procedure |
This table lists unresolved procurement questions. It does not assert that every setting exists. The supplier may offer a simpler rule than the buyer expects; the brief should record that limit so operators understand what the email actually represents.
Who Should Buy This
This review suits a buyer comparing inventory-management offers, an operator designing refill planning and a team accepting a new AI fridge configuration. It is especially useful when the offer contains a percentage but no explanation of its reference quantity.
A procurement team can use it to align the software discussion with the intended assortment. An alert for an overall cabinet total would answer a different question from an alert for an individual drink. Neither should be assumed until the supplier confirms the offered scope.
An experienced operator may already use a stock rule internally. Explain that rule to the supplier, but distinguish the desired process from the software’s confirmed capabilities. A familiar operating practice does not prove that a new machine reports inventory in the same way.
How We Evaluate Smart Vending Machines
We assess how the public format relates to the inventory question. The AI fridge listing describes camera recognition for compatible packaged products and a stock-email feature. WM22 describes an inventory-management function in a dispensing format. The dual-cabinet station has two distinct selling areas whose reporting scope requires confirmation.
We do not assign a best-alert ranking. The pages do not provide comparable evidence for trigger definitions, per-product scope or message timing. The shortlist is intended to identify which configuration questions must be answered before a buyer relies on the feature.
A useful acceptance demonstration ties visible quantities to the written rule. Ask the supplier to show the relevant inventory value, configuration and expected notification using an agreed example. We have not performed this test, and the example below is arithmetic rather than evidence of system behaviour.
Key Buying Factors
Unit definition: establish whether the value concerns saleable units, another supported measure or an aggregate. Do not infer a count from basket capacity, lane count or a photograph. The offered software definition must be documented.
Reference quantity: identify how the denominator is established and who may change it. A physical cabinet’s maximum capacity is not automatically the software’s reference. Packaging and assortment changes can also make an old planning assumption unsuitable.
Scope mapping: ask whether the rule is supported at cabinet, compartment, lane or product level. These are questions, not claimed options. Record the actual available scope and avoid describing an aggregate notification as though it identifies every low product.
Boundary behaviour: ask for an example at the threshold and just below it. Clarify the relationship between the displayed percentage and the trigger condition. A rounded display can otherwise create a misleading impression of exactly when the rule should apply.
Refill procedure: ask which documented steps update stock after replenishment. If a loading baseline or assortment changes, ask whether the reference quantity needs a separate change. Do not assume that adding products automatically resets a threshold definition.
Configuration record: retain the agreed definition, responsible person and demonstration evidence. If required functionality is not offered, state that limitation in the buying file. A claim that emails exist does not resolve every detail of inventory reporting.
Best Smart Vending Machines
Single-Door AI Vision Smart Fridge for Packaged Drinks
The single-door AI fridge public listing describes compatible packaged drinks and snacks, camera recognition and email notification when stock falls below a preset value, with 50% given as an example. This is the direct shortlist candidate for a discussion of that wording. It does not establish 50% as a recommended refill rule.
Request the denominator, product scope and refill-update process for the quoted configuration. Confirm packaging compatibility and the actual shopping workflow separately. Camera recognition is not independent proof that every inventory or notification requirement has been satisfied.
Review the public product listing
WM22 Snacks and Drinks Vending Machine
WM22 is a snacks-and-drinks dispensing format with a 21.5-inch product-selection touchscreen. Its public page describes an inventory-management function. That makes it a candidate for an inventory discussion, but the AI fridge’s percentage-email wording is not assumed to apply to this machine.
Ask for the proposed configuration’s stock definition, notification capabilities and demonstration. Public language suggesting that inventory reminders prevent shortages is not adopted as a guarantee. Final capacity, cooling and energy details require their own review.
Review the public product listing
Two Cabinets, More Choice: Snack & Drink Vending Station
The dual-cabinet station combines a main cabinet and a secondary visible spiral-lane selling compartment, with a portrait menu interface. The two selling areas make reporting scope a useful procurement question. No combined or separate percentage-alert behaviour is established here.
Request a labelled inventory-reporting example for both selling areas. Ask whether the proposed system distinguishes the compartments and what any alert refers to. Confirm product limits and final configuration rather than inferring them from the smaller window.
Review the public product listing
Feature Comparison
| Listed format |
Publicly described inventory context |
Unresolved threshold question |
| AI vision fridge |
Stock email below a preset value; 50% example |
What quantity and scope define the percentage? |
| WM22 |
Inventory-management function |
Which rule and notification are actually offered? |
| Dual-cabinet station |
Main and secondary selling areas |
How are the two areas represented in reporting? |
The table compares evidence boundaries rather than tested software performance. It does not establish a shared dashboard, common alert engine or identical reporting fields. Obtain a final proposal for each machine and compare the confirmed definitions.
If a supplier provides a screenshot, ask how the fields relate to the agreed quantities. A percentage shown on a dashboard is useful only when the team understands the values behind it. Keep the field explanation with the configuration record.
Cost & ROI Analysis
Fictional arithmetic example, not actual software behaviour: assume a hypothetical rule uses a reference quantity of 40 units. Eighteen remaining units would be 18 divided by 40, or 45%. If the reference were instead 60 units, the same eighteen units would be 30%. The denominator changes the interpretation even though the remaining count is identical.
Under a purely hypothetical strict “below 50%” rule using 40 units, twenty remaining units equal 50%, while nineteen equal 47.5%. This explains why a buyer should ask about equality and rounding. It does not verify the WEIMI system’s trigger logic or establish the correct setting for a site.
For a separate fictional review-cost example, assume a team spends one hour preparing and reviewing a configuration example at an internal rate of $32 per hour. That would be $32 of assumed staff effort. This is not a supplier fee or required test duration.
No notification price, refill saving or ROI has been established. Request any software and service fees and use actual operating evidence before assigning financial value. A stock email by itself does not prove fewer journeys, higher sales or elimination of stockouts.
Best Choice by Scenario
| Buying situation |
Useful supplier request |
Avoid assuming |
| Percentage shown without a definition |
Written numerator and denominator |
Physical capacity is the reference |
| Assortment varies between machines |
Configuration example for each assortment |
One reference applies everywhere |
| One product can run low early |
Confirm supported alert scope |
Cabinet-level percentage identifies that product |
| Two selling compartments |
Map reporting to each compartment |
Separate or combined alerts are included |
The best choice is a configuration whose confirmed reporting definition supports the buyer’s actual decision. If the available alert has a broader scope than the intended refill process, record that gap and plan the necessary additional review. Do not rename the feature to make it appear more specific than it is.
Applications
During an initial pilot, prepare an example with known quantities and agree what the configuration should show. Keep this as a defined acceptance exercise rather than an open-ended request to “test inventory.” A precise question helps identify whether the supplier’s explanation matches the buyer’s expectations.
When changing the assortment, review whether the old stock reference still describes the intended loading plan. Different packaging or product allocation can change how an operator interprets an aggregate percentage. Obtain the documented update method for the actual configuration.
For a multi-site rollout, maintain a short definition record alongside each approved setup. Teams should know which products or compartments the rule covers and how the reference was established. This avoids comparing percentages that represent different underlying quantities.
FAQ
Is 50% the default or recommended threshold?
The public page gives it as an example. No default or recommended site setting is established here.
Does the email identify an individual low product?
Per-product scope is not verified. Ask the supplier which scope the offered configuration supports.
Is the denominator the cabinet’s maximum capacity?
That is not established. Request the actual reference definition and configuration method.
Will exactly 50% generate the email?
Ask for the boundary logic and displayed rounding. The listing wording alone does not verify the implementation.
Does replenishment automatically reset the reference?
The refill and configuration procedures must be confirmed. Do not assume an automatic reset.
Does the feature guarantee no stockouts?
No. This guide does not adopt a stockout-prevention guarantee or measured operational benefit.
Final Recommendation
Before accepting a percentage stock alert, identify the quantity being counted, the reference quantity and the scope of the rule. Use a worked example to separate a clear definition from an attractive but ambiguous feature description. Retain the result with the final configuration.
The AI fridge is the direct listed candidate for the preset-value email discussion. WM22 and the dual-cabinet station offer other vending formats whose inventory scope needs its own confirmation. They are procurement candidates, not independently tested alert-system winners.
Sources: the three linked WEIMI public product listings, reviewed on 13 October 2026. Notification timing, rounding, repeat behaviour, per-product settings and offline operation remain unverified. The financial and percentage examples are explicitly fictional.
CTA
Send WEIMI your planned assortment, loading quantities and the refill decision you want the stock report to support. Ask for the offered threshold definition, supported scope and a worked configuration example. Request any relevant software or service fees in the quotation.
Get My Custom Quote
