Understand Moola

---

At a glance

Moola is OneClick's reward system for recognizing 2nd Mile Service. Leaders award Moola to team members for great work, team members spend their Moola in the store's Moola Store on rewards the store has set up, and the whole flow, from award to approval to fulfillment, happens inside OneClick. This article is the canonical reference for how the system works; separate How-To articles cover the specific workflows.

Before you start

This is a reference article. Read it once to build the mental model, then come back for specific concepts when you need them. Related How-To articles (Award Moola to a Team Member, Build Your Moola Store, Set Moola Budgets, Approve or Reject a Moola Redemption, Transfer Moola to Another Team Member) link here for the concepts and focus on the workflows.

Core reference content

What Moola is

Moola is a virtual currency operators use to recognize team members for going beyond expected service. Moola values are set by your store, earned through leader awards, and spent in a store-defined Moola Store on physical rewards (shirts, branded gear, gift cards, store credit, whatever the store has set up). Moola helps build a culture of positivity, recognition, and appreciation, which in restaurant environments translates directly into team member retention and 2nd Mile Service consistency.

The reward items themselves are purchased and distributed by your store, not by OneClick. OneClick tracks who has how much Moola, who earned it, what is available to redeem, and which redemptions are pending, approved, or rejected. Fulfillment of the actual reward (handing over the shirt, applying the store credit) is handled by the store.

Who can do what

Six functional areas define the Moola permission surface. Your store's Customization Rubric defines exactly which roles have which of these, and the default permission tier per area is shown in parentheses. See Understand Permission Levels and Understand Your Customization Rubric for how to check or change your store's configuration.

1. Award Moola to team members (default: any leader role). Gives Moola out of your weekly budget.
2. Deduct Moola from team members (default: Manager and above). Removes Moola from a team member's balance, for example if an award was given in error.
3. Transfer Moola (available to team members themselves). Team members send Moola from their own balance to another team member's balance, with a note.
4. Redeem Moola in the Moola Store (available to team members themselves). Buys a reward from the store-defined Moola Store.
5. Manage the Moola Store (default: Manager and above). Creates, edits, activates, deactivates, or deletes the reward items in the Moola Store.
6. Manage Moola budgets (default: requires the "Manage Moola" permission, typically granted at Manager and above; budgets at the permission-group level can only be edited by Director and above). Sets the weekly budget limits per permission group or per individual.

[VERIFY: exact row labels for each of the six areas on the rubric Moola tab. The six functional categories above are descriptive; the rubric may use different wording.]

How awarding works

Leaders award Moola to team members in two places. On the Shifts screen, a Rewards button in the upper left opens a panel where the leader drags Moola amounts onto team member names in the shift layout; the amount applies instantly. From a team member's profile, the Moola tab has a Reward button that opens the award form with an amount field and a note.

Each leader has a weekly budget that determines how much Moola they can award in a given week. The budget refreshes automatically every Sunday. Budgets are set at the permission-group level by default (for example, all Shift Leaders start with the same weekly budget), and individual adjustments are possible for specific cases. See Set Moola Budgets.

How the Moola Store works

The Moola Store is a list of rewards your store has configured. Each reward has a name, description, image, cost in Moola, and optionally a total quantity, max-per-employee cap, launch date, expiration date, and a specific leader assigned as the distribution owner. Team members see the Moola Store from their profile; they can favorite items for later, and when they have enough Moola, they can buy an item. The purchase goes through an approval workflow (next section) before the store distributes the physical reward.

Store items are purchased and distributed through your store, not OneClick. OneClick tracks the request, the approval, and the ledger; the actual reward handover is a store-level activity.

Examples of Moola Store items observed across customer stores include branded apparel (shirts, jackets, shorts, pants, chef coats, fleece jackets), branded gear (tumblers, tote bags, lanyards), footwear, and cost-varies items where the reward price depends on selection. Your store decides what to offer.

How redemption works

