Referral 'Refer & Earn' Program

Name: Referral 'Refer & Earn' Program
Brand: ECOSIRE
SKU: referral-refer-and-earn

اہم خصوصیات

Unique, collision-safe referral code per customer, generated on a dedicated referral.code model and surfaced in the customer portal and website account page

Dual-sided rewards: independently configurable payouts for the referrer and the referee (credit, coupon, or points) so you can run 'give X, get Y' campaigns

Wallet credit engine — a per-partner balance that increments automatically via an Odoo automated action when the referred sale.order reaches a qualifying state (paid/delivered/confirmed)

Native coupon rewards issued through Odoo's loyalty.card / gift-card mechanics, redeemable at website and POS checkout with real discount enforcement

Points-based rewards option with configurable point-to-currency conversion and redemption thresholds

Configurable reward rules with no code: minimum order value, first-order-only, reward caps per referrer, cooldown windows, and reward expiry dates driven from a Settings screen

Referral leaderboard and analytics dashboard (top advocates, conversions, pending vs. paid rewards) built on Odoo list/pivot/graph views

Full attribution ledger — every referral, redemption, and reward links back to the source referral.code, the referee, and the originating sale.order on a referral.reward model

Automatic fraud guards: self-referral blocking, duplicate-account heuristics, and reward-only-on-qualified-purchase logic to protect margins

Branded referral emails and shareable links generated via QWeb templates, with one-click social/WhatsApp/email sharing from the portal

Reward statement QWeb PDF/report so customers (and finance) can see earned, redeemed, and expiring balances

XML-RPC / JSON-RPC endpoints to register referrals and read wallet balances from an external storefront, mobile app, or marketing-automation tool

Access control via ir.model.access.csv plus record rules — customers see only their own referrals and balances; marketing gets back-office control

Compatible with Odoo 17, 18 and 19 on both Community and Enterprise editions, with the reward mechanism matched to your edition's available modules

آرڈر پر تیار، مکمل طور پر آپ کے لیے

خود سیٹ اپ کی ضرورت نہیں — ایک کام کرنے والی ایپ جو ECOSIRE بناتا، انسٹال اور سپورٹ کرتا ہے۔

آپ آرڈر دیتے ہیں

ایک بار کی تعمیر کی قیمت سے آغاز کریں۔ آغاز پر ہم آپ کے ساتھ مل کر دائرہ کار طے کرتے ہیں۔

ہم بناتے اور انسٹال کرتے ہیں

ECOSIRE اسے آپ کے Odoo پر بناتا، ترتیب دیتا اور انسٹال کرتا ہے۔

لائیو + معاونت

آپ تقریباً 2–4 ہفتوں میں لائیو ہو جاتے ہیں، لانچ کے بعد معاونت کی مدت کے ساتھ۔

اس مصنوع کے بارے میں

Turn your happiest customers into a repeatable acquisition channel — inside the Odoo system you already run. This is a build-to-order referral engine that ECOSIRE designs, develops, installs and supports specifically for your business; it is not an instant apps.odoo.com download. After purchase we scope your reward rules, build the module against your Odoo 17, 18 or 19 database (Community or Enterprise), and hand you a clean, maintainable app in 2–4 weeks.

Every customer gets a unique referral code minted on a dedicated referral.code model, exposed through their portal account and the website via QWeb templates. When a friend redeems that code and completes a qualifying purchase, the module fires an Odoo automated action / server action that credits rewards to both sides — a wallet balance, an auto-generated loyalty.card/coupon, or points — with the full attribution chain recorded on sale.order and a referral.reward ledger.

Because it is native Odoo, the whole program lives where your data already is. Reward logic is expressed as ORM computed fields (@api.depends) so wallet balances and reward eligibility recompute automatically. Access is locked down with ir.model.access.csv plus record rules so customers only ever see their own referrals, while your marketing team gets a back-office dashboard, a leaderboard, and configurable rules from a Settings screen — no code required to tune reward amounts, minimum order value, expiry windows, or per-customer caps.

ECOSIRE grounds the build in real Odoo engineering: a proper __manifest__.py with pinned dependencies (base, sale, portal, website_sale, and loyalty/gift_card where relevant), models under models/, XML + OWL views, QWeb PDF/email reports for reward statements, and JSON-RPC/XML-RPC endpoints so your storefront, mobile app, or marketing automation can read balances and register referrals. You own the code outright, it upgrades cleanly, and we back it with a post-launch support window.

What you get

Complete, production-ready Odoo module source code (models, views, security, data files) with a documented __manifest__.py, delivered in a Git repository you own outright

