WEIMI INSIGHTS / CORPORATE CAMPAIGN OPERATIONS
Define eligibility, redemption status and failed delivery before treating a code scanner as the complete solution.
QUALIFY
The campaign decides who earns a gift.
REDEEM
The system applies the agreed claim rule.
DELIVER
The machine completes the physical handover.
A scanner can read a code, but eligibility, one-time redemption and delivery recovery require a defined integration. Confirm each part rather than assuming a QR reader provides the complete workflow.
01 / BUYER NOTES
A campaign may ask visitors to complete a quiz, registration or other online activity before collecting a souvenir. The campaign system needs to determine completion and issue the appropriate entitlement. The vending machine then has a different job: verify the presented claim and deliver the authorised item.
Draw the boundary between those systems. State which party owns eligibility rules, code generation and the physical equipment. This avoids a common gap where the campaign team expects the machine to understand its website while the equipment supplier expects a ready-to-use redemption interface.
02 / BUYER NOTES
A code might refer to a claim record, a particular gift or another identifier in the agreed design. Specify the meaning and the information required for validation. Do not place unnecessary personal information in a public-facing code when a narrower identifier can meet the business need.
The technical design should be reviewed by the responsible teams. This guide does not prescribe a security protocol or claim that a printed code is inherently single-use. Confirm how validity, expiry if applicable and redemption status are maintained by the actual implementation.
03 / BUYER NOTES
Decide whether the participant earns one fixed gift, chooses from a range or receives an approved substitute. The screen and campaign wording should agree. A promise of a specific souvenir creates a different stock obligation from a clearly explained choice among available items.
Map the redemption record to the correct physical position and test the real gift pack. If stock runs out, tell the participant what happens next under the agreed campaign rules. Avoid silently substituting a different item or treating an empty machine as proof that the person has already received a gift.
04 / BUYER NOTES
A participant may scan twice because the first screen was slow, return after an interruption or present the code on another device. Define the expected response to these normal behaviours. A clear message should distinguish an invalid code, an already completed claim and a temporarily unavailable service.
Do not assume duplicate scans are automatically prevented just because a database exists. Include repeated and concurrent attempts in the agreed integration test plan. The campaign and machine teams should confirm how the system avoids conflicting redemption states without exposing unnecessary participant details on screen.
05 / BUYER NOTES
A code may be accepted before the gift reaches the collection area. If delivery then fails, the participant needs a recovery route. Agree when the claim is considered completed and what evidence supports that state in the proposed system.
The support team should be able to distinguish a rejected claim from an authorised but incomplete vend. Define who can review or reissue an entitlement and how that action is recorded. Do not promise automatic reactivation or an automatic second gift unless that behaviour is implemented and demonstrated.
06 / BUYER NOTES
At the end of a shift or event, compare issued entitlements, completed claims, unresolved attempts and physical stock movements. Those are different measures. A high number of issued codes does not prove that the same number of gifts was collected.
Use the records to resolve open participant issues and evaluate the campaign. Keep reports limited to the information needed by each team. Before launch, run a complete test from the real online task through code presentation and collection, including at least the documented failure and recovery paths.
Meaning: The campaign requirement was met.
Owner: The campaign platform or responsible team.
Meaning: The presented claim was accepted.
Owner: The confirmed integration.
Meaning: The machine reported the defined handover event.
Review: Customer issues may still need investigation.
PRACTICAL ANSWERS
No. The scanner must be connected to the agreed validation, redemption and dispensing workflow.
No. Code acceptance and physical delivery are separate events.
Compatibility depends on the documented interfaces and project-specific implementation. It must be reviewed and tested.
YOUR NEXT STEP
Share the online task, proposed claim rules and actual souvenir packaging with WEIMI to review the vending scope and required integration.
Explore equipment →Discuss your requirements →