Approve or Reject a Moola Redemption

---

At a glance

When a team member buys an item from the Moola Store, the purchase enters a pending state that a leader must approve or reject before the store fulfills the reward. Approvals and rejections happen in the Moola Transaction Log. This article covers the full workflow from notification to final status.

Before you start

1. You need a role with approval permission for Moola redemptions. By default, Manager and above are included in redemption notifications and can approve or reject. Specific items can also route to other named leaders if the item was configured that way.
2. You should have received an in-app or push notification titled Moola Redemption Requested. If notifications are off on your device, you can still find pending requests by opening the Moola Transaction Log directly.
3. Decide if the redemption is valid before you act. Rejections should be rare and explainable; arbitrary rejections damage trust in the reward system.
4. Estimated time: thirty seconds per decision.

Steps

1. From the notification, tap or click Moola Redemption Requested. Alternatively, go to Team in the left navigation menu, then click Moola Transaction Log in the top right of the Team view.
2. The Transaction Log shows every Moola activity at the store. Filter by Status: Pending to see only redemptions awaiting a decision. You can also filter by date, type, or specific user if there are many entries.
3. Click the pending redemption row to expand its detail. The row shows the team member, the item they requested, the Moola cost, and the timestamp.
4. Click Approve or Reject.
5. If approving: the Moola deduction stands, the team member receives a Moola Redemption Approved notification, and the reward moves into a fulfillment state. The leader assigned as Leader in Charge of Distribution (or the store's default fulfillment owner) hands over the physical reward.
6. If rejecting: the Moola amount credits back to the team member's balance, and the rejection appears in the Transaction Log. [VERIFY: whether the team member receives a rejection notification and whether a reason can be attached to the rejection.]
7. You should now see the redemption's status change from Pending to Approved or Rejected, and the team member's balance updated accordingly.

Video

Video coming soon.

Common gotchas

I missed the notification and the team member is asking about their reward.

Open the Moola Transaction Log, filter by Pending, and find their redemption. Act on it from the Log. Notifications are convenient but not the only access path; the Log is authoritative.

I rejected by accident.

[VERIFY: confirm whether a rejected redemption can be re-approved from the Transaction Log, or whether the team member needs to re-request. If a rejected state is final, the recovery path is to re-award the equivalent Moola (which comes from your weekly budget) and ask them to re-submit; or transfer the Moola from another leader if your budget is exhausted.]

A team member redeemed an item but my store has run out of inventory physically.

Approval status in OneClick reflects the request disposition, not inventory. If the store cannot fulfill a request due to physical inventory shortage, reject the redemption (which credits the Moola back) and leave a note explaining the issue, or approve and then follow up with the team member directly about timing. Then update the Moola Store item's Total Quantity to match real stock.

I do not have authority to approve an item that was routed to another leader.

Each Moola Store item can be configured with a specific Leader in Charge of Distribution and additional notification recipients. If an item is routed to someone else, your Approve button may be hidden or inactive. Check the item's configuration under the Moola Store admin surface, or ask the assigned leader to act on the request.

The pending queue is piling up.

Moola redemptions left pending too long erode the reward's feel. Set a cadence (for example, checking the Transaction Log at the start of every shift) and stick to it. If the volume is too high for a single person, split approval coverage across multiple leaders by assigning different items to different Leader in Charge of Distribution values.

A team member is asking why their redemption was rejected.

Transparency helps. If your store does not have a standing rejection policy, agree on one (for example, "rejections only for inventory shortages or configuration errors, never for reward type"). Communicate the policy so team members know what to expect.

Related articles

1. Understand Moola (Reference, Core slot 17)
2. Build Your Moola Store (How-To, bonus). If an item needs to be routed to a different leader, update it here.
3. Award Moola to a Team Member (How-To, Core slot 18)
4. Troubleshoot a Moola Redemption Issue (Troubleshooting, bonus, drafting soon)

Still stuck

If approvals or rejections are not saving, the Moola Transaction Log is empty despite pending requests being visible in notifications, or balances do not update correctly after a rejection, submit a support ticket and include your store number, the team member and item, a screenshot of the Transaction Log row, and the expected vs actual behavior.

---

Pre-publish checklist status

1 3145e08b-4c6c-4de6-8879-69a98d457e45 complete Seven sections filled.

2 630836af-a763-4266-8113-ee7b31f7ff05 complete Final step is a confirmation step.

3 59438c84-e19b-4663-91fd-39fd61acb564 complete No em dashes, no hedge words, permission-based role references.

4 6668fe98-121e-45d2-90ea-6c3405760c1c complete No real identifying data.

5 e49f4538-e251-41bf-99c2-b0a74582af49 incomplete UI verified against Production.

6 7bff3265-a361-48ca-b421-e6afd0353c2a incomplete VERIFY blocks resolved (rejection notification and reason field, re-approval after rejection).

7 3e6f9d8f-8dc4-41da-bec1-ad98166bea95 incomplete Screenshots at decision points (Step 1: Transaction Log entry point; Step 2: Pending filter; Step 4: Approve/Reject actions).

8 a6966c18-856c-40ad-80c2-1630d18f3e17 incomplete Related article links activated.

9 8a512169-31f6-4157-aca0-bced4b849027 incomplete Primary search term tested (likely "approve moola" or "moola request").

10 8efc34cb-0187-4972-8172-ad1472ec1e15 incomplete Reviewed by Jared and Kevin.

Source

Existing kb.oneclickapp.com Moola article, Tracking section (Moola Transaction Log, filter options, approve/reject workflow) plus the Redeeming section (state transitions from pending to approved or rejected and the Moola-credits-back-on-rejection behavior).