Sellina Architecture:
Magento 2 and Next.js / React
Thanks to the technology used, your company receives a platform that operates stably under heavy load, is secure, and doesn't lock you into a single provider. We achieve this through an open architecture: a Magento 2 backend and a headless Next.js/React frontend, connected via API. This allows you to integrate with any external system and develop your store with any development team.
Magento 2 as the backend of Sellina's system
We chose Magento 2 as the foundation for Sellina because it's the most efficient and popular open source eCommerce engine—a large, mature platform supported by a vast, global developer community. What does this mean in practice for your business?
Magento is supported by a vast, active community of developers worldwide. Regardless of Adobe's decisions, the community has also created its own, independent versions of the engine (e.g., Mage-OS), which guarantee continued development and support without being tied to a single vendor. This ensures the technology remains in the market and you'll always find someone to maintain it.
Thousands of ready-made plugins for Magento allow you to add features to Sellina faster than writing them from scratch.
Magento's open architecture allows Sellina to connect with most popular ERP, PIM, OMS, and marketplace systems. The exceptions are rare cases where the other system is completely closed and doesn't provide any interface for connection.
Magento under Sellina can handle extensive product catalogs and high order volumes without sacrificing speed.
The system grows with your needs, so you won't "outgrow" it in a few years and don't have to invest in expensive platform replacement.
The Magento engine allows for seamless handling of catalogs exceeding one million SKUs and sales of several thousand orders per day.
Why does Sellina's frontend run on React / Next.js?
The store's frontend operates independently of the backend—it's written in React and Next.js, two of the most popular frontend technologies today. This means easy access to developers for you when you want to expand your store, and fast-loading pages and improved search engine visibility thanks to Next.js' server-side rendering are available to your customers.
Separating the frontend from the backend and connecting them via API ensures that your customers – both B2B and B2C – shop on a store that works lightning fast, regardless of how many visitors are browsing the catalog at the same time.
How do Sellina's frontend and backend connect via API?
The frontend and backend are connected via an API based on the API Platform framework, physically separating the two layers – a direct benefit for your IT department. An attack on the frontend doesn't provide access to the database or business logic – it can only target precisely defined, monitored API endpoints. We plan Magento and Next.js updates individually with each client – together we determine when and which security patches to implement, ensuring they don't interfere with your ongoing work.
The benefits of headless architecture in Sellin
React and Next.js are a popular technology stack, so expanding the system or changing the team doesn't limit the company to a handful of specialists.
Separating the frontend and backend limits what an attacker can see or compromise.
You have the option of creating multifrontends, which means that when creating a new brand, entering a new market or customer segment, you don't have to build the system from scratch and you can manage all your stores from a single panel.
The technology really translates into convenience for users who can make purchases without long waits for the page to load, especially on mobile devices.
Multiple stores from one Sellina backend
(multi-frontend)
Thanks to its headless architecture, Sellina allows you to launch multiple, independent stores based on a single, shared backend—without having to build each one from scratch. In what situations is this solution applicable?
New market or customer segment
When you want to allocate a narrower section of your product range to a separate website, enter a new foreign market, or serve a new customer segment with a separate store, while maintaining a common product catalog, integrations, and administration panel.
Quick launch of a new store
When you want to quickly launch a new store – in this model, sales usually start within a few days, not months.
Integration with ERP – the role of the Intermediary Database in Sellin
Connecting a store to other systems—usually ERP—is usually the biggest challenge of any eCommerce implementation. In practice, off-the-shelf plugins and API integrations implemented by external integrators often result in:
Delays in implementing the integration, because the integrator must first understand the structure of the Magento databases.
Refusal to integrate or additional costs when this structure proves too complicated for him.
Intermediate Database (data bus)
One solution is the Intermediate Database (also known as a data bus) – an external database to which Sellina sends key data in a simple, well-documented structure. This allows:
Your integrator – even without prior knowledge of Magento – immediately knows where to get the data and where to send it.
Data is easier to map between systems, so it goes exactly where it needs to go, with less risk of error.
We integrate Sellina with ERP using one of several methods – depending on what is on the other side: directly via API, through a ready-made module or connector, or with the involvement of a partner who manages the ERP system.
You can find a list of systems that Sellina can connect to in the Integrations tab. This is a basic list that can be expanded and adapted to the needs of your sales model.
Product management at Sellin.
Integration with PIM systems
PIM systems, i.e. Product Information Management (e.g. Akeneo or Ergonode), allow you to digitize your product database in one place, ensure the current and completeness of product information, and synchronize everything with other company systems.
When does PIM make sense?
This is especially true where the catalog is large and has many technical attributes – even with a catalog of several thousand products, manually maintaining data consistency in several systems simultaneously becomes difficult to manage.
What if you don't have a PIM system yet?
We implement it from scratch:
We build a data model, i.e. a structure that determines what categories, attributes, and relationships between products will be in the system before we enter real data into it.
We organize the product database, which is often scattered across price lists, marketplaces, and websites.
We select a specific solution for your situation.
Which system: Akeneo or Ergonode?
An effective, cost-effective solution, especially in its open source version. It works well in most standard implementations where quick startup and low maintenance costs are a priority.
We recommend it when you need more extensive product data flow management (workflow) between teams responsible for the catalog, and built-in digital asset management (DAM) – photos, files, product documentation.
You can find a complete comparison of PIM systems – including Pimcore and when to choose one – in our article:
Comparison of PIM systems: Akeneo, Ergonode, Pimcore.
Additional modules for PIM Akeneo clients
We have created additional modules that speed up work with an extensive product database.
A module for generating product content using AI (GPT chat model) based on product attributes.
A module enabling mass translation of existing text-type attributes (descriptions, titles, names, etc.) into any language.
A module for generating catalog cards and product catalogs using product data available in Akeneo.
Most frequently asked questions
Why is Sellina on the Magento 2 engine?
Magento 2 is the most popular open-source eCommerce system, with a community of over 300,000 developers and over 5,660 ready-made plugins. This scale means easier access to developers and a reduced risk that the chosen framework will be discontinued in a few years.
How does headless architecture differ from classic Magento?
In classic Magento, the frontend and backend operate as a single application. In a headless architecture, the frontend (React/Next.js) and backend (Magento) are separated and communicate via API. This allows for faster store performance, and an attack on the frontend doesn't provide direct access to the database.
Does headless mean slower development than in a monolithic store?
No – React and Next.js are among the most popular front-end technologies today, so access to developers is easier than with less popular solutions.
Can I run several stores (different brands, markets) on one system?
Yes – this is one of the main advantages of Sellin's headless architecture. For example, we have implementations where a client runs multiple stores from a single backend for different foreign markets. In such cases, launching each additional store costs approximately 20% of the price of the basic implementation and does not generate a second license fee.
How does Sellina secure data if the frontend is separated from the backend?
Communication takes place via an API based on the API Platform framework. An attack on the frontend does not provide access to the database or business logic – it can only be directed at precisely defined, monitored API endpoints. We regularly implement Magento and Next.js update policies for each client.
Does integration with my ERP or PIM require custom development?
Typically not – depending on the system, we use ready-made plugins or API integration, and in more complex cases – especially with ERP – we use an Intermediary Database. You can find a full list of systems ready for integration with Sellina in the Integrations tab.
let's talk!
Schedule a demo and see if Sellina's architecture meets the needs of your IT team and business.
Michał Kozik, Head of Design and Strategy / co-CEO