Gift vouchers can turn a staff reward from an informal purchase into a controlled business process. SIMcloud gives the operator a live voucher catalogue, wallet-funded ordering, bulk CSV fulfilment and order history that can be reconciled to the approved reward list.
This tutorial covers the operational design around the purchase: approval, product choice, recipient privacy, duplicate prevention, delivery and reconciliation.
Define the staff reward programme first
Do not start with a voucher spreadsheet. Start with a written rule that answers:
- Who qualifies for a reward?
- Who approves the recipient and value?
- May the recipient choose the voucher brand?
- Which cost centre or campaign funds it?
- How will payroll, tax and accounting treatment be reviewed?
- Who may see and deliver completed voucher codes?
- How are failed or unavailable products handled?
The technical workflow should enforce the programme rather than silently inventing its policy.
Choose products from the live catalogue
Open SIMcloud’s Gift Cards catalogue and identify the approved options. Depending on current availability, the catalogue can include grocery, retail, restaurant, transport and lifestyle products.
A practical programme often uses one of three approaches:
| Approach | Advantage | Control needed |
|---|---|---|
| One standard brand and value | Simple approval and reconciliation. | Confirm the product suits the whole recipient group. |
| Approved catalogue choice | More useful to recipients. | Capture the selected product before creating the batch. |
| Different values by award level | Supports tiered recognition. | Document the rule and prevent manual value overrides. |
Do not promise a brand before checking availability. Supplier availability and denominations are live. Build an approved fallback process rather than automatically substituting a different voucher.
Prepare the approved recipient file
Keep the approval record separate from the fulfilment file. The fulfilment CSV should contain only what SIMcloud requires plus a non-sensitive reference that maps back to the authorised list.
- Export the final approved recipients from the responsible HR or campaign system.
- Assign a unique reference to every reward.
- Resolve each approved voucher brand against the current SIMcloud catalogue.
- Select an amount currently available for that product.
- Remove duplicates using the programme identifier, not only the employee name.
- Have a second person review the row count and total value where required.
- Export the clean file as CSV for SIMcloud.
Do not put completed voucher codes into the input CSV. Codes are output from successful fulfilment and require stricter access.
Upload and confirm the reward batch
- Sign in and open the bulk Gift Card CSV workflow.
- Download the current template rather than reusing an old header.
- Upload the prepared CSV.
- Correct every invalid product, amount, reference or duplicate row.
- Review the accepted row count and total wallet requirement.
- Confirm that the wallet balance covers the batch.
- Release the approved batch once.
- Monitor the batch and individual order results.
Confirmation creates value-bearing orders. If the review is wrong, cancel before confirmation, correct the source file and upload it again. Do not edit the approved list informally during fulfilment.
Deliver vouchers privately
Separate the people who can report on a reward campaign from the people who can view voucher codes. Most reporting needs the recipient reference, product, value and status—not the code itself.
- Deliver each code only after the order is successful.
- Verify that the reference matches the intended recipient.
- Use a controlled private channel.
- Include supplier redemption and expiry information as returned.
- Record delivery without copying the code into a general report.
Reconcile the campaign
Compare the original approval list with the final SIMcloud results using the unique reference. Divide rows into successful, pending and failed groups. The total approved, total ordered and total successfully fulfilled should be explainable without opening voucher codes.
Retain:
- Programme approval and budget.
- Approved recipient reference and value.
- SIMcloud batch and order identifiers.
- Final processing and billing status.
- Delivery confirmation.
- Documented resolution for failed or unavailable rows.
When to automate with the VAS API
Use the VAS API when rewards originate inside another application and the volume or frequency makes manual CSV handling inefficient. The integration should fetch the live catalogue, validate the approved selection, check wallet balance, create one traceable order, store its identifiers, poll to a final state and deliver the completed voucher securely.
Automation does not remove approval, reconciliation or code-protection requirements. It makes them more important because fulfilment can happen faster.
Frequently asked questions
Can SIMcloud send staff reward vouchers in bulk?
Yes. Use the bulk Gift Card CSV workflow for an approved list and reconcile every row.
Should employees choose their voucher?
That is a programme decision. If choice is allowed, capture the approved selection before creating the fulfilment batch.
Can managers see voucher codes in reports?
Ordinary reporting should use references, values and statuses. Restrict voucher-code access to the delivery function.
What if a product becomes unavailable?
Pause that row and follow the approved fallback process. Do not silently substitute another brand.
Can we integrate our rewards platform?
Yes. Use the documented VAS API for live catalogue lookup, order submission and result polling.