Products

Register sellable products/services with description and price. A product can have versions and price history; packs per client control what each client has contracted (including environments).

Products, packs, versions and prices — this is the role of the "Products" screen within the platform.

Beyond price, this is where you say whether the item is RECURRING (generates revenue every month, feeds MRR and churn) or one-off. That choice changes reports, forecasts and profitability — it is the most important decision on the screen, and the easiest to leave at the default without thinking.

Creates and edits a product in a master-detail: the data tab holds name, description, group and status; Packs is the detail tab where the product's compositions are recorded; and Prices and Versions are grandchildren — each price and each version belongs to a pack, not directly to the product. There is also the "Chat" tab to talk with the product's persona via AI. Save the product first: the dependent tabs only work once the record exists.

This list runs on the standard engine: it exports Excel, PDF and CSV of the whole set (not just the visible page), keeps saved views and column preferences per user, and has a recycle bin reachable via ?excluidas=1 in the URL. Search and filter work by link — ?q=text and ?fd_=value open the list already narrowed down —, so any slice of the catalog can be shared by URL. And Ctrl+K, on any screen, searches the platform's screens by name or synonym.

In the price dialog you enter base price, discount, commission and tax — and the final price is calculated on the spot, in a read-only field: you can't type a final that doesn't add up with the components. Each price has a validity period (start and end), which preserves history: a price increase means creating a new price with a new validity, not overwriting the old one. The whole Prices tab only appears for those with the "View Amounts" permission in their profile.

The list's "current price" comes from the product's price registration, which is recorded per pack with a start and end validity: the value shown is what applies today. An adjustment doesn't overwrite — a new price is created with a new validity, and the previous one is preserved as consultable history in the product's form (Prices tab, visible to whoever has "View Values"). This way you can answer how much it cost on any date, without spreadsheet archaeology.

When you save a view with the Views button, it stores four things: the search text, the applied filters, which columns appear (and in what order) and which column the list is sorted by. Applying the view restores everything at once — including resetting the sort and the page you were on, so the result is exactly what the view describes. Views saved before this version remain valid: whatever they didn't store simply doesn't change when applied.

Nas fichas, sair de um campo já dispara a conferência do que dá para conferir na hora: campo obrigatório deixado em branco e e-mail mal formado. O aviso aparece embaixo do campo e desaparece quando você começa a corrigir. Campo numérico não precisa de aviso: ele simplesmente não aceita letra enquanto você digita. Isso é conforto, não a validação final: ao salvar, o sistema confere tudo de novo do lado do servidor.

The gear next to the search opens the list Preferences: rows per page, wrap lines, striped rows, compact mode and the visible columns, in the order you drag them. You can also drag and widen the columns in the header itself, and the order is saved. The actions of each row are in the ⋯ of the last column: favorite, view, edit, duplicate, open in new tab and send to the trash. Clicking the row opens the record.

The download icon, in the right corner of the view tabs strip, takes what is filtered in the list: Excel or PDF with all the rows of the filter, not just the page. The full CSV brings the whole base, with all fields, and asks for your password — it is logged under your name.

The "Add price" and "Add version" buttons stay disabled while the product has no pack — because price and version are recorded per pack, not for the standalone product. The order that works: save the product, register at least one pack in the Packs tab, and only then record prices (with start and end validity) and versions (with publication date and status). A product with several packs can have a different price and version for each composition.

In the record's activity panel, each note has "Turn into request". The click creates a ticket with the note's text, who wrote it and the link to this record — nothing is retyped. Use it when the note is a request for action ("someone needs to review this"); the note stays where it was. The button only appears once the record has been saved; a read-only session (demo) doesn't create one.

Whoever has permission to view this screen in their profile, with the module unlocked in the plan. The verbs create, edit and delete are granted separately per profile — you can browse the catalog without being able to touch it. And there's an extra layer here: the current-price column and the form's Prices tab obey the "View Values" permission, so a user may see the products and still not see how much they cost.

Open the record and look at the Timeline on the right: it shows each change as "from one value to another", with the person and the date. When there are many changes, use the two filters at the top of the timeline — one by field, the other by person. The search runs in the database, so old changes show up just the same. You can also ask Tenkai: "who changed contract 482?".

"Where do I see products?" — whenever that question comes up, this is the screen that answers it.