Coffee Kit / Coffeetale: loyalty evidence addendum

Checked 12 November 2026. Public official documentation and pricing only; capabilities below are documented vendor claims, not integration tests. Recommendations and engineering requirements are explicitly identified. This supplements the existing competition study; product design remains with the parent agent.

Recommendation. Make loyalty a first-class coffee experience. Start provider-backed with Appstle Starter ($10/month) for points and POS, or Business ($30/month) for a free-bag reward. Its documented quantity earning is particularly relevant. However, these prices establish an affordable provider popup/page route, not unrestricted access for a bespoke Coffeetale balance and redemption card. Appstle offers an API/webhook add-on on any plan, but its public price is undisclosed. Custom UI is therefore a conditional option, not a validated inexpensive integration. Appstle listing, vendor pricing, API row tooltip.

Plan and UI gates — USD, observed on the date above. Provider subscriptions are additional merchant costs; Coffee Kit installation does not confer their API entitlements.

Rivo's own pricing page differs from its App Store listing on Scale's included order band and trial, and lists three POS locations on Scale versus unlimited on Plus. Treat Essential's location allowance and actual billed volume thresholds as unresolved, not interchangeable entitlements. Rivo pricing.

What “earn a stamp for every bag” actually means. Points are a general balance; stamps represent qualifying purchase units. Rendering arbitrary spend, signup and referral points as bags would misstate progress. Proposed narrow rule: one eligible bag equals one stamp; six stamps redeem one specified reward, with carryover and reward issuance defined separately. Per-order earning gives the same award for one bag and three bags; per-bag earning must count eligible line quantities. Define multipacks, bag sizes, bundles and excluded merchandise before promising equivalence.

Appstle explicitly supports points per item, product/variant exclusions, channel selection and subscription orders including renewals. Its quantity rule can stack with purchase earning. Critically, it lacks the purchase rule's sale/discount switches: a fully discounted item still earns. Excluding a dedicated reward SKU is a possible design, but excluding that SKU also excludes paid purchases of it. A free bag using the ordinary sale SKU needs a demonstrated eligibility solution. Quantity earning.

Rivo's standard order rule supports fixed points per order or spend-based increments. Product-purchase bonuses also exist; these sources do not establish a repeatable, quantity-based six-bag stamp cycle. Do not infer that capability from a product-count VIP tier. Smile's exact per-bag rule is likewise unresolved here. Rivo order rule, points program.

Subscriptions: earning and spending have different gates. Appstle documents initial and recurring order earning, including other providers using native Shopify subscriptions and Shopify billing. Its app embed must be enabled; overlapping legacy subscription and purchase rules require inspection. This establishes renewal earning, not automatic reward insertion into a future subscription. Subscription earning.

Rivo specifically claims Skio renewal earning and automatically adding redeemed free-product rewards to the next Skio order. That is provider-specific evidence, not a guarantee for every subscription app or cheap plan. Smile advertises subscription rewards from Standard, but contract eligibility and renewal redemption behavior remain unverified. Rivo–Skio, Smile plans. Initially support one confirmed subscription combination; exclude failed, skipped or unpaid renewals from any proposed paid-bag promise.

Refunds, partial returns and double benefits. Treat reversing earned points, returning spent points, and cancelling an issued reward as separate events. Proposed policy: reverse only refunded eligible bag quantities; handle already-spent earnings through a recorded deficit or review, never silently mint replacement rewards.

Appstle's purchase rule requires its refund clawback setting enabled; pending points are cancelled, and merchants must refund line items rather than only a monetary amount for accurate deductions. Exact quantity-rule partial-return behavior and redeemed-code invalidation remain test gates. Purchase/refund rules.

Rivo documents proportional partial-refund adjustments, separately configurable restoration of redeemed points, and possible negative balances. Cancellation needs a qualifying financial-state update. Its automatic reversal applies to the standard order rule, not custom Shopify Flow earning rules. Exchanges with additional payment do not automatically earn extra points. Rivo refund behavior.

