Skip to content

Products and offerings

Your catalog is made of three pieces. This page says what each one is and how you create it in the portal.

They stack. A product holds features. An offering prices a product and decides which of its features a buyer gets. Nothing is for sale until there is an offering.

A product is your app, as Monaiq lists it: the thing a license unlocks. It is the subject of the license, not the thing with a price on it.

You create and edit products at monaiq.com/manage/products. One product can carry any number of offerings. That is how you sell the same app at several prices, or on several schedules.

A product is Draft until you make it Active, and its offerings sell only once it is. While a Draft product has an offering ready, your Home lists it under Needs you. If you are keeping it off sale on purpose, choose Not for sale yet on its status menu and Home stops asking; making it Active clears the mark.

The Products page shows each product’s licenses held, the customers holding one, and what was paid this month: money in this calendar month (UTC), before refunds and fees.

A feature is a part of your app that a license turns on. You define features on the product, then choose per offering which of them that offering includes. A basic offering and a full one can point at the same product and differ only in the features attached.

There are four kinds. Choose New feature on the product’s features page, then answer what the feature does. You set each offering’s number in Pricing.

Kind Your answer What the customer gets
Access Unlock a part of your app The part of your app is on, or off, such as Export to PDF.
Rate limit Cap how fast it can be used So many uses per second, minute, hour or day, or unlimited, such as API calls.
Allowance Limit how much it can be used So many uses per seat each billing period, such as AI generations. Choose No cap to count every use without refusing any.
Limit Set a number your app holds to A number your app keeps to, or unlimited, such as 10 projects or 90 days of history. Your app counts against it; the platform does not.

A Limit needs SDK 2.4.0 or later. An older .NET SDK fails the whole authorization for a license carrying a Limit, not just that feature, so update your app before you add one.

A seat is one person or device on a license. A billing period is the period one invoice covers: a month, on a monthly offering.

Counting uses needs your app to report them. Consumption and metering is the developer page for that.

An offering is what a customer buys: a price and a schedule, for one of your products, with the features you attach. You create offerings from the product’s page at monaiq.com/manage/products.

There are two, and you choose one per offering.

Pricing model What the buyer pays Schedule
Subscription The price again every period, until they cancel A schedule you set, in days, weeks, months or years, up to a year apart
One-time purchase The price once None

A price is 0, which makes the offering free, or at least the smallest payment Stripe takes in its currency, such as 0.50 USD. A price below that is refused when you save it, and the message says the smallest price you can set. A per-use price is not held to it.

A subscription can also bill for usage: give a feature a per-use price, and the uses your app reports are billed for the period they happened in, on top of the recurring price. A one-time purchase has no billing period, so its uses are counted and shown in Usage but never billed.

The price you set is the price of one seat. The buyer picks how many seats at checkout, on the marketplace, on your storefront, or inside your own app. They pay that price for each seat, on the first payment and on every renewal. Monaiq issues one license with a seat for each, under one subscription.

Each seat has its own license code and shares the license’s features. Who holds which seat is decided outside Monaiq, by the buyer or by your own server. Seats can be added or retired later, by the buyer in the portal or by your server. The HTTP API reference is the developer page for that.

Monaiq’s own plans are one seat and cannot be bought in multiples.

Allow more than one seat. The box shows for subscription and one-time plans. It starts ticked for a plan with a base price and unticked for a plan with no base price. With it ticked, the buyer can pick several seats at checkout and add more later from their license page; with it unticked, a license of the plan holds one seat. A free plan always has one seat, so the box matters for pay-as-you-go plans: tick it to let a pay-as-you-go license hold more than one seat. Each seat carries the full allowance of every allowance feature, so a trial is always one seat.

On a one-time purchase, the buyer pays for added seats once, from their license page. Your own server cannot add seats to a one-time license, because it cannot pay for the buyer.

An offering is a plan: a customer holds one plan of a product at a time. Buying a second plan of the same product is refused with a pointer to change plan, so a customer never pays for two overlapping tiers. A customer who already holds a live license of an offering cannot buy that same offering again; they add seats to the license they have, where seats are allowed.

A paid plan ends only when you cancel it. Buying never ends what a customer paid for: a free plan or a trial is replaced by the paid plan they buy, but a one-time plan is never replaced. A customer who holds a one-time plan and asks for a subscription of the same product is refused and told to ask you, with your support contact. To move them, cancel the one-time license (with the refund you choose, see Customers), then they subscribe.

Add-on. Tick Add-on on a paid offering that customers should hold alongside their plan, such as extra storage on top of Pro. Add-ons sit outside the one-plan rule, so a customer can hold a plan and any number of add-ons. Leave it off and the offering is a plan.

Change plan. A customer on a paid plan changes plan from their license page. The choice lists your other public plans of the product. The seats move to the new plan and keep working, and the license, its history and the seat codes stay the same.

  • A subscription can change to another subscription. A dearer plan changes now and the customer is charged the difference for the rest of the period, or nothing when it is too small to be charged; a cheaper plan takes effect at the end of the period they have paid for, with nothing credited.
  • A change to a plan billed at a different interval, monthly to yearly say, starts the new period now: the customer is charged the new plan in full, less a credit for the unused time on the old one.
  • A subscription can change to or from a pay-as-you-go plan. Moving to pay as you go takes effect at the end of the paid period; moving to a priced subscription changes now and charges its price for the rest of the period.
  • A one-time purchase can change to another one-time purchase. A dearer plan costs the difference, paid once; a cheaper or equal plan changes straight away, with nothing charged and nothing refunded.
  • Plans billed in different ways cannot be switched into each other. A customer on a subscription cancels it, then buys the other; a one-time purchase only you can cancel.
  • A plan with more than one seat can change only to a plan that allows more than one seat. If the new plan is one seat only, the customer retires the extra seats first.

The new plan’s allowances apply as soon as the plan changes, which for a cheaper plan is the end of the period.

A free trial is an offering in its own right. You publish a trial offering for your product, alongside the paid ones, and buyers start there. You set the trial length in days on the offering, from 1 to 90; the default is 7 days.

Trials do not auto-renew. A trial that reaches its last day ends rather than rolling into a paid period on its own. A trial is one seat, and a free plan or trial is once per account: a customer who has had it before cannot start it again. A customer on a paid plan of the product cannot start a free plan or trial of it. A customer on a free plan or trial buys a paid plan with plain Buy, and the paid plan replaces the trial: the trial ends when the paid license starts.

Each offering sits in one marketplace category. That is how buyers browsing the marketplace narrow down to things like yours. The categories are:

  • Developer tools
  • Data and analytics
  • AI and automation
  • Integration
  • Security
  • Productivity
  • Infrastructure
  • Other

Create the product first, then its features, then an offering that prices it. Leave the offering in Draft (not for sale yet) while you are still deciding. Nothing is visible to buyers until you make it Public. Publish to the marketplace covers that step.

If you would rather have your AI assistant build the catalog with you, it can create the same products, features and offerings. See Integrate.