Transactions and Administrative Follow-Up - Article
Summary
A reward redemption creates a promise to fulfill. Incentives Transactions gives your team a practical record of the order, recipient, point cost and operational state so that the learner’s experience remains clear after redemption.
Use this article to:
- Find reward orders and assign fulfillment follow-up
- Maintain status and tracking information deliberately
- Understand the operational notification routes
- Investigate cancellation or delivery exceptions without assuming automatic reversals
Transactions and Administrative Follow-Up
Incentives do not end when points are earned or rewards are redeemed.
From an administrative perspective, the Transactions layer is where incentives move from motivation to execution—ensuring rewards are delivered, tracked, and auditable. A transaction is created every time a learner redeems points for a product in the incentives shop.
Each transaction represents:
- A confirmed redemption
- A deduction of points from the learner’s balance
- An operational task (shipping, digital delivery, or follow-up)
Transactions within Incentives exist independently of learning activity. They are part of incentive operations, not training delivery.
Transaction Overview
The Transactions overview serves as the operational control center for all reward redemptions. It allows administrators to track each redemption through its lifecycle, update statuses, and follow up on exceptions such as delays, errors, or manual handling needs.
Transactions are managed via Settings → Incentives → Transactions, providing a centralized and lightweight way to oversee reward fulfillment without introducing unnecessary complexity.
The list includes the following fields:
| Column or control | What it tells you | How to use it |
|---|---|---|
| ID / Buyer / Created | Identifies the order, recipient and creation time | Confirm the correct redemption before following up |
| Track number / Copy | Shows the recorded dispatch reference where supplied | Copy it accurately into your delivery follow-up |
| Status | Shows the operational fulfillment state | Keep it aligned with the actual work, not merely the intention to dispatch |
| Search | Finds buyer name, email or tracking number | Locate a specific obligation |
| Filter by status | Narrows the working list to an order state | Review Created or In progress orders that need attention |
| Load more | Displays further orders when available | Continue beyond the currently displayed results |
A status dropdown is available on each row, allowing administrators to update the transaction as it moves through the fulfillment process.
The overview keeps these working controls beside the order records, as illustrated below.

Transactions provide a lightweight, native way to manage incentive redemptions and fulfillment status. The intent is not to replace full logistics or ERP systems, but to give administrators a simple, reliable overview of what has been redeemed and what action is required.
While fulfillment emails provide order details, the transactions view acts as a practical bookkeeping layer—allowing you to update statuses, track progress, and maintain visibility over rewards that have been handled manually or by different teams.
In some organizations, these emails are routed directly to a “merchandises partner”, back-office or external fulfillment system. In others, administrators manage fulfillment directly within Eurekos. The transactions view supports all these approaches by providing a minimal but structured management option that keeps incentive handling transparent and auditable without adding operational complexity.
Transaction Detail View
Selecting a transaction opens the detail page, which provides the full context needed to complete fulfillment.
| Field | What it shows or allows |
|---|---|
| Buyer | Including email reference |
| Product | With a direct link to the product definition |
| Tracking number | Editable allowing administrators to add a shipping tracking code and a copy action |
| Address | Shipping address for physical rewards |
| Phone | Shown if provided by the user |
| Total | Points spent |
| Status | Editable via dropdown |
| Created | Timestamp for audit and traceability |

