How the Stoify Loyalty Points Module Turns Repeat Orders Into a Storefront Workflow

Customer loyalty is easy to describe and surprisingly easy to scatter. Points get shown in one place, balances live somewhere else, checkout has its own rules, and customer service eventually has to explain why the number a shopper saw does not match the order record.

The new Stoify loyalty points module is built to keep that workflow closer together. Merchants can enable loyalty points per site, configure earning and redemption rates, show shoppers estimated points on product and checkout pages, and keep the ledger tied to orders, customers, invoices, and dashboard reporting.

The first version started as earn-only. The module now also supports checkout redemption, so points can become a real payment option instead of only a post-purchase signal.

Why loyalty should be part of checkout

Loyalty points become more useful when they are visible at the moments where customers are already making decisions.

That means the product page can show the points a shopper is likely to earn. Checkout can explain the points attached to the current basket. If the customer has enough points, checkout can offer a loyalty payment path alongside Stripe.

That visibility matters because loyalty should not feel like a hidden account feature. It should feel like part of the purchase experience.

What merchants can configure

The loyalty settings page keeps earning and redemption separate.

Merchants can configure:

• How many points customers earn per major currency unit spent
• Whether earning previews appear on the storefront
• How many points are worth one major currency unit at redemption
• Whether the loyalty module is enabled for the current site

That separation is important. A store may want a generous earning rate while keeping a more conservative redemption rate. Stoify keeps those settings readable instead of blending them into one opaque conversion rule.

How points are earned

Points are awarded from paid orders using the eligible merchandise amount after discounts. Shipping and tax are excluded, which keeps the points calculation tied to product spend rather than fulfilment or tax rules.

Stoify records earning activity in a loyalty ledger, then updates the customer balance from that ledger. The order-level transaction also prevents duplicate earning if a checkout flow is refreshed or finalized more than once.

Refunded orders can create a reversal transaction so the customer balance remains auditable. Instead of silently editing history, the ledger shows what happened.

How redemption works at checkout

When loyalty points are enabled and the shopper is signed in, checkout can show a loyalty points payment option if the customer has points and the basket has eligible product spend.

When selected, Stoify applies the maximum usable points to eligible item spend after discounts. Points do not cover shipping or tax. If the points cover all eligible product spend, Stripe only charges any remaining shipping or tax. If the final amount is zero, the order can be placed without Stripe.

Orders that spend points do not earn new points in this version. That keeps the first redemption model simple and avoids circular earning loops.

Why the ledger matters

The most important part of a loyalty system is not the orange star icon, though we are fond of it. The important part is being able to explain the balance.

Stoify stores loyalty activity as transactions:

• Earned points from paid orders
• Spent points from checkout redemption
• Reversed points from eligible refunds
• Manual adjustments for future operational workflows

That lets the dashboard show customer balances, transaction history, recent activity, and outstanding point totals without inventing a separate reporting surface.

Where loyalty appears in Stoify

When the module is enabled, loyalty points now show up in the places merchants naturally expect:

• Product cards and product detail pages
• Checkout totals and payment method selection
• Customer tables and customer detail views
• Order tables and order detail pages
• Invoice tables, invoice detail views, and invoice PDFs
• A dedicated loyalty points dashboard page

When the module is disabled, those loyalty surfaces stay hidden. That keeps the storefront and dashboard clean for stores that are not using rewards yet.

Loyalty as an operating workflow

The larger goal is not only to add rewards. It is to make rewards feel operationally understandable.

For small teams, loyalty can become another disconnected system very quickly. Stoify’s module approach keeps it tied to the same site settings, checkout flow, customer records, and order history that teams already use every day.

That is the kind of loyalty system we think merchants actually need: visible to customers, explainable to operators, and quiet when it is not enabled.