Logging Gear Purchases
How the "Add purchase" flow works — per-unit vs total price, and the toggles that decide whether a purchase hits your financials.
What a purchase records
Every gear item keeps a purchase history — the ledger of when you acquired units and what they cost. This is the source of truth for the item's quantity and (optionally) for the one-off expenses that show up in your financials.
Use Add purchase whenever you buy gear: one row per purchase, with how many units, the price, and the date you bought them.
Per unit vs total price
The Purchase price field has a toggle so you never have to do the maths by hand:
| Mode | What you enter | Example (3 units) |
|---|---|---|
| Per unit | The price of a single unit, excluding VAT. | Enter 5.310 → total becomes 15.930. |
| Total | The combined price for all units on the row, excluding VAT. | Enter 15.930 → per unit becomes 5.310. |
Whichever mode you pick, ProductionPal stores the figures the same way and books unit price × quantity as the cost. Type the invoice total straight from your supplier and let the app split it.
Count as one-off expense in financials
When this is on (the default), the purchase becomes a one-off expense in your financials in the month you bought it. Turn it off for gear you already owned and are just logging for inventory — it still counts toward the item's quantity and history, but it won't hit the P&L.
Spread evenly across the purchase year
By default the full amount lands in the purchase month. Enable Spread evenly across the purchase year to average the cost across the 12 months of that year instead — useful for big acquisitions you think of as a yearly investment rather than a single hit.
This option only applies when Count as one-off expense is on — if a purchase isn't in the financials, there's nothing to spread.