Spryker Core Back Office feature overviewEdit on GitHub
A Spryker-based shop ships with a comprehensive, intuitive administration area comprised of numerous features that give you a strong hold over the customization of your store. Here you can tailor features to your specific needs, manage orders, products, customers, modify look & feel of your store by, for example, designing the eye-catching marketing campaigns and promotions, and much more.
The Spryker Back Office provides you with a variety of sections that are logically connected to each other.
It provides the product and content management capabilities, categories and navigation building blocks, search and filter customizations, barcode generator, order handling, company structure creation (for B2B users), merchant-buyer contracts’ setup.
With Spryker Back Office, you can:
- Manage orders placed by your customers as well as create orders for customers
- Create and manage customers
- Build and manage product categories
- Create and manage CMS blocks and pages
- Handle translations
- Manage products and all elements related to them (availability, labels, options, types, etc.)
- Customize search and filters for the online store
- Create and manage discounts
- Build and manage the main navigation of your online store
- Create new carrier companies and shipment methods as well as manage those
- Create admin users, add roles and user groups
Depending on the roles and teams in your project, you can limit the access of different Back Office users to specific Back Office areas.
Back Office provides both, B2B and B2C capabilities.
The following diagram shows what features are used for both B2B and B2C, and which are B2B specific.
You can always define what exactly is going to be needed for your specific project.
Currently, the feature has the following functional constraint:
Each of the Identity Managers is an ECO module that should be developed separately. After the module development, the Identity Manager’s roles and permissions should be mapped to the roles and permissions in Spryker. The mapping is always implemented at the project level.
Related Business User articles
Are you a developer? See Spryker Core back Office feature walkthrough for developers.
For submitting the form