Unified invoices across all OS products?

Looking at building a site which would have your membership pro and eventbooking systems.

It would be really great if there was the ability to have a centralised invoicing system - because people would require invoices on becoming a member and on signing up for events, which would need to be accessed in one central system.

Any thoughts/suggestions?

Ruth

Hi Ruth

I don't know what's the best way to support this feature. Maybe we can develop a plugin which will show registration history of a user in his Membership Pro profile. Please look at Membership Pro user profile page and let me know if it works. If Yes, then where do you want to show the registration history (which contains the link to download invoice) so that I can think about it and implement this option

Regards,

Tuan

It's more than just showing things in one place.

If you have two different systems posting invoices you have two different numbering systems going. You would get order numbers clashing, for example, if you don't have a different prefix.

It would be more sensible I would have thought to have a single invoicing system that is used by all your extensions with an option for each one to have its own numbering system, or an option to use one centralised numbering system?

So for example using a single centralised numbering system, say we start off with INV-001 for our first membership, They then register for an event - INV-002 is generated. New member joins, INV-003, and registers for an event, INV-004. Then our first member registers for another event, INV-005.

If they had their own invoicing number system (say a prefix of INVM for Membership and INVE for Events) it would be something like:

Member 1 - INVM-001 , INVE-001, INVE-003
Member 2 - INVM-002, INVE-002

Does that make sense?

Ruth

Hi Ruth

For now, I think I could not add an option to the extensions to have an unique invoice numbers like that, actually, you are the only customer needs this option so far

So for now, I think I will leave the system as how it is. If you need this feature, you can submit a support ticket and we are willing to help customizing the code so that the invoice number will be shared between the two extensions as you explained above:

So for example using a single centralised numbering system, say we start off with INV-001 for our first membership, They then register for an event - INV-002 is generated. New member joins, INV-003, and registers for an event, INV-004. Then our first member registers for another event, INV-005.

There would be modification to two plugins, you can keep a backup modifications of these plugins and re-install it each time you update to future releases of the extension

Regards,

Tuan

PS: Sorry for lately response, I thought I replied before but I am wrong. I should reply to this topic last Saturday

No problems, actually we're going to use a third party provider to do this, it just seemed strange that developing multiple extensions that do invoicing, there hadn't been consideration for people who would use both

Ruth