Not yet available and workarounds

13 capabilities are not yet available to apps. Each entry says what is missing, the workaround where one exists, and which example apps depend on it. The full entry, with routes and scopes, is on its area page. 7 more capabilities are not offered by design; they are listed at the end, under Not offered by design, with what to use instead.

Example apps are listed on the overview.

Orders

Returns and exchanges

Apps can refund an order with line-level restocking through the refund operation, but there is no return workflow: no return request, no receive or inspect step and no exchange.

• Workaround: Handle returns in the app-hosted flow, then refund the order with POST /orders/{order}/refunds; send the returned lines in line_items to put the stock back.
• Example apps that depend on it: None of the example apps depend on it.
• Details: Returns and exchanges

Discounts and coupons

App checkout validation rules

No app extension point validates a cart or order on the server beyond the platform’s own request checks.

• Workaround: Enforce merchant-side rules through discount targeting and coupon limits when you create them.
• Example apps that depend on it: B2B wholesale app
• Details: App checkout validation rules

Payments

Create and resolve payment sessions

App credentials expose no payment-session endpoint. Queek checkout runs the merchant or platform provider flow, so an app cannot create, resolve or reject a payment session.

• Good to know: Apps cannot start Queek checkout payments or receive payment-session callbacks through app credentials.
• Workaround: An installed app can import orders already charged on its external platform with POST /orders/import. This records the payment but does not create or resolve a payment session.
• Example apps that depend on it: Payment gateway app, Subscriptions app
• Details: Create and resolve payment sessions

Shipping and fulfilment

Live carrier rates at checkout

A shipping app cannot return live rates into checkout. Apps can manage static shipping zones, but checkout has no carrier callback for live quotes.

• Workaround: Keep merchant-configured flat zones, or quote live rates on the app-hosted page before handing the shopper to checkout.
• Example apps that depend on it: Shipping carrier app
• Details: Live carrier rates at checkout

Tax

App-calculated tax at checkout

Apps have no tax-calculation callback, and there is no tax-provider integration. Checkout applies only the tax rows the merchant configured.

• Workaround: Ship jurisdiction logic in the app-hosted flow and keep the store rows aligned with it.
• Example apps that depend on it: Tax app
• Details: App-calculated tax at checkout

Subscriptions

Recurring purchases

The subscription feature bills merchants for their Queek plan, not shoppers. Apps get no customer subscription plans, billing contracts, renewal orders or billing attempts.

• Workaround: Bill repeat purchases outside Queek and create each order through normal checkout when it is due.
• Example apps that depend on it: Subscriptions app
• Details: Recurring purchases

B2B

Company catalogs and price lists

Apps have no company, contact or location model, no negotiated catalogs or price lists, and no company payment terms. Price resolution stays on the single customer-price path.

• Workaround: Keep the business-buyer mapping in the app database; it cannot change the platform price.
• Example apps that depend on it: B2B wholesale app
• Details: Company catalogs and price lists

Markets and translations

Regional catalogs and display currency

Apps have no market, catalog or currency-context API. Currency is store and provider configuration, with no market-specific publication.

• Workaround: Run one store per currency region and convert for display on the app-hosted page.
• Example apps that depend on it: B2B wholesale app, Marketplace channel feed, Tax app, Translation app
• Details: Regional catalogs and display currency

Storefront

Shopper account extensions

Apps cannot mount on shopper account pages: there are no full-page, order, profile or block targets in the signed-in customer area.

• Workaround: Serve account-adjacent features on the app-hosted page with the customer reads.
• Example apps that depend on it: Reviews app
• Details: Shopper account extensions

Run consent-aware tracking pixels

Apps have no pixel runtime for shopper events, consent-gated execution or conversion delivery.

• Good to know: Storefront page-view tracking is not an app event subscription, and apps cannot register a pixel or receive consent-aware conversion events.
• Good to know: The store itself can run Meta, TikTok and Pinterest browser pixels from ids the merchant sets (page view only, after the shopper accepts marketing cookies). An app cannot set, read or add to them.
• Workaround: Ask the merchant to enter the network id in the dashboard Ad pixels card, or use the app backend for server-side events it can observe through the webhooks; do not install shopper-side tracking through Queek.
• Example apps that depend on it: None of the example apps depend on it.
• Details: Run consent-aware tracking pixels

Platform

Workflow automation

Webhooks are notifications, not workflows. There is no trigger and action registry, no merchant workflow builder and no run history.

• Workaround: Consume webhook events and run app-owned automation on the app server.
• Example apps that depend on it: Automation app
• Details: Workflow automation

App billing and usage metering

Manifest pricing is display-only. There is no app-charge, recurring-billing or usage-metering API, so apps are free or bill outside Queek.

• Workaround: Bill on the app-hosted page with an off-platform provider; gate features by installation in the app database.
• Example apps that depend on it: None of the example apps depend on it.
• Details: App billing and usage metering

POS extensions

The POS is a first-party client with device sign-in and sync. App manifests have no POS target and there is no scoped POS bridge, so a third-party app cannot add tiles, cart actions or panels.

• Workaround: Apps use the Merchant API where their credential permits; nothing renders inside the POS.
• Example apps that depend on it: POS extension app
• Details: POS extensions

Not offered by design

Queek does not offer these to apps on purpose, so they are not on the roadmap. Each says why and what to use instead.

Loyalty points ledger

Apps keep their own points ledger and reward customers with discount codes created through the Merchant API.

• Workaround: Credit points off paid-order webhooks in the app database and reward with coupons; reconcile reversals off cancelled-order events.
• Details: Loyalty points ledger

Tailor checkout delivery options

Queek presents one resolved Delivery option per order; shape the offer with shipping zones and the store’s own delivery settings.

• Workaround: Shape the offer with the merchant-configured fulfilment modes for each store.
• Details: Tailor checkout delivery options

Manage storefront theme assets

Queek does not let apps inject scripts into storefronts or edit theme files. Use storefront embeds and product-page app blocks instead.

• Workaround: Use registered storefront blocks for app content, or ask the merchant to make theme edits in the storefront editor.
• Details: Manage storefront theme assets

Send shopper messages

Apps send through their own email or SMS provider. Queek provides consent state and events, not a send API.

• Workaround: Send through an app-owned provider. Read Queek’s campaign audience and channel consent state, report consent and suppression changes through the consent endpoints, and handle STOP replies with the provider.
• Details: Send shopper messages

Active carts

Carts belong to the shopper session. Apps do not read live carts; they see the order once it is placed.

• Workaround: Share the storefront cart URL into the chat and read the converted order through the order webhooks.
• Details: Active carts

Call an AI runtime from an app

Apps bring their own model. Queek does not host a model for apps to call.

• Workaround: Call an AI provider from the app server and keep provider credentials and usage controls there.
• Details: Call an AI runtime from an app

Checkout UI extensions

Checkout stays one platform path so the price and the payment are exactly what the shopper saw; collect extra input on product blocks, through order attributes, or on an app page before checkout.

• Workaround: Collect input and payment on the app-hosted page before handing off to checkout.
• Details: Checkout UI extensions