Template overrides
Every customer-facing surface renders through a template your theme can override, or carries a filter on its final HTML. Both, usually.
The guarantee
Elite Balance treats frontend customization as a contract: every customer-facing output either renders through a theme-overridable template, carries a documented filter on its final HTML, or both. There is no hardcoded frontend markup you cannot reach.
Overriding frontend templates
Copy any template from the plugin’s templates/ directory into your theme under rb-elite-balance/, keeping the relative path, and edit freely. Your copy wins.
| Template | Renders |
|---|---|
myaccount/wallet.php | The customer wallet page: summary, history, pagination. |
myaccount/topup-form.php | The top-up form. |
balance.php | The balance block and [rb_elite_balance] shortcode output. |
So the wallet page override lives at yourtheme/rb-elite-balance/myaccount/wallet.php.
Prefer hooks over full overrides when you only need to insert content: the wallet page exposes rb_elite_balance_account_wallet_after_summary, _before_history, and _after_history action points, and every template receives its data through the filterable rb_elite_balance_template_args.
Overriding email templates
The wallet emails follow WooCommerce’s standard email template system. Copy from the plugin’s templates/emails/ (HTML) and templates/emails/plain/ into your theme under woocommerce/emails/ and woocommerce/emails/plain/:
wallet-credited.phpwallet-debited.phpwallet-low-balance.php
Text-level changes rarely need an override at all: subject, heading, and the body text are editable on each email’s settings screen.
After plugin updates
Overridden templates are yours to maintain: after an update, compare your copies against the plugin’s originals for structural changes, exactly as you would with WooCommerce’s own templates. Templates carry version headers to make the comparison easy.
Stuck, or found a gap in these docs? Tell us and a human who works on the plugin answers.
Contact support →