What does a Loyalty Officer FTE own?
A Loyalty Officer FTE on ftes.ai owns the economics of a store's loyalty program, in the Customer department of the e-commerce org chart. It is judged on enrolled customer value versus matched unenrolled, and accountable for that comparison being measured honestly. It exists because most loyalty programs are reported by comparing members with non-members, which proves only that people who buy a lot join programs.
It does not own the program's design, which is the owner's, or the messaging platform, which the Lifecycle Officer FTE runs. It owns the measurement and the proposals that follow from it.
How does the matched comparison work?
The Loyalty Officer FTE pairs each enrolled customer with an unenrolled customer who looked the same at the moment of enrolment: similar first-order value, the same acquisition cohort and channel, similar order count before that date. It then compares what the two groups did afterwards, orders, contribution and returns over a horizon the owner set. The difference is the program's effect on behaviour, separated from the selection effect of who chooses to join.
The comparison is built from the Customer Intelligence FTE's record and the Controller FTE's contribution figures, and its inputs are shown so the owner can challenge the matching rule.
What is points liability, and why report breakage?
Points liability is the value of rewards customers have earned and not yet redeemed, which a store carries as an obligation. Breakage is the share of points that expire or go unredeemed. The Loyalty Officer FTE tracks both from the program's records, reports them monthly, and shows how a proposed change to tiers, earning rates or expiry moves each, because a change that raises engagement can also raise the liability faster than the revenue it brings.
These are the numbers a finance lead asks for at year end, and most stores assemble them by hand from an export.
What does it propose, and what waits for approval?
The Loyalty Officer FTE proposes changes to tier thresholds, earning rates, rewards and expiry rules, each with the matched evidence behind it, the reward cost, the liability effect and the break-even, meaning how many extra orders the change needs to pay for itself. It proposes member messaging rules that fit the Lifecycle Officer FTE's frequency budget. Every proposal waits in Approvals; the program's design is the owner's.
Where a tier shows no measurable lift at its threshold, the proposal may be to lower the threshold, to change the reward, or to remove the tier, and each option's economics are shown side by side.
What does the Loyalty Officer FTE never do?
It never changes a tier, a reward, an earning rate or a customer's points balance without approval, never messages members outside the Lifecycle Officer FTE's frequency budget, and never reports a program lift measured against the average customer, because that comparison flatters every program. It never reports liability from an estimate; the figure comes from the program's records.
It also never treats breakage as free money without saying so. Breakage improves the liability figure and can damage the relationship with the customer whose points expired, and the report shows both.
What does it report, and how honestly?
The Loyalty Officer FTE reports enrolled value versus matched unenrolled by segment and tier, points liability and breakage, reward cost, redemption patterns, and proposals with their measured effect after approval. The matched comparison is reported with its horizon and matching rule, and with the caveat that a matched comparison is observational; where a holdout on a program change is possible, the FTE proposes one.
A program that shows no lift over its matched comparison is reported as showing no lift, with the tiers where that is true named.
How does it work with the other roles, and in which tools?
The Loyalty Officer FTE reads the Customer Intelligence FTE's record for matching, the Controller FTE's contribution for value, and hands member messaging to the Lifecycle Officer FTE. It reads Smile.io, LoyaltyLion or Yotpo Loyalty for enrolments, points and redemptions, and Shopify, WooCommerce or BigCommerce for orders.
It earns its place at any store with a program old enough to have a liability worth measuring and enough members to match, which is most programs after their first year.