Monthly COGS Tracking

SKU value, shipped value, and expected future cost refresh.

Loading Refresh Control SOP & Tab Guide

Refresh Control

Loading current Monthly COGS status...

Accounting Month

Open Sheet

Last Completed Build--

SKU Mapping Month-Expected cost months -

SKU / Ledger Rows-Ledger rows -

Sam Worker-Last heartbeat -

Latest Output

Clean report-

Support workbook-

Run folder-

Write proofOdoo writes off; Google publish locked

Latest Job

Status-

Requested by-

Updated-

Summary-

What This Refresh Builds

Inventory valueFull known history refreshed; month-end book unit value, units, and total value by SKU.

Shipped valueAverage and total shipped COGS by SKU/month from the rebuilt flow.

Expected costForward-looking buy/build cost saved by month so old columns stay intact.

Each run refreshes all known history from current source data. The accounting month only controls SKU Mapping column F.

Recent Runs

Employee SOP

Monthly Update & Google Sheet Guide

Use this page to run the monthly refresh, confirm it worked, and understand what every tab is showing.

Back to Refresh Open Sheet

The Regular Job

Monthly Update Process

Finish the month-end entries

Wait until the normal receipts, landed costs, manufacturing orders, scrap, inventory adjustments, and known cleanup for the month have been entered in Odoo.

Open this control page

Confirm the Sam Worker says Online. Sam's Mac must be on and the local Monthly COGS service must be running.

Select the accounting month

Choose the month whose rebuilt inventory cost should be copied into SKU MAPPING - DOMO column F. This choice does not limit the data pull or erase later months.

Click Dry Check

This confirms the worker and required local files are available. It does not pull Odoo, rebuild the report, or change the Google Sheet.

Click Build + Publish Sheet

The tool pulls fresh read-only Odoo data, rebuilds all known history, runs its controls, and updates the one approved Google Sheet when no blocking check fails.

Wait for Complete

A normal full run can take several minutes. Do not start another run while the page says Queued or Running.

Open and review the Sheet

Confirm the newest expected-cost month is present, the selected mapping month is correct, and any visible review items make sense before sending or using the output.

What the month selector really does Every full run refreshes all known historical inventory and shipped-cost months from today's Odoo facts. The selected month only chooses which month's rebuilt unit cost is written to SKU MAPPING - DOMO!F:F. Expected Future Cost is saved under the current expected-cost snapshot month, and older expected-cost columns remain in place.

Old months can change A landed cost, receipt, manufacturing move, or inventory adjustment entered later with an older effective date can change an older month the next time the report is rebuilt. That is expected because the report uses the best information currently recorded in Odoo.

What You Will See

Screen Guide

Monthly COGS refresh controls showing the accounting month, Dry Check, Build and Publish, and current status — **Refresh control.** Select the mapping month, run the Dry Check, then use Build + Publish Sheet. The status cards show the latest successful output and whether Sam's worker is online.

SKU Mapping DOMO tab with Odoo SKUs and the color-coded COGS column F — **SKU MAPPING - DOMO.** Column F is refreshed for the accounting month selected in the tool. Its cell color tells you where the value came from.

Expected Future Cost by Month tab with SKU rows and monthly cost columns — **Expected Future Cost.** Each saved month remains as its own column so the team can see how the estimate to buy or make a new unit changes over time.

Clean Rebuilt Ledger tab with source documents and running inventory fields — **Clean Rebuilt Ledger.** Filter this tab by SKU to trace the receipts, landed cost, manufacturing, shipments, scrap, and adjustments that created its running units and value.

Google Sheet Reference

What Each Tab Is Telling You

The SKU-by-month tabs use the same SKU list down the left and months across the top, which makes the rows easy to compare from one tab to another.

Read Me

A short description of the report's main calculations and the important accounting caution.

Use: Start here when sharing the Sheet.Do not use: It contains explanations, not report totals.

SKU MAPPING - DOMO

Carola's sales-channel-to-Odoo SKU mapping. Column F holds the accounting-month unit cost that feeds the downstream Domo process.

How built: Rebuilt unit cost first, shipped COGS average second, existing manual value last.Use: Mapping and monthly reporting feed.Do not use: Do not treat every manual/red value as an Odoo-calculated cost.

