The alpha360 ERPs are core ERP applications, based on the alpha360 Universal Data Models v2.
The new v2 Data Models have been redesigned to be more simple to understand and use, without losing any of their prior functionality.
All v2 alpha360 applications use our new UI Framework, that is programmer and user friendly, robust and includes access control at the heart of its design.
The alpha360 ERPs come with full fource code, a licence for unlimited distribution of your compiled apps, free rebranding and free email and forum support.
To understand and work with the WX implementation of the alpha360 ERPs you need a basic knowledge of WD [v21 or newer] and a basic understanding of relational theory and SQL.
The system is also a GREAT introduction to WD programming, especially for programmers coming from other environments [like Clarion or Delphi].
Note: You need a valid license for WINDEV v21, to work with the system.
What's new in v2
v1 of the alpha360 Data Models had a very "strict" relational design.
Referential integrity was everywhere in the design, giving us "security" even if we tried to do "dangerous things" with our data - but it was complicated and difficult to understand.
With v2 we have "eliminated" many referential integrity constraints, either because they are not needed anymore or because they have been replaced by BPs (Business Processes).
Major changes have been done with TAX/VAT calculations, Payments, Transactions and the iWorkFlows - everything now is "super simple".
But the biggest changes have been done in the Business Documents area:
Now we have separate tables for all major Business Documents - Quotes, Orders, Shipments and Invoices - both for Sales and Purchases. The idea of one general table for all the above, although "elegant", was for most developers, confusing.
Although we did not change the basic concepts in BPs - the use of transactions, records and arrays - we have introduced a new concept in v2 - the code bricks.
They have helped us "reduce code" by 50% or more and at the same time make it a lot easier for programmers to "follow the code".
We have also "eliminated" ALL previous quick adds and quick deletes and replaced them with 2 general ones.
We have totally redesigned the UI code, simplified it, made it more robust and added many features that our clients asked. And probably the most important thing, we added access control at the "heart" of its design.
See the introduction video for the alpha360 ERP or Retail System for more ...
Another big change in v2 is in the area of supporting many languages and cultures.
In v1 we had our own translation procedures - embeded in the apps. This was rather "a stupid decision" and it took us a lot of time to make it work the same way in WINDEV and WEBDEV implementations. All v2 apps now use PCSofts multilingual features, something we should have done in v1 apps also.
There are currently 2 ERP versions: Standard and Professional.
the Standard version supports ERP and CRM functionality and is based on PC Soft's WINDEV application development environment [requires v21 of WINDEV].
the Professional version supports ERP, CRM, B2B, Manufacturing and HORECA functionality and is based on PC Soft's WINDEV and WEBDEV application development environments [requires v21 of WINDEV/WEBDEV]
Take a look at the compare page for more information ...
Retail vs ERPs
The Retail System and the ERPs are different products, aimed at different markets, that can work side by side. Both have their unique features and none of them is a real subset (or super set) of the other.
So how do you choose?
If you need to develop a product ONLY for Retailers, use the Retail System.
If you need to develop a product ONLY for WholeSalers (or Hotels, or Manufacturers), use one of the ERPs.
If you need to develop a product for the Retailers and WholeSalers (or Hotels, or Manufacturers) use both of them.
You can of course use one of the ERPs and add YOUR OWN extensive Retail functionality.
Note that the ERPs include some basic POS and Restaurant functionality, but NOT as extensive as the ones in the Retail system.