Redemption runs on a request-and-approval model. When a team member buys an item from the Moola Store, four things happen. First, the Moola cost is immediately deducted from the team member's balance (the ledger holds the amount pending approval). Second, a redemption request is created in the Moola Transaction Log. Third, everyone configured to receive redemption notifications for that item gets an in-app and push notification (the store sets who receives notifications per item; by default, Manager and above are included). Fourth, the team member sees a pending-purchase notification letting them know the request is in flight.

The assigned leader reviews the request in the Moola Transaction Log and either approves or rejects it. Approval keeps the Moola deducted and moves the request into a fulfillment state the store acts on to hand over the reward. Rejection credits the Moola back to the team member's balance; nothing else changes.

Transfers between team members

Team members can send Moola from their own balance to another team member's balance. The transfer happens from the recipient's profile using the Transfer action. The sender's balance drops by the transfer amount; the recipient's balance rises by the same amount. A note accompanies the transfer so context is preserved. Transfers are peer-to-peer recognition (for example, thanking a coworker for covering a shift) and do not pull from a leader's weekly award budget.

The Moola Transaction Log

The Moola Transaction Log is the central ledger for all Moola activity at the store. Managers and above access it from Team, then Moola Transaction Log in the top right. The log shows awards, deductions, transfers, and redemption requests in one list, filterable by date, type, user, and status. Pending redemption requests can be approved or rejected directly from the same view.

Individual team members also see a Moola history on their own profile under the Moola tab, filtered to just their own activity, sortable by time frame, date range, or transaction type. Rejected redemptions appear in the history as credited-back transactions so the ledger stays balanced and auditable.

Budgets

Every leader with award permission has a weekly Moola budget that caps how much they can give out in a seven-day window. Budgets refresh automatically every Sunday. Two configuration surfaces exist:

1. Per permission group (default). Set in Settings, then Moola, then the Budget section. Every leader in the group inherits the group's weekly budget. Changes to the group budget apply to new hires promoted into the group as well as existing members.
2. Per individual. Set from a specific team member's profile, on the Moola tab, using the Adjust Budget action. Overrides the group default for just that person. Useful when a specific leader has demonstrated great judgment and should get more runway, or when a leader has been over-rewarding and should be pulled back.

Budgets include an Unlimited option at the permission-group level that removes the weekly cap entirely. [VERIFY: confirm whether the Unlimited box grants unlimited award capacity to that permission group, or unlimited in the sense that no tracking applies.]

Only users with the Manage Moola permission (by default, Manager and above) can change budgets for other people. Director-level or above is required to change budgets at the permission-group level. Lower-tier leaders cannot edit their own or others' budgets.

Notifications

Moola generates five notification types, all delivered in-app and via push notification (email delivery is planned but not yet available):

1. Get Moola. Team member is notified when Moola has been awarded to them, with the reason.
2. Charged Moola. Team member is notified when Moola has been deducted from their balance, with the reason.
3. Moola Redemption Requested. Leaders with access to the Moola settings and any additional leaders set up on the specific item are notified when a team member requests a redemption.
4. Moola Redemption Approved. Team member is notified when their redemption has been approved.
5. Moola Redemption Rejected. Team member is notified when their redemption has been rejected. Moola is credited back to their balance.

Reports

Moola reports live under Reports in the left navigation. They support timeframe and date-range filtering and export for records or payroll reconciliation. A list-view alternative is available from Team using the Moola Only filter, which shows team members with columns for name, age, highest position, Moola balance, budget, and amount handed out. Sortable by any column.

Video

Video coming soon.

Common gotchas

A team member says their balance dropped but they did not buy anything.

Balances drop immediately when a redemption request is submitted, not after approval. Check the Moola Transaction Log for a pending redemption in their name. If the redemption was rejected, the Moola credits back to the balance; if approved, the deduction stands.

A leader feels they have no weekly Moola left even though the week just started.

The weekly budget refreshes automatically every Sunday, but the timing can catch leaders off guard if they award heavily early in the week and hit their cap days before the Sunday reset. Check the leader's current budget under Settings - Moola - Budget (for permission-group defaults) or on their profile (for individual adjustments). If the budget looks too tight for the store's recognition culture, adjust it upward.