Rebuilt Unit Cost by Month

The estimated average value of one usable unit still in inventory at each month end.

How built: Month-end rebuilt total value divided by rebuilt units on hand after the location and subcontracting presentation rules.Use: Month-end inventory value per unit.Do not use: It is not shipped COGS and not the cost to make the next unit.

Rebuilt Units by Month

The number of usable units the rebuilt history says were on hand at each month end.

How built: Physical receipts and production add units; shipments, MO use, scrap, and other removals take units out.Use: Quantity support behind inventory value.Do not use: It does not replace a physical count.

Rebuilt Total Value by Month

The estimated total dollar value of usable inventory still on hand for each SKU at month end.

How built: Rebuilt units multiplied by rebuilt unit value, after the approved period-end presentation rules.Use: Month-end inventory value support by SKU.Do not use: It is a balance at month end, not the month's COGS expense.

Units Shipped by Month

The number of customer units shipped during each month.

How built: Customer outbound shipment rows in the rebuilt ledger.Use: Shipment volume behind sold-unit cost.Do not use: It is not ending inventory or every non-customer removal.

Shipped COGS Avg by Month

The rebuilt average inventory value per customer unit shipped during that month.

How built: Each shipment uses the running average value immediately before it leaves; monthly shipped value is divided by shipped units.Use: Management COGS per shipped unit.Do not use: It is not Odoo's official posted COGS or future replacement cost.

Shipped COGS Total by Month

The total rebuilt inventory value that left through customer shipments during each month.

How built: The rebuilt cost assigned to every customer outbound row is added by SKU and month.Use: Reconstructed monthly shipped COGS dollars.Do not use: It excludes non-customer removals such as scrap or MO consumption.

Expected Future Cost by Month

The best current estimate of what one new unit would cost to buy or make, saved as a monthly snapshot.

How built: Purchased items use supported recent receipt/PO cost; made items use the current BOM and current component expected costs; subcontracted items also add the latest same-unit finished-item PO charge.Use: Pricing, margin, purchasing, and future build planning.Do not use: It is not the value of old inventory or units already shipped.

Clean Rebuilt Ledger

The transaction-by-transaction trail showing how each SKU's units, total value, and average unit value changed over time.

How built: Odoo receipts, landed costs, MO use/production, shipments, scrap, and other physical adjustments are replayed in effective-date order.Use: Filter by SKU and trace a number back to source documents.Do not use: It is support detail, not the fastest monthly summary.

Example Cost Flow

A worked example showing component value leaving inventory through an MO and becoming the value of the finished good produced by that same MO.

How built: The example uses actual same-MO component quantities and their rebuilt running values, including landed cost already carried by those components.Use: Explain why finished-good cost changes when newer-cost components are actually used.Do not use: It is one teaching example, not the full SKU population.

SKU Mapping Color Key

White

Updated from that month's Rebuilt Unit Cost.

Yellow

No rebuilt on-hand cost was available, so the month's Shipped COGS Avg was used.

Red

No rebuilt or shipped value was available. The existing/manual value was kept for review.

Behind The Numbers

How the Rebuild Works

Source data

Fresh read-only Odoo valuation layers and stock movements.
Purchase orders, receipts, and supported landed-cost entries.
Manufacturing orders and the components actually consumed by each MO.
Products, categories, units of measure, and current BOM information.

Core cost flow

Receipts and production add units and value to a SKU.
Shipments, MO use, scrap, and other removals leave at the running average value immediately before the move.
Landed cost stays with the component and flows into a finished good when that component is actually consumed by an MO.
Manual zero-quantity cost-change rows remain visible for audit but do not instantly reprice old inventory in the rebuilt calculation.

Why this is different from simply using today's BOM Historical finished goods are valued from the components that actually moved into their manufacturing order at that time. A later BOM change or lower component price does not rewrite finished goods that were already made.

Inventory scope The published usable-inventory view includes the approved warehouse inventory population, including historical Zon/Stock, and excludes QC Hold. A supported subcontracting bridge keeps components and unfinished outside processing from being mistaken for available finished goods.

What To Review

Success Signs, Warnings, and Boundaries

A successful run

