Accurate Purchase Costs for Packs and Bug Fixes

We have rolled out Cost Basis to improve how purchase costs are stored and used — especially for products ordered in packs.

What’s changing:

• You’ll now be able to save costs per pack when pack size is greater than 1
• For products with Pack Size greater than 1, Sumtracker will treat the entered cost as per pack and auto-calculate the per-unit cost internally
• For Pack Size = 1, nothing changes — the cost remains per unit.

Purchase Prices with Cost basis

Purchase Order with Cost basis

Example:

If you buy a pack of 10 units for $25, you’ll enter $25 as the cost of the pack, and Sumtracker will handle the per-unit calculation as $2.50 per unit.

This update eliminates rounding errors and better aligns your PO totals with actual supplier invoices.

Notes:

• The above change applies to Supplier Purchase Costs, POs
• Changes for API v2025.03: Field renames for cost_per_unit → cost, shipping_cost_per_unit → shipping_cost

⏳ No action needed from your end.

We have auto-migrated your existing data safely based on pack size.

Bug fixes

• Supplier SKU and cost will be fetched correctly when importing products in a PO.
• When importing products through CSV upload in a PO, you have the option to add a cost column. Even if you leave some values empty in the cost column the import will work fine.
• Barcode scanning has been fixed for PO, stock transfer and stock adjustment form. Now you can scan products to add them to the form.