Store Wallet & Store Credit for Odoo

ECOSIRE builds a dedicated wallet layer on top of Odoo's own accounting and eCommerce plumbing. At the core is a store.wallet model (one balance per res.partner, company_id-scoped for multi-company) plus a store.wallet.transaction ledger where the running balance is a stored compute field driven by @api.depends over every credit and debit line, so the figure on screen and the figure in the database can never drift. Top-ups run through Odoo's existing payment.provider / payment.transaction flow (Stripe, PayPal, bank transfer — whatever you already accept); on a confirmed transaction a server action posts a top_up ledger row. Optionally each wallet is backed by a dedicated account.account liability so your accountant sees outstanding credit as a real balance-sheet number rather than a spreadsheet guess.

At checkout — both the website sale.order and the POS pos.order — we add a "Pay from wallet" option that debits the balance and can be combined with card or cash for partial payment, so a customer with 40 in credit can spend it against a 100 order and pay the rest normally. Refunds are the headline feature: from an order or a credit note, staff (or an automated rule) issue an instant refund credit that lands in the wallet in seconds instead of days. Cashback and loyalty rules are configurable records — percentage or fixed, per product category, per customer group, or per campaign window — evaluated by an @api.depends-aware engine and posted as cashback ledger rows on order confirmation. Every movement is exposed in the customer's /my portal via a QWeb-rendered statement, and the same balances are reachable over the XML-RPC / JSON-RPC API so a POS terminal, mobile app, or marketplace connector can read and debit the wallet programmatically.

Because this is build-to-order, nothing ships until we agree on scope. A short scoping call establishes your edition (Community vs Enterprise — it changes how we hook eCommerce and POS), your target versions (17.0 / 18.0 / 19.0), and the exact top-up, refund and cashback rules for your business. We then build the module against your data on a staging instance, secure it with ir.model.access.csv and record rules so customers only ever see their own wallet, run UAT with you, and deploy behind a rollback plan. Typical delivery is 2–4 weeks from confirmed scope, and you receive the full source and git repository at handover.