PRODUCT IDENTITY / UNIT QUANTITY
Knowing the SKU is only part of the record.
Check the number of identical units as a separate outcome.
An AI fridge demonstration identifies a drink correctly when one bottle is selected. The buyer then plans an offer where shoppers may take two identical bottles in the same purchase. Correct product identification in the first example does not establish the unit count in the second.
The WEIMI single-door AI fridge listing describes multiple-item purchases in one transaction and asks buyers to validate recognition using their actual products and shopping scenarios. Repeated units of one SKU are a specific scenario worth including when they reflect the intended offer.
This guide compares three real public equipment listings as a procurement shortlist. It is not an independent recognition test and contains no measured accuracy rate. The purpose is to make a quantity requirement reviewable before purchase, with the exact packs and quoted configuration.
Record product identity and physical unit quantity separately. An item record can name the correct SKU while showing the wrong number of units. Define the expected result for each agreed demonstration scenario and compare both dimensions with the offered transaction record.
Include repeated identical units where they are part of the proposed shopping pattern. Ask the supplier to use the actual approved packaging and shelf arrangement. Do not treat a demonstration with two different products as equivalent to one with two units of the same product.
Keep the evidence tied to the configuration and conditions demonstrated. No particular quantity limit, pack combination or performance threshold is verified here. Agree the relevant scope and acceptance criteria with the supplier before relying on multi-item wording in a buying decision.
| Proposed scenario | Expected identity record | Quantity question |
|---|---|---|
| One bottle of SKU A | SKU A | Does the record show one unit? |
| Two identical bottles of SKU A | SKU A | Does the record show two units? |
| Two A plus one B | SKU A and SKU B | Are A=2 and B=1 represented separately? |
| Repeated units under another approved layout | Same approved SKU identity | Does the changed scenario have its own evidence? |
| Different pack size sold separately | Correct separate product identity | Is this a new SKU scenario rather than a repeated unit? |
This review helps buyers planning purchases that may contain more than one unit of a product. An office operator may offer drinks that colleagues buy together, while a venue operator may expect several identical refreshments in a single visit. These are proposed use cases, not reported customer behaviour.
A procurement team can use the distinction to specify a demonstration rather than accepting a general claim about camera recognition. A merchandising team can identify the actual pack sizes and repeated quantities relevant to the intended range.
Buyers comparing direct selection with controlled dispensing can also use the same identity-and-count record. The physical selection mechanism differs, so the demonstration should reflect the product’s actual workflow. This guide does not presume that every shortlisted product offers the same basket controls.
We examine the public retail format and the evidence needed for the buyer’s quantity requirement. The AI fridge describes camera-based recognition and multiple-item purchases, with actual packaging, shelf arrangement and shopping scenarios requiring validation.
WM22 describes touchscreen selection and multiple purchases in one transaction. That is a different selection-and-dispense approach. Its wording does not establish the repeated-unit behaviour or quantity controls of a particular quoted configuration.
The dual-cabinet station asks buyers to demonstrate selection and delivery from each selling area. It does not establish a combined multi-item basket across both sections. We therefore compare procurement questions, not untested recognition accuracy or a claimed universal basket feature.
Actual sellable unit: identify what the operator sells as one item. A bottle, a can and a packaged multipack may be different sellable units. Do not count the contents of a sealed retail pack as independently selected items unless that is the agreed offer.
Identity versus count: preserve both in the expected result. Write “SKU A, two units” rather than “product recognised.” That wording makes a correct name with an incorrect count visible as a different outcome.
Relevant scenarios: choose repeated quantities that reflect the proposed assortment and shopping pattern. The supplier should confirm the supported scope. This article does not prescribe an invented maximum number of products per purchase.
Packaging and layout: use the actual samples and approved arrangement. Similar labels, pack shapes and loading changes belong in the discussion where relevant. A result obtained with a different pack or layout should retain those conditions in its evidence.
Record availability: ask which offered transaction view can demonstrate the selected identities and quantities. Do not assume a downloadable log, a video archive or a specific export field is included. Request the actual evidence surface proposed by the supplier.
Discrepancy review: ask how an observed difference will be documented and investigated during acceptance. Keep the expected count, reported count and scenario reference together. A corrected demonstration should be traceable to the conditions changed, without rewriting an earlier result as a success.
Read the public AI fridge listing. This model supports direct selection of compatible packaged products and describes multiple-item purchases in one transaction. It is the directly relevant shortlist entry for camera-based recognition. Request repeated-unit quantity evidence using the actual packs. The public page does not provide a tested result for two identical units or a guaranteed recognition percentage.
Read the public WM22 listing. The page describes touchscreen selection, inventory management and multiple purchases in one transaction. Ask how the actual proposed interface represents repeated quantities and how the configured mechanisms deliver them. Do not infer that all optional slot types are supplied or that its multi-purchase workflow matches direct-selection retail.
Read the public dual-cabinet listing. The main cabinet and secondary spiral-lane compartment provide two selling areas. Demonstrate the requested product selection and delivery from each relevant section. A shared front view does not prove a cross-section basket, quantity selector or simultaneous dispensing capability. Confirm those requirements individually if they matter to the proposed offer.
| Equipment | Published selection basis | Repeated-unit evidence request |
|---|---|---|
| Single-door AI fridge | Open, select, close; camera recognition | Actual identical packs and resulting identity/count record |
| WM22 | Touchscreen selection and configured dispensing | Offered repeated-quantity selection and delivery sequence |
| Dual-cabinet station | Menu addressing two selling sections | Requested selection and quantity scope per relevant section |
Fictional arithmetic only: assume a bottle costs $1.10 to purchase and is offered at $2.00. A correctly counted two-unit example would have $4.00 gross receipts and $2.20 product cost, leaving $1.80 before all other expenses. These values are invented and do not represent WEIMI prices or an actual operator’s result.
If an illustrative record showed only one unit while two were selected, the record would differ from the expected count by one. That hypothetical discrepancy does not establish actual lost revenue, payment outcome or stock loss in any deployed system. It simply shows why the quantity should be reviewed independently of the SKU name.
For demonstration planning, assume one hour of preparation and review at $36 per hour, giving a fictional $36 allowance. Actual effort depends on the assortment and agreed scope. No accuracy rate, reduction in disputes, sales uplift or payback period has been measured for this article.
| Buyer requirement | Procurement direction | Evidence boundary |
|---|---|---|
| Direct selection of repeated identical drinks | Review the AI fridge with actual samples | Correct identity and quantity under agreed conditions |
| Customer chooses a quantity on screen | Ask WM22 supplier to show offered controls | Actual selection and delivery behaviour confirmed |
| Repeated units from two selling areas | Specify the dual station requirement explicitly | No cross-section basket inferred from imagery |
| Only one item per planned purchase | Define that narrower operating scope | Do not generalise its result to repeated-unit scenarios |
For a workplace drinks offer, a buyer can propose a demonstration with one bottle, then two identical bottles, then two bottles plus a different snack. The supplier should confirm whether these scenarios fall within the offered configuration. The sequence is a suggested review plan, not a performed test.
For a leisure venue, an operator may plan packaged drinks purchased in repeated quantities. Provide the exact samples and expected sellable-unit definitions. Keep changes to pack sizes and product identities visible rather than treating visually similar products as interchangeable.
For a phased rollout, retain the scenario evidence with the approved packaging and arrangement. If later changes alter those conditions, ask what review is required before relying on the earlier result. The AI fridge listing specifically asks for recognition testing of actual products and shopping scenarios.
No. Review the identity and quantity separately. The expected record for two identical units should distinguish that scenario from a single-unit selection.
No. Two different SKUs and two units of one SKU address different quantity scenarios. Include the relevant cases in the agreed demonstration scope.
This guide does not verify a maximum. Request the supported quantities and conditions for the actual configuration and intended products.
The reviewed pages describe different retail approaches. Do not transfer camera-based recognition claims to WM22; demonstrate its offered selection-and-dispense workflow.
The public listing does not establish that. If required, ask the supplier to confirm and demonstrate the actual cross-section purchasing scope.
No. It is a public-listing procurement shortlist. Repeated-unit identity and quantity outcomes require a configuration-specific demonstration using the actual packs.
Specify the sellable unit, expected SKU identity and expected physical count before the demonstration. Include repeated identical units when they reflect the operating plan. Preserve the actual packaging, arrangement and configuration associated with each result.
Choose the retail format after the supplier confirms and demonstrates the required scope. Do not turn a successful single-item recognition example into a general repeated-unit acceptance claim. Keep untested quantities and combinations explicit in the procurement record.
Send your destination, quantity, product samples and expected shopping scenarios. Identify which products may be selected in repeated quantities and request evidence of the corresponding identity and unit-count records.
Source boundary: the three linked WEIMI product listings were reviewed for their stated retail workflows. No identical-unit test result, quantity limit, analytics export, cross-section basket or recognition accuracy rate has been independently verified.