The deal card is where your sales team lives: the closer its fields match your actual process, the less data gets lost between a call and a contract. In Bitrix24 (Alaio), deal fields come in two kinds — system and custom — and you can hide them, group them into sections, make them required per stage, and fill them automatically. Let's walk through all of it, from "how do I add a field" to visual widgets inside the card.
Which deal fields exist by default?
System fields are created by Bitrix24 itself: Title, Amount and currency, Stage, Responsible person, Client (the contact/company link), Deal type, Source, created and closed dates. You can't delete them, but you can hide them from the card or rename their labels. System fields are wired into CRM mechanics — the kanban and the funnel are built on Stage, reports run on Amount — so repurposing them ("let's append the contract number to the title") breaks both filters and analytics.
How do I add a custom field to a deal?
Two ways. The quick one — right from the deal card: "Create field" at the bottom of the field list, pick a type, name it. The systematic one — CRM → Settings → Field settings → Deal: here you see every field at once, including the ones colleagues created on the fly. The field type is chosen at creation and cannot be changed later — if you picked wrong, you recreate the field and migrate the data. Bitrix24 allows up to 1,016 custom fields per entity type, but the practical limit arrives much earlier: a card with fifty fields is unreadable. The rule of thumb: create a field only for what you will filter by, report on, or automate; everything else belongs in comments and the timeline.
How do I keep the deal card organized?
Fields group into sections: drag them in card-settings mode and assemble thematic blocks — Finance, Logistics, Documents. Card layout can be personal or shared: "Set for everyone" pushes your layout to the whole team; otherwise each person stares at their own chaos. Hide unused fields — they stay in the data and filters but stop cluttering the card. Separately, check the quick deal creation form (the one that pops out of the kanban): it should contain only fields known at creation time — otherwise managers type "whatever" just to save.
How do I make deal fields required?
Requiredness is set per field in the card: "always required" or "required at a stage". For deals, the second is almost always right: Budget becomes required when moving into Negotiation, Loss reason — only at the Lost stage. The card fills up as the deal moves down the funnel instead of collecting garbage at creation. Keep in mind: the check fires only on manual moves in the UI — imports, the API, and automation rules bypass it. The full mechanics, bypasses and countermeasures are in our dedicated guide to required fields.
How do I fill deal fields automatically?
Four typical operations. Writing a value — the stock "Edit item" rule or a workflow step. Clearing — the Clear field robot: it properly empties any field type, including lists and multiple fields where an empty string doesn't work. Moving data between the deal and related entities — the pair Get related entity field and Set related entity field: read the city from the contact into the deal for reporting, or push the deal status into the company card. Checking a field is filled before generating a document or changing stage — Check field is not empty returns Y/N, and the process either proceeds or creates a follow-up task.
How do I make the deal card visual?
Stock field types display data as text. For a card a manager scans in a second, that's not enough — this is where widget fields from the Roboteka field type catalog come in: Color status paints the deal state as a colored badge, Progress bar shows completion as a bar, Deadline countdown counts days to a date and changes color as it approaches, Formatted money renders amounts with digit grouping and currency, Link button turns a URL into a clickable button, and Star rating shows a client score as stars. Such a field is added to the card like any custom field — only its type comes from an app; the values are stored by Bitrix24 itself.
Common mistakes with deal fields
Duplicate fields: before creating "Project budget", check field settings for an existing "Budget" — data smeared across two fields can't be joined by a filter. A string instead of a list: filters and reports don't work on free text. "Always required" instead of per-stage — garbage at creation time. Fifty fields with no sections — a card nobody reads. And zombie fields: audit field settings quarterly and retire what nobody fills anymore.
Summary
Deal fields are the skeleton of your sales process: leave system fields alone, create custom ones only for filtering, reporting and automation, assemble the card into sections and share the layout, attach requiredness to stages, hand filling and checking to automation rules, and add visual clarity with widget fields from the Roboteka catalog. Missing a robot or a field type for your case — describe the task, we build it for free and add it to the shared library.