`subscription` and `invoice grouping` modules compatible?

Hello,

I’m trying get an idea whether I can use Tryton for my food cooperative.

We’re delivering food packages on subscription base, fees are collected monthly. With the subscription module, when using the “generate invoice” wizard I always get one invoice with all monthly fees up to the given date. With monthly payments, it’s not conveniant to check if all subscibers actually paid their fees.

Having the invoice grouping module installed as well, I wonder whether that one is the problem? The result is all the monthly invoices collected into a single one, even creating one single invoice line.

So - are subscription and invoice grouping module compatible? -

For this purpose,

  • a monthly invoice with subscription fee should be created anyway
  • additional orders would be paid separately, so should be invoiced separately as well.

Thank you in advance for your thoughts,
EG

The Sale Invoice Grouping Module does not modify the behavior of the Sale Subscription.
A subscription is always invoiced at once for all the pending consumption. So if you want to have more invoices per subscription, you must create the invoices more often.

Thank you, Sir. On that base, I could create monthly invoices.

But I do not understand the idea of “consumption”. My understanding of “subscription” is that I pay a fixed fee for a fixed product or service on a regular base. How does “consumption’” come into this concept?

EG

It is the record of the consumption of the service in a fixed point in time.

Thank you, Sir, but that doesn’t answer my question.
Would somebody please be so kind and answer the question I asked above at #3 ?

EG

At a good talk with a Tryton colleague, we got this impression:

  • the term “consumption” is a little confusing, as subscription fees, AFAICS, are usually not dependent on consumption, but on deliveries,
  • so instead of “consumption recurrence”, something like “delivery recurrence” would be a better expression,
  • the same with “consumption delay”,
  • instead of wizard name “create line consumptions”, something like “create delivery positions” would be more easy to understand,
  • as the “recurrence” features are quite sophisticated, maybe “schedule” instead would even be better, but agreed, that’s a little of nit-picking…

In the German translation, things are worse, I filed some suggestions at translate.tryton.org.

Greetings,
EG

I do not think it is right because nothing is delivered (especially because such term implies goods) but a service is provided (aka consumed).
As the Sale Subscription Module is based only on service, I think it is more appropriated to talk about consumption to avoid misunderstand that this module is kind of recurring sale module.
For example phone companies talk about consumption not deliveries.

It is sophisticated because this is a powerful tool that is more than just a schedule. More over a schedule does include the notion of repetition.

I do not know but in past I knew there was some liberties taken about translation. But the only good way to translate Tryton terms is by being a literal as possible and agnostic about your personal use case.

“Consumption” seems to be a technical term from accounting and AFAIU this term is correct. Anyhow, to understand this term one needs to be a accounting specialist :-/

Thank you for all your effort. Now I know how to deal with the module.

Regards,
EG

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.