Extend your store safely with reviewed apps.

App Store is a dedicated Prebit capability focused on sandboxed runtime environment with oauth authorization-code + pkce & scoped api access. It is positioned as part of the wider Prebit platform rather than a disconnected add-on.

App Store is best suited to merchants looking to extend their store functionality with verified, secure apps and developers wanting to build, monetize, and publish commerce apps on Prebit.

App Store relies on Commerce Engine contracts for product, cart, order, customer, or event state so teams are not duplicating business logic across separate tools.

Yes. Boron is Prebit's Next.js commerce framework, and this feature is designed to surface cleanly inside Boron storefront implementations.

Krypton is Prebit's mobile commerce framework. Where mobile parity matters, this feature is designed to share contracts with the same storefront APIs and platform services.

Yes. The feature set is designed so agencies can standardize workflows, theme patterns, or integration playbooks instead of rebuilding each project from scratch.

Yes. Prebit's direction is API-first and framework-aware, so custom logic can be added through typed interfaces, event flows, and deployment pipelines instead of fragile UI workarounds.

Usually yes, although the mechanism depends on the feature. Prebit's architecture aims to reduce plugin sprawl, tighten data contracts, and keep storefront rendering paths cleaner.

Start with the workflow you already run today, map the manual steps and integration points, then validate how this feature reduces handoffs, errors, or duplicated implementation effort.

It is part of the Prebit ecosystem, but the feature pages are intentionally written as independent product narratives so merchants, agencies, and developers can evaluate each capability on its own merits.

A third-party app usually means a second data model, a second permissions surface, and a second thing that can silently drift out of sync. App Store reads and writes through the same Commerce Engine contracts as the rest of Prebit, so there is one source of truth instead of an app-plus-platform reconciliation problem.

App Store is modeled at the platform layer, not inside a specific theme or frontend. Switching themes, or moving a storefront from one framework surface to another, does not require re-entering or migrating the underlying data.

No for the core merchant workflow, which is designed to work out of the box. Yes if a team wants deeper customization, custom UI, or integration with an external system, which is why the developer-facing contracts exist alongside the merchant UI.

The goal is for platform-level features to add negligible overhead compared to stitching together equivalent third-party scripts or apps, since the logic runs closer to the same data layer instead of making extra round trips.

It is included as part of the relevant Prebit plan rather than sold as a separate paid add-on, though final packaging can vary by plan tier — check current plan details before assuming feature-by-feature pricing.

Prebit maintains the underlying platform logic and ships improvements centrally. Merchants and developers configure and extend it, rather than owning the core implementation the way they would with a self-hosted plugin.

Generally yes. Most Prebit capabilities are additive rather than mandatory, so a team can adopt them when the workflow actually calls for it instead of being forced into every surface on day one.

The same contracts that make a single store work cleanly are what let multi-store and enterprise operators standardize the same workflow across several storefronts instead of re-implementing it per store.

Start a trial, look at the relevant dashboard surface directly, and compare it against whatever manual process or third-party tool currently handles the same job — the difference is usually clearest in a real side-by-side.

Specific and technical, by design — this page describes real architecture and real behavior, not vague marketing claims, so a merchant, agency, or developer can evaluate it accurately.