Status changes to Complete.
The Latest Job summary says the clean report was published to the approved Google Sheet.
Odoo writes remain off and Google Sheet updated is shown in Write Proof.
The Sheet keeps all historical month columns and adds or refreshes the correct expected-cost month.

Review items are not automatically errors

Temporary negative inventory or backdated timing.
A purchased receipt that may still be waiting for landed cost.
An active SKU without enough support for expected future cost.
An incomplete BOM, missing subcontract charge, unusual cost, or unresolved unit-of-measure item.

Publication stops on a blocking failure The tool will not publish if critical source, correction, reconciliation, expected-cost, or arithmetic controls fail. Keep the old Sheet in place and contact Matt or Sam; do not manually force the generated tabs over the failure.

Odoo is read-only. The hosted tool is permitted to update only the locked final Monthly COGS Sheet and the approved SKU Mapping column F behavior. It does not create a new report Sheet each month.

When Something Looks Wrong

Troubleshooting

What you see	What it usually means	What to do
Worker Offline or Local Offline	Sam's Mac or the local Monthly COGS service is not reachable.	Leave the Sheet alone and contact Sam. The refresh buttons remain disabled until the worker is healthy.
Dry Check fails	A required worker, file, or local service is unavailable.	Do not run Build + Publish. Send Sam the exact status and time shown on the page.
Job stays Queued or Running	The worker may be busy, offline, or the Odoo pull is still processing.	Wait several minutes and refresh the page. Do not submit duplicate jobs.
Build fails or publication is blocked	One of the locked controls did not pass.	Keep the prior report. Contact Matt or Sam with the Latest Job summary; do not overwrite Sheet tabs manually.
A past month changed	Odoo now contains a backdated landed cost or movement that was not known on the earlier run.	Review the SKU in Clean Rebuilt Ledger and confirm the source entry is legitimate.
SKU Mapping cell is red	No rebuilt inventory cost or shipped-cost fallback was available for that selected month.	Review whether it is a new/unbuilt or virtual SKU. Keep or correct the approved manual value rather than inventing an Odoo cost.
Expected cost is blank or looks incomplete	The latest receipt/PO support, BOM, component cost, or subcontract charge may be missing.	Check the current Odoo setup and the review items. Do not substitute the rebuilt inventory cost without understanding why expected cost is missing.

Quick Answers

FAQ

Is the selected month the start or end of the month?The rebuilt value is the estimated inventory value at the end of the selected month.

Does selecting March remove April through today?No. All known history is refreshed. March only controls the cost copied into SKU Mapping column F.

Does Dry Check update anything?No. It checks readiness only.

Does Build + Publish change Odoo?No. Odoo remains read-only.

Are landed costs included?Supported posted landed costs are carried in component value and flow into finished goods when those components are actually used by an MO.

Why do Book/Rebuilt Unit Cost and Shipped COGS Avg differ?Rebuilt Unit Cost values what remains at month end. Shipped COGS Avg values what left through customer shipments during the month.

Why can Expected Future Cost differ from both?It estimates the next unit to buy or make using current purchase/BOM information, not the cost of old inventory or past shipments.

Owner And Admin

Ownership, Change Control, and Manager Check

Business ownersMatt / Carola / Eric

Technical ownerSam

Normal cadenceManual, after month-end close entries are complete

Approved destinationMonthly COGS Tracking - Final only

Current process versionLocked V2

Technical admin notes

The Cloudflare page stores queued requests and status. It does not hold Odoo credentials.
Sam's local worker polls the queue and calls the local Odoo Data Control service.
The locked reconstruction starts on 2024-09-01.
Every build pulls a fresh read-only Odoo snapshot, applies the approved stable correction schedule, rebuilds the ledger, creates the clean and support workbooks, runs blocking QA, then publishes.
Expected-cost history is prospective. Current made-item BOM cost is saved by snapshot month; old BOM history is not invented.
Changes to the algorithm, source scope, corrections, Google Sheet ID, tab names, location rules, or write boundary require Matt's approval and a new process version.

Manager checklist

The accounting month selected for SKU Mapping is correct.
The run says Complete and the latest build time is current.
Odoo writes are off and the locked Google Sheet was updated.
Review items were considered, especially missing landed cost and incomplete expected cost.
The new expected-cost month is present and earlier expected-cost columns remain available.