I want automated Moola earning (for example, every stamped passport earns 10 Moola).

The current product does not support automated earning rules. All Moola is awarded manually by leaders or transferred between team members. If automated earning is a product direction, that is a feature request, not a configuration change.

A leader appears to be playing favorites with Moola awards.

The Adjust Budget action on that leader's profile lets you cap their weekly awards until the pattern resolves. Monthly reports show Moola handed out per leader, which is the audit surface for this concern.

A team member transferred Moola to someone they did not intend.

Transfers do not have a built-in undo. The simplest path is for the recipient to transfer the amount back, with a note explaining the correction. The Moola Transaction Log preserves both transactions for auditability.

I configured a Moola Store item but team members do not see it.

Check the launch date (the item is hidden until the launch date arrives), the expiration date (hidden after expiration), and whether the item is active (Deactivate hides it, Activate restores it). If Limited to Employees is set, only the named employees see the item.

A team member redeemed something but the leader never got a notification.

By default, Manager and above receive redemption request notifications. If a specific item should route to someone else, set the Leader in Charge of Distribution during item creation and add any other notification recipients through the Select Team Members field. Items without a specific distribution leader fall back to the default notification rule.

Related articles

1. Award Moola to a Team Member (How-To)
2. Build Your Moola Store (How-To)
3. Set Moola Budgets (How-To)
4. Approve or Reject a Moola Redemption (How-To)
5. Transfer Moola to Another Team Member (How-To)
6. Troubleshoot a Moola Redemption Issue (Troubleshooting)
7. Understand Permission Levels (Reference)
8. Understand Your Customization Rubric (Reference)

Still stuck

If Moola balances, transfers, or budgets are behaving in a way this reference does not explain, submit a support ticket and include:

1. Your store number.
2. The team member or leader involved.
3. A screenshot of the Moola Transaction Log or the affected profile.
4. The exact action taken and what happened versus what you expected.

Support typically responds within one business day.

---

Pre-publish checklist status

25 10c8e8b2-7f07-40b3-ba5d-ea36668cd78a complete All seven sections filled, adapted for Reference category (Steps section replaced with Core Reference Content).

26 ce257175-ec52-4b4c-bcb1-b5c66e1ef487 complete No em dashes. UI paths rendered with hyphens ("Settings - Moola - Budget" not "Settings → Moola → Budget").

27 e5d5aa40-021d-42ee-98d9-b4942353da8e complete No hedge words.

28 eaa215e9-ac0c-4269-aabb-76b9adb2194e complete Role references are permission-based, not role-name-based.

29 ec64ef13-9589-47cd-9df5-2b1ca520544b complete No real identifying data in body or metadata (April 24 privacy pass; source PDF's real first-name example substituted with generic phrasing).

30 22a90f88-a6d4-402f-b10e-0b4d86e72c0a complete First Phase 2 Core article, slot 17.

31 e53866ea-f791-4c5a-8a18-409a64dae889 incomplete UI verified against Production before publishing. Source material is the existing live KB article; Production parity for the current release is a separate Jared-owned check.

32 c4634a73-bdca-4c27-aff7-7e843dbc4bd1 incomplete VERIFY blocks resolved (rubric row labels for the six functional areas, Unlimited budget semantics).

33 0f36d455-cdb1-4ed6-9390-5f0294904f15 incomplete Related article links activated once those articles exist.

34 f0b99b0c-b31c-49b7-8080-0b0d76e1caa1 incomplete Primary search term tested in HubSpot KB search (likely "what is moola," "moola system," "moola rewards").

35 d57e8bb2-c669-46e4-a5e1-6ca0aa817719 incomplete Reviewed by Jared.

36 f561b832-5aa1-4d3a-b488-0d07184b2a97 incomplete Reviewed by Kevin.

Source

Source of content is the existing kb.oneclickapp.com Moola article as uploaded to KBRW Turn 21 (April 24, 2026), plus the rubric Moola tab captured during Turn 6-7 walkthroughs. The existing article covered everything except verbatim rubric permission-row labels.