Product Cost Visibility

[HADCO]

I setup items, and I have the following screenshots. Cost isnt being shown on the front, did I do this right?

Edited 4 hours ago by HADCO

[HADCO]

IS this true:
 

Guidance:

 

Forcing the “Cost” field via import (Option C) can cause bad downstream effects.
But it depends on what Matthew needs and how HADCO will use Advanced Inventory going forward.

Below is a crisp breakdown so you can decide safely.

Why Option C can cause problems

1) Loyverse is not designed for you to manually set “Cost” when Track Stock is ON

Official documentation states that when Track stock is enabled, the Cost field is replaced by Average cost, which Loyverse computes automatically when receiving items.
This is explicitly documented:

“When you switch on ‘Track stock’, the ‘Cost’ field will be replaced with ‘Average cost’.”    [loyverse.com]

So if we import a value into “Cost”, we are:

Overwriting something Loyverse expects to calculate

Short‑circuiting the inventory valuation logic

Creating conflicting cost baselines

Impact:
Loyverse may display cost, but it will NOT match actual average cost once they start receiving stock.

2) It will break future COGS calculations once the hotel starts receiving stock

Average cost updates when you receive items:

“The value of the average cost… will be updated when you receive items.”    

If we force a static cost:

The forced value may be overwritten

Or worse: Loyverse may calculate new average cost using incorrect opening cost

Impact:
COGS will be wrong until they manually fix stock adjustments or force a reset.

3) It disconnects “Inventory Valuation” from the item’s real transaction history

Right now, Average cost = 0 because no stock was received.
If we force Cost = Purchase cost in v7:

Inventory valuation will show an opening value

But that value will not be tied to any real Receive Inventory event

Meaning the valuation history will not reconcile with purchase orders or adjustments later

Impact:
Accounting, audits, and month-end reconciliation become messy or inaccurate.

When Option C is safe (rare but valid)

Option C is only safe if HADCO will NOT use Receive Inventory and instead:

Manually manages on‑hand stock

Does NOT use Advanced Inventory workflows

ONLY needs cost to appear in reports for visibility

Does NOT rely on Loyverse’s COGS or valuation accuracy for accounting

This is the exception, not the rule.

The safe and correct option: Set costs by performing “Opening Stock Receipts”

This is what Loyverse is built for.

Create a Purchase Order per supplier

Add items + quantities

Loyverse auto‑injects Default purchase cost

Click Receive

Inventory valuation instantly corrects:

Average cost = purchase cost

Inventory value = cost × qty

COGS becomes functional

Reports become accurate

This aligns fully with Loyverse’s documented workflow.
(We can automate creating these starting POs for all SKUs.)

Recommendation for HADCO

Do NOT do Option C unless The business explicitly agrees that:

They are OK with valuation and COGS not matching future receipts

They will not use purchase orders

They will not rely on Average cost

They understand this becomes a “static” cost import, not true COGS

If HADCO wants correct cost-of-goods reporting:
Do Option A (Opening inventory receipts)

If HADCO only wants short‑term visibility and is NOT using Advanced Inventory:
Option C is acceptable with a warning