| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 620 |
| Technical Name |
scopysoft_cogs_fixer |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules?author=ScopySoft |
COGS Fixer
For products where Odoo's stock moves and journal entries have drifted apart - missing entries, wrong debit/credit amounts, or COGS reports that don't add up.
What it does
Dry run first
Preview every change before anything is written to your books.
Fills in missing entries
SVLs with no journal entry get one created, correctly balanced.
Fixes wrong entries
Mismatched debit/credit lines get corrected to match the SVL.
Date range filter
Target one period instead of a product's whole history.
Full change log
Every run is logged with the exact before/after values, browsable in the UI.
CSV export
Download a record of what changed, per SVL, for your files.
See it in action
1. Pick a product and run mode
Select the product, optionally set a date range, and choose dry run or live before anything happens.
2. Preview before committing
See exactly what would be created, updated, or is already correct - no changes made yet.
3. Apply with confidence
Same summary, this time with real changes committed and a backup reference you can look up later.
4. Full transparency
A timestamped log of every step, account, and journal used during the run.
5. Every run is logged
Browse past runs under COGS Fixer Backups, with the product and line counts for each one.
6. Line-level detail
Exactly what each journal line looked like before the fix - account, debit, credit, all of it.
FAQ
Does this support AVCO or other costing methods?
It's built around standard costing. If your category uses a different method, review the proposed entries carefully in dry run before applying.
What if a journal entry is in a locked period?
Locked or reconciled entries can't be reset, so the fixer skips them and logs the specific reason instead of guessing.
Can I undo a run?
Every run is logged with full before/after values under COGS Fixer Backups, but there's no automatic restore. Test in a duplicate database first.
Does it work on Odoo Enterprise?
Yes - it only touches standard stock_account and accounting models, no Community-only dependencies.
Built by ScopySoft · Odoo 16
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Invoicing (account) • Discuss (mail) |
| Lines of code | 620 |
| Technical Name |
scopysoft_cogs_fixer |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules?author=ScopySoft |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module