Storage by Product Volume calculates storage charges per product (SKU) based on the product's physical dimensions and the quantity stored.
Peak units × Volume per unit × RateInvoices show the billing period (e.g. March 1–31 for monthly billing), not per-SKU receiving dates. This is by design — the current storage billing model is based on daily inventory snapshots, not on when individual units were received.
Note: Receipt-date-based storage billing (tracking how long inventory has been in a specific location since it was received there) is a model used by some 3PLs and is being evaluated as a future enhancement. This approach requires operational discipline: if inventory moves between locations, the storage period resets at the new location, since inventory is fungible and specific units can't be traced. It works best for warehouses where products are received into a location and stay there until shipped.
Storage by Product Volume charges based on product dimensions and quantity, regardless of how the inventory is physically stored. The distinction between BOX and EACH is an operational concern at the warehouse level.
PRO TIP: If different storage rates are needed for different storage configurations (e.g. eaches vs. cases), this can be achieved today by using different location types for each storage method and configuring separate billing rates per location type. Location type filtering directly on the product volume billing rate is being evaluated as a future enhancement.
Packiyo provides inventory movement history through the Inventory Logs feature, which tracks all inbound and outbound movements per SKU per location. This can be accessed via the product detail page.
The product detail page currently shows raw dimensions (L x W x H) but not the computed volume. Displaying the calculated cubic footage per unit on the product detail page is planned as a future enhancement.
If a storage charge looks higher than expected based on current or end-of-period inventory counts, remember that charges are driven by the peak daily inventory during the billing period — not the count on any single reference date.
For example, if inventory was higher at some point during the month (e.g. after a receiving event, before shipments went out), that peak is what drives the charge, even if inventory was lower by month's end.
If a charge looks off:
Why doesn't my invoice show per-SKU receiving dates? Storage billing is based on daily inventory snapshots, not receiving dates. The invoice reflects the billing period as a whole.
Why is the "quantity" on my invoice not the unit count? The quantity field reflects total volume (e.g. cubic feet), not the number of units. Unit count is used internally to calculate volume.
Can I get different storage rates for boxes vs. eaches? Yes — set up different location types for each storage method and configure separate billing rates per location type.
Where can I see inventory movement history for a SKU? Use the Inventory Logs feature, accessible from the product detail page.
Why is my storage charge higher than I expected? Charges are based on the peak daily inventory during the billing period, not the current or end-of-period count. Check Inventory Logs to see the actual peak.