Skip to content
Ayra Docs

Developers overview

Ayra is one Shopify app built entirely from Shopify’s extension surfaces: an embedded admin for merchants, theme app extensions (an app embed plus app blocks) for the storefront, customer account UI extensions for the account hub, checkout UI extensions and Functions for reward redemption, a POS UI extension for in-store loyalty, and Shopify Flow triggers for automation. It writes to a documented ayra.* metafield namespace and ayra_* metaobjects that themes and other apps can read, and every signal and action is a typed event. Nothing is injected into theme files, and there are no ScriptTags.

SurfaceWhat Ayra uses it forReference
Embedded admin appModules, settings, customers and timelines, analytics, billing—
Theme app extension: app embedThe storefront core bundle (wallet state, events, block runtime)Storefront bundle & performance
Theme app extension: app blocksPoints, wallet summary, referral card, reviews, wishlist and restock blocks, placed from the theme editorTheme app blocks & embeds
Customer account UI extensionsThe account hub tabs (wallet, orders, referrals, reviews, wishlist, subscriptions) and order status blocksCustomer account extensions
Checkout UI extension + FunctionReward redemption inside checkout (Plus), validated by a signed cart attributeCheckout extensions
POS UI extensionLook up a customer, award points, apply rewards in storeLoyalty
Metafields and metaobjectsBalances, tier, stage, ratings and attribution readable by themes and appsMetafields & metaobjects reference
Shopify Flow triggersAyra signals and decisions as Flow triggersShopify Flow triggers
Web pixelStorefront signals (views, wishlist clicks) without theme scriptsEvents
WebhooksShopify → Ayra for orders, customers, products, GDPR; Ayra → you after betaWebhooks & API
  • Extensions, not injections. Every storefront element is a theme app block added, moved and removed from the theme editor. Uninstalling Ayra removes them; no theme cleanup.
  • Shopify primitives first. Store credit, discounts, selling plans, metaobjects, new customer accounts and Flow are used as they are. Ayra’s own ledgers sit behind them for audit and reversal.
  • One profile, typed events. Everything that happens is an event with a name, a customer and a payload; the admin timeline, Flow triggers and the (post-beta) API all read the same stream.
  • Readable state. What a theme or another app needs (balance, tier, stage, rating, attribution) is written to metafields with a stable schema rather than requiring API calls.
  • Budgeted. The storefront core is at most 15 KB gzipped and each block at most 25 KB; the pixel is separate and tiny. See the bundle page.
  • Build theme sections around Ayra’s blocks and metafields; do not scrape the DOM of a block. Blocks emit DOM events you can listen for.
  • Use Flow triggers or metafields to connect Ayra to other apps today; the public API opens after private beta.
  • For a client migrating from another app, the migration guides list what moves and the cut-over order.

Something missing or wrong on this page? Ask us and we will fix the docs.