Stages and gates
Sales stages are defined per installation; when stage gates are on, an opportunity advances only once it meets their conditions.
Each installation's sales pipeline is defined on the Settings → Stages (Ayarlar → Aşamalar) page: the key, name, and color of each open stage; the names for won, lost, and canceled; whether the Cancel stage is enabled; and the stage rules.
Stage keys
The API always uses the key; the name is what users see. The closing keys are fixed:
| Key | Meaning |
|---|---|
Win |
Won |
Lost |
Lost |
Cancel |
Canceled (may be disabled in the installation) |
Account |
Customer-tracking container (not counted in the sales funnel) |
Open stage keys are specific to each installation. For example, the Technical sales process — 8 stages preset uses Qualify, Viable, Present Solution, Negotiation, Expect to Close, while a new installation defaults to the Quick start — 4 stages preset with Lead, In Progress. Pick a preset in Settings → Stages, then edit the stages freely (Pipeline and sales forecast). Don't hard-code keys — read them from the GET /api/v1/me response:
"constants": {
"stages": ["Qualify", "Viable", "Present Solution", "Negotiation", "Expect to Close", "Win", "Lost", "Cancel"],
"open_stages": ["Qualify", "Viable", "Present Solution", "Negotiation", "Expect to Close"],
"stage_labels": { "Qualify": "Qualify", "Win": "Win", "Lost": "Lost", "…": "…" },
"stage_sla": { "Qualify": 30, "Viable": 60, "Present Solution": 60, "Negotiation": 30, "Expect to Close": 15 },
"stage_rules": true
}Stage gates
Gates are edited in Settings → Stages → Rules — in every pipeline, not only the technical sales process:
- Stage gates switch: when on, a deal's exit conditions for its current stage are checked before it moves forward; when off, stages change freely.
- Move in order: forward moves go only to the next stage. When off, stages can be skipped; the skipped stages' conditions are checked too.
- Exit conditions: click the stage's row in the gate map (or Exit conditions in the stage drawer) and pick from the list with Add condition. Each condition either Blocks (no move until it's met) or Warns (the move goes through, the gap is pointed out); up to 10 conditions per stage.
- Won: which stages it can be chosen from (all selected = any stage) and extra To win conditions. The current stage's exit conditions also apply when winning.
- Moving back, Lost and Cancel are always free. A closed deal can't be reopened; Revive opportunity creates a new record.
- Reset to default brings back the pipeline's default gates. Applying a preset or template also resets the gates to its defaults.
Conditions:
| Condition | Met when |
|---|---|
| BANT 4/4 | Budget, authority, need and timing are ticked |
| Decision maker linked | At least one person is linked to the deal (decision makers or the person met) |
| Product selected | A product is set on the deal |
| Amount entered | Quantity × price or an estimated amount |
| Close date current | The expected close date hasn't passed |
| Meeting held | A visit, call or online meeting since the deal started |
| Face-to-face meeting | An in-person visit since the deal started (online counts if the workspace setting says so) |
| Trial held · Trial positive | A trial record · the latest trial is Successful or Partially Positive (Trials module) |
| Quote price · Quote record | A quote price (or estimated amount) is entered · the deal has a saved quote |
| Order received | The first order linked to the deal |
| Checklist complete | The stage's checklist steps are done |
| Next step planned | A dated next step, follow-up or task for today or later |
| Custom field filled | The chosen deal custom field isn't empty |
Default gates of the technical sales process preset: Qualify → BANT 4/4 · Viable → face-to-face meeting + product · Present Solution → positive trial · Negotiation → quote price; in order; Win only from Negotiation and Expect to Close. As long as you don't change the gates, behaviour is the same as in earlier versions.
If a blocking condition isn't met, the stage endpoint returns 409 gate:
{
"ok": false,
"error": "gate",
"message": "Viable aşamasına geçmek için: Fırsata en az bir karar verici (kişi) bağlanmalı",
"gate_problems": ["Fırsata en az bir karar verici (kişi) bağlanmalı"]
}The single-deal endpoint carries gate_ok, gate_problems (blocking), gate_warnings (warn-only) and next_stage; the full gate setup is in GET /api/v1/me → constants.stage_gates. The stage strip on the deal page shows the current stage's conditions with ticks, and Quick Entry warns by the same rules when you pick a stage.
Durations (SLA)
Each open stage has a target in days (stage_sla), and each opportunity has a total lifetime (opp_lifetime_days, 180 days by default). Overruns show up as negative values in the opportunity's sla_left and lifetime_left fields and lower its health score. The values vary by installation and are set on the Settings → Stage setup (Ayarlar → Aşama kurulumu) card.
Checklist
Every open stage has a checklist: when an opportunity enters the stage its steps open on the opportunity, and a step with a due date shows up in Actions. Edit the list in the stage details in Settings → Stages (drag to reorder, Enter to add).
- While stage gates are on, the Technical sales process steps are locked: they complete themselves when BANT boxes, a face-to-face visit, a product, a trial result, an offer price and an order are entered. You can add your own steps to these stages; they come after the locked ones.
- In other stages (and with gates off) the list is entirely yours.
- Existing opportunities get new steps when their page is opened; steps removed from the list stay on those opportunities.
Winning and losing
Win: the company becomesAC(active customer), the line items of the accepted quote are written to the company as contracted prices, a draft contract is created if the Contracts module is enabled, and theopp_wonevent is sent to apps.Lost/Cancel: thereasonfield is stored as the loss reason (constants.loss_reasons;Diğer(Other) if the reason isn't in the list). OnLost, theopp_lostevent is sent to apps.- Every stage change also sends an
opp_stageevent (with the old and new stage).