Products, offers and payment

Products, offers and orders belong to the project. A site purchase and a Telegram purchase use one catalogue and a shared order history.

Product and offer

A product describes what you sell. An offer sets the terms: contents, price and sales window. The same product can appear in several offers, such as a regular offer and a promotion.

Manage them in Data → Products and Data → Offers. Use this catalogue when you need orders and access, rather than creating a duplicate in a custom collection. Collections are useful for additional data such as leads, forms and bookings.

Archive retired offers to preserve order history.

Prices and provider

An offer needs a price and an active way to receive payment. Available currencies and methods depend on the provider and its binding to the offer. When a price or price-transfer mode is incompatible with the provider, readiness checks report the problem. An “active” label alone is not enough.

Discounts apply to an existing offer with their own conditions and deadline. Before sharing an offer, check the final price and payment method the buyer will see.

Payment link

Use a platform link or the site's checkout page rather than copying a temporary provider invoice. The platform checks current conditions and creates a fresh invoice when needed. A link does not bypass a closed sales window, an unavailable price or missing delivery.

How buyers receive their purchase

• On the site — a published protected page or course is linked to the product and access conditions. Purchase access is checked for the signed-in person.
• In Telegram or project automation — an active flow handles successful payment and delivers an invite, message or another configured action.
• Outside the platform — for manual delivery, describe exactly how the buyer receives the service or materials. This is an explicit setting, rather than an unfinished flow.

Do not add duplicate delivery to a flow when purchasing the product already provides the site's access. An instruction message can supplement access, but cannot replace its check.

Readiness to sell

The offer card includes a readiness check for payment, the sales window and delivery. Blocking failures prevent offer activation, order creation or publishing a site with checkout. If a dependency breaks after activation, fix it; offer status alone does not prove readiness.

A settings check does not prove delivery. Follow the pre-launch checklist from purchase to actual access.