What it is
An engine is one of six: forecasting, baseline, pricing, families and attributes, replenishment, verdicts. Each one computes a figure from your data on a schedule; everything else on a page is a read of something you or a connected system put in. Four of the six are the engines the platform is named by: the forecast, the baseline that grades a style for an account, the pricing engine that measures price response, and product information with family joins and attributes. Replenishment and the weekly verdicts run on the same record and speak in the same words, so a customer meets one vocabulary for all six.
An engine figure can carry four things: when it was computed, how far the data behind it reached, a provenance word, and a confidence word. Every engine answers "did you run?" in the same eight states, so a Late forecast and a Late grade read the same. Those two ideas have their own articles: Provenance words and Engine states.
How Tightly decides it
Most engines run inside every sync. When your sales land, a chain follows: sales velocity, attribution and forecast confidence, then the forward forecast, the grades, the buy, product tags and price response. Three run weekly: the Monday re-score of forecast methods, the Monday accuracy pass, and the weekly verdicts, whose walk runs every night but Sunday so a Monday that did not finish is scored on a later night. Analogs refresh daily.
Each run of the sync's chain leaves a record: what ran, when it started and finished, what it wrote, or which of the reasons it did not run. The re-score, the accuracy pass and analogs leave none the page reads yet, so they read Not measured; the weekly verdicts now leave one too, so an empty ledger reads No weekly verdict has run yet. rather than Not measured. That record is what a page reads for its as-of and its state word, so the page's date is the run's date and never the clock on your wall. You never see the record itself; you see the state, the true as-of, and one sentence when something needs saying.
The words on the face
| Engine | Its name on a page | Where it shows | Its words |
|---|---|---|---|
| Forecasting | Forecast | Demand forecasting and its Forecast performance drawer, a product's Demand tab, a variant's Demand pane; the desk's Demand column on Tightly Pro | Own record, Borrowed method, From an analog, Fallback method; Watch closely, New item |
| Baseline | Grades | An account's pages in Tightly Connect, on Essentials+ and Pro; the showroom's Grade column and the buyer's Forecast for my stores on Tightly Pro | Winner, Sleeper, Bleeder; measured, borrowed, brand; Sell-in only |
| Pricing | Price response | A variant's Price intelligence tab; the Price sensitivity column on Sales performance | measured, borrowed, prior; High, Moderate, Low, Inconsistent, Still learning |
| Families and attributes | Attribution, Analogs | Catalogue, Families, Analogs and a product's Attributes tab, on Essentials+ and Pro | declared, measured, auto, default, connector; Measured, Not yet measured, Refused |
| Replenishment | The buy | Smart Replenishment on Lite, Essentials and Essentials+; the Commitments desk, the Bench and the Reorder lines on Pro | from system, from an analog, past the forecast, lower confidence |
| Verdicts | Weekly verdicts | All commitments, a room's five and This week, Hindsight, Home and Today, on Tightly Pro | on plan, approaching, breached; firm, thin, not measured |
In the retailer chair the same six engines run under the chair's words: the baseline engine grades a vendor's style from your own store history and prints Vendor grade, a second key and not a second engine.
What you can do about it
Nothing is pressed to make an engine run; each follows your sync. The forecast holds the one act a customer has, Recalculate now, for any seat that can write, once every two hours; on Demand forecasting it stands beside the engine's sentence under Forecast status in the Forecast performance drawer. Where an engine's source is paused, its door is Integrations, and the sync's own state is repaired there. Everything else waits for the next run, which retries on its own.
An engine that is Late changes only the as-of line. Stale or Failed puts one sentence on the page and one row in your Inbox, which closes itself when the run recovers. On Demand forecasting that sentence is under Forecast status in the Forecast performance drawer. Ask Tightly on any page answers "why does this say Stale?" from Engine states and from What each engine says, state by state.
Glossary line
One of six: forecasting, baseline, pricing, families and attributes, replenishment, verdicts.