WEIMI INSIGHTS / ACCEPTANCE TESTING
Use a repeatable purchase script to check quantities, returned products and final charges before a smart cooler goes live.
QUANTITY
Take more than one of the same product.
RETURN
Put an item back before finishing.
RECONCILE
Compare the physical basket with the final record.
An acceptance test should describe exactly what the customer did and compare that physical result with the final item list and amount.
01 / BUYER NOTES
Start with products the machine will actually sell, including similar-looking variants and different package sizes. Record each product identifier, price and shelf position. A demonstration using an easier substitute range may not reveal the issues that matter at your site.
Agree the test plan with the supplier before running transactions. Use the authorised test or payment procedure and document how charges will be handled. Keep the number of tests and expected outcomes clear so the exercise produces usable evidence rather than a collection of informal impressions.
02 / BUYER NOTES
Begin with a simple single-item purchase, then take two identical items and a mixed basket. Add a sequence in which one item is picked up and returned before the door is closed. Record the order of actions and which products finally leave the cabinet.
Include realistic handling, but follow the supplier’s operating instructions. Ask how the system treats an item returned to a different shelf, a partially obscured label or two products lifted together. The purpose is to discover the supported operating conditions and limitations, not to assume every possible action is handled identically.
03 / BUYER NOTES
Some systems may need time after the door closes to finalise a transaction. Confirm the expected workflow and how the customer knows the purchase is complete. Compare the final item list and amount with the products removed, including quantities and any applicable pricing rules.
Keep temporary payment authorisations separate from the final sale. If a discrepancy appears, preserve the transaction reference and the written action sequence for review. Ask the supplier to explain whether the cause was product setup, placement, handling, software or another part of the configuration.
04 / BUYER NOTES
A corrected product map or layout is not the end of the test. Repeat the relevant sequence and a small set of ordinary purchases to check that the change resolved the issue without introducing another one. Record the configuration used for acceptance.
Use the same approach when adding difficult new products or materially changing the shelf layout. Staff need to know when routine replenishment becomes a configuration change that requires review. A short repeatable script is more useful than relying on someone’s memory of a successful launch demonstration.
Action: Remove two units of the same approved product.
Expected record: The correct product, quantity and final amount.
Action: Remove different approved products in one session.
Expected record: Each selected item appears once at the correct price.
Action: Pick up two products, return one, then finish.
Expected record: Only the product actually taken is included.
PRACTICAL ANSWERS
The final sale should match the products purchased under the system’s supported workflow. If it does not, record the transaction and have the discrepancy reviewed.
Only if the supplier says they are representative for that purpose. Weight, shape and handling can differ from stocked products and affect the usefulness of the test.
No. It confirms that particular sequence under the recorded conditions. Use a representative set of tests and monitor real operation after launch.
YOUR NEXT STEP
Share the intended range and a few realistic multi-item purchase sequences. Agree the acceptance record and exception workflow before approving the final smart-fridge configuration.
Explore equipment →Discuss your requirements →