CUSTOMER SUCCESS STORIES
iCube by SIRCLO
Building with Magento 2.0
iCube built the Body Shop Indonesia site on Magento 2.0 back in 2016, using Fooman PDF extensions. Read what CTO Muliadi Jeo had to say about the build, and being a Magento 2 early adopter.
Building with Magento 2.0
We built the Body Shop Indonesia site on Magento v2.0. Overall when we reviewed the requirements of their design and the checkout process, it fitted nicely into M2 default Luma template. So the skinning effort is quite flawless.
The site requirements included a customized PDF printout for the warehouse to print custom picking lists and order receipts. We decided to use Fooman PDF Customiser and Fooman PDF Picking List to achieve this. We used the extensions out of the box.
The site requirements included a customized PDF printout for the warehouse to print custom picking lists and order receipts. We decided to use Fooman PDF Customiser and Fooman PDF Picking List to achieve this. We used the extensions out of the box.
Favourite Features
Custom PDF functionality
Could use out of the box
The [Body Shop] site requirements included a customized PDF printout for the warehouse to print custom picking lists and order receipts. We decided to use Fooman Pdf Customiser and Fooman Pdf Picking List to achieve this.
Magento 2 Early Adopters
We have decided to jump ship to M2 on almost all of our projects this year [2016]. We know there is a big risk but to make sure that our clients are getting the latest support from Magento (and because Magento is only selling M2 Enterprise licenses), we decided to go with M2. We are fully embracing M2 at this point.
The other reason we recommend M2 is because it has cleaner interface and much better backoffice function (manage product, manage orders, etc). One of the issues that I had with M1 that I am so glad they fixed in M2 is the way configurable products are now driven by simple product price.
In general, I think M2 is moving to the right direction. Technology wise, it adopts all the new stuff like knockout js, less, clear separation between backend and frontend development.
The other reason we recommend M2 is because it has cleaner interface and much better backoffice function (manage product, manage orders, etc). One of the issues that I had with M1 that I am so glad they fixed in M2 is the way configurable products are now driven by simple product price.
In general, I think M2 is moving to the right direction. Technology wise, it adopts all the new stuff like knockout js, less, clear separation between backend and frontend development.
Be careful choosing between M 2.0.x and M 2.1.x. Don’t assume that what works on one version will work on another without code changes. There are a few major changes that can make your code break. For our projects, we have to build new payment modules. That is one of the major headaches here in Asia. There are so many payment providers here so we have to build our own custom modules. We started a project with M 2.0.4. But then when we tried to use that same module on another project on M 2.1.x, we found out that a lot of re-work needed to be done to make it compatible.
iCube by SIRCLO
iCube is one of the leading Magento Professional Solution Partners in Asia Pacific, with 40+ developers and 15+ certified Magento developers in house. Clients are mostly retailers and e-commerce startups, serving both North America and Asia Pacific.
