Allamah Access
A subscription library for Islamic homeschool resources
A WordPress membership platform selling monthly and yearly access to a library of over a thousand downloadable teaching resources, with separate plan structures for individual families and for schools.

What this system is
An education publisher needed to sell recurring access to a growing library of downloadable resources rather than sell each resource individually. The platform handles the whole path from choosing a plan to paying, to downloading, with the entitlement and the download allowance derived from the plan rather than managed by hand.
- Category
- Membership platform
- Technologies
- WordPressWooCommerceMembershipsSubscriptionsStripeCustom theme
- Client
- Available on request
- Live
- Visit site
What was actually wrong
- Two different customer types — individual families and schools — need different plan structures on the same platform, without turning the pricing page into a wall of options.
- A monthly plan sells an allowance rather than unlimited access, so the number of downloads a member has used has to be tracked and enforced, not just whether they are a member.
- Recurring billing has to fail gracefully: a lapsed payment should end access cleanly, and a cancellation should keep access until the paid period actually ends.
- The library keeps growing, so a yearly member has to receive resources added after they joined without anyone re-issuing their entitlement.
How it was solved
- A custom theme built for the platform rather than a configured off-the-shelf template, so the plan comparison and the member area present the offer directly.
- Plans modelled as WooCommerce products with membership and subscription behaviour attached, keeping billing, renewal and cancellation on well-tested infrastructure.
- Custom logic layered on top for the parts the stock plugins do not cover — chiefly the download allowance on the monthly plan and how it resets.
- A Single and Schools split on the pricing page, so each audience sees only the plans that apply to it.
- Entitlement checked against the library at access time, so newly published resources are available to existing members with no migration step.
- Stripe handling payment and recurring collection, with email marketing wired in so member communication is not a manual export.
How the system is put together
The parts, and why each one is there.
- 01WordPress with a purpose-built theme for the member-facing interface.
- 02WooCommerce as the commerce layer, with Memberships and Subscriptions for entitlement and recurring billing.
- 03Stripe as the payment gateway for both one-off yearly and recurring monthly collection.
- 04Custom PHP for the platform-specific rules that sit above the plugin layer.
- 05Scheduled tasks for the periodic work — allowance resets and access changes on renewal or lapse.
What it does
The functionality that carries the system, described from the user's point of view.
Monthly and yearly plans
Monthly access with a download allowance, or yearly access without one, priced so the yearly plan is the obvious choice for committed members.
Single and Schools tiers
Two audiences with different needs served from one platform, split at the point where the visitor chooses a plan.
Metered downloads
The monthly plan carries a per-month download allowance that is counted and enforced, rather than an honour system.
Recurring billing
Subscription collection through Stripe, with cancellation leaving access intact until the end of the period already paid for.
Growing library access
Members reach resources published after they joined without their entitlement being reissued.
Multi-device access
Membership follows the account rather than a device, so a family can use it wherever they teach.
Stack
Platform
- WordPress
- WooCommerce
- WooCommerce Memberships
- WooCommerce Subscriptions
Language
- PHP
- JavaScript
Payments
- Stripe
Frontend
- Custom theme
- Elementor
Data
- MySQL
Development highlights
Billing, renewal and dunning stay on maintained plugins; only the genuinely product-specific rules are custom, which keeps the update path safe.
The download allowance is enforced server-side at the point of download, not merely hidden in the interface.
Cancellation is treated as end-of-period rather than immediate, because revoking access someone has already paid for generates support tickets and refunds.
Entitlement is evaluated against the current library, so publishing a new resource is a content action rather than an engineering one.
Where it ended up
Described in terms of what the system now does. No invented metrics.
Access is sold as a subscription and granted automatically, instead of resources being distributed individually.
Families and schools are served by one platform with plans that suit each, rather than a single compromise offer.
Adding to the library reaches existing members immediately, so publishing is decoupled from entitlement management.
Building something like this?
Tell me where your situation is similar and where it differs. The differences are usually where the real work is.
Typical first reply within one business day · Lahore, PKT (UTC+5)