Installation and configuration on your target Odoo 17/18/19 database (staging first, then production), including dependency wiring and initial reward-rule setup

Data model and security layer: referral.code, referral.reward and wallet models with ir.model.access.csv and record rules scoped to portal customers

Configured reward rules and campaign settings tailored to your scoping call (reward amounts, qualifying conditions, caps, expiry)

Branded portal and website referral UI plus QWeb email/PDF templates matched to your theme

Admin and end-user documentation, including a runbook for creating campaigns and reading the leaderboard

A live training/handover session for your marketing and support teams (recorded on request)

Post-launch support and bug-fix window (typically 30 days) with clear terms for updates and Odoo version compatibility

Who this is for

eCommerce growth marketer

Runs an Odoo website_sale storefront and wants a self-serve referral loop that turns existing buyers into new-customer acquisition without paying per-click ad costs — with a leaderboard and rule controls they can tune themselves.

Subscription / recurring-revenue operator

Sells plans or memberships and needs referrals that only pay out on a qualified, retained purchase, with wallet credit that flows straight into the next invoice — all attributed cleanly inside Odoo.

Odoo administrator / operations lead

Owns the Odoo instance and cares about a clean, upgrade-safe module: proper manifest, ORM computed fields, record-rule security, and an API so the referral data isn't trapped in a black-box third-party app.

How Referral 'Refer & Earn' Program Compares

Criterion	ECOSIRE	Custom Build	Competitor
Time to a working referral program	2–4 week build-to-order, tested on staging then deployed	Months of in-house dev, testing and iteration	Instant install, but generic and often unmaintained
Dual-sided rewards (referrer + referee)	Fully configurable per side: credit, coupon, or points	Possible but you design and build it all yourself	Partial — often single-sided or fixed reward types
Reward rules (caps, expiry, min-order, cooldown)	No-code Settings screen tuned to your campaigns	Whatever you find time to build	Limited to the app author's fixed options
Native Odoo integration (ORM, record rules, wallet, loyalty)	Deep — models, @api.depends computes, ir.model.access.csv, loyalty.card	Depends entirely on your team's Odoo expertise	Varies; many bolt on shallow or bypass core models
API access (XML-RPC / JSON-RPC) for external storefronts	Included endpoints to register referrals and read balances	Only if you build and document it	Rarely exposed or documented
Code ownership and upgrade path	You own the source; clean upgrades across Odoo 17/18/19	You own it, at full build cost and risk	Vendor-controlled; upgrades depend on the author
Support and post-launch fixes	Included support window + optional migration retainer	You maintain it forever	Best-effort marketplace support, often slow

Frequently Asked Questions about Referral 'Refer & Earn' Program

How long until the referral program is live — is this an instant download?

No, this is a build-to-order module, not an instant apps.odoo.com download. After purchase we run a short scoping call to confirm your reward rules and Odoo version, then build, test on staging, and deploy to production — typically within 2–4 weeks depending on customization depth. You'll see a working build on staging before it touches your live database.

What support and updates do I get after launch?

Every build includes a post-launch support window (typically 30 days) covering bug fixes and adjustments to the delivered scope. Because you receive the full source code in a repo you own, the module upgrades cleanly across Odoo point releases; we also offer optional ongoing support and version-migration retainers for Odoo 17→18→19 upgrades.

Does it work with my Odoo version and edition?

Yes — we build against Odoo 17, 18 or 19, on either Community or Enterprise. The reward mechanism is matched to what your edition ships: wallet credit and portal referral logic work everywhere, while coupon/gift-card rewards use Odoo's loyalty modules where available. We confirm the exact dependency set in your __manifest__.py during scoping.

How are rewards actually paid out and protected from abuse?

Rewards fire only when a referred sale.order reaches a qualifying state you define (for example paid or delivered), enforced by an Odoo automated/server action rather than at signup. Built-in guards block self-referrals, cap rewards per referrer, and apply cooldown and expiry windows — all configurable from a Settings screen so you protect margin while staying flexible.

Can I connect the referral data to my storefront or other tools?

Yes. The module exposes XML-RPC/JSON-RPC endpoints to register referrals and read wallet balances, so a headless storefront, mobile app, or marketing-automation platform can plug in. Every referral and reward is also queryable through standard Odoo list/pivot/graph views and stored on dedicated models, so nothing is locked away.

Can we run different reward types and campaigns over time?

Absolutely. Reward type (wallet credit, coupon, or points) and all rule parameters — minimum order value, first-order-only, per-customer caps, cooldowns, and expiry — are configured, not hard-coded. Your marketing team can adjust amounts and conditions from the back office without a developer, and we can extend the rule engine further as part of scope.