The Vendor Prices Manager and your item’s cost layers are how Bizuno answers two questions that often get confused: what did it cost me last time? and what’s it worth on the shelf right now?
How to get there #
Menu: Inventory → Prices Manager
Direct URL pattern: https://yourdomain.com/?bizRt=inventory/prices/manager&type=v
Vendor Prices vs. cost layers #
Two different things:
- Vendor Prices — a catalog of what each vendor charges you for each SKU. Used to pre-fill the cost when you create a PO.
- Cost layers — the historical record of what you actually paid when goods arrived. Used to calculate COGS on sale.
Vendor Prices let you know before the order that CrankCo is $38 and BrakeBros is $41 for the same chainring. Cost layers track what you actually paid in each shipment, so COGS is correct even when costs change over time.
Managing vendor prices #
Adding a vendor price #
- Open Prices Manager.
- Click New.
- Pick the SKU.
- Pick the Vendor.
- Enter the Cost, optional Quantity break thresholds, the Vendor’s part number, and an optional Lead time.
- Save.
How vendor prices get used #
- When you create a PO and pick a vendor, line items pre-fill with that vendor’s price (or the quantity-break tier appropriate to the qty you’re ordering).
- The vendor’s part number appears on the printed PO — saves the vendor the lookup.
- Lead times feed the Reorder report so you can order ahead of time for slow suppliers.
Multiple vendors per SKU #
Most consumables in a bike shop come from more than one source. Stack them in the grid, and each PO picks up the right price automatically based on which vendor you’re ordering from. Mark one as the Preferred Vendor on the item record — that’s who the reorder report defaults to.
Cost layers (FIFO) #
By default, Bizuno uses FIFO (First-In-First-Out). Every receive creates a cost layer:
- Date received
- Quantity
- Cost per unit
- Source document (PO or receiving transaction)
When you sell an item, Bizuno relieves from the oldest layer first. Your COGS reflects the actual cost of the goods that went out the door.Important: If you chose average cost instead of FIFO during initial setup, layers still exist but COGS uses the rolling weighted average. The choice is global per company and can’t be changed after transactions exist.
Viewing cost layers #
On any SKU, open the Stock tab and click Cost Layers. You’ll see a chronological list: date, receive qty, cost, remaining qty. The sum of “remaining qty × cost” for all open layers equals the item’s on-hand valuation.
When costs change #
- A new receive at a higher price creates a new layer at the new cost. Older layers at older costs keep their prices.
- As you sell, old layers deplete first. Once they’re empty, the new cost starts flowing into COGS.
- Your Last Cost field on the item updates to the most recent receive.
- Your Standard Cost field does not update automatically — you decide when to refresh it.
Negative inventory and cost #
If you sell before you receive (it happens), you go negative on hand. COGS uses your Standard Cost as a placeholder and Bizuno flags the transaction. When the receive finally arrives, cost layers catch up and a reconciliation transaction smooths out any COGS difference. Watch the Inventory Variance report if you see a lot of these.
Tips for Ridgeline Cycles #
- Keep Vendor Prices current for your top 100 SKUs — it turns every PO into a 30-second job.
- Update Standard Cost once a quarter from the Last Cost column — it keeps placeholder costs on negative-inventory transactions close to reality.
- When a vendor raises prices mid-year, don’t adjust old cost layers. Let them deplete naturally; your next receive will create the new layer.
- On a special one-off buy where the cost is way higher than normal, tag the PO with a note — it saves confusion six months later when COGS looks off on a single invoice.
Where to go next #
- Receiving (Vendors) — creating cost layers.
- Inventory Reports — valuation and variance reports.
- Stock Levels — reorder planning using vendor lead times.