There are currently three relevant ways to customise or extend SAP Business One. Firstly, there are the SAP board tools: the Software Development Kit (SDK) and the in-built functions such as user-defined objects, tables and fields. This also includes SAP's UI designer.
Building on the SAP SDK, it is also possible to operate with frameworks from SAP partners such as coresystems (coresuite country package). The same applies to the usability package (b1up) from Boyum.
The latter two frameworks have become very powerful over the years. They significantly accelerate the customisation and enhancement of SAP Business One. However, it can be said that nothing that is possible with these tools cannot theoretically be realised with the SDK. Secondly, anything that is customised in standard software should always be carefully considered. The following always applies here: first check how a requirement can be implemented in the standard. Because sometimes you solve a problem at one point, only to create a new problem at another point in the process.
Sometimes adaptation tools also blur the line between Customising and coding. They also have the option of integrating their own code.
In a webinar by Boyum, we demonstrated relatively well what is possible with the "Advanced Item Placement Tool", for example, and how the SAP Standard UI designer relates to it.
It is noticeable that Boyum has already gone the extra mile here. However, it is also good that Boyum describes what one has to bear in mind with partly massive interventions and where the limits lie.
However, if you follow the rules on Customization of SAP Business One, one thing can be guaranteed: In contrast to many other ERP packages with customisation options, the release and update capability of SAP Business One remains unaffected.
Coding or customizing: Correctly adapting ERP software
coresuite easy functions - SAP Business One customizing made easy
Generative AI in ERP: How LLMs are changing the role of ERP systems
Monolithic ERP systems in SMEs: challenges, solutions and risk management
ERP for discrete manufacturing - or why screws don't flow
