Custom storefronts and headless commerce
Design your buying experience with your team or agency. Connect the new site to Open2b and define how to manage your catalog, customers and orders with us.
For B2B and B2C businesses, agencies and software companies building a custom store connected to their business processes.
A connection designed around your business
The project defines which functions stay in Open2b and which are handled by the new site.
Shape navigation, product pages and purchase journeys with the people who understand your brand and customers.
Plan the new store around the data and activities you want to keep managing in Open2b.
Your business, agency and Open2b agree on data flows, development responsibilities and support arrangements.
Choosing the architecture
The choice depends on the role you want Open2b to play: commerce engine or backoffice connected to an independent sales system.
Headless storefront
Your team or agency builds the storefront, using the Open2b commerce capabilities available to the project through APIs.
Consider this when you want a new buying experience with Open2b as your commerce engine.
Synchronized independent store
The new site runs on its own sales system. Open2b keeps its backoffice role and exchanges the data defined by the integration.
Consider this when your new project has its own sales system and you want to connect it to Open2b.
We start with your business processes and give each system a clear role.
Define the source of the data and how the store reads or updates it.
Assess the customer access, groups, price lists and commercial rules needed for the planned experience.
Assess the complete purchase journey, required payment methods and operations to integrate.
Decide where orders originate, which information passes to Open2b and how updates are managed.
Tell us your goals, the planned site, the systems you use and the activities you want to keep in Open2b.
Assess the edition, version, APIs, workflows and responsibilities. The proposal distinguishes software, storefront development, integration and support.
The project team builds the connection and tests the agreed journeys, from product browsing to ordering and subsequent management.
For agencies and developers
The documentation describes available operations. We assess their applicability to your edition and version alongside the project requirements.
Documented operations for products, carts, customer login, quotes and order creation.
Explore the documentation →Backoffice operations for products, price lists, customers, orders, documents and other store data.
Explore the documentation →The project can retain Open2b for agreed backoffice activities, with a custom storefront or a connected independent store. We start with the data and processes you want to keep.
Headless describes the store’s architecture. The Open2b edition, API availability, infrastructure, development and support are defined during the project assessment.
The storefront choice is separate from cloud or installed deployment. We assess the appropriate configuration according to the planned edition, version and infrastructure.
You can involve your own team or agency. The initial assessment defines who handles the interface, Open2b connections, testing and support.
The proposal distinguishes Open2b software, storefront development, integration and support. Activities and terms are agreed according to the project.
Tell us what you want to build, who will develop the site and which activities you want to manage in Open2b. These are the starting points for assessing the right approach.