Scope 3 is hard to pull together
SB 253 requires disclosing Scope 1, 2 and 3. Scope 3 comes from suppliers, logistics and purchasing; without a process inside your system, collecting it every year is slow and incomplete.
California's SB 253 and SB 261 require large companies to disclose their greenhouse gas emissions and climate-related financial risk. Pulling that inventory and risk report together by hand, with the data scattered across purchasing, energy, logistics and finance, is slow and hard to audit. This module runs the scoping, structures your Scope 1, 2 and 3 GHG inventory, records assurance, prepares the SB 261 TCFD risk report and keeps an immutable audit trail, all inside Odoo.
Your emissions and climate-risk data live across energy, purchasing, logistics and finance. Gathering it every cycle, keeping it audit-ready and hitting the filing deadlines is not a job for a spreadsheet.
SB 253 requires disclosing Scope 1, 2 and 3. Scope 3 comes from suppliers, logistics and purchasing; without a process inside your system, collecting it every year is slow and incomplete.
SB 253 and SB 261 each have their own phase-in and filing calendars. Without reminders inside your ERP, it is easy to close a cycle with the data only half done.
Your assurance provider and reviewer need to know where every figure comes from. If the inventory lives in loose Excel files, proving the origin of each number is manual and fragile.
It does not promise to comply for you or file with California on your behalf. It does the concrete, useful part: scoping, the GHG inventory, assurance, the SB 261 report and the audit trail.
Works out whether your company falls under SB 253, SB 261 or both, and which reports and deadlines apply, so you do not waste time on what does not concern you.
Structures your Scope 1, 2 and 3 emissions inventory and records the third-party assurance SB 253 requires, with the evidence of the process stored inside Odoo.
Prepares the climate-related financial risk report SB 261 requires, aligned with the TCFD framework, ready to review and publish.
Tracks the SB 253 and SB 261 deadlines inside your ERP and keeps an immutable audit trail of every figure, so you can prove its origin to your reviewer.
Runs entirely inside Odoo 17, 18 and 19, depending only on standard modules. No separate platform, no monthly SaaS fee, and every figure stays in your own database.
You get the full source code for 399 € as a single one-time payment, with direct support from the developer who wrote it, no per-seat or per-report billing.
Install the module in your own Odoo, define what applies to you, then run each SB 253/261 cycle the same way every year.
Answer the applicability questions and the module tells you whether SB 253, SB 261 or both apply, and lays out the reports and deadlines you are on the hook for.
Enter Scope 1, 2 and 3 data, log the third-party assurance, and draft the TCFD-aligned SB 261 risk report, all in one place instead of across scattered spreadsheets.
Hit each deadline with reminders inside Odoo, then hand your reviewer an immutable audit trail that shows who entered every figure and when.
FlexigoTech is Flexibles y Accesorios Gobe, S.L., based in Barcelona. Development is handled by a single developer, so when you ask about SB 253 scoping or the SB 261 report, you talk directly to whoever wrote the code, not a salesperson.
This is a native Odoo module, with no external platform and no extra SaaS fee. We do not invent reviews or certifications: the tool structures your scoping, GHG inventory and SB 261 report. Third-party assurance, the official filing and the reporting entity's responsibility stay with you, and we tell you that before you buy.
399 € as a single one-time payment. No per-user cost, no per-report charge, no annual renewal to keep it running.
Buy it once through the Odoo App Store. There is no SaaS subscription and nothing to renew: the module keeps running on your Odoo for as long as you use it.
You get the complete Odoo source, so your team or your integrator can review it, extend it and keep it under your control. No obfuscation, no black box.
Ships and is tested for Odoo 17, 18 and 19, on both Community and Enterprise, so it fits whichever version your team is running today.
Questions about scoping, the inventory or install go straight to the developer, not through a support tier. Optional help is available for your first disclosure cycle.
Climate disclosure rarely comes alone. It usually shows up next to other ESG obligations and the need to keep compliance organized inside a single Odoo.
SB 253, the Climate Corporate Data Accountability Act, requires large companies doing business in California to disclose their Scope 1, 2 and 3 greenhouse gas emissions. SB 261, the Climate-Related Financial Risk Act, requires publishing a climate-related financial risk report aligned with the TCFD framework. This Odoo module supports both requirements in one place inside your ERP.
The module structures your Scope 1, 2 and 3 GHG inventory and records the assurance process, but it does not replace an independent verifier. SB 253 requires third-party assurance from an accredited provider. The module organizes the data and stores the evidence of the process, while certification and responsibility for the disclosure remain with your company as the reporting entity.
The module tracks the SB 253 and SB 261 filing deadlines inside Odoo and keeps an immutable audit trail of who entered each figure and when. That means you can show exactly where every number in your emissions inventory and risk report came from, without rebuilding it by hand in spreadsheets at audit time.
Both. You can buy the module license on the Odoo App Store, and if you need it, we can help you configure the scoping, map your emissions data sources across purchasing, energy and logistics, and get your first SB 253/261 disclosure cycle set up correctly.
It works with both Odoo Community and Enterprise, on Odoo 17, 18 and 19. The module only depends on standard Odoo modules (base, mail, web, account, purchase, portal), so Enterprise apps like Helpdesk are optional and not required for the compliance workflow. There is no external SaaS: all of your emissions and climate-risk data stays inside your own ERP.
The only question is whether you rebuild it by hand each time or keep it solved inside Odoo. Try the live demo and see the full flow before you decide.