FrontAccounting comparison to weberp and comunionerp

Thanks Tim,
I was just about to write something similar, but have asked my partner, Janusz, to do it instead. I had the same feeling as you have. Yes, I have the feeling too, that we both push forward the cause of open source. Nice to hear that we are on the same wavelength. I also think that the clients should examine the projects extensively before planning to do something dramatic.

/Joe

ok, thanx for prompt answers, a good sign of a vivid community for both projects ;-)

there are several points I want to react, so...

Ad Tim:
"it seems to me that you fall into a common misconception regarding open source projects, that in some way the developers should act as salesmen, and should sell the product to you..."

Well, I think that any SW project (not excluding an open source one) should take into account not only developers but also its target audience - with all the regard to developers, I think they are not target group of the majority of OS projects, and feeling so, may often hurt the spread of OS concept.

ad: itronics
"Yes, I think TIm has explained excellent that the question is bad addressed. Having so much spare resources you can use some small part of them for recognizing differences between the three projects yourself. We are developers not software retailers nor consultants."

I supposed, that this is not forum only for developers, but also for users. I DO NOT expect developers to sell project, but I do expect project leaders respect the needs of their potential customers and communicate benefits of their product.

I am not in the quest for finding pleasure in pushing forward a OOS project, but I search a solution for satisfiying my needs and I am prepared to pay my bill in return, in lets say development participation. I think this is a case of 99% of OS users.

My resources are not SPARED, I simply try to allocate them as effectively as possible, thats why a posted this question. You may basically answer it in 5-10 minutes in more details than me/my developer would after 10 hours of research. The saved time might be spend on a feature in your project, which would help community, development and me as well. Thats my point.

If there is also a forum for users/not developers question, could I get a link pls.

And Janusz, thanx for welcome, I hope I do not sound rude, this is just a view from a economic perspective

Ludo

Hello Ludo,

I don't think so. The only man who know your requirements are you. The start constraints you have explained in first post are obviously fulfilled by both webERP and FA (comunion seems to be in alpha stage and seems not support multicurrency you need). I cannot advice which user interface philosophy is more suitable for you or which coding style is more compatible with your habits.
If you would ask me about features you want I could answer without problem. But seems you wanted me to make comparative study of the three projects. Sorry, I have not too much time to study other projects to give you satisfactory answer.

This forum is mainly for Front Accounting users, not developers, so feel free to ask us about any aspect of FrontAccounting usage, if you know what you want. You can also test the application on our demo site at http://fa2.iron.from.pl. Hope it will be helpful in your decision.

Best regards
Janusz

Hello Ludo,
Yes, maybe you are right that it would be useful for potential FA/webERP users to have some list of unique features available in the applications.

I think the main functional differences are listed below.

webERP:
* serial numbers/batch/lot control
* special (one time) orders
* automatic freight cost calculations
* SOAP API for easier integration with third party applications
* geocode support for customers/suppliers

FrontAcounting:
* three stage sales chain: orders-deliveries-invoices
* simple POS functionality
* template invoices
* dimensions for easy project/cost center GL inquires
* bank account reconciliation
* quick GL posting definitions
* support for network printers
* VAT/GST payable/return inquires/reports
* scanned document attachments

Of course beside above there is a lot of other features supoorted by both applications. There is also a lot of differences from developers point of view and in overall look and feel. Which of the individual coding/ui solutions are more convenient is certainly in main part matter of habits.  I have compiled the lists just for those users who know at least one of the applications, and want to know what the other can additionally offer.

Tim, give me a note if I've missed something unique for webERP. Your project has changed a lot since I was somewhat involved in its development .

Hope it helps.

Janusz

I'l give you my view because I believe I did my homework (being NOT a developer either I probably share your view of things).

I chose FA mainly because of its interface and the simplicity yet elegance of how certain crucial things are handled. People very often overlook the fact that the first impression (which is the UI) is more important than a particular function that may be easily added if the need arises.

I believe that weberp has the deeper functionality but it's sometimes hard to understand and thus hard to set up and hard to teach. The only real issue I have with FA so far is the lack of customer codes.

But of course - the only real test is the one against your requirements. If you did your business requirement analysis you should have a list of your KO criteria as well as one for important/nice to have things. Check them against both systems and if there is no clear preference let your programmers look which code is easier to change and where there is more future potential (in terms of adding functions/modules without changing the core code).

OS fortunately never is a dead end road because the code is yours.

Hi Janusz,

As you say in your post your knowledge of webERP is not current, and likewise my knowledge of FA is nowhere near as detailed as it is of webERP. There are some things in your list that webERP has had for a while, and some that webERP has that FA doesn't but aren't mentioned. This is why the original question really makes no sense. Features can change, whereas this post will remain as an historical record. If I was to list a feature that webERP has and FA doesn't, you may release that feature next week making this post nonsense. However a potential user may come along and read this post and believe that FA doesn't have that feature. The only way to do a feature comparison is to provide two links to the features sections on our websites.

The true difference between the two projects is one of development philosophies. This is why the original developers of OA (the father of FA) split from webERP. This was an amicable split, and webERP still has much code provided by those developers.

I have a great deal of respect for FA as a project, and have often urged people to look at it as well as webERP.

Ludo, you say that you will probably need a great deal of customisation to fit either project into your company. I have been implementing systems in companies for over 25 years and have never yet met a company that doesn't think its needs are special, and that a lot of customisation will be necessary. This is rarely if ever so. The skill in implementation is to see how a companies needs can be married with the softwares features. This is why good consultants can command high fees.

Thanks
Tim