For either route, explicitly decide whether subscription discounts and loyalty earnings coexist; prevent overlapping quantity/order/subscription rules from accidentally awarding twice. Do not restore points while leaving an equivalent reusable reward outstanding. Appstle says already-issued codes remain valid when a reward is paused, so pausing is not revocation. Reward lifecycle.

Customer identity and POS. Proposed integration identity is shop plus Shopify customer ID, mapped to provider identity; email alone is insufficient for reconciliation. Attach the customer to POS sales and account for guest enrollment and duplicate profiles. Appstle has a documented loyalty-data merge operation, separate from Shopify's orders/address merge. Automatic synchronization of Shopify merges, outstanding rewards and duplicate bonuses is unresolved across these providers. Appstle merge operation.

Smile explicitly supports POS Lite and Pro on all plans, with one online/in-store balance and amount/percentage rewards. Appstle documents a POS tile and Starter entitlement; Rivo documents POS on eligible paid plans, with fixed-amount/percentage POS rewards. Their inspected docs do not explicitly resolve Lite versus Pro. Do not add a Pro requirement by assumption, or promise feature parity. Smile POS, Appstle POS setup, Rivo POS.

Appstle warns that manual loyalty opt-in cannot be completed through POS. Rivo requires a customer attached to the cart and eligible rewards; points earned during that checkout become usable on a later purchase. Free-product redemption at POS must be verified independently of online support. Appstle enrollment, Rivo POS.

Redemption and discount combinations. A reward code is not cash. Shopify requires both discounts to permit the relevant combination classes; incompatible offers can produce a different best discount. Product-plus-order discounts are possible; multiple product discounts on the same item require Shopify Plus under current documented rules. Buy-X-get-Y has additional exclusions. Online checkout, subscription contracts and POS therefore need separate eligibility assertions. Shopify combination rules.

Native Shopify store credit is a reward instrument. It supplies a monetary balance and payment redemption, not coffee purchase qualification, stamp cycles or reversal rules. Customers need new customer accounts or Shop Pay; POS requires payment enablement and staff permissions. Credit can fund the initial subscription purchase, not recurring subscription bills. Currency restrictions apply, customers cannot choose an arbitrary partial credit amount, and Shopify documents transaction fees for credit-paid amounts on stores created on/after May 12, 2025. Include those costs in comparisons. Shopify store credit.

Own narrow ledger is a fair long-term option — engineering assessment. A single program, eligible paid-bag quantities, one reward and explicit channels could justify ownership: exact coffee semantics, custom UI, predictable economics and no premium API dependency. It need not recreate VIP tiers, referrals or a general loyalty platform. Shopify discounts or store credit could deliver its rewards.

Ownership still means durable earn/reverse/redeem records; duplicate-event protection; refund allocation; concurrent redemption protection; customer-merge reconciliation; reward invalidation; staff adjustments; and an auditable history. POS earning from completed orders and an interactive POS redemption experience are separate deliverables. A mutable customer metafield alone is insufficient. For three people, begin with one channel and subscription combination, then expand after measured demand and support effort justify it.

Decision and handoff. Prefer Appstle's affordable provider UI initially. A custom explanatory coffee card can link to that experience; a live balance/redemption card needs confirmed add-on pricing, endpoints and authentication. The public JavaScript event hooks alone do not establish that entitlement. Appstle JavaScript documentation. Rivo/Smile custom routes fit merchants already paying the required plans better than a new $99 Coffee Kit purchase. Keep the website reward card explicitly demonstrative until connected. Neither these prices nor vendor capabilities validate merchant willingness to pay for Coffee Kit loyalty. No implementation, merchant changes or outreach performed.

Source: loyalty-evidence.md The complete Markdown handoff and private datasets remain in the local project. This web edition includes selected supporting visuals and scenario downloads.