Square Loyalty Gap Analysis — Where Guild Builds
Square Loyalty: What It Does
Square’s built-in loyalty program (bundled into Square plans, 30-day free trial):
- Points accrual — by visit, amount spent, item, or category
- VIP tiers — customizable names/structure (new feature)
- Reward redemption — discounts (amount/percentage), free items, with optional caps
- Auto-enrollment at POS checkout
- Digital loyalty passes — Apple Wallet integration
- Bonus point promotions — limited-time or recurring
- Text notifications on point/reward events
- Built-in CRM — customer directory, activity tracking
- Marketing integration — email/text campaigns via Square Marketing
- Analytics — loyalty-attributed sales, avg spend comparison (loyalty vs non-loyalty)
Critical API Limitation
You cannot create or update a loyalty program via the Square Loyalty API. Program setup, accrual rules, and reward tiers must be configured manually in Square Dashboard. The API only manages accounts, points, and redemptions.
This means no third-party tool can programmatically set up or manage a Square Loyalty program — only interact with an existing one.
Transactional vs. Relational Memberships
Square Loyalty is a transactional points program: “buy 10, get 1 free.” It drives repeat purchases through discounts.
The Starbucks redesign (March 2026) moves toward relational: tiered status, exclusive experiences, personalized engagement, cross-brand partnerships. But it’s still fundamentally free — no recurring revenue for the business.
Two-Type Framework
Type A — Marketing/loyalty tool (margin negative):
- Barnes & Noble model: $99/year for 20% off
- Overall margin negative (-10% to -5% on membership margins)
- Goal: generate more sales volume to offset discount cost
- Only works at volume — most indie shops can’t sustain this
- Square Loyalty already covers the basic version
Type B — Memberships as profitability tool (margin positive):
- $25/mo for 20% off + perks (book-of-the-month, events, community)
- Directly profitable — recurring revenue the business keeps
- Only viable for small businesses with loyal local customer bases
- Especially valuable for bookstores (low-margin products, need alternative revenue)
Guild builds the all-in-one loyalty (A) + memberships (B) + subscriptions platform for indie shops.
The Gap — What Square Loyalty Lacks
| Capability | Square Loyalty | Starbucks | Guild |
|---|---|---|---|
| Points/rewards at POS | Yes | Yes | Build on Square’s |
| Tiered membership with recurring payment | No | No (free program) | Core product |
| Member events (book clubs, tastings, meetups) | No | Reserve-only trips | Core product |
| Community/social engagement | No | Minimal | Core product |
| Membership upsell at POS screen | No | No | Killer feature |
| Visit frequency tracking → insights | Basic CRM | App-based | Build on Square data |
| Recurring revenue for the store | No | No | The whole point |
| Self-serve program setup via API | No (dashboard only) | N/A | 30min onboarding |
| Member discount at register | No | No | Built and validated |
Strategic Position
Square Loyalty and Guild are complementary layers, not competitors.
- Square Loyalty = transactional. Earn points, get discounts. Every Square merchant can turn it on.
- Guild = relational. Become a member, get a monthly book box, come to member-only events, get your discount at the register. Recurring revenue for the store.
A bookstore cafe could run both:
- Square Loyalty for casual customers (earn points on coffee)
- Guild membership for committed regulars ($20/mo → book-of-the-month, member events, member pricing, early access to signings)
The POS upsell bridges the two: “You just spent 38. Want to join for $20/mo?” This screen doesn’t exist in Square Loyalty.
Why Square Won’t Build This
- API limitation is telling — they can’t even programmatically manage their own loyalty programs. A membership/community platform is not on their roadmap.
- Square is a payments company, not a memberships/community platform. Their incentive is transaction volume, not recurring membership revenue for merchants.
- The relational layer requires domain expertise — knowing how bookstores, game stores, and cafes actually run membership programs. Square builds horizontal tools, not vertical community features.
Competitive Moat
The moat isn’t the software — it’s the membership design expertise + vertical playbooks.
Most membership programs fail because of bad design (see starbucks-rewards-playbook — common failure modes: bad pricing, too hard to run, not enough marketing). The platform needs to encode best practices so a store owner can’t accidentally design a program that loses money.
See Also
- starbucks-rewards-playbook — Starbucks Rewards redesign details and stealable patterns
- guild-manifesto — the full Guild thesis
- square-loyalty-decision — why we own loyalty instead of delegating to Square