When should I use Store API/Admin API for custom frontends?
Our Take
Use the Store API for anything customer-facing and the Admin API for backend operations, integrations, and management tasks. In most headless Shopware builds, your frontend should talk almost exclusively to the Store API—and only use the Admin API through a secure middleware layer when you need admin-level data or automation.
This is one of the first architecture decisions that affects performance, security, and long-term maintenance in a custom Shopware frontend.
The Store API exists for storefront experiences. Product listings, carts, customer accounts, checkout, CMS pages, search, pricing, promotions, shipping methods, and context-aware data all belong here. Shopware already handles sales channel logic, currencies, customer groups, and rule builder conditions through the Store API. If you’re building a Vue, React, Nuxt, Next.js, or mobile frontend, this should be your default choice almost every time.
The Admin API is different. It’s meant for managing the platform itself. That includes creating products, syncing ERP data, importing orders, updating inventory, triggering automation, or accessing internal entities that the storefront should never expose publicly. It gives you much broader access—which is exactly why you should never call it directly from the browser in a production storefront.
We don’t recommend using the Admin API as your main frontend data layer for most businesses. It usually creates more problems than it solves. You lose built-in storefront context handling, permissions become messy, caching gets harder, and developers often end up rebuilding logic Shopware already provides through the Store API.
The exception is when you’re building something operational rather than storefront-focused. For example, a warehouse dashboard, marketplace connector, custom admin app, subscription engine, or internal B2B tooling. In those cases, the Admin API is often the right foundation because you need direct entity control instead of sales-channel-aware storefront responses.
Worth it if:
You’re building a headless storefront, PWA, mobile app, composable frontend, or multi-region customer experience where pricing, promotions, and checkout logic should match Shopware’s native storefront behavior.
Skip it if:
You’re trying to expose admin-level product management or ERP workflows directly to frontend users. Use a backend middleware layer with controlled Admin API access instead.
Recommended
Store API
- Built specifically for storefronts and headless commerce experiences
- Handles pricing, rules, currencies, and customer context automatically
- Safer to expose to frontend applications and PWAs
- Usually faster to implement because Shopware already solves most commerce logic
Best if: You’re building customer-facing experiences and want Shopware to remain the commerce engine behind the scenes.
Admin API
- Provides deep access to entities, administration data, and automation workflows
- Better for integrations, imports, middleware, and operational systems
- Requires stricter authentication and permission handling
- Easy to misuse in frontend projects if your architecture is not planned properly
Best if: You’re building internal tools, syncing external systems, or extending Shopware administration capabilities.
Who This Is For
Stores building headless Shopware frontends with Next.js, Nuxt, Vue Storefront, or custom mobile apps that need native commerce behavior without rebuilding pricing and checkout logic.
Technical managers planning ERP, PIM, marketplace, or warehouse integrations where backend systems need structured entity access through secure APIs.
B2B stores with custom quoting, account permissions, or procurement flows where frontend and operational systems need separate API responsibilities.
Small stores trying to bypass Shopware’s storefront stack just to fetch product data faster. Most of the time, the Store API already solves this cleanly.
Teams exposing Admin API credentials directly in frontend JavaScript. That’s one of the fastest ways to create a security incident.
Related Answers
Was this answer helpful?
Your feedback helps us improve our answers.
Still need help?
Talk to our Shopware experts
We've handled GDPR/CCPA compliance for dozens of EU & US Shopware stores.