What Offer Suite is
| Fact | Answer |
|---|---|
| What it is | Realized profit for Shopify brands, then the offers and experiments that move it, run by the brand's own agents through an API. It is not open yet: brands join a waitlist. |
| Who it is for | Shopify brands, starting with those that sell bundles, gifts or subscriptions, and the agents and developers who work for them. |
| What it shows on install | Realized profit per store and per item from the store's last 60 days of orders, or up to a year once the store grants access to all orders, net of refunds and costed at the costs in effect on each order's date. Orders placed before the brand's first offer count toward the store and its items, not toward an offer. |
| What it reports | Forecast and realized profit per offer and per option once an offer sells, after every cost the brand enters, net of refunds, with first orders and renewals apart and each order costed at the costs in effect on its date. |
| What an offer is | A custom offer is one validated, versioned document: tiers, bundles, subscribe and save, build-your-own picks, add-ons and free gifts. An agent writes it through the API or MCP; there is no offer type to choose. |
| How a price goes live | Every visible option is checked on a real Shopify cart before it goes live, so what the page shows is what checkout charges. A version that fails a check stays a draft, and the live version keeps selling. |
| How shoppers see it | Through a theme block that draws the buy box, the brand's own code on the public API, or an agent. What the page shows is what checkout charges. Offer Suite supplies the data and the cart; it never builds the brand's page. A browser SDK and React bindings are not available yet. |
| How offers are tested | An experiment splits an offer's traffic between its live version and up to three challengers and is judged on realized profit per visitor, never on conversion. |
| How it is operated | Through a hosted MCP server, an HTTP API described in OpenAPI 3.1, a Shopify app inside the store's admin, and a dashboard for the brand's team. |
| Platform | Shopify only. |
| Who runs it | Blackout Media, a company established in Brazil. |
What runs in production
Production is the service invited brands use. Each feature page says, part by part, what runs there and what it does not do yet. Offer Suite is not open yet, so nothing on this site reports a customer's results.
| Feature | What it does | Product | Availability |
|---|---|---|---|
| Profit | Forecast and realized profit per offer, option, version, item and traffic source from one margin engine in whole cents, with ad spend, realized CAC and subscription LTV. | Profit | In production |
| Costs | Costs live in an append-only, dated ledger: a correction recosts past orders in the current view; the as-recorded view keeps what each order was booked with. | Profit | In production |
| Tracking | Shopify orders are attributed to the offer, option and version that sold them and to the traffic that brought the buyer, with a funnel that keeps confirmed sales apart from browser tracking. | Profit | In production |
| Offer documents | An offer is one validated, versioned document your agent writes: tiers, bundles, subscriptions, gifts and prices, with no offer types to pick from. | Offers | In production |
| Publish and verify | Publishing writes the offer to Shopify, builds a real cart for every visible option and goes live only if each one charges what the offer promises. | Offers | In production |
| Buy box | Show a verified offer through the Verified offer theme block, your developers' code on the public API, or your agent, with every price computed by the server. | Offers | Includes parts not in production yet |
| Post-purchase | Show one offer on Shopify's post-purchase page after the purchases you choose, charged at exactly the option's price and booked to the offer that sold it. | Offers | In production |
| Experiments | Test a live offer against up to three verified challengers on realized profit per visitor, with always-valid statistics and a daily real-cart guardrail. | Experiments | In production |
| Agents | Agents run Offer Suite through the hosted MCP server or plain HTTP and an OpenAPI 3.1 document, with one error shape and a confirm to publish over MCP. | Run it | In production |
| Shopify app | A Shopify-managed install, an App Home inside the admin, Sidekick answers, a standalone dashboard for your team, and a daily sync that repairs what drifted. | Run it | In production |
What is not available yet
The parts a feature page marks as missing or partly available. Each page's own list, "What it does not do yet", is longer and says every limit.
| Part | Feature | Availability |
|---|---|---|
| Renewals are not yet linked back to their first order, so LTV runs on renewal curves you supply, not on observed ones. | Profit | Partly available |
| The browser SDK is not published yet (no npm package or hosted script). Your developers call the HTTP API directly. | Buy box | Not available yet |
| The React bindings are not on npm either. | Buy box | Not available yet |
The <os-offer> element ships only inside the theme block; it is not hosted as a script of its own. | Buy box | Partly available |
Neither the theme block nor <os-offer> draws category builders (options with several category groups or a unit cap); price those through the API. | Buy box | Partly available |
| No command-line client is offered. | Agents | Not available yet |
| One store per workspace for now: each install creates its own workspace, and a second store cannot join an existing one yet. | Shopify app | Partly available |
What has been measured
Every figure the feature pages cite, with where it happened and when. None is a customer's result or a production volume.
| Figure | What it is | Where | When |
|---|---|---|---|
| 878 carts | Offer Suite's prices matched what Shopify charged on 878 real dev-store carts. | A development store | 28 September 2026 |
| $21.47 | On the first real order, the realized margin ($21.47) matched the forecast to the cent before the estimated refund and processing rates; the full forecast, rates included, was $17.87. | A development store | 16 September 2026 |
| $58.60 | A full paid order went through the Verified offer theme block on a Plus dev store (order #1033, $58.60). On a Basic-plan dev store the block's cart reached a checkout charging the $800.00 it showed; no order was placed there. | A development store | 29 September 2026 |
| 48 of 48 | One category-builder offer had 48 of 48 options matched and 377 of 377 audit carts, and test order #1023 charged $154.06. | A development store | 29 September 2026 |
| 338 ms | Measured from São Paulo, serving an offer fell from 1,389 ms to 338 ms at the median, uncached. Production latency has not been measured. | The development API | 16 September 2026 |
| 1 call | In an internal test in September 2026, a fresh agent with only the MCP resources wrote a valid offer on its first create_offer call. | The development API | 16 September 2026 |
| 2 of 2 | On two test checkouts on a dev store, the buyer accepted the post-purchase upsell and Shopify charged exactly the promised cents: $69.95 at catalog price, and $10.50 after a $4.50 discount. Each accept was recorded as applied to its order within 20 seconds. | A development store | 3 October 2026 |
| $11.43 | On the second test checkout on a dev store, the post-purchase page showed the added line's $15.00 catalog price struck through and $10.50 after the $4.50 discount; Shopify added $0.93 tax and no shipping, and the buyer paid $11.43 in one click. The accept was recorded as applied 11 seconds later. | A development store | 3 October 2026 |
| 78 tools | The production MCP server has 78 tools, one per operation in https://api.offersuite.io/openapi.json. | Production | 3 October 2026 |
The waitlist
| Fact | Answer |
|---|---|
| What it is | The only way in today. Offer Suite opens to Shopify brands a few at a time; a brand tells us about its store on the waitlist form. |
| Who is invited first | Brands that sell bundles, gifts or subscriptions. |
| What happens next | The answers reach us by email. When Offer Suite opens to a store like the brand's, we write to it with an invitation. |
| When | No dates are set, so none is promised. |
| What is kept | Nothing on our servers. The email is the only record, and privacy@offersuite.io deletes it on request. |
Where agents reach it
| What | Address | What it needs |
|---|---|---|
| The API, described in OpenAPI 3.1 | https://api.offersuite.io/openapi.json | An invited workspace's key |
| The MCP server, one tool per API operation | https://mcp.offersuite.io/mcp | An invited workspace's secret key, sent as a bearer token |
| The calculators as an API | https://offersuite.io/api/calculators | Nothing |
| The calculators as an MCP server | https://offersuite.io/mcp | Nothing |
| This site's pages, one line each | https://offersuite.io/llms.txt | Nothing |
| This site's pages in full, in one file | https://offersuite.io/llms-full.txt | Nothing |
| Any page of this site as markdown | Its address with .md added, such as https://offersuite.io/llm-info.md; the homepage is https://offersuite.io/index.md | Nothing |