WEIMI / OPERATIONS FIELD GUIDE
New pack.
Clear identity.
Readable history.
A buyer's cutover workbook for a product replacement that reaches the cabinet, stock ledger and reporting team.
Introduction
A supplier replaces a bottle with a slimmer pack. The product name stays almost the same, but the label, dimensions and carton quantity change. Someone edits the dashboard and refills the machine. A week later the stock report looks wrong, and the finance team cannot tell which version sold at which price.
The purchasing question is specific: can your proposed system support a controlled product replacement while keeping earlier transactions understandable? This is different from choosing an assortment or finding out who clicked an edit button. It requires a bridge between physical packs, product records and the date each machine adopted the change.
This guide proposes a practical cutover, not a claim that a particular platform automatically versions every field. Get the exact behaviour demonstrated before turning it into an operating procedure.
Quick Answer
Comparison Table
| Equipment route | What a pack change affects | Evidence to request |
|---|---|---|
| AI vision smart fridge | Product recognition and shelf arrangement | Approved new-pack onboarding and observed old/new identification |
| Touchscreen dispensing machine | Channel mapping, pack delivery and screen content | Exact slot setup, retrieval test and product-record mapping |
| Employee-system PPE machine | Issue identity, staff permissions and reporting | Correct item unit, approved access rules and report interpretation |
The rows describe buying checks, not guaranteed migration functions. A successful pack delivery alone does not establish that old reports remain accurate.
Who Should Buy This
This review is useful for route operators who replace products frequently, retailers introducing new pack sizes, and industrial buyers changing an issued supply. It also belongs in the brief for a fleet where different sites receive replacement stock on different days.
A buyer with only a small fixed range may handle the cutover with a simple signed worksheet. A larger operator may require supported data interfaces and a repeatable approval process. Choose the operating burden you can sustain; an elaborate platform is not useful if nobody owns product identity.
How We Evaluate Smart Vending Machines
This is a desk-based shortlist, using linked supplier descriptions and an InHand Networks manual reviewed on 8 October 2026. It is not an independent machine test or an industry ranking. InHand's manual documents product-list export and separates cloud configuration from machine synchronization. It illustrates why a visible export or dashboard edit should not be mistaken for a complete product migration. It does not establish that WEIMI uses InHand software.
Our proposed acceptance exercise starts with fictional, non-sensitive test items. Record an old-version purchase, introduce a replacement pack under an agreed identifier rule, and inspect both transactions afterward. Check the displayed price, physical item, stock movement and report interpretation. Ask the supplier to demonstrate the disputed behaviour rather than promising a universal compatibility result.
Key Buying Factors
Separate four identities before editing anything
A supplier item reference, a barcode, the platform product identifier and a machine channel are different concepts. Ask which fields are keys and which are editable descriptions. A channel can be reassigned to another item; that does not make the old and new product the same. Preserve the relationship between these fields in your approved mapping.
Decide what counts as a replacement
A new wrapper with unchanged contents differs from a different serving size or a different glove count. Define the selling or issuing unit explicitly: one bottle, one packet, one pair, or another approved unit. Do not compare unit sales across different sizes without identifying the difference. Your product supplier and local team should review any changed storage or use instructions separately.
Use a cutover record that someone can actually complete
Proposed worksheet fields
- Old item identifier, approved name and unit.
- New item identifier, approved name and unit.
- Old stock removed, transferred or retained, with a reason.
- Machine identifier, channel or shelf, operator and local time zone.
- Requested configuration time and observed machine confirmation.
- New-pack test result, first transaction reference and unresolved exceptions.
Retain versioned copies according to your organization's record policy. Include a short explanation of whether historical reports use transaction-time names and prices or current product descriptions. If a name changes when an old report is reopened, the retained mapping becomes essential for interpretation.
Handle a mixed-stock period deliberately
Do not place both versions together just because they share a familiar brand name. The proposed configuration must support the arrangement, and users must receive the product described at the point of selection. If the old and new packs cannot coexist reliably, withdraw the old version before loading the replacement. Record withdrawals as withdrawals, not unexplained negative sales.
Best Smart Vending Machines: Three Products to Review
The best format depends on the product and how the change will be controlled. These three WEIMI listings provide different starting points; none is rated for historical-data preservation without a demonstration.
WEIMI Single-Door AI Vision Smart Fridge
The listing describes direct selection of compatible packaged products, camera-based checkout and cloud management. This can suit a browsable range where shoppers select several items. For a pack replacement, submit both finished versions and ask how the approved product catalogue is updated.
Test the intended shelf arrangement and a take-and-return action using the supplier's process. Keep the recognition review separate from financial history: identifying the new pack does not prove that earlier baskets retain their original interpretation.
Review the AI fridge listingWEIMI WM22 Touchscreen Snacks & Drinks Machine
The WM22 listing describes cooling, a touchscreen and configurable dispensing arrangements. It is a candidate for a defined packaged assortment. A slimmer bottle or softer wrapper needs a fresh delivery test in the exact proposed slot configuration.
Ask how a changed channel assignment appears in previous sales. Check screen image, unit and price against the physical replacement pack. Do not infer that adjustable slots accept every package or that every listed option is included in the quote.
Review the WM22 listingWEIMI WM22-W PPE Employee-System Machine
The employee-system listing describes staff-card access, permissions, issue limits and remotely downloadable reports. A supply replacement must preserve the intended issuing unit and approved access policy as well as product identity.
Replacing a packet of gloves with a different count can change the meaning of an issue limit. Test the authorized and denied cases after the change, and ask whether earlier issue records remain understandable. Integration and historical versioning require specific confirmation. The machine does not certify PPE suitability.
Review the employee-system listingFeature Comparison
| Review point | AI fridge | WM22 retail | PPE employee system |
|---|---|---|---|
| Physical change | Recognition and shelf arrangement | Slot fit and delivery | Approved pack and issue unit |
| Digital change | Product catalogue; confirm exact process | Product-to-channel mapping; confirm scope | Item mapping and permissions; confirm scope |
| History question | How are earlier basket lines represented? | Does a channel reassignment alter old descriptions? | How is an earlier employee issue interpreted? |
| Export boundary | Fields and retention not established here | Fields and retention not established here | Report download is described; schema and retention still need confirmation |
A report button is a starting point for inspection. Open a sample with your finance or supplies team and verify that they can reconstruct the old unit and distinguish it from the replacement. Avoid requiring unnecessary personal information in test files.
Cost & ROI Analysis
A SKU-change review has its own costs: sample packs, test time, catalogue work, stock withdrawal, operator training and reconciliation. Include these alongside hardware, software, payment and service quotations. Do not attribute all time saved to the machine if some of it comes from a better operating procedure.
Suppose one controlled cutover takes three staff-hours at $24 per hour, sample packs cost $18, and an approved stock withdrawal costs $30. The direct example cost is 3 × $24 + $18 + $30 = $120. These are invented planning inputs, not WEIMI prices or observed customer results.
Suppose a repeatable process later saves two administration hours per month at the same assumed rate. The illustrative labour value is $48 per month. A simple comparison of $120 ÷ $48 gives 2.5 months, only if those hours are actually saved and valued that way. It excludes other project costs and does not establish equipment payback.
Record the old reconciliation workload before the change, then measure ordinary work afterward. If the new procedure requires ongoing manual joins, include that work rather than describing an export as automation. When no saving is demonstrated, justify the process through traceability and operating control instead of promising ROI.
Best Choice by Scenario
- A bottle receives a new label: an AI fridge is a shortlist candidate if the new appearance can be onboarded and tested under the proposed catalogue process.
- A snack changes size: a WM22 route may suit a controlled channel replacement after physical delivery and mapping checks.
- A glove packet changes quantity: the PPE employee-system route needs an explicit issue-unit and permissions review before the replacement becomes available.
Choose a format only after product compatibility is established. If historical reporting is a decisive requirement, ask for that evidence on each shortlist candidate. It should not be assumed because one product page describes a cloud dashboard.
Applications
Use this workflow for a routine supplier pack change, a discontinued product replacement, or a fleet rollout where new stock arrives in stages. Give each machine its own observed cutover time. An organization-wide approval date is not proof that every cabinet has adopted the new product.
Export or retain the available approved records, count remaining stock and confirm the replacement identity.
Account for old stock, apply the supported configuration and inspect the new pack and customer-facing information.
Review the first ordinary records, reconcile the remaining stock and preserve the mapping for future reports.
For a wider fleet, track exceptions rather than forcing one change date onto machines that are offline or awaiting stock. An uncompleted cabinet should remain visible in the rollout register.
FAQ
Should every new wrapper receive a new SKU?
Not automatically. Ask how your platform handles identity and history, then use an agreed product-master policy. A materially different selling or issuing unit deserves explicit treatment. Do not invent an identifier rule without knowing the software consequences.
Can we reuse an old product identifier?
Only after confirming the effect on earlier records and retained mappings. Reusing an identifier for a different item can make old reports ambiguous. Prefer a documented rule over convenience.
Does a successful export prove we can restore the configuration?
No. An exported catalogue may have a specific format and destination. Restoration requires a supported import process and an appropriate test. The cited InHand XML example is specific to that documented system.
Can old and new packs share a shelf or channel?
Only within an approved and tested arrangement that presents the correct product and price. Where that cannot be established, handle the old stock separately and record the transition.
What if the cloud report displays only the current product name?
Retain the approved identifier mapping and transaction-time evidence the platform actually provides. Ask the supplier about supported historical views. Do not claim that a manually retained worksheet changes the platform's own behaviour.
Final Recommendation
Make one replacement demonstrable before scaling the procedure across a fleet. The acceptance result should connect the old transaction, replacement pack, physical stock movement, confirmed machine configuration and new transaction. Record any missing historical field as a limit.
Select the equipment for the product journey, then evaluate the data process separately. For broader control of who changed settings, read our guide to vending software change records. This cutover worksheet addresses how the old and new product remain interpretable after the change.
CTA: Bring Both Packs to the Buying Review
Send WEIMI the old and new finished-pack dimensions, intended unit, destination country, assortment and proposed machine quantity. Explain whether you need retail sales history or employee issue records. Request a configuration-specific sample test and a demonstration of the available product mapping and reports.
Discuss a controlled product-change planSources and Scope
The linked WEIMI listings support the equipment descriptions; they do not establish universal data versioning, migration or restoration capabilities. The InHand Networks InVending Cloud manual, issue V1.1-2023, provides a separate industry example of XML product export and configuration synchronization. Reviewed on 8 October 2026. It is not evidence of an integration with WEIMI.
The cutover worksheet and acceptance exercise are proposed buyer procedures. The financial example is hypothetical.
