What it is
The pricing engine measures how a product's sales moved when its price moved, and says how far that measurement can be trusted. It never writes a price anywhere: every markdown in Tightly is a decision recorded for a person, and the cut itself is made in the store or sales channel by whoever owns it.
It is made of six parts:
- The price sensitivity tier, set for every variant inside every sync from its pool's price response.
- The evidence read, which says whether a variant's own sales carry a measurement, take one from its product, or carry none.
- The pooled price response fit, measured across a family, a category or the whole book, which Tightly Pro uses to answer a discount depth.
- The discount arithmetic, which moves a demand forecast, revenue and margin by that fit and refuses a depth deeper than the pool actually trades in.
- Compare discounts, the Pro comparison of up to six discounts for one product, and the discount forecast it can apply.
- Markdowns, the Pro page where a markdown is proposed and decided.
How the tier and the evidence are measured is in Price sensitivity and the price response.
Where you see it, by plan
On every plan: a variant's Price section (sell price, every move of the last twelve months, units sold against price, and the Tier, Confidence and Basis chips) and the Price sensitivity column and filter on Sales performance.
On Pro: Compare discounts in the variant's Price section and Pricing, Discount scenarios, Work the buy's price response, and Markdowns. Pricing includes opportunities, floor headroom and price response. See Compare discounts and the discount forecast, and Markdowns.
Pricing keeps recorded decisions visible without new automatic opportunities. Manual scoped drafts retain comparison dates: inclusive Through becomes an exclusive proposal end. Cancel, then return to restore the selection. Approval and selling-channel prices remain separate.
Set a selling price
In the Selling prices card on a variant's Price section, Add price (or Edit on a row) lets editors choose a channel, optional account, net selling price, currency and dates. Account prices take precedence over channel prices, then catalogue defaults. Use inherited price removes an override; saved changes keep a revision history. Overlapping dates and stale edits are refused. This records a planning price in Tightly; it changes neither past orders nor store prices. Finance and scenarios use these prices. Demand's revenue view remains a catalogue-price estimate.
When it runs
The tier is set with every sync, near the end of the chain, from the pooled fit already held for each variant's pool; it never makes a fit itself. A pool with no fit yet is asked for one, at most ten pools each sync and the ones with the most variants first, and its variants keep the tier they were showing until the fit exists. Full sync is due daily at 04:00 UTC; daytime updates are incremental. Existing exceptions retain their cadence. Its run promise follows that slot, or a configured independent refresh schedule. Source sync health can be Late or Stale before a job is due; Running keeps its limit. It is an add-on step: if it fails, the sync still succeeds and the last tiers stay on screen.
The pooled fit is never made while a page loads. A page that needs one files a request, and a scheduled job, Refresh requested pooled price fits, picks requests up every two minutes and makes at most two per pass. A fit is remade after a day and served for up to seven.
The words on the face
The Price section's Price response row carries the run's stamp, and while a run is in flight the stamp is followed by measuring now. Where the run did not happen or did not finish, the section prints the engine's own sentence, character for character:
Price response has not been measured for this tenant yet.
Last measured {as_of}; no sync has reached it since.
Measured {as_of}; some items could not be measured.
Price response was not measured today; showing {as_of}'s.
No price has moved yet, so there is nothing to compare.
Price response is off for this tenant.
Paused with the connection; pricing waits for the sync.
This tenant is not on the price response run.
A variant the engine never tiered reads Not scored; Still learning is a tier the engine reached, not an absence.
How pricing reaches the buy
The replenishment engine does not read price sensitivity, so a reorder is never cut or raised by it. On Tightly Pro, Commitments reads the pooled fit: Work the buy and Trade the week print the price response per product, and a discount applied to the demand plan from Compare discounts changes the working demand for that product and those dates.
What you can do about it
Nothing is pressed to measure a tier: the pool's fit is made by the scheduled job, and the next sync reads it. A Paused engine resumes with its connection on Integrations. Read the Basis row before acting on a tier.
Glossary line
Pricing: measured, pooled or prior price response, without automatically changing selling-channel prices.
On a commitment, the Pricing product selector uses its assortment, including products without a markdown recommendation. Select a product before narrowing its variant, channel and location. An assortment read failure offers a retry; an empty assortment offers Account prices.