Stock cost truth

Change the cost of the stock you still have—without changing the quantity.

“I changed the cost, but my profit still looks wrong.” That usually means the business changed a product field without correcting the value of the stock that is still on hand. IGFirstERP gives the correction a controlled workflow.

Do not reduce and re-add stock merely to correct its cost. Quantity and value are different records and should be corrected through different controls.

Find my plan Book an Operations Fit Call

Published 2026-07-11 · Verified 2026-07-11 · Editorial policy

Decision points before a demo

What the owner needs to know

What changes?

The cost assigned to the remaining stock for the chosen SKU and location.

What stays unchanged?

The physical quantity. A cost correction is not disguised as a stock movement.

What if the stock layers disagree?

The revaluation is blocked so the mismatch can be investigated and repaired before value is changed.

Best fit

  • Businesses with meaningful stock value and location-level cost errors.
  • Teams that need a dated reason and reviewable before-versus-after value.
  • Operators correcting costs after receiving, migration, landed-cost, or data-entry errors.

Probably not fit yet

  • A physical quantity shortage or surplus; use stocktake and reconciliation.
  • A historical financial restatement without accounting review.
  • A request to hide an unexplained variance by changing cost.

Why it returns

Changing a product cost field does not explain what should happen to stock already on hand

A basic edit can change the cost used tomorrow while leaving the value of today’s remaining stock unresolved. That is how margin reports and stock value continue to disagree.

  • Separate current quantity from its recorded value.
  • Scope the correction to the SKU and location that are wrong.
  • Keep the reason and effective date beside the correction.

What IGFirstERP controls

Preview the value change before applying it

The workflow calculates current quantity, old unit cost, new unit cost, old stock value, new stock value, and the difference before the operator commits the change.

  • Choose whether related default or selling prices should also change.
  • Block incomplete inputs and stock-layer mismatches.
  • Apply the approved change as one transaction with an audit record.

Owner control

A correction should leave evidence, not another mystery

The owner can review who changed cost, why it changed, when it became effective, which location was affected, and how much inventory value moved.

  • The quantity remains visible and unchanged.
  • The value difference is explicit before approval.
  • Price changes remain a separate operator choice.

Demonstration workflow · not customer data

Correct a remaining-stock cost

Demonstration data: 40 units of SKU DEMO-001 at Lagos Warehouse. No customer or live business data is used.

Step 1

Select the record

Choose the SKU and location whose quantity is already trusted.

Step 2

Enter the correction

Set the new cost, effective date, reason, and optional price decisions.

Step 3

Review the preview

Compare old and new stock value and check for a layer-mismatch block.

Step 4

Apply and verify

Post the transaction and review the retained audit details.

What the owner can verify

  • Quantity before and after is the same.
  • The SKU, location, reason, date, old value, new value, and difference are visible.
  • Any default or selling-price update was an explicit choice.

When the happy path fails

  • A stock-layer mismatch blocks revaluation instead of silently forcing a value.
  • The repair path identifies the affected layer before the operator retries.
  • A failed transaction does not leave a half-applied cost update.

Explicit limitations

What this page does not promise

  • This corrects stock value; it does not prove why the original cost was wrong.
  • Data quality, permissions, and accounting review still matter.
  • It is not a statutory valuation opinion or a replacement for an accountant.

Operational proof, not vanity claims

These proof assets show what became visible, traceable, faster, or easier to review after IGFirstERP was implemented. Named customer metrics are used only where permission has been granted. Results vary by operating discipline, data quality, implementation scope, and adoption.

Proof library Named customer evidence Review what became traceable, visible, or easier to control, with limitations stated. Methodology How claims are governed See the evidence, permission, review-date, and limitation rules behind public claims. Product Walk through the operating system See how stock, sales, staff, storefronts, and reporting connect.
Pain-answer hub Start from the problem Find the repeated stock-control problem your team is still rebuilding by hand. Academy Operator education Use practical lessons to strengthen the process around the system. Documentation Product guides and SOPs Review the current operating instructions for IGFirstERP workflows.

Questions serious buyers ask

Should I reduce and re-add stock to change its cost?

No. If the quantity is already correct, use a cost-revaluation workflow so value changes without inventing a stock movement.

Can selling prices change at the same time?

The operator can choose whether supported default or selling-price records should also be updated. The price decision is not silently assumed.

What happens when stock layers do not match?

The change is blocked and routed to a repair path. That protects the audit trail from a forced correction on inconsistent layers.

Operations Fit Call

Choose the path that fits your operation

Use Find my plan when the workflow is clear. Book an Operations Fit Call when branches, warehouses, integrations, migration, permissions, or reporting need to be mapped first.

Book an Operations Fit Call