Transaction Status and Lifecycle
The available operational states are Created, In progress, Shipped, Completed and Cancelled. Use a state that reflects what the responsible team has actually done.
| Status | Operational meaning | Action or consequence |
|---|---|---|
| Created | A redemption is recorded and needs handling | Identify the promised product and fulfillment owner |
| In progress | The team is processing the order | Resolve any missing recipient or delivery information |
| Shipped | The order is marked as dispatched | Record the tracking reference where relevant; the configured shipped email is sent |
| Completed | The operational handling is finished | Use after the deliverable has been provided and the record is ready to close |
| Cancelled | The order is marked cancelled | Review point, stock, communication and external fulfillment effects separately |
Shipped records a fulfillment state; it is not proof of delivery or a live carrier integration. For a digital reward, a clear completion process can be more appropriate than dispatch language. Make sure the recipient receives the promised code, benefit or other deliverable through your actual process.
A cancellation status alone does not establish that points were refunded, stock was restored, a digital code was revoked or a parcel was recalled. Check the actual effects before promising a reversal or issuing a replacement.
Connect order events to the right messages
Keep the order event, recipient and required action together when planning communication. Administrators maintain reusable messages under Settings → Email sending → System emails → Incentives. Email Sending - Article owns the template and delivery procedure; the table below explains the operational responsibilities. A message does not itself pack, dispatch or deliver the reward.
| Order event | Recipient and purpose | What to verify |
|---|---|---|
| Reward order created | Registered logistics recipient — an actionable new-order notification | The operational owner can identify the order and required action |
| Redemption confirmed | Learner — confirmation of the recorded reward order | The recipient can identify the order and the next fulfillment expectation |
| Order set to Shipped | Learner — dispatch information for the recorded order | The message and tracking reference reflect the actual process |
The logistics address is configured under Settings → Incentives → Shop and must belong to the intended registered platform user. Expiry reminders and reset messages belong to the points lifecycle, not this order lifecycle; Setting Up Incentives covers that separate configuration.
Digital vs. Physical Rewards — Operational Considerations
Digital rewards or non-physical incentives do not automatically mean no management. Vouchers, licenses, access codes, or third-party rewards often still require manual steps—such as issuing codes, initiating communication, or coordinating with external partners responsible for fulfillment. These flows frequently span multiple systems, processes, or teams rather than a fully automated integration.
Physical products can introduce similar—or even greater—complexity. Shipping, ordering, and fulfillment may involve internal teams, regional offices, or external vendors, each with their own timelines and dependencies.
Do not underestimate this operational layer when designing your incentive mix. The type and volume of rewards you offer directly impact the administrative effort required to sustain the program. A well-balanced mix considers not only motivational value, but also the practicality of fulfillment at scale.
This is why complete and accurate order details matter. The transaction record becomes the single source of truth, ensuring that whoever fulfills the reward—internally or externally—has all necessary information to process requests efficiently and without unnecessary follow-up.
Investigate an order without duplicating the obligation
Begin with the order ID, buyer, product and current status. Check what the fulfillment team has already sent, whether a tracking reference or digital code exists and what the learner has been told. Then decide the next operational action.
For example, a workshop voucher may have been issued manually while the order still shows In progress. Confirm the code and delivery before issuing another voucher. A physical item marked Shipped may need carrier follow-up rather than a second redemption. Keep the native record and the external process consistent.
Best Practices for Administrators
To keep incentives effective and trusted:
- Review transactions regularly
- Update statuses promptly
- Communicate clearly if fulfillment is delayed
- Align reward availability with operational capacity
- Treat transactions as part of customer or partner experience—not back-office noise
Well-managed transactions reinforce the value of the entire incentives program.
Verify the configuration
Check the intended learner and operational owner, including the relevant role and organization scope. A saved setting and a completed downstream outcome are different evidence.
| Scenario or check | Expected result or evidence |
|---|---|
| A new reward order appears | The logistics owner can find the buyer, product, point total and delivery details |
| Processing starts | The operational status identifies who should act next |
| A dispatch is recorded | The tracking reference and order-shipped message correspond to the actual shipment |
| A digital reward is completed | The learner receives the promised deliverable and the order record reflects completion |
| An order is cancelled | The team separately verifies point balance, stock, messages and any external fulfillment |
| Finance reviews a training purchase | Commerce Transactions is used for the financial record; Incentives Transactions remains the reward-order view |
Troubleshooting
| Problem | What to check |
|---|---|
| The order cannot be found | Search buyer name/email or tracking number, check the status filter and confirm that you are in Incentives Transactions |
| No new-order message reaches operations | Check the registered logistics recipient and the administrative new-order System Email configuration |
| The learner has no tracking information | Open the order and review the recorded reference and actual dispatch process |
| Shipped was selected before dispatch | Correct the operational handling and communication deliberately; do not treat the label as proof the carrier has the item |
| A cancellation did not produce the expected reversal | Check the actual points, quantity and external-delivery effects before promising an automatic refund or replacement |
| A reward is Complete but the learner has no deliverable | Confirm the code, shipment or benefit with the fulfillment owner rather than relying on the state alone |
FAQ
-
Who fulfills digital vouchers or physical rewards?
Your organization’s named fulfillment owner handles the reward. The shop records the redemption and supports notifications and order follow-up; a product description, SKU or external link does not by itself issue a voucher, ship an item or enroll the learner in training.
-
Where can I find my reward order?
Open your own profile and use Orders where available. Find the order ID, product, points, status and tracking reference. Administrators investigate fulfillment through Settings → Incentives → Transactions rather than another person’s own-account tabs.
-
What does cancelling a reward order reverse?
Cancelled records the order state. Do not assume from that label alone that points, product quantity, a shipped item or an externally issued code has been reversed. Review the actual balance, stock and fulfillment effects before promising a refund or replacement.