Gift Cards & E-Vouchers at Checkout for Odoo

Key Features

`gift.card` model with compute-tracked `balance_amount` via `@api.depends` over an immutable `gift.card.transaction` ledger — no mutable balance field to drift

Server-side code generation with configurable prefix/format, uniqueness constraint, and collision retry; optional hashed storage of card codes

Partial redemption at checkout: apply part of a balance to an order and carry the remainder, with a DB-level guard so a card never goes negative under concurrent redemptions

Website eCommerce checkout hook via a controller that validates, reserves, and applies card balance during the `sale.order` payment step

POS integration so cashiers can scan/enter a card, see live balance, and split payment between card and other tender

Digital and physical card support — batch/bulk generation for physical stock plus instant digital issuance

`ir.cron` automated actions for expiry enforcement, activation windows, and scheduled future-dated delivery

Branded QWeb email and PDF templates with your logo, terms, and a QR/barcode rendered per card

Record-rule + `ir.model.access.csv` security matrix: cashier can redeem, manager can mint/void/adjust, finance can view liability

Full audit trail — every issue, redeem, refund, and adjustment is a ledger row with user, timestamp, and related order

`account`-side reconciliation so outstanding gift-card liability posts to a control account and is visible in finance reports

XML-RPC/JSON-RPC endpoints to issue cards, check balances, and post redemptions from external POS, kiosks, or marketing tools

Balance-lookup portal page and a `GET` balance check for recipients without exposing the full ledger

Multi-currency and multi-company aware; expiry/refund behavior configurable per company, built for your Odoo 17.0/18.0/19.0 edition

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Retailers leave real money on the table when their store can't sell gift cards properly. Odoo Enterprise ships a loyalty-based gift card feature, but it runs out of road fast for a serious gift-card program: codes are simple, there is no branded email delivery with your own QWeb design, scheduled/future-dated delivery isn't supported, physical card fulfillment and batch generation are missing, and balance reporting is thin. On Community edition you often have nothing at all. The result is manual spreadsheets, ad-hoc coupon abuse, and a checkout that can't cleanly apply a partial balance across an order.

We build a dedicated gift-card and e-voucher engine as a proper Odoo module. At its core is a gift.card model (extending or replacing the native card where it exists) with a compute-tracked balance_amount derived from an immutable gift.card.transaction ledger via @api.depends, so every issue, redemption, refund, and expiry adjustment is auditable rather than a mutable number. Codes are generated server-side with a configurable prefix/format and collision checks, stored hashed where you need PCI-adjacent hygiene, and validated through a controller that hooks the website sale checkout and the POS payment flow. Partial redemption is first-class: a customer can apply part of a card to one order and carry the remainder forward, with the ledger enforcing that a card can never go negative even under concurrent checkout attempts.

The build wires into the parts of Odoo your team already uses. Access is locked down with ir.model.access.csv plus record rules so cashiers can redeem but not mint cards, and only managers can adjust balances or void codes. Expiry, activation windows, and scheduled future delivery are enforced by ir.cron automated actions that flip states and fire notifications. Branded delivery is a QWeb email/PDF template you control — your logo, terms, and the code (or a scannable barcode/QR) — sent on purchase or on the recipient's chosen date. Everything is exposed over Odoo's XML-RPC/JSON-RPC API so an external POS, kiosk, or marketing tool can issue and check balances programmatically. We target your exact edition and version (17.0, 18.0, or 19.0) and reconcile with account so outstanding gift-card liability is visible to finance, not just to sales.

Because this is build-to-order, nothing is a stock download you self-install and hope fits. It starts with a short scoping call where we pin down your edition, POS vs eCommerce vs both, code format, expiry policy, and email design. We then build against a staging copy of your database, run UAT with you, and hand over installable source, documentation, and a git repository. Typical delivery is 2 to 4 weeks from confirmed scope, and we support the module after go-live.

What you get

Installable module source code targeted at your exact Odoo edition and version (17.0, 18.0, or 19.0)

Installation and configuration on your staging instance, including code-format, expiry, and email-design setup

Technical documentation: model/field reference, security matrix, cron jobs, and XML-RPC/JSON-RPC endpoint specs

User guide plus a live training session for cashiers, managers, and finance

UAT sign-off on a staging copy of your database, with a documented rollback plan before production cutover

Post-go-live support window for defect fixes and configuration adjustments

Git repository handover with full commit history so your team or any developer can maintain it

Branded QWeb email/PDF card templates configured to your brand assets and terms

Who this is for

Multi-store retailer

Runs Odoo POS across several outlets and wants gift cards that work identically at every till, split-tender at checkout, and roll unused balance forward. Needs one code to redeem partially across multiple visits without spreadsheets.

eCommerce merchant

Sells on Odoo website and wants digital gift cards as a revenue line — instant branded email delivery, scheduled gifting for holidays, and clean partial-balance application in the online checkout.

Finance / controller

Needs outstanding gift-card value posted as a liability to a control account, reconciled against redemptions, and reportable — not a hidden number living in the sales team's heads.

Marketing manager

Wants promo e-vouchers with expiry and activation windows for campaigns, issued in bulk via the API and tracked so redemption rates are measurable.

How Gift Cards & E-Vouchers at Checkout for Odoo Compares

Criterion	ECOSIRE	Custom Build	Competitor
Partial redemption at checkout	First-class; ledger-backed, carries remainder forward, guarded against negative balance	Possible but you design the ledger logic and concurrency guards yourself	Often coupon-style; partial handling varies and can be brittle
Branded email delivery	Custom QWeb template with your logo, terms, and QR/barcode	Whatever you build and maintain	Usually a fixed template with little control
Scheduled / future-dated gifting	Yes, via `ir.cron` on the recipient's chosen date	Buildable, needs cron plus state logic you own	Rarely supported
Physical card fulfillment	Batch/bulk generation for physical stock included	Custom effort per your workflow	Frequently digital-only
Finance liability reconciliation	Posts outstanding value to a control account, reconciled to redemptions	You wire the `account` integration	Usually absent
External API access	Documented XML-RPC/JSON-RPC issue/check/redeem endpoints	Depends on what you expose	Often closed to the module UI
Security & audit	Record rules, access CSV, append-only ledger, per-user audit trail	Your responsibility to design and test	Varies; often coarse permissions
Support & handover	Post-go-live support, training, docs, git repo handover	In-house or contractor dependent	Vendor ticket queue, no source control

Frequently Asked Questions about Gift Cards & E-Vouchers at Checkout for Odoo

How long until it's live?

This is build-to-order, not an instant download. After a short scoping call to confirm your edition, channels (POS/eCommerce/both), code format, expiry policy, and email design, typical delivery is 2 to 4 weeks from confirmed scope. We build against a staging copy of your database and only cut over to production after your UAT sign-off.

How does support and updates work after go-live?

Every build includes a post-go-live support window for defect fixes and configuration adjustments. You also receive the full git repository, so your own team or any Odoo developer can maintain and extend it. When you upgrade Odoo (e.g. 18 to 19) we can quote a version-migration pass to keep the module compatible.

Isn't there already a gift card feature in Odoo?

Odoo Enterprise has a basic `loyalty`-backed gift card. It lacks branded QWeb email delivery, scheduled/future-dated gifting, physical-card batch generation, robust partial-redemption ledgering, and finance-grade liability reconciliation. Community often has nothing usable. We build the pieces your program actually needs rather than fight the limits of the stock feature.

Does it work with POS as well as the website?

Yes. We can hook the website eCommerce checkout, the POS payment flow, or both — you tell us at scoping. In POS the cashier scans or enters a card, sees the live balance, and splits payment between the card and other tender; online the balance is applied during the `sale.order` payment step.

Can other systems issue or check cards?

Yes. The module exposes Odoo's XML-RPC/JSON-RPC API so an external POS, kiosk, or marketing platform can issue cards, check balances, and post redemptions. We document the endpoints in the technical handover.

How do you keep balances accurate and prevent fraud?

Balance is a computed field derived from an append-only `gift.card.transaction` ledger, so it can't silently drift, and a database-level guard prevents a card going negative under concurrent redemptions. Access is locked down with record rules and `ir.model.access.csv` — cashiers redeem, only managers mint or void, and every action is an auditable ledger row.

Which Odoo versions and editions do you support?

We build for Odoo 17.0, 18.0, and 19.0, on Community or Enterprise. We target your exact edition at scoping because the native gift-card baseline and available dependencies differ between them, and we tailor the build accordingly.