Perhaps I am a little inclined towards Silius, since I constantly work with him - I tried to use Sonata packages in projects earlier, but I could not use them.
The reasons for using Sylius are that it is highly decoupled and customizable, which is exactly what you want if you need an e-commerce solution that is not the usual βadd to cart, pay for it onceβ model.
There are two approaches that you can use to use Sylius: either use the full stack application, or configure it, which is the most common approach and is better supported. Another approach is to install Sylius as a library, not an application, and create the application and use it yourself, using Sylius classes and services when you need (which I do).
When using Sylius, you need to be careful, as it is still in beta, with breaking changes between releases. In addition, the documentation is very incomplete or outdated (which I plan to improve), with the exception of Resource and ResourceBundle - these packages are the most important part of Sylius and therefore are very well documented. For your project, I recommend the first option.
To subscribe to areas of Sylius that you want to look at customization and extension, OrderBundle , PricingBundle and PaymentBundle . If you are familiar with Symfony, this should be easy.
Adam elsodaney
source share