Basics | Plugins | Howtos

Storage management

A provision (Vorrat) is when a given quantity of a given product is in a given storage state for a given partner.

A storage state is a name given to a certain type of provision. Some typical storage states:


auf Lager

in stock


bestellt vom Kunden

ordered by customer


bestellt bei Lieferant

ordered from provider



rented out





in Reparatur

under repair




For some storage states the partner is irrelevant. For example when we see that 3 books are “ordered by customer”, we need to know the customer who ordered them, but when we have 30 books “in stock”, then these books aren’t assigned to a given partner.

In Lino Noi we use only one storage state “purchased”, and two transfer rules:

  • A sales invoice (SLS) credits “purchased”

  • A service report (SRV) debits “purchased”

transfer rule

A configuration data row that specifies when a given voucher “transfers” a product from one provision to another provision.

And there would be only one product with storage management enabled, and that product would be named “Time credit”. Maybe there will be multiple products in order to differentiate between “temporary” (befristet) and “timeless” (unbefristet) time credit.

A subscription agreement must somehow specify the “required provision”, which means that the customer must always have a minimum provision of time credit. For example they buy 10 hours, which are being used up with each working session, and when the time credit gets used up they want to buy new credit. This can be done by Subscription.get_invoice_items. For each subscription that has such a “required provision”, it would check whether the partner still has enough provision. If not, it would generate an invoice to buy new time credit.

To specify this, we could simply add three new fields:

  • “product” : a pointer to the “Time credit” product

  • a minimum quantity (e.g. 5 hours)

  • an order quantity (e.g. 10 hours)

This reminds what the Tariff model and the InvoicingInfo class do until now. And indeed the storage plugin will partly replace these classes.

We have two basic approaches for generating invoices:

  • get_invoicing_periodicity() or “period-based invoicing” : The enrolment has a start_date and an end_date, and the “subscription periodicity” gives renew_unit, renew_every and renew_before. Period-based invoicing is for subscriptions, with a monthly or yearly fee.

  • get_invoicing_pass_type() or “occurence-based invoicing” : Lino needs a number_of_events, a min_asset and max_asset. This is used e.g. in Voga when a customer buys a “multi-pass card” for 10 sessions of an activity.

I am not yet sure where to store these information. Maybe we just want to add a Tariff.product field. The current flatrates (Tariff) do not currently point to another product.









Side note. How to handle quantity-related prices? For example the unit price of an hour would be 90 € while 5 hours would cost only 400 € and 10 hours only 750 €. –> This is not related to the storage plugin and should be addressed by “price rules” or “complex products”.

A storage filler