ONE PURCHASE / DIFFERENT ITEM OUTCOMES
A basket status cannot tell the whole story.
A public-listing buying brief for partial fulfilment, customer explanation and resolution evidence.
Introduction
A customer selects two products in one vending purchase. One arrives and the other does not. A single headline status such as “successful” or “failed” cannot explain the complete outcome. The buyer needs to know how the supplied configuration distinguishes the product quantities, customer message, payment result and operator follow-up for that same purchase.
WM22 publicly describes multiple purchases in one transaction. The dual-cabinet page specifically asks buyers to define delivery-failure and refund procedures. These statements support a concrete pre-purchase demonstration request, but they do not establish automatic partial refunds, delivery sensors or any particular recovery mechanism.
This article focuses on partial fulfilment within a confirmed multi-item dispensing workflow. It is narrower than general payment reconciliation: the problem is one purchase with different physical outcomes for its items. The AI fridge is included as a distinct public shopping format, with a clear boundary: direct product removal is not the same mechanism as a failed dispense.
Quick Answer
Request one supplier-approved example in which a supported multi-item purchase has different item outcomes. Agree the expected physical result, recorded quantities, customer explanation and payment-handling path before the demonstration. Keep an unresolved outcome visible instead of forcing the whole purchase into one misleading label.
Ask whether the exact proposed configuration supports multi-item purchasing first. If it does, ask how item-level outcomes are established and who resolves missing evidence. A public multi-buy statement does not prove every exception workflow is available.
Do not induce a jam, obstruct a mechanism or experiment on a real customer. The supplier should choose a safe supported demonstration method, with any test-payment arrangements agreed by the payment provider. This guide does not perform or prescribe a physical fault test.
Comparison Table
| Evidence layer | Question for a two-item example | Unwarranted shortcut |
|---|---|---|
| Physical product outcome | Which item and quantity reached the agreed collection point? | Treating a payment result as proof both items arrived. |
| Machine record | What does the supplied system know about each outcome? | Assuming a sensor or detection method exists. |
| Customer communication | What amount and next step does the customer see? | Promising an automatic refund without a demonstration. |
| Operator resolution | Who reviews an incomplete result and closes the case? | Marking the whole purchase resolved while an item remains disputed. |
These layers are proposed evidence distinctions. They are not verified fields, statuses or capabilities in the offered software. Ask the supplier to identify its actual equivalent records and limitations.
Who Should Buy This
Use this review when buying a multi-item dispensing cabinet or a confirmed station workflow in which several products belong to one purchase. It is useful for an operator who wants a clear customer-support path before launch and a distributor who must explain exception handling to its customer.
The equipment supplier should explain physical delivery and the available machine record. The payment provider should explain the supported financial handling. The operator should assign the customer contact and resolution owner. Those roles may be separate; the cabinet brand alone does not identify who can issue a refund.
For an open-door fridge project, adapt the question to the actual recognition and collection workflow with the supplier. Do not use a dispensing failure script as though products move through a delivery mechanism in that format.
How We Evaluate Smart Vending Machines
We compare three real WEIMI public listings as a procurement shortlist. We have not tested partial delivery, inspected private software or measured refund speed. Public functions identify relevant questions; they do not establish the complete exception response.
Begin with one ordinary successful purchase in the offered configuration. Identify how products, quantities and payment references relate. Then agree a supported exception example with a written expected outcome. Record what was observed separately from what the supplier says the system inferred.
The accepted evidence should make the distinction between requested, delivered or collected, recorded and financially resolved quantities understandable. The exact terminology must come from the supplied workflow. No universal detection method or automatic resolution rule is assumed.
Key Buying Factors
1. Confirm the purchase scope
Identify whether the cabinet can sell several items in one transaction and which sections participate. The dual-station listing does not establish a shared basket. If the offered system processes separate purchases, document that scope instead of inventing a partial-basket feature.
2. Separate requested quantity from physical outcome
Retain the intended product and quantity for each item. Ask how the system determines or records delivery, and what remains uncertain when evidence is unavailable. A customer report, an observed product and a software status are different evidence sources; none should be silently substituted for another.
3. Ask how unknown outcomes are handled
A record may be incomplete rather than an explicit success or failure. Ask who investigates, which evidence is available and what the customer is told while the outcome remains unresolved. Do not infer that absence of a failure alert proves successful delivery.
4. Define the financial path explicitly
Ask whether the supplied arrangement changes the final charge, initiates a supported refund process or requires an operator review. These are possible questions, not established options. Confirm the actual provider, responsibilities, fees and completion evidence. Avoid promising immediate bank credit from an operator-side message.
5. Keep recovery separate from another purchase
If a retry or replacement is offered, ask how it relates to the original case. A new successful product collection does not by itself explain the original payment. Do not instruct customers to buy again without an agreed supported process and clear financial treatment.
6. Reconcile stock without assuming a returned unit
Ask how the supplied inventory record treats the item with an unresolved delivery outcome. A financial adjustment does not prove where the physical product is. The operator should use the approved inspection or reconciliation procedure rather than automatically adding stock because a refund occurred.
7. Preserve one case reference across the handoffs
Ask which supported reference links the purchase, item outcome and customer resolution. A common identifier or cross-reference can be useful if available, but its format is not established here. Retain only the information needed for the case and avoid unnecessary payment-card details.
Best Smart Vending Machines
WM22 Touchscreen Snack and Drink Vending Machine
Read the WM22 public listing. It describes multiple purchases in one transaction, a 21.5-inch touchscreen and optional spiral, conveyor, direct-push and hanging arrangements. This makes it a relevant starting point for a multi-item delivery-outcome demonstration.
Ask for the exact selected mechanism and actual product samples. Then request the supported item-level exception and customer response. The page does not establish a particular delivery sensor, guaranteed failure detection, automatic partial refund or recovery time. Those details need a configuration-specific response.
Two Cabinets, More Choice | Snack & Drink Vending Station
Read the dual-cabinet public listing. The station has a main product display and a secondary visible spiral-lane compartment. Its technology section asks buyers to define sold-out handling, delivery failure, refunds and behaviour during power or network interruptions.
First confirm the actual transaction scope and product-to-section mapping. If one purchase can include both sections, request that exact partial-outcome example. If it cannot, use the supported separate-purchase workflow. Do not infer a shared basket, the main internal mechanism or the secondary collection route from the front view.
Single-Door AI Vision Smart Fridge for Packaged Drinks
Read the AI fridge public listing. Customers open the door, select compatible packaged products and close for automated checkout. The page supports multi-item shopping and calls for actual packaging and scenario testing. This is a direct-selection format, not a spiral dispensing system.
Its relevant exception question is whether the final recognized product quantities and charge match the actual supported shopping scenario. Ask the supplier for a recognition-exception process rather than describing a missing dispensed item. We do not claim that recognition disputes and dispensing failures use the same software or refund path.
Feature Comparison
| Candidate | Public workflow | Evidence request before purchase |
|---|---|---|
| WM22 | Multi-item selection and configured dispensing. | Different item outcomes within one supported purchase, with financial follow-up. |
| Dual-cabinet station | Two selling sections; purchase scope requires confirmation. | Confirm shared or separate purchases before testing cross-section outcomes. |
| AI vision fridge | Direct selection with camera-based checkout. | Recognized quantity versus actual shopping outcome; avoid dispensing assumptions. |
This comparison does not rank measured reliability or customer recovery speed. Select the physical format that fits the assortment, then confirm its complete exception procedure and support scope.
Cost & ROI Analysis
Fictional illustration only. Assume one purchase requests Item A at US$2.50 and Item B at US$3.50, giving an initial example total of US$6.00. Assume the controlled example establishes that A was collected and B was not. The agreed financial treatment still has to be defined; the physical facts alone do not establish a provider’s procedure.
| Illustrative amount | Arithmetic | Meaning within the assumptions |
|---|---|---|
| Initial requested total | US$2.50 + US$3.50 | US$6.00 |
| Value assigned to collected A | 1 × US$2.50 | US$2.50 |
| Value assigned to uncollected B | 1 × US$3.50 | US$3.50 |
| Difference if final payable amount is agreed as A only | US$6.00 − US$2.50 | US$3.50 to reconcile through the supported process |
The last row is conditional arithmetic, not a refund promise or a legal determination. Discounts, tax, provider fees and other adjustments are excluded. If a promotion changes the item allocation, agree its treatment explicitly rather than borrowing the ordinary-price example.
For a separate planning allowance, assume a case needs 12 minutes of staff review at a fictional US$30 hourly rate. The example labour amount is 0.2 × US$30 = US$6. Neither the duration nor rate is measured. Do not multiply this example into projected savings without real case volumes and evidence.
A complete investment case includes actual equipment, software, payment, product and service costs. A documented exception path can improve operational clarity, but no reduction in failure rate, refund cost or payback period is established by this article.
Best Choice by Scenario
Several items from one dispensing cabinet
Start with WM22’s public multi-item statement. Ask the supplier to demonstrate the selected configuration with written expected product and financial outcomes. Keep the normal multi-item result and the supported exception result as separate evidence.
Items from two selling sections
Use the dual station only after transaction scope is confirmed. A successful item from one section cannot establish the outcome in the other. Retain product-to-section and collection references in the same case review.
A shopper directly removes products from a fridge
Use the AI fridge’s recognition and checkout context. Ask how disputed quantities are reviewed and how any payment correction is confirmed. Do not transfer a dispensing-failure claim to a door-based shopping session.
Applications
At quotation stage, describe the partial-outcome requirement and ask the supplier to identify what is supported, what requires another party and what remains outside scope. Include any service fees or software options in the offer.
At commissioning, use the agreed safe demonstration method and provider-approved payment arrangement. Record the requested items, observed outcomes, system record and customer next step. If the example cannot be safely demonstrated, retain that limit instead of reporting a passed test.
During handover, assign an owner for unresolved cases and define the evidence needed to close them. A message sent to support is not the same as a completed financial resolution. Keep the customer explanation accurate while the responsible parties review the case.
FAQ
Does multi-item purchasing prove automatic partial refunds?
No. The public multi-item statement does not establish the exception mechanism or provider refund behaviour.
Can the buyer create a jam to test this?
This guide does not authorise that. Ask the supplier for a safe supported method and agree any test-payment arrangements beforehand.
Is a successful charge proof that every product arrived?
No. Payment evidence and physical product outcome answer different questions. Connect them for the same purchase.
Should a refund automatically increase stock?
Not without the supported physical and inventory reconciliation. A financial correction does not establish where a product is.
Is the AI fridge a dispensing candidate?
No. Customers select products directly. Its relevant review concerns recognized quantities, shopping outcomes and the supported correction path.
Is US$3.50 a guaranteed refund?
No. It is conditional arithmetic in a fictional example. Actual financial treatment and completion evidence require supplier and provider confirmation.
Final Recommendation
Do not allow one purchase-level label to hide different item outcomes. Confirm the supported purchase scope, request a safe exception demonstration and connect physical evidence, the machine record, customer communication and financial resolution.
WM22 is the clearest public multi-item dispensing starting point here. The dual station needs its transaction scope confirmed; the AI fridge requires a different recognition-focused review. These are public-listing procurement candidates, not independently tested winners. Select the configuration whose complete supported process meets the project.
CTA
Request an item-level exception review
Send WEIMI your country, site, quantity, product list, package dimensions, storage needs and payment preferences. Explain whether the project needs one purchase containing several products or products from multiple sections.
Ask for the supported partial-outcome procedure, safe demonstration method, customer communication and payment-provider responsibilities. Confirm the available records, support scope and charges in the quotation.
Get My Custom QuoteSource basis: the three public WEIMI product listings linked above, reviewed 15 October 2026. No physical fault test, private software inspection, automatic refund feature, legal entitlement or measured financial return is established. All numeric examples are assumptions.
