Edit History

About the main topic:

If your business is growing, and you also want to enhance your front-end customer experience, the PrestaShop Headless solution would be a great choice.

To be honest, if we want to avoid a full re-platforming, we need to think in terms of a large-scale architecture — a system composed of multiple connected components, integrations, and an API gateway that aggregates everything. It’s truly a complex ecosystem that involves different technologies working together.

To achieve such a sophisticated setup, headless architecture is the first step.

This is the key advantage of going headless — along with the smoothness and flexibility that simply can’t be achieved with classic themes.

So, if we don’t take these steps, re-platforming won’t be the solution either and does not guarantee our scalability. This scenario applies to any platform or system: if we truly want to take control of our business and grow technically, adopting a headless approach is the way forward.

"What challenges or limitations might arise during implementation and later maintenance?"

answer: we need to add another server to run the storefront application, a small vps server for serving the front, nothing will be changed on your main server and shop.

"How does maintaining and updating Prestashop look when using a headless setup – does it complicate daily operations?"

answer: it does not need daily operations, just like your main shop.

This demo storefront: https://react.binshops.com/ is running on a VPS server. So, the main shop was: https://rest.binshops.com/ and we just installed the REST API and it's giving us: https://rest.binshops.com/rest/bootstrap then, we just added a VPS server for running our storefront. That's it. 

for more look at: https://www.binshops.com/prestashop-headless-pwa

Kind regards,
Sam

@MartinCz

About the main topic:

If your business is growing, and you also want to enhance your front-end customer experience, the PrestaShop Headless solution would be a great choice.

To be honest, if we want to avoid a full re-platforming, we need to think in terms of a large-scale architecture — a system composed of multiple connected components, integrations, and an API gateway that aggregates everything. It’s truly a complex ecosystem that involves different technologies working together.

To achieve such a sophisticated setup, headless architecture is the first step.

This is the key advantage of going headless — along with the smoothness and flexibility that simply can’t be achieved with classic themes.

So, if we don’t take these steps, re-platforming won’t be the solution either and does not guarantee our scalability. This scenario applies to any platform or system: if we truly want to take control of our business and grow technically, adopting a headless approach is the way forward.

"What challenges or limitations might arise during implementation and later maintenance?"

answer: we need to add another server to run the storefront application, a small vps server for serving the front, nothing will be changed on your main server and shop.

"How does maintaining and updating Prestashop look when using a headless setup – does it complicate daily operations?"

answer: it does not need daily operations, just like your main shop.

This demo storefront: https://react.binshops.com/ is running on a VPS server. So, the main shop was: https://rest.binshops.com/ and we just installed the REST API and it's giving us: https://rest.binshops.com/rest/bootstrap then, we just added a VPS server for running our storefront. That's it. 

for more look at: https://www.binshops.com/prestashop-headless-pwa

Kind regards,
Sam