A made-to-order Odoo Stock Card report that shows opening balance, every in/out move, and running closing balance per product, location, and date range. ECOSIRE builds, installs, and supports it after you request a quotation. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
App-Manifest
Auf Ihren Workflow zugeschnitten
A made-to-order Odoo Stock Card report that shows opening balance, every in/out move, and running closing balance per product, location, and date range. ECOSIRE builds, installs, and supports it after you request a quotation.
Keine Selbsteinrichtung — eine funktionierende App, die von ECOSIRE erstellt, installiert und betreut wird.
Starten Sie mit einem einmaligen Entwicklungspreis. Den Umfang legen wir beim Kickoff gemeinsam fest.
ECOSIRE erstellt, konfiguriert und installiert sie auf Ihrem Odoo.
Sie gehen in etwa 2–4 Wochen live, mit einem Support-Zeitraum nach dem Launch.
Warehouse and finance teams constantly need a single ledger-style view of how a product's on-hand quantity got to where it is: what it opened at for a period, every receipt and delivery that moved it, and where it closed. Odoo core gives you the stock.move and stock.move.line data and the on-hand/forecasted figures on the product form, plus the Inventory Report and Stock Report pivots — but none of them render as a classic stock card: an opening balance, a chronological in/out transaction list with a running balance, and a closing balance you can hand to an auditor or reconcile against your accounts. Teams end up exporting move lines to spreadsheets and rebuilding that running balance by hand, per product, every month-end. That is slow, error-prone, and impossible to audit consistently.
This is a build-to-order module that ECOSIRE designs, builds, installs, and supports for your specific Odoo database — it is not an existing download you install yourself. We build a dedicated stock card engine on top of Odoo's native inventory ledger. A transient wizard (a models.TransientModel) collects the report parameters — product or product variant, warehouse/location, date range, and optional lot/serial — and a computed query walks stock.move.line (with state = 'done') to derive the opening balance as of the start date, list each qualifying move with quantity in, quantity out, unit of measure, source/destination location, reference document, and a @api.depends-style running closing balance carried down the rows. The report respects the same location_id domain logic Odoo uses for on-hand quantities, so the numbers reconcile to the standard Inventory valuation rather than drifting from it.
Delivery is rendered as a QWeb PDF/HTML report and a filterable on-screen list/pivot view (XML views, OWL where interactivity helps), so users can drill from a card row into the underlying stock move. Access is scoped with ir.model.access.csv and, where you need warehouse-level separation, record rules so a branch only sees its own locations. We wire the report into the Inventory menu, expose it over the XML-RPC/JSON-RPC API if you want to pull cards into a BI tool or portal, and can add an automated action or scheduled export (email the month-end cards to finance) if that is in scope. Everything ships with a proper __manifest__.py, is version-pinned to your Odoo edition, and works on Community or Enterprise (Enterprise-only widgets are used only when you run Enterprise).
Because it is built to order, we start with a short scoping call to confirm your exact fields, filters, valuation basis, and multi-warehouse rules, then build against Odoo 17.0, 18.0, or 19.0 to match your database. Typical delivery is 2-4 weeks from confirmed scope, on a fixed quote agreed after scoping. Pricing starts from $249 (indicative, single-company base scope); multi-company consolidation, extra localization or valuation methods (FIFO/AVCO nuances, lot/serial-level cards), heavy historical data migration, or additional integrations increase the quoted scope. You receive the full installable source and git repository at handover — no lock-in.
Runs Odoo Inventory daily and needs a proper stock card per product — opening balance, every movement, closing balance — to answer 'why is on-hand this number?' without exporting move lines to a spreadsheet each time.
Reconciles inventory value to the general ledger at month-end and wants an auditable, ledger-style card that ties movements to closing quantities and standard valuation, ready to hand to internal or external auditors.
Needs traceable, chronological evidence of stock movements per product and location — including lot/serial where tracked — with drill-down to the source document, exported as PDF or XLSX for the audit file.
Oversees several branches or warehouses and needs per-location stock cards with record-rule isolation so each site sees only its own stock while head office gets the consolidated view.
| Kriterium | ECOSIRE | Benutzerdefinierter Build | Konkurrent | Odoo Native |
|---|---|---|---|---|
| Opening/closing balance card | Purpose-built ledger card with running balance | Possible but you build the balance logic from scratch | Generic card, may not fit your fields/filters | |
| Fit to your process | Scoped to your exact fields, filters, and warehouse rules | Fully bespoke if you have the developer time | Fixed feature set; you adapt to it | |
| Reconciles to Odoo valuation | Reuses native `location_id` domain, ties to on-hand | Depends on your implementation quality | Varies; often recomputes independently | |
| Multi-warehouse isolation | Record rules per branch plus consolidated view | You design and test the security model | Rarely includes record-rule isolation | |
| Install & configuration | We install on staging then production | Your team or contractor handles it | Self-install from the marketplace | |
| Support & warranty | Post-go-live support window plus source handover | Only what you arrange internally | Vendor ticket queue, variable SLA | |
| Version coverage | Built for 17.0/18.0/19.0, Community or Enterprise | Whatever you build and maintain | Depends on the listing's supported versions | |
| Ownership | Full source and git repo, no lock-in | You own it outright | Licensed, source may be obfuscated |
No. This is a build-to-order module. ECOSIRE builds it for your specific Odoo database, then installs, configures, and supports it. There is no instant download — you request a quotation and we build it to your confirmed scope.
Typical delivery is 2-4 weeks from confirmed scope. We start with a short scoping call, agree the exact fields, filters, and warehouse rules, then build, test on staging, and deploy. Complex multi-company or heavy data-migration scope can extend the timeline, which we state in the quote.
Pricing starts from $249 as an indicative from-price for single-company base scope. After a scoping call we give you a fixed quote. Drivers such as multi-company consolidation, lot/serial-level cards, extra valuation methods, historical data migration, or API/BI integrations increase the quoted scope.
Yes. The report is built on Odoo's native `stock.move.line` ledger and reuses the same `location_id` domain logic Odoo uses for on-hand quantities, so opening and closing balances reconcile to standard Inventory figures rather than drifting from them.
We build and version-pin to Odoo 17.0, 18.0, or 19.0 to match your database, on Community or Enterprise. Enterprise-only widgets are used only when you run Enterprise; the core stock card logic works on Community.
Every build includes a post-go-live support window for defect fixes and questions. Because you receive the full source and git repository, you can extend it yourself or engage us for version upgrades and enhancements later — there is no lock-in.
Yes, if it is in scope. We can expose the stock card over Odoo's `XML-RPC`/`JSON-RPC` API for BI tools or portals, and add an automated/scheduled action to email month-end cards to finance or drop CSV/XLSX exports for reconciliation.
A made-to-order Odoo Stock Card report that shows opening balance, every in/out move, and running closing balance per product, location, and date range. ECOSIRE builds, installs, and supports it after you request a quotation.