ERPLI
A white-label chess LMS should be evaluated screen by screen and workflow by workflow. Your logo on a sign-in page is only one part of the purchase. Academy and franchise owners also need to establish how domains, emails, curriculum, staff access, records and support work under their business arrangement.
This guide is for founders, multi-centre operators and franchise decision-makers planning a branded teaching platform. ERPLI publishes it and sells Chess LMS. The checklist is designed to make a purchase review concrete; it is not a claim that every capability discussed is included in ERPLI or any other supplier's current plan.
Cover image: original AI-generated editorial illustration, not a customer photograph or an ERPLI interface screenshot.
Define what “white label” means in the quote
Write a list of the places families and staff will encounter the product: sign-in, lesson room, homework, reports, invitations, transactional emails and support links. Ask the vendor to show each one. Mark where vendor identification remains, what can be configured and what requires a different plan or custom work.
The ChessCore white-label documentation illustrates why this inspection matters: its current page distinguishes supported branding surfaces from partially implemented features. Product descriptions can change. Check the actual plan and live demonstration at the time you buy instead of relying on an older comparison or a general claim of complete branding.
For ERPLI's documented offering, review the white-label and custom-domain page, then request the same branded journey in a demo. Confirm scope in writing. A buyer should be able to distinguish an available setting from a proposed customisation without interpreting a mockup as a delivered feature.
Separate a domain, a web app and an app-store listing
An academy website at its own address, an installable web experience and a branded native app are different deliverables. Ask exactly what families install, where updates are delivered and who controls any store account. Do not assume that “your own app” includes publication in both major stores.
Record who registers and renews the domain and who controls DNS. If the academy already owns its address, ask what must change and how existing email or website services are protected during setup. Define responsibility for certificate renewal, domain changes and support when a record is configured incorrectly. These are implementation questions, not reasons to buy a domain through an unfamiliar process during the first sales call.
Inspect the emails as well as the dashboard
Send a sample invitation, password-reset message and available progress notification to a test inbox. Inspect the sender name, reply address, logo and links. A branded dashboard does not establish that a family's first email will carry the same identity. Ask who receives replies and handles delivery problems.
If the product uses the academy's email service, confirm setup responsibilities and any separate charges. Use the supplier's documented configuration process rather than handing over unrestricted mailbox access. Keep ownership of the business's communication channels clear so staff changes or a later vendor migration do not disrupt family contact.
Test the franchise structure, not just multiple logos
Create an illustrative demonstration with head office, two branches and a coach assigned to one branch. Ask which records each role can view or change. Check whether one branch can access another's roster, whether head office can review the information it needs and whether a coach's access can be removed promptly.
This is a procurement test, not an assertion that ERPLI already provides every franchise permission. The coach-management page describes batch delegation and role-based access. Institution-level separation, branch consolidation and partner-school arrangements need explicit confirmation for your deployment. Multiple coach accounts alone do not prove a franchise management model.
Keep curriculum ownership and control explicit
Ask who owns the teaching material you upload and which permissions apply to staff. Establish who can change a shared lesson, whether branches can add local material and how an update is communicated. A standard curriculum is useful only when the responsible trainers understand how revisions reach their batches.
Bring one academy lesson and one homework set to the demonstration. Use sample material you have the right to share. Ask how a head trainer would update the lesson and what an existing learner would see. The ERPLI level-curriculum page explains its teaching structure; confirm any content-control requirements that matter to your business.
Build the implementation plan around one branch first
Choose a small representative group rather than the easiest possible demonstration account. Include one administrator, a regular coach and a substitute. Test invitations, lesson access, homework and the available reporting process. Record what staff can repeat independently and which tasks still need vendor support.
Only expand when the outstanding requirements have an owner and an agreed resolution. A launch date should include staff training, data preparation and a way to help families who cannot log in. Do not let the appeal of a branded portal obscure the basic question: can your team run next week's classes through it?
Ask for a total implementation quote
| Cost or commitment | Question for the supplier |
|---|---|
| Subscription | Which learners, coaches, branches and features are covered? |
| Branding | Which screens, emails and reports are included? |
| Domain setup | Who handles DNS, certificates and future changes? |
| Content migration | Which formats and how much assistance are included? |
| Additional delivery | Is an installable web experience or store app included? |
| Support | What channels, hours and response commitments are written down? |
| Exit | Which records and files can be exported, and with what assistance? |
Use the same scenario with each vendor and ask for optional services separately. Avoid treating an introductory monthly figure as the full cost of a franchise rollout. If the number of branches or users changes, request the revised quote rather than extrapolating a plan that may have different limits.
Make ownership and export claims demonstrable
“Your data belongs to you” should lead to practical questions. Ask which learner records, lesson files, attendance information and available progress data can be downloaded, in which formats and by whom. Request a sample export using test data. Establish what is retained or removed when the contract ends through the supplier's written terms.
Not every platform stores the same records, and export functionality may differ by record type. This guide does not claim an ERPLI export feature that has not been demonstrated for the required workflow. Put essential migration and exit requirements into the evaluation rather than discovering them after your academy depends on the system.
Test service continuity before switching everything
Ask what staff should do if a lesson room is unavailable or an integration stops working. Identify how you will contact support and where status information is published. Keep a lesson fallback that teachers understand. These are ordinary operating requirements for a business delivering scheduled classes.
Also ask about backups and restoration in concrete terms: what is backed up, how frequently, who initiates recovery and what the written service commitment covers. Do not equate a statement about cloud hosting with a demonstrated recovery process. Your purchasing decision should distinguish technical descriptions, contractual commitments and anything the vendor has actually shown.
Keep the buyer comparison grounded
Lichess Class provides a documented free classroom toolset, while GreyChess's academy page describes broader academy workflows. Neither description alone answers whether a particular branded franchise arrangement is supported. Compare the job you need done rather than assuming that a chess teaching tool and a multi-branch platform are interchangeable.
If your immediate problem is one coach's homework review, begin with the chess coaching software checklist. If you sell programmes into schools, also use the school software evaluation guide. Let the operating requirement determine the purchase scope.
Bring a questionnaire to the demo
Download the white-label chess LMS vendor questionnaire. For each item, record demonstrated, confirmed in writing, planned or unavailable. Ask a responsible person from your academy to approve the critical items before rollout. Avoid converting an unanswered question into an assumed capability.
For an ERPLI discussion, start with the academy solution and provide the branch structure, branding requirements and lesson workflow you want to test. A good demonstration should leave you with clear scope, a practical pilot and a written quote that your team can review.
