Hi, I'm not sure if this is the right place to post this, so my apologies if this should be on another forum. Our company has been working to customize Sugar for our internal needs for approximately the last year. During the course of that, we have added a number of custom modules and functionality. One of the most extensive enhancements has been basically turning Sugar into a "Billing System" of sorts. Currently we use it to bill Internet Service for approximately 10,000 customers.
In short, we configure various "Products" and assign them to Accounts. From there, the system generates invoices based on the established intervals and then charges the customer (now via Authorize.net). We have functionality to support a wide variety of billing related tasks such as entering payments, payment methods, issuing refunds, reporting, declined credit cards, and even provisioning external services based on billing events (i.e. turning service on and off), plus a lot more.
All that is to ask, do others have a use for this type of functionality? I see a few posts here and there about something similar, but I'm not sure what to make of that. Ultimately, we recognize these tasks normally live in other systems, but for us it made sense to bring into Sugar for a lot of reasons.
Anyhow, we are considering making this code available to the community. I think we would have some cleanup, packaging, and documenting to do in order for someone to really implement and use and I want to get some insight as to whether we should pursue that.
Any thoughts would be greatly appreciated.


LinkBack URL
About LinkBacks



Reply With Quote

Bookmarks