Start here when you need the short version of what Enad is before choosing where to work next.

Orientation only. Use SDK, API, Search, Event, and reference pages for exact names, fields, payloads, and generated types.

Enad in plain English

Enad is the system behind commerce data and commerce experiences. It helps a business organize what it sells, how those products appear, where they can be bought, what customers see, and which technical surface to use next.

That means Enad is broader than a storefront theme kit. A storefront can be one expression of the platform, but the platform model also covers product information, prices, stock, media, customer-facing content, and the context that changes what shoppers see.

The basic shape of the platform

A simple way to think about Enad is that each experience belongs to a workspace, a business surface, and a selling context.

• Teams are the top-level workspace where work is organized.
• Apps are the business or storefront surfaces inside that workspace.
• Store groups describe the selling context for an experience.
• Markets describe where that experience applies, such as country, language, or currency context.
• Products, media, and customer-facing content are the information those experiences draw from.

You do not need every internal term on day one. Start with the idea that Enad keeps commerce information and storefront delivery connected, then learn the deeper terms as you need them.

Selling in different contexts

One of the main ideas in Enad is that the same business may sell in more than one context.

For example, a brand may sell across contexts in several ways:

• It can run different storefront experiences for different kinds of customers.
• It can sell into multiple countries or language regions.
• It can show different assortments, pricing, or content depending on where the shopper is.

That is why terms like store group and market matter. At a high level:

• a store group helps describe the kind of selling experience
• a market helps describe where that experience applies

You do not need the exact implementation details here. The useful mental model is that Enad lets the same underlying commerce setup behave differently across selling contexts without treating every context as a completely separate business.

Product, price, stock, and content

A customer may think in terms of one product. The platform still has to coordinate several related kinds of information:

• The main product a shopper recognizes.
• The specific version or option they can buy.
• The price shown in a given selling context.
• The stock available from a given inventory context.
• The content and media that explain the product.

That is why Enad should be read as a platform model, not only as a UI layer. The storefront experience depends on the data model behind it, and that model can change by context.

Where to go next

• Want the shared vocabulary and reading order first? Go to Start concepts.
• Need the selling-context model next? Read Store groups and markets.
• Need the workspace and runtime model next? Read Teams, apps, and environments.
• Need the catalog model next? Read Products, variants, prices, and stock.
• Building storefront UI? Start with React SDK latest.
• Choosing or integrating REST APIs? Start with APIs.
• Working on search, autocomplete, or facets? Start with Search latest.
• Working with assets, images, or media delivery? Start with Media.