WEIMI / FLEET EVIDENCE
Map the population before choosing the sample.
Build a configuration map before agreeing which installed terminals can represent a larger deployment.
01 / PROCUREMENT NOTES
Introduction
A distributor demonstrates one cabinet at headquarters. Its reader approves a payment and the operator dashboard shows the purchase. The proposed rollout includes another country, a different acquiring arrangement and a second payment application. The demonstration is useful evidence for that demonstrated setup. It does not describe every terminal in the planned fleet.
Buyers of multiple smart vending machines need a configuration map before they can have a meaningful conversation about representative assessment samples. A machine count answers how many cabinets are being purchased. It does not answer how many terminal types, application combinations or service arrangements must be understood. Even identical cabinet exteriors can contain payment configurations that deserve separate attention.
This guide uses PCI Security Standards Council FAQ 1301, dated August 2023 and read on 9 October 2026. The FAQ says terminals in the cardholder data environment are included in assessment; for large terminal populations, an assessor may select representative samples that include terminal types, locations, acquirers and payment applications. It does not prescribe the sample size for your project. The procurement map and budgeting examples here are recommendations to make that discussion concrete, not an assessment methodology or compliance conclusion.
02 / PROCUREMENT NOTES
Quick Answer
Ask for a fleet configuration register, not a single “payment tested” statement. Identify each installed payment arrangement and map which devices belong to it. Have the appropriate assessor determine whether sampling is suitable and what evidence or access is needed. Keep operational purchase testing separate from the technical security assessment.
The buyer should be able to answer four questions without guessing: Which terminal types are installed? Where are they deployed? Which acquirers serve them? Which payment applications are actually present? Add service ownership and evidence references so the answers can be maintained as the rollout changes.
A representative sample is not a buyer-selected shortcut that makes unreviewed differences disappear. A demonstration of the AI fridge cannot automatically stand for a selection-and-dispense machine, and a payment application in one region cannot automatically stand for another application carrying a similar commercial name. Give the assessor the population information before agreeing the assessment work.
03 / PROCUREMENT NOTES
Comparison Table
This comparison concerns the quality of fleet evidence rather than a ranking of security products.
| Procurement approach | What it establishes | What remains unresolved |
|---|---|---|
| One showroom payment | Observed purchase behavior on the demonstrated setup | Other installed terminals, applications and acquiring arrangements |
| Cabinet model list | Retail equipment quantities and formats | Actual payment configurations inside those cabinets |
| Reader model list | Named hardware types, if accurate | Installed applications, locations, acquirers and interfaces |
| Configuration register | Documented population and differences, with evidence references | Whether evidence is sufficient and sampling is appropriate |
| Assessor-agreed assessment plan | Professional decision on scope, evidence and any representative samples | Completion, findings and resolution of identified gaps |
Do not purchase the final row as a checkbox in the cabinet quotation. Agree the responsible professional, information access and deliverables with the relevant parties. The equipment supplier may provide installation facts without being the entity that determines the merchant’s assessment obligations.
04 / PROCUREMENT NOTES
Who Should Buy This
This buying approach suits distributors coordinating several payment partners, operators expanding across locations, and procurement teams ordering different retail formats under one equipment program. It is especially useful when the same cabinet name appears on several quotations but the payment hardware or installed applications may differ.
A small pilot can also benefit. Record its configuration accurately and state the limits of the demonstration before colleagues reuse its results for a larger order. If the next site introduces a new acquiring arrangement or application, treat that as information to review, rather than assuming the pilot result applies unchanged.
Organizations with one confirmed configuration should avoid inventing complexity. Their register may be simple. The decision about assessment sampling still belongs with the appropriate assessor, and the register should remain tied to actual installed devices. A spreadsheet containing unconfirmed supplier guesses is not better evidence than a short, accurate record.
This article helps buyers specify evidence for a multi-machine procurement. It does not tell merchants which self-assessment questionnaire to complete, select an assessor for them, or decide that a particular payment environment is out of scope.
05 / PROCUREMENT NOTES
How We Evaluate Smart Vending Machines
We compare public manufacturer listings for retail format and the practical information that a buyer should request. We have not independently tested these machines or inspected their payment networks. The three models below are a procurement shortlist, not security rankings.
First, separate retail format from payment configuration. Open-door camera retail, selected-item dispensing and elevator pickup have different operational acceptance journeys. Those journeys can inform a purchase demonstration, but they do not identify the installed payment application or establish protection of payment data.
Second, describe the population. Ask each supplier or payment party to identify the terminal type, deployment location, acquirer and application for its units. Record unknowns openly. Do not collapse all unknown applications into one group labelled “standard payment.”
Third, connect evidence to the right configuration. A demonstration video, provider confirmation or installed-device record needs a configuration reference and date. The buyer should know whether it describes a showroom unit, the production order or an installed machine.
Fourth, let the assessor decide the assessment approach. The PCI FAQ describes representative samples for large populations and expects technically knowledgeable assessment work. We do not provide a sample-size formula, select a sample on behalf of the assessor or recommend that a buyer capture payment traffic.
Fifth, preserve changes. At deployment and later changes, review whether the register still describes the population. That is evidence administration; it does not independently certify that every device remains compliant.
06 / PROCUREMENT NOTES
Key Buying Factors
Configuration identity
Give each documented arrangement a stable reference. Link it to the individual machines that use it. Suggested procurement fields include cabinet format, terminal make and model, installed application and version where available, location, acquiring party, managing party and date confirmed. These proposed fields are not a claim that the PCI FAQ mandates our exact template.
Evidence provenance
Distinguish quoted options from installed facts. A catalogue can name payment categories while the destination installation uses a specific reader and application. Require the responsible party to confirm that installed combination. Keep a document reference so a reviewer can find the supporting evidence without repeatedly asking sales staff.
Application diversity
The PCI FAQ explains that payment applications can vary by merchant, terminal model, acquirer and region. Ask whether a “same reader” statement hides different applications. Do not infer the application from an operating-system name or from the cabinet touchscreen.
Management and access
Determine whether a terminal management system is used and which party is responsible for it. The FAQ discusses TMS responsibility and whether it is a connected-to system for assessment scope. Buyers should provide facts and involve the relevant professional rather than deciding scope from a supplier’s marketing phrase.
Support evidence
Ask for confirmation that the actual device and installed applications are supported and that relevant vendor security updates have been applied. The FAQ identifies these as assessment considerations. A long cabinet warranty alone does not document application support or update status.
Change notification
Put responsibility for reporting a new reader type, application, location or acquiring arrangement into the project handover. Agree who updates the register and who informs the assessor when needed. Do not invent a universal review frequency; use the project’s actual requirements and professional advice.
Unresolved differences
Maintain an exception list. “Application not confirmed” should remain visible until the responsible party supplies evidence. Avoid treating a missing field as proof that two installations are equivalent.
07 / PROCUREMENT NOTES
Best Smart Vending Machines
The following are three real WEIMI models verified against public product pages. None of the pages establishes the installed reader, payment application, assessment scope or representative sample for a buyer’s fleet. Use them to choose a retail format and prepare a configuration-specific request for quotation.
WEIMI Single-Door AI Vision Smart Fridge
The listing describes direct selection of compatible packaged drinks and snacks, camera-based checkout, an electronic lock, multi-item purchasing and cloud management. It asks buyers to confirm the terminal, local service and transaction workflow. The cabinet is packaged retail equipment; it does not prepare fresh juice.
Fleet-map question: Will every destination use the same confirmed reader and payment application, or will the payment partner choose different configurations? Record the approved answers against the installed units. Do not make the camera algorithm the identifier for the payment environment.
Operational demonstration: Observe the approved access, selection and closing journey with real products. Document which configuration was demonstrated. Those purchase results complement the register; they do not replace technical payment assessment.
Review the AI fridge listingWEIMI WM22 Touchscreen Snacks & Drinks Machine
The WM22 page describes a 21.5-inch touchscreen, cooling, remote operation, multi-item purchases and optional spiral, conveyor, direct-push and hanging slot arrangements. Confirm the actual channel configuration in the quote and test the intended packs.
Fleet-map question: Does a local acquiring arrangement change the payment terminal or its installed application? A WM22 model label can remain unchanged while the payment setup differs. Require the responsible party to identify those differences, and link the answer to the relevant delivery batch.
Operational demonstration: Verify selection, payment response, delivery and agreed exceptions for the quoted setup. Keep the dispensing-path result distinct from evidence about payment data. Capacity and generic electricity figures with inconsistent public wording are excluded from this comparison.
Review the WM22 listingWEIMI 32-Inch Toy Vending Machine with Elevator Pickup
The page lists a 32-inch touchscreen, pusher slots, elevator pickup and a non-refrigerated configuration. It describes broad payment categories and says the reader company’s local service requires an account with that company. Confirm the specific payment company and installed setup for the destination.
Fleet-map question: Which units use which local reader-company arrangement? Record actual applications and managing parties instead of using “cashless” as a configuration group. A similar customer-facing payment logo does not answer that question.
Operational demonstration: Test approved boxed goods through selection and pickup. The machine provides neither refrigeration nor rights to branded merchandise. Its mechanical format does not establish equivalence with the payment setup in another retail model.
Review the toy machine listing08 / PROCUREMENT NOTES
Feature Comparison
| Candidate | Public retail feature | Fleet evidence request | Boundary |
|---|---|---|---|
| AI vision fridge | Direct access and camera checkout | Installed reader/application by destination and approved purchase journey | Recognition is not payment-security evidence |
| WM22 snacks and drinks | Touchscreen selection with quoted delivery channels | Configuration by delivery batch, acquirer and application | Cabinet name does not identify its payment setup |
| 32-inch toy machine | Pusher slots and elevator pickup | Specific local reader-company arrangement and installed application | Listed payment categories do not identify an installed provider |
Review the evidence field by field. An operator buying all three models may have one payment arrangement or several. Conversely, buying only one cabinet model can still produce several payment configurations. Neither outcome can be established from the retail-format table alone.
The practical selection criterion is whether the supplier and payment parties can deliver reliable installation facts for the chosen assortment and destinations. If they cannot identify a configuration yet, request a dated follow-up commitment before treating it as ready for rollout.
09 / PROCUREMENT NOTES
Cost & ROI Analysis
The following is a hypothetical administrative planning example in US dollars, not a WEIMI price, assessor quotation or promised saving. Assume a 60-machine purchase contains four documented payment configurations. Assume internal staff spend 45 minutes documenting each configuration at an assumed labor cost of $40 per hour, 10 minutes linking each machine to its configuration at the same rate, and eight hours coordinating evidence and resolving exceptions.
| Assumed task | Calculation | Illustrative cost |
|---|---|---|
| Document four configurations | 4 × 0.75 hours × $40 | $120 |
| Map 60 installed machines | 60 × 10/60 hours × $40 | $400 |
| Coordinate evidence and exceptions | 8 hours × $40 | $320 |
| Total internal evidence administration | 3 + 10 + 8 = 21 hours | $840 |
This arithmetic contains no assessment sample size. Four configurations do not mean four samples are sufficient. The assessor determines the assessment approach and may require additional evidence, access or work. Its fees, technical remediation, site visits, translation, downtime and payment-provider charges are excluded from the $840 example.
For a conservative administrative comparison, assume a later unstructured evidence chase would require 30 internal hours at the same $40 rate, or $1,200. The difference is $360. That is a comparison of assumed workloads, not proof that the register saves money. If actual preparation takes 35 hours, the assumed saving reverses. Track real hours before using either estimate in a business case.
Retail equipment ROI requires a separate operating model: actual product contribution, transactions, rent, replenishment, connectivity, cooling where applicable, payment charges and support. Evidence administration is one deployment cost. It does not create demand, guarantee assessment success or establish a sales uplift.
10 / PROCUREMENT NOTES
Best Choice by Scenario
One retail format across several regions
Choose the appropriate cabinet for the actual products, then ask each destination payment party to confirm its configuration. A unified cabinet order can simplify spares without making all payment applications equivalent. Build the map before colleagues reuse a demonstration from the first country.
Several cabinet formats under one payment partner
The AI fridge, WM22 and toy machine may require different operational acceptance journeys. Ask the payment partner whether their terminal and application arrangements are the same or different. Let the evidence establish the grouping rather than making a decision from cabinet appearance.
A phased pilot followed by expansion
Label the pilot evidence with its actual configuration and date. At each expansion, identify new locations, acquiring arrangements, terminal types or applications and bring relevant changes to the professional review. A pilot result should remain useful without being represented as fleet-wide assurance.
Acquired or mixed-age installations
Start with an accurate inventory and openly identify missing records. The newest unit is not automatically representative of older devices. Ask who can confirm installed applications and support status. Resolve uncertainty before agreeing that two groups are equivalent.
11 / PROCUREMENT NOTES
Applications
Office refreshments: Compare the AI fridge and WM22 using the approved assortment and access workflow. Map installed payment setups across the office locations and record which party supplies each application. Staff familiarity with a checkout screen is not evidence that the underlying configuration is unchanged.
Shopping-center dry-goods retail: The toy machine may fit tested boxed goods. Separate merchandise acceptance from the local reader-company arrangement. A procurement team should be able to locate both the product testing record and the payment configuration evidence.
Distributor documentation: Attach configuration references to delivery batches, while preserving individual machine mapping. Share appropriate non-sensitive evidence with the authorized parties; do not put credentials or payment account data into a general procurement spreadsheet.
Management reporting: Report known configurations, unresolved fields and evidence owners. Avoid publishing a percentage such as “100% secure” based on a completed register. A complete register describes information coverage; a technical assessment answers a different question.
12 / PROCUREMENT NOTES
FAQ
Can one successful payment represent the entire fleet?
No. It documents observed behavior on that setup. The PCI FAQ discusses representative assessment samples across the actual terminal population. Your assessor needs accurate information about the configurations, and a purchase demonstration is not the same as a technical assessment.
Who decides how many terminals should be assessed?
The appropriate assessor determines the assessment approach and any representative samples. This article gives no numerical sampling rule. Procurement should supply a reliable population map and agree access, evidence and responsibilities.
Are two identical cabinets necessarily one configuration?
No. The actual terminal, installed application, acquirer or region may differ. Confirm installed facts with the responsible parties. The retail model name alone does not establish payment equivalence.
Does the register prove PCI DSS compliance?
No. It helps organize evidence. The FAQ discusses technical assessment of terminals, protection of payment data, support, updates and responsibilities. Completing our proposed register is not certification or an assessment result.
Must buyers capture payment traffic for this guide?
No. The FAQ describes technical assessment activities for qualified assessors. Our procurement recommendations concern configuration facts and coordination. Do not collect cardholder data or perform technical payment testing without the appropriate authorized professional process.
What should happen when an application changes?
Have the responsible party update the configuration record, preserve the change reference and review which installed devices are affected. Ask the appropriate professional whether the assessment evidence or approach needs revision. Do not assume our article sets a universal notification deadline or review interval.
13 / PROCUREMENT NOTES
Final Recommendation
Choose a retail format that handles the approved assortment, then buy the information needed to understand its installed payment population. The AI fridge is a candidate for browsable packaged retail, the WM22 for configured dispensing, and the non-refrigerated toy machine for compatible boxed goods. None supplies a fleet assessment conclusion through its product label.
Before the order expands, request a configuration map covering terminal types, locations, acquirers and payment applications. Include evidence references, managing parties and visible exceptions. Give that information to the appropriate assessor so any representative sampling decision reflects the actual deployment.
Source and limits: PCI SSC FAQ 1301 supports the assessment-population considerations and discussion of applications, support and TMS responsibility. It is dated August 2023; the cited requirement numbering belongs to that FAQ, and this article does not restate a current PCI DSS checklist. The three linked WEIMI pages support the retail features only. All four pages were read on 9 October 2026. No WEIMI terminal configuration, security certification, assessment result, installed-device population or customer saving was verified.
14 / PROCUREMENT NOTES
CTA
Prepare a fleet brief before requesting equipment prices. Send the planned assortment, locations, cabinet quantities, proposed payment partners and known configuration differences. Ask WEIMI which retail format can support the project and which installation facts it can supply. Separately confirm payment evidence and assessment responsibilities with the authorized payment parties and assessor.
Keep unknown applications and acquiring arrangements visible in the brief. Request model-specific quotations, demonstration boundaries and a named evidence owner for each delivery batch. Share project requirements without credentials or cardholder information.
Discuss your fleet equipment requirements →