# Tightly help centre

> The knowledge base behind Ask Tightly: one article per concept, page, act and refusal of the platform.

## Home

- [Home](https://docs.tightly.io/help/home/home): What needs me this morning, and where is the rest? Home greets you, holds the box that asks Ask Tightly, lists the handful of decisions worth opening with their money in a column, shows the money you have left to place, and carries the blocks your role reads

## Commitments

- [A colourway the style is not offered in](https://docs.tightly.io/help/commitments/a-colourway-the-style-is-not-offered-in): Where a colour split names a colourway the style does not come in:
- [A refused compile](https://docs.tightly.io/help/commitments/a-refused-compile): On [Declare](../commitments/declare), the review step runs the dry run, and where it refuses, the sentence beside the Declare button reads:
- [A size split that does not total](https://docs.tightly.io/help/commitments/a-size-split-that-does-not-total): Where the shares of a size split do not add up to the whole buy:
- [Declare a plan month](https://docs.tightly.io/help/commitments/act-declare-a-plan-month): Declare a plan month declares one cell of a commitment's plan: for one category and one month, planned sales, reductions as markdown and shrink, the closing target as a level or as cover weeks, and on the season's first month the opening level
- [Decline a scenario](https://docs.tightly.io/help/commitments/act-decline-a-scenario): Decline a scenario records that a scenario was not taken, with a stated reason
- [Preview what signing arms](https://docs.tightly.io/help/commitments/act-preview-what-signing-arms): Preview what signing arms writes nothing at all: it is the dry run that compiles a commitment's stored declaration and answers with what each of the five would bind to, at pair grain, or with a first-class refusal and its stated reason
- [Promote a scenario](https://docs.tightly.io/help/commitments/act-promote-a-scenario): Promote a scenario backs a recorded scenario and records the prediction it is backed on
- [Record a scenario](https://docs.tightly.io/help/commitments/act-record-a-scenario): Record a scenario saves a planner's working copy of a range as a named diff over the plan on one commitment
- [Add to Bench](https://docs.tightly.io/help/commitments/act-send-to-the-bench): Add to Bench hands a commitment's worked buy to the Bench: for every style with a depth a person decided, one Bench line per item, the quantity from the worked depth, the split from the worked colour and size curves (colour first, then size, with any remainder landing so the parts add back to the depth), the supplier the item's own default
- [Set a colour split](https://docs.tightly.io/help/commitments/act-set-a-colour-split): Set a colour split records how one style's buy divides across its colourways, keyed on your own colourway names: a share per colourway in basis points, summing to ten thousand, on one commitment
- [Set a size split](https://docs.tightly.io/help/commitments/act-set-a-size-split): Set a size split records how one style's buy divides across its sizes: a share per size in basis points, summing to ten thousand, on one commitment
- [Set a worked depth](https://docs.tightly.io/help/commitments/act-set-a-worked-depth): Set a worked depth records how many units of one style a person decided to buy on one commitment: one row per style, or one per declared channel leg where the depth is set channel by channel
- [Set colour depths](https://docs.tightly.io/help/commitments/act-set-colour-depths): Set colour depths records units per colourway for one style on one commitment, and writes the style's depth and its colour split in one transaction, so a half-written pair cannot exist: a failure anywhere leaves neither changed
- [The agreed book](https://docs.tightly.io/help/commitments/agreed-book): What has one account agreed to take from this commitment's season, style by style, at what price, and how does that sit against what they took last time and against the money declared?
- [Allocation on a commitment](https://docs.tightly.io/help/commitments/allocation): Where does this order's committed quantity physically go, and what stopped it?
- [Amend a commitment](https://docs.tightly.io/help/commitments/amend): Which of the five numbers is changing, from what to what, on what basis, and why?
- [Availability floor](https://docs.tightly.io/help/commitments/availability-floor): The availability floor is the share of the commitment's range that must be in stock, declared as a percentage with a basis
- [Buy envelope](https://docs.tightly.io/help/commitments/buy-envelope): The buy envelope is the money a commitment may place in total, at cost, in dollars: the living envelope every other money figure on the commitment is read against
- [Capital](https://docs.tightly.io/help/commitments/capital): How much cash is in this book's stock, how old is it, and which way is it moving?
- [Channel scope on money](https://docs.tightly.io/help/commitments/channel-scope-on-money): On [Work the buy](../commitments/the-desk), where the styles of a commitment scoped to a channel would be worked:
- [Release the chase](https://docs.tightly.io/help/commitments/chase-release): Which style has won, how much of the reserve goes to chasing it, and what does the release leave held?
- [Chase reserve](https://docs.tightly.io/help/commitments/chase-reserve): The chase reserve is the part of the buy envelope held back so a planner can react in season: chase a style that is selling ahead, rather than spend every dollar before the season has told you anything
- [Close a commitment](https://docs.tightly.io/help/commitments/close): The window has ended
- [Close the book](https://docs.tightly.io/help/commitments/close-the-book): The season is over
- [Declare](https://docs.tightly.io/help/commitments/declare): What is this commitment, what does it cover, which numbers does it promise, and what would declaring it write?
- [Finish clean](https://docs.tightly.io/help/commitments/finish-clean): What is still here at close, where does it go, and what does not come back?
- [Handovers](https://docs.tightly.io/help/commitments/handovers): Has the replacement arrived before the outgoing style runs out of shelf?
- [Hindsight](https://docs.tightly.io/help/commitments/hindsight): Knowing what the season did, were we as confident as we said we were?
- [Margin floor](https://docs.tightly.io/help/commitments/margin-floor): The margin floor is the blended margin the season may not close under, declared as a percentage with a basis
- [Open to buy](https://docs.tightly.io/help/commitments/open-to-buy): Month by month, what does the plan still need to arrive, against what the envelope allows?
- [Open to commit and free to commit](https://docs.tightly.io/help/commitments/open-to-commit): Open to commit is the rung of the ladder that says what room is left: the buy envelope as declared, less the chase reserve still held, less what has been placed
- [Pace shapes: glidepath, corridor, wave](https://docs.tightly.io/help/commitments/pace-shapes): A pace shape is the form a sell-through pace is expected to follow, and it is decided by what the commitment is
- [Pre-season](https://docs.tightly.io/help/commitments/pre-season): Which season has not opened yet, does its buy land inside the envelope, and which styles still need a person?
- [Re-assign a commitment](https://docs.tightly.io/help/commitments/re-assign): What should this commitment cover, and what would bringing something in or taking it out arm?
- [Reorder lines](https://docs.tightly.io/help/commitments/reorder-lines): This retail month, what does the engine recommend for this assortment, where does the money left run out, and what do I put on the Bench?
- [Retire a commitment](https://docs.tightly.io/help/commitments/retire): What stops being defended if this commitment ends now, and where does its scope go?
- [Scenarios](https://docs.tightly.io/help/commitments/scenarios): Which alternatives were considered against this commitment's plan, how does each compare with it, and which one was chosen?
- [Sell-through pace](https://docs.tightly.io/help/commitments/sell-through-pace): Sell-through pace is the declared rate at which the season sells down, read every week against a pace shape
- [Selling periods](https://docs.tightly.io/help/commitments/selling-periods): Which windows has this tenant declared, when does each open and close, and what is each measured against?
- [Sign off](https://docs.tightly.io/help/commitments/sign-off): What am I signing, what becomes true when I sign it, and may I be the one to sign?
- [Stage and status](https://docs.tightly.io/help/commitments/stage-and-status): A commitment lives on two axes at once
- [Supply on a commitment](https://docs.tightly.io/help/commitments/supply): What has a factory accepted here, and will it arrive before the season closes?
- [Terminal stock ceiling](https://docs.tightly.io/help/commitments/terminal-stock-ceiling): The terminal stock ceiling is the most stock, valued at cost, a boxed commitment may still be holding when its window closes
- [All commitments](https://docs.tightly.io/help/commitments/the-book): What does this book hold, what needs a person this week, and what is waiting on a second signature?
- [Commitments: the promise Tightly keeps](https://docs.tightly.io/help/commitments/the-commitment): A commitment is the promise a season is run to
- [The declaration](https://docs.tightly.io/help/commitments/the-declaration): What was signed, and what has moved since?
- [Work the buy](https://docs.tightly.io/help/commitments/the-desk): How deep do I buy each style before the season opens, and with what money?
- [The five terms of a plan](https://docs.tightly.io/help/commitments/the-five-terms): Under every commitment sits a plan of record: the month by month sheet that says what still has to arrive
- [The ladder: declared, held, open to commit, placed](https://docs.tightly.io/help/commitments/the-ladder): The ladder is the live money position of a commitment against its buy envelope, in four terms that tie in cents: declared, held for the chase, open to commit, placed
- [Declare the plan](https://docs.tightly.io/help/commitments/the-plan): What does the plan command, month by month and category by category, and where does it stand against the envelope?
- [The commitment room](https://docs.tightly.io/help/commitments/the-room): The envelope was declared
- [This week](https://docs.tightly.io/help/commitments/this-week): What needs a decision on this commitment this week, and which inputs need attention before the team acts?
- [Two signatures](https://docs.tightly.io/help/commitments/two-signatures): A commitment is declared by someone who holds the Commitments door and armed by a signature
- [Variance tiers: on plan, approaching, breached](https://docs.tightly.io/help/commitments/variance-tiers): A variance tier is how far a declared number stands from its declaration this week, said as one standing word and one dot beside it
- [Weekly verdicts](https://docs.tightly.io/help/commitments/weekly-verdicts): Every Monday the verdicts engine scores each declared number of every signed commitment over the retail week that closed, Sunday to Saturday on the 4-5-4 calendar, and writes one verdict per number per week

## Finance

- [The buy plan](https://docs.tightly.io/help/finance/buy-plan): What three company numbers am I declaring, against what the book did, and what sales plan, receipts and cover fall out?
- [The cash gate](https://docs.tightly.io/help/finance/cash-gate): Can the coming weeks pay for the buy we intend, week by week, on each supplier's payment terms, against the cash we hold above the floor we declared?
- [Finance declarations](https://docs.tightly.io/help/finance/declarations): Which company terms have we declared for this fiscal year, and what stays unmeasured or ungraded until we do?
- [Investment review](https://docs.tightly.io/help/finance/investment-review): What did each closed season's buy cost, what came back from it, and how much of that can be trusted?
- [Markdowns](https://docs.tightly.io/help/finance/markdowns): Which styles are behind pace, what depth was proposed on each, and who decided it? Markdowns records decisions and never changes a price: the cut is made in the POS or store system by whoever owns it
- [Open to buy: the plan's, the month's, the envelope's](https://docs.tightly.io/help/finance/open-to-buy): Open to buy is what a plan still needs to arrive against what is already placed, at cost
- [The ledger](https://docs.tightly.io/help/finance/the-ledger): Week by week through the plan year, what did the book hold, sell and take in, how much cover is left, and which week can I still change?
- [The split](https://docs.tightly.io/help/finance/the-split): Where does the trade divide, direct to consumer against the trade, by category and month, against the same months a year before?

## Demand

- [Manual forecast](https://docs.tightly.io/help/demand/change-the-forecast): A Manual forecast is a figure a planner types over the system's for one line, one channel and one period on Demand forecasting
- [Confidence as a word](https://docs.tightly.io/help/demand/confidence): Confidence is always a word and never a percentage
- [Demand forecasting](https://docs.tightly.io/help/demand/demand-planning): Which lines have a forecast I should check before I buy against it, and what do I change?
- [Demand signals](https://docs.tightly.io/help/demand/demand-signals): Which products need attention, what evidence explains the change, and what should I do next?
- [Forecast engine status](https://docs.tightly.io/help/demand/forecast-trust): How much of my forecast can I trust, where is it weakest, and is it getting better? Forecast engine status was the page for that question
- [The forecast's words](https://docs.tightly.io/help/demand/forecast-words): Every forecast line stands on a basis, which says what the forecast was built from, and carries a confidence, which says how firmly to hold it
- [Sales performance](https://docs.tightly.io/help/demand/sales): How did the selected period sell, in total and line by line, against the period before it, and which lines are leaking margin or out of stock while still selling?

## Product

- [Analogs](https://docs.tightly.io/help/product/analogs): Which new products could launch on a past product's demand history, does the case for each pair hold, and which pairs are already in place? Analogs is a Product page of the [families and attributes engine](../engines/families-and-attributes.md)
- [Bill of materials](https://docs.tightly.io/help/product/bills-of-materials): Which variants are made rather than bought, from what, in what run, how long until ready to sell, and where? A bill of materials is the components a product is made from, at an amount per finished unit, made in runs of a batch at one warehouse
- [Bundles](https://docs.tightly.io/help/product/bundles): Which variants are declared bundles, what does each consume, and how many can the stock on hand build? A bundle is products sold together as one: an existing variant declared as the bundle, and the variants it consumes at a quantity each
- [Capital quadrants](https://docs.tightly.io/help/product/capital-quadrants): Capital quadrants sort every variant at every warehouse into one of four, a Winner, a Traffic Driver, a Sleeper or a Bleeder, by how fast it turns and how much margin it earns
- [Families](https://docs.tightly.io/help/product/families): Which families exist and how does each vary, what has arrived that is on no product yet, where does each arrival belong, and what was done here? Families is the desk of the [families and attributes engine](../engines/families-and-attributes.md)
- [Health and tags](https://docs.tightly.io/help/product/health-and-tags): Health is the replenishment engine's word on one variant at one warehouse: whether the stock there is Covered, holds more than it can sell, which reads Overstocked, or is out or due a reorder, which reads Needs ordering; where nobody measured it, Not measured
- [Movements](https://docs.tightly.io/help/product/movements): What moved this product at this warehouse, and which document caused each change?
- [The product page](https://docs.tightly.io/help/product/product): Which stocked lines need ordering, hold too much or are covered, and where is the buy worked? A product is one style with its variants, available on every plan
- [Catalogue](https://docs.tightly.io/help/product/products): What is in my catalogue, what is each product missing for planning and for its family, and which values are mine rather than the connector's? The Catalogue is the Product zone's front door
- [Stock on hand](https://docs.tightly.io/help/product/stock-on-hand): What stock is physically held, by variant and warehouse, how many days of cover does it give, what money rides it, and is the data ready to replenish? The page is open on every plan, and a stock figure opens its position
- [Stocktakes](https://docs.tightly.io/help/product/stocktakes): Which counts exist, how far along is each, and did the count agree with the system, in units and money? A stocktake is a count of what is held, recorded against what the system says
- [The position](https://docs.tightly.io/help/product/the-position): Behind one stock figure, what is on hand, what is held, what is coming, and what can be promised?
- [The variant room](https://docs.tightly.io/help/product/variant): Is this variant at risk before a reorder can land, and where? A variant is one sellable item, a product in one size and colour

## Supply

- [Draft a purchase order](https://docs.tightly.io/help/supply/act-draft-a-purchase-order): Drafting a purchase order creates one order per supplier and warehouse from a set of lines and lands it Drafted
- [Exceptions](https://docs.tightly.io/help/supply/exceptions): What could a delivery, a hold or a sync not settle on its own, and what do you decide?
- [Lead time](https://docs.tightly.io/help/supply/lead-time): Lead time is how long a supplier takes, in days, from the day you order to the day the goods land at one of your warehouses
- [Manufacturing orders](https://docs.tightly.io/help/supply/manufacturing-orders): Which make orders exist, for what product and quantity, at which warehouse, whether raw material is short, and how far along each is; and on one order, do I have the material to build it and how do I cover it if not?
- [Minimum order value, MOQ and batch](https://docs.tightly.io/help/supply/minimum-order-value-moq-and-batch): A supplier's brackets are the conditions an order has to meet before the supplier will take it
- [The order](https://docs.tightly.io/help/supply/order): What is this order, what state is it in, what is still missing before I send it or how much has arrived, and what is the one next move?
- [Order status words](https://docs.tightly.io/help/supply/order-status-words): Every order in the Buy book stands in one of seven words: Drafted, Confirmed, In production, Shipped, Delivered, Completed or Cancelled
- [Orders](https://docs.tightly.io/help/supply/orders): Which orders exist, where does each stand, and which of them require action?
- [Purchase orders](https://docs.tightly.io/help/supply/purchase-orders): Which purchase orders exist, where is each in its life, which need a person, and which orders Tightly has drafted are waiting for your approval?
- [Record delivery](https://docs.tightly.io/help/supply/record-delivery): Which of the outstanding lines arrived, how many of each, and does this delivery close the order?
- [Returns](https://docs.tightly.io/help/supply/returns): What is on its way back, what came back in the period, and what did the channel refund?
- [Size pack](https://docs.tightly.io/help/supply/size-pack): A size pack is the sizes a line ships in, as one unit
- [Suggested orders](https://docs.tightly.io/help/supply/suggested-orders): A suggested order is a purchase order Tightly drafted for you and holds until you approve it
- [The supplier](https://docs.tightly.io/help/supply/supplier): How reliable is this supplier, on what terms do we buy from them, what needs my attention, what do they supply and in what packs, and what is on order with them?
- [Suppliers](https://docs.tightly.io/help/supply/suppliers): Who do I buy from, on what terms, where, and which records are too incomplete for replenishment to read?
- [Transfer orders](https://docs.tightly.io/help/supply/transfer-orders): Which moves between my own warehouses are drafted or in flight, and which moves does Tightly propose because one warehouse will run short before it can be restocked while another holds more than it needs?
- [Variant suppliers](https://docs.tightly.io/help/supply/variant-suppliers): For this variant and each supplier that carries it: what is the minimum quantity, batch size, unit cost, cadence and per-warehouse lead time, and which supplier is the default?

## Replenishment

- [Allocation acts: plan, commit, call off, receipt](https://docs.tightly.io/help/replenishment/act-allocate): The split of a purchase order moves through four states, and three acts move it
- [Allocation](https://docs.tightly.io/help/replenishment/allocation): For this purchase order, where do its units go: how many to each warehouse serving its channels, how many have nowhere to go, and what stopped each warehouse taking more?
- [The Budget](https://docs.tightly.io/help/replenishment/budget): What can each month of this fiscal year still spend on stock once what has been spent, what is on order and what replenishment is asking for are counted, and where did the year's buying money go?
- [Cover, and why cover is a minimum](https://docs.tightly.io/help/replenishment/cover): Cover is how long the stock on hand lasts at the rate it is selling: days of cover on one line, weeks of cover on a book or a ledger
- [Policies](https://docs.tightly.io/help/replenishment/policies): Which replenishment rules run my restocking: what does each trigger on, how much does it order, which variants does it own, is it switched on; and can I write a new one and see how often it would have fired before I switch it on?
- [Smart Replenishment](https://docs.tightly.io/help/replenishment/smart-replenishment): What do I need to order over the coming period, what is it worth, how much of it is already too late to save, and which lines do I accept onto the Bench, move from another warehouse, or make in-house?
- [The Bench](https://docs.tightly.io/help/replenishment/the-bench): What have I staged to buy, what is it worth, how many purchase orders does it become, which of them can be placed right now, and whose money does it draw on, before I convert?

## Tightly Connect

- [Accounts](https://docs.tightly.io/help/connect/accounts): Accounts is the front door of Tightly Connect: which accounts need me this week, and where the season's book stands against what they should buy
- [Close a seat or a showing](https://docs.tightly.io/help/connect/act-close-a-seat-or-showing): Two separate closes on the buyer portal, and both only narrow what a buyer can reach
- [Declare how sell-out reads](https://docs.tightly.io/help/connect/act-declare-sell-out-reporting): Four answers one account's weekly report needs before the first file from them can be read: what the figures cover (each store, their distribution centres, or the whole account), the currency, whether prices include tax, and what a missing row means (the product sold none, or the account did not report it)
- [Record a booking](https://docs.tightly.io/help/connect/act-record-a-booking): Recording a booking adds lines to the season's order book for bookings a rep has already taken outside Tightly
- [Record or decide a claim](https://docs.tightly.io/help/connect/act-record-a-claim): A claim is what an account said about its own book: cancel, move the ship window, change the quantity, change the price, or put the line on hold
- [Firmness: firm, walkable, unknown](https://docs.tightly.io/help/connect/firmness): Firmness is how much of an account's book can still walk
- [Invite a buyer](https://docs.tightly.io/help/connect/invite-a-buyer): Invite a buyer gives a person at one of your accounts a seat on the buyer portal: their own sign-in to the pages you choose for that account
- [Claims](https://docs.tightly.io/help/connect/portal-claims): Claims answers what you have asked this brand to change on your orders, and what they decided
- [Forecast for my stores](https://docs.tightly.io/help/connect/portal-forecast): Forecast for my stores answers what this brand expects your doors to sell of the season, and whether that is read off your doors or theirs
- [Home on the portal](https://docs.tightly.io/help/connect/portal-home): Home is the first page of your seat at a brand
- [My orders](https://docs.tightly.io/help/connect/portal-orders): My orders answers what you have committed to at this brand, at what price, and how firm it is
- [Sell-through](https://docs.tightly.io/help/connect/portal-sell-through): Sell-through answers how what you bought is selling in your doors, and what you should reorder while it can still land
- [Ship windows](https://docs.tightly.io/help/connect/portal-ship-windows): Ship windows answers which windows are coming, what sits inside each, and whether a window the brand promised has opened with your lines still unshipped
- [Showroom on the portal](https://docs.tightly.io/help/connect/portal-showroom): Showroom answers what this brand has shown you, when, and what you answered
- [Sell-in only](https://docs.tightly.io/help/connect/sell-in-only): The word under a demand figure, on the account's Book and, where an active Commitment declares the season, on Accounts:
- [Sell-out, sell-in and the unreported week](https://docs.tightly.io/help/connect/sell-out-and-sell-in): Sell-in is what an account orders from you: the lines on the account's book, at the account's own price, with a ship window and a cancel date
- [Sell-out intake](https://docs.tightly.io/help/connect/sell-out-intake): Which of my accounts sent their weekly sell-out, which did not, and what happens if I land this file? Sell-out intake is where an account's own report becomes measured demand
- [Showroom](https://docs.tightly.io/help/connect/showroom): Which accounts have I shown the season to, what did each answer, and what should I offer this one? A seller here shows a commitment's styles to one account, graded by how each will sell in its doors, sets the take, shares it as a link and records what was agreed
- [The account](https://docs.tightly.io/help/connect/the-account): One account is one record: what it has booked this season, how firm that is, what its doors sold, what it sent you and the terms it trades on
- [The grade: measured, borrowed, brand](https://docs.tightly.io/help/connect/the-grade): The grade is the baseline engine's word on one style at one account: how that style is likely to sell in that account's doors, and what the word stands on
- [The seat and the showing link](https://docs.tightly.io/help/connect/the-seat): An account's buyer reaches your Tightly through two doors

## Ask Tightly

- [Keep an answer: Board, Home, the room](https://docs.tightly.io/help/ask/act-keep-an-answer): Keeping an answer preserves the selected answer and where it came from
- [Approve, Reject, Undo everything on a run](https://docs.tightly.io/help/ask/act-run-decisions): Three presses decide what a skill's run does next
- [Save and fire a skill](https://docs.tightly.io/help/ask/act-save-and-fire-a-skill): Two acts share one door
- [Update saved insight](https://docs.tightly.io/help/ask/act-update-saved-insight): Update saved insight writes the question on your screen to the kept answer's record: the period, the grain, the breakdown, the filters, the measures, their order and how many rows
- [Ask Tightly: answers, the Board, the workspace](https://docs.tightly.io/help/ask/ask-tightly): What can Ask Tightly see, what did I ask last, and what does an answer rest on? Ask Tightly is the one assistant on every page of Tightly
- [The Board](https://docs.tightly.io/help/ask/board): Has anything changed since I last looked, and which kept answers need re-running? The Board is where answers are kept
- [Inbox](https://docs.tightly.io/help/ask/inbox): What is waiting on my decision, and what happens if I say yes? The Inbox holds everything pending that is assigned to you, grouped by kind, the biggest first, with its money in a column
- [The Board on Lite](https://docs.tightly.io/help/ask/lite-board): How did my store trade, what moved, and where is the money sitting? On Tightly Lite the Board is ten charts that are always there
- [Mark an internal transfer](https://docs.tightly.io/help/ask/mark-intercompany-transfer): Ask Tightly to preview an internal transfer using the exact NetSuite sales order ID and the purchase order that matches it
- [New skill](https://docs.tightly.io/help/ask/new-skill): How does a skill get written, and where does what it builds appear? Write a skill is a conversation with Ask Tightly beside the skill it is building
- [The knowledge base has no article](https://docs.tightly.io/help/ask/no-article): > The knowledge base has no article for that
- [A page act asked of Ask](https://docs.tightly.io/help/ask/page-acts): What Tightly answers when Ask Tightly tries to perform a page's own act itself, instead of offering it to you:
- [Change a commitment product range](https://docs.tightly.io/help/ask/propose-commitment-product-range): Ask Tightly to propose the products one channel, or one account on a channel, can sell within a commitment
- [A read-only seat asks and performs no act](https://docs.tightly.io/help/ask/read-only-seat): When a viewer asks Ask Tightly to fire a skill, the skill is not started and Ask Tightly relays the refusal it was given:
- [Row limits](https://docs.tightly.io/help/ask/row-limits): When a read asks for more rows than any read in Tightly may ask for, it is refused in the engine's own words and draws no figures:
- [Set an account’s fulfilment warehouses](https://docs.tightly.io/help/ask/set-account-fulfilment-locations): An account's fulfilment warehouses are the warehouses whose stock serves that account
- [Your company](https://docs.tightly.io/help/ask/setup-company): What should Tightly know about your company before it reads any of your data? It is the second card of setup and the last one before you connect anything
- [Setup: Connect](https://docs.tightly.io/help/ask/setup-connect): Where am I in setup, what does this step need, and can I leave and come back? Setup is one wizard in three phases, Connect, Review and Finish
- [Setup: Finish](https://docs.tightly.io/help/ask/setup-finish): What rhythm should Tightly plan my orders against, and when can I start? Finish is the third phase of Setup: your planning rhythm, then, on Essentials+ and Pro, the accounts you sell to, then the moment the account is ready
- [Importing, and the dead end](https://docs.tightly.io/help/ask/setup-importing): > Your {source} import stopped at {set}
- [Setup: Review](https://docs.tightly.io/help/ask/setup-review): What came in from my system, and is it what Tightly should plan against? Review is the second phase of Setup
- [The skill editor and its evals](https://docs.tightly.io/help/ask/skill-editor): What does it do step by step, what would it do today, how far does it go, is it proven, what waits on me, and what has it done? One skill's page is its sequence and its record on one page
- [A skill's run](https://docs.tightly.io/help/ask/skill-run): What did it do step by step, what changed, what waits on me, and can all of it go back? A run is one execution of a skill
- [Skills and the ladder](https://docs.tightly.io/help/ask/skills): What runs without me, how far does each go, is it proven, does it fire, and what is waiting on my decision? A skill is something that runs without you, written with Ask Tightly in a conversation
- [Skills and a Lite plan](https://docs.tightly.io/help/ask/skills-on-lite): A skill is something a person writes once and Tightly then runs without them: it watches for a thing to happen, works out what to do about it, and either tells someone or writes the change itself
- [Stamps: Live, Data as of, Not yet refreshed, Snapshot](https://docs.tightly.io/help/ask/stamps): A stamp is the one claim an answer makes about when its figures were read
- [The caveat](https://docs.tightly.io/help/ask/the-caveat): The caveat is the sentence Ask Tightly's earlier chat printed about itself, under the box:
- [The Ask Tightly panel](https://docs.tightly.io/help/ask/the-panel): Can I ask about the page I am on without leaving it, and will the answer know where I am standing? The panel is Ask Tightly beside every working page
- [The workspace](https://docs.tightly.io/help/ask/the-workspace): Can I adjust this one number, read it against something else, ask about it, and decide whether the Board should keep the change? The workspace is one kept answer opened on its own page

## The engines

- [The baseline engine](https://docs.tightly.io/help/engines/baseline): The baseline engine grades a style at one account, Winner, Sleeper or Bleeder, from what that account's own doors sold before
- [Engine states](https://docs.tightly.io/help/engines/engine-states): An engine state is one word for whether an engine has run for you and how current its figures are: Running, Late, Stale, Partial, Failed, Not measured, Nothing yet, Not on your plan, Paused, Not on the run
- [The families and attributes engine](https://docs.tightly.io/help/engines/families-and-attributes): The families and attributes engine keeps each product's own facts: its family, how that family varies, the attributes the family asks for, and two measured figures, a price band and a size curve
- [Forecast accuracy](https://docs.tightly.io/help/engines/forecast-accuracy): Forecast accuracy is the forecast's track record: how far Tightly's forecast missed what actually sold, week by week, set beside the misses of doing it by hand
- [Forecast methods and the Monday re-score](https://docs.tightly.io/help/engines/forecast-methods): The forecasting engine keeps a set of methods and lets each line's own sales decide which one reads it
- [The forecasting engine](https://docs.tightly.io/help/engines/forecasting): The forecasting engine says what each line is expected to sell, day by day, from what it has sold
- [Compare discounts and the discount forecast](https://docs.tightly.io/help/engines/markdown-forecast): Compare discounts is Tightly Pro's side-by-side of one product at its current price and at up to six discounts, over dates you pick inside a Commitment's window
- [Forecasts for products that have never sold](https://docs.tightly.io/help/engines/new-product-forecasts): A product that has never sold has no record of its own, so the forecasting engine borrows one: it reads how comparable past styles sold from their launch week on, blends them into one curve, and gives the new product that curve
- [Price sensitivity and the price response](https://docs.tightly.io/help/engines/price-response): Price sensitivity is the pricing engine's tier for one variant: how much its sales moved, on average, when its list price moved
- [The pricing engine](https://docs.tightly.io/help/engines/pricing): The pricing engine measures how a product's sales moved when its price moved, and says how far that measurement can be trusted
- [Provenance words](https://docs.tightly.io/help/engines/provenance-words): Computed, declared, measured, read in, or the name of the engine that made it: where a figure came from
- [The replenishment engine](https://docs.tightly.io/help/engines/replenishment): The replenishment engine works out what to order and when, from the forecast, the lead time and the cover you must hold
- [What each engine says, state by state](https://docs.tightly.io/help/engines/served-sentences): One sentence per engine per state, served whole and printed character for character on the page that reads the engine, in the Inbox row and in an answer from Ask Tightly
- [The engines](https://docs.tightly.io/help/engines/the-engines): An engine is one of six: forecasting, baseline, pricing, families and attributes, replenishment, verdicts
- [The verdicts engine](https://docs.tightly.io/help/engines/verdicts): The verdicts engine reads each declared term of a commitment against what traded, once a week, and says what happened

## Settings

- [API keys](https://docs.tightly.io/help/settings/api-keys): Which keys can reach Tightly from outside, what can each one read and write, when was each last used, and how do I make, replace or stop one? API keys sits in the Developer group of the settings rail, beside Metrics; the `Product data API` row under `Reads from Tightly` on Integrations opens the same page
- [Approvals](https://docs.tightly.io/help/settings/approvals): Who signs off a commitment before it owns money: must a second admin sign what another admin submitted, or may one admin declare and approve? Approvals is where the organisation chooses, and the record of every time it chose
- [Asking for a new connection](https://docs.tightly.io/help/settings/asking-for-a-new-connection): A request is how you tell Tightly you want it to read from, or write to, a system it does not
- [Billing](https://docs.tightly.io/help/settings/billing): How is this workspace paid for, where are its cards, invoices and receipts, and is a change or a cancellation scheduled? Billing carries no price list, no plan picker and no plan name: pricing is negotiated, and the plan is set with Tightly
- [Data](https://docs.tightly.io/help/settings/data): Did my import complete, how do I fix refused rows, and where can I download data or manage custom fields?
- [Data mapping](https://docs.tightly.io/help/settings/data-mapping): Which of a source's sets does Tightly read, who is right when two sources describe the same thing, which source column feeds which Tightly field and how is it transformed on the way, and what changes if I save? Data mapping is not a page of its own: it is a wizard reached from a connector page on Integrations, where a set's Match the fields act opens it on that set's fields
- [Email](https://docs.tightly.io/help/settings/email): Which mailbox does Tightly read and write from for me, who else sees it, and does Tightly read the files that land in it? Email is under You: the mailbox is yours, one per person, connected and disconnected by you
- [General](https://docs.tightly.io/help/settings/general): What is this tenant called, what does it plan in and where, what kind of company is it, and what address does a purchase order print? General is the first page under Settings and the one `/settings` lands on
- [Integrations](https://docs.tightly.io/help/settings/integrations): What feeds Tightly, is it live, what synced when, what failed, what can I connect or ask for, and what reads from Tightly? Integrations is the list; every source opens onto its own connector page
- [The NetSuite role Tightly connects with](https://docs.tightly.io/help/settings/netsuite-role): The role your NetSuite administrator builds so Tightly can read your account
- [Notifications](https://docs.tightly.io/help/settings/notifications): Which events email me, and where do they go? Notifications is yours: it decides what reaches your own address
- [Planning](https://docs.tightly.io/help/settings/planning): What defaults do the engines plan on for this workspace: how stock is synced, the service level, how often replenishment runs, the default lead time, the calendar every buy plan follows, the guardrails on the envelope, the tolerances the verdicts read, and the containers a fill plan counts in?
- [Profile](https://docs.tightly.io/help/settings/profile): Who am I here, how do I sign in, which tenants does my account hold, what is each one connected to, and how do I switch or add another? Profile is the first page under You, and the old Organisations page folded into it as the Tenants section
- [Channels](https://docs.tightly.io/help/settings/sales-channels): Which channels sell your stock, which side of the trade is each one on, which place ships for it, whose channel it is where an account owns it, and where do its figures come from? Channels is the settings page; the rail row says the same word
- [Team](https://docs.tightly.io/help/settings/team): Who can sign in to this workspace, what may each person do, which doors do they hold, and who is still waiting on an invitation? Team is the roster: people, invitations and the rungs they stand on
- [Locations](https://docs.tightly.io/help/settings/warehouses): Where does stock sit, what kind of place is each one, which is the default, which are active, how does each one restock, and how long does a transfer take between any two of them? The page is Locations on the brand chair and Stores & DCs on the retailer chair; the rail row and the head take the same name, so the door and the page cannot disagree
- [Webhooks](https://docs.tightly.io/help/settings/webhooks): Which outside systems are told when a purchase order is created or changes, is the last post arriving, and how do I add, re-sign or stop one? The Webhooks page is built but not yet open on Tightly: it has no address a customer can reach, so the Developer group of the settings rail shows API keys and Metrics without it, Integrations draws no Webhooks row, and an old Webhooks link lands on the Integrations list
- [What comes in and goes out on a connection](https://docs.tightly.io/help/settings/what-comes-in-and-goes-out-on-a-connection): A connection has two halves, and the connection's own page shows both

## Mail

- [Draft and send an email](https://docs.tightly.io/help/mail/act-send-an-email): Two acts, and only the second writes anything that leaves
- [Mail](https://docs.tightly.io/help/mail/mail): What have my suppliers and accounts said that changes something, and what waits on me? Mail is a work queue of threads bound to records, not a mailbox: no folders, no sent view, no inbox-zero count, and no thread without a party
- [The email agent's proposals](https://docs.tightly.io/help/mail/the-email-agent): A proposal is an act the email agent proposes as an Inbox row; a person presses

## Signing in

- [Back from Amazon](https://docs.tightly.io/help/access/amazon-return): Did Amazon accept my authorisation; is my Seller Central account connected to Tightly now, or do I have to go back and try again? This address is the one Amazon sends you back to after you approve the connection
- [Something went wrong](https://docs.tightly.io/help/access/error): Tightly just broke on me: what happened, is my work safe, and how do I get back to it? This is the crash page
- [Forgot password](https://docs.tightly.io/help/access/forgot-password): I have forgotten my password; email me a link so I can set a new one and get back in
- [Authorise an MCP client](https://docs.tightly.io/help/access/mcp-authorise): Do I let this AI agent into my Tightly account, as whom, into which organisation, reaching how far, for how long? An AI agent, Claude in a desktop or a connected client, arrives here when it asks to connect to Tightly
- [Not found](https://docs.tightly.io/help/access/not-found): There is no page at this address: where was I going, and where do I go now? Not found is the page every address that names nothing lands on, whatever the reason: a mistyped address, an old bookmark, a page your seat does not include, or a record that once existed and does not any more
- [Privacy policy](https://docs.tightly.io/help/access/privacy-policy): What personal data does Tightly collect about me, what does it do with it, who else sees it, and what can I do about it? The privacy policy is one legal document, given by its author, rendered whole
- [Reset password](https://docs.tightly.io/help/access/reset-password): I followed the link in the email; can I set a new password now and get back in? This page is reached from the recovery email only
- [Sign in](https://docs.tightly.io/help/access/sign-in): Let me into Tightly, with my email and password or with the Google or Microsoft account I already use, and put me back where I was going
- [Sign up](https://docs.tightly.io/help/access/sign-up): I was sent here to join Tightly: which address is this account for, what do I need to give, and what happens if the link is old? Sign-up is invite-led
- [Version](https://docs.tightly.io/help/access/version): Which version of Tightly is this tab running? A customer asks it when Tightly's support has pointed them here, usually while chasing down a fix that has since shipped; a Tightly person asks it to see that a release landed on a particular tab

## The platform

- [A failed read, never an empty page](https://docs.tightly.io/help/platform/a-failed-read): There is no one sentence: each page says in its own words that it could not read, and most say it beside a Try again
- [Absence words](https://docs.tightly.io/help/platform/absence-words): An absence word names which kind of nothing a figure is: two or three words for a fact nobody has
- [The for-sale page](https://docs.tightly.io/help/platform/for-sale-pages): Under the room's name, on the page a marked row opens, one sentence naming the plan that sells it:
- [Plan denial](https://docs.tightly.io/help/platform/plan-denial): Where a request reaches a room your plan does not include:
- [The four-five-four calendar](https://docs.tightly.io/help/platform/the-calendar): The four-five-four calendar is the retail calendar Tightly plans on
- [The brand chair and the retailer chair](https://docs.tightly.io/help/platform/the-two-chairs): Every company that plans a season with Tightly sits on one side of a table
- [Tiers: Lite, Essentials, Essentials Plus, Pro](https://docs.tightly.io/help/platform/tiers): A tier is the rung of the commercial ladder your organisation is sold on: Tightly Lite, Tightly Essentials, Tightly Essentials+ or Tightly Pro

## Glossary

- [Glossary](https://docs.tightly.io/help/glossary/glossary): Old words and wire words, each with the word the face prints instead

## What changed

- [Aug 11, 2026](https://docs.tightly.io/help/releases/2026-08-11): Stocktakes sit beside Stock on hand, the Bench checks every supplier minimum, and a delivery is recorded on its own page
- [Aug 11, 2026 · Essentials and Pro](https://docs.tightly.io/help/releases/2026-08-11-essentials): Demand signals read as a prioritised queue, and the Board holds the answers you keep
- [Aug 11, 2026 · Lite and Essentials](https://docs.tightly.io/help/releases/2026-08-11-lite): The Budget is an editable twelve-month grid, and Smart Replenishment has a Projection view
- [Aug 11, 2026 · Pro](https://docs.tightly.io/help/releases/2026-08-11-pro): Declaring a commitment is a full page, and the book lists every commitment in one place
- [Aug 12, 2026](https://docs.tightly.io/help/releases/2026-08-12): The dark theme is readable on every page, and a status tag prints its word instead of a colour
- [Aug 12, 2026 · Pro](https://docs.tightly.io/help/releases/2026-08-12-pro): Signing off and closing are full pages, and a commitment covers a list of entries with exceptions
- [Aug 13, 2026](https://docs.tightly.io/help/releases/2026-08-13): The accuracy figure names the weeks it measured, and a page that has gone stale reloads instead of hanging
- [Aug 13, 2026 · Pro](https://docs.tightly.io/help/releases/2026-08-13-pro): A commitment's state says what has and has not been measured, in five distinct words
- [Aug 20, 2026](https://docs.tightly.io/help/releases/2026-08-20): Every control has a name a screen reader can say, and charts follow the theme in both modes
- [Aug 20, 2026 · Essentials and Pro](https://docs.tightly.io/help/releases/2026-08-20-essentials): A product's family sits beside its category, and a missing family is proposed from similar products
- [Aug 20, 2026 · Lite and Essentials](https://docs.tightly.io/help/releases/2026-08-20-lite): Allocation shows where a purchase order's committed units go
- [Aug 20, 2026 · Pro](https://docs.tightly.io/help/releases/2026-08-20-pro): The book ranks what needs attention this week, and the on-track chart shows the declared band
- [Aug 24, 2026](https://docs.tightly.io/help/releases/2026-08-24): An allocation split saves and says what happened, and every button wears the one brand colour
- [Aug 24, 2026 · Pro](https://docs.tightly.io/help/releases/2026-08-24-pro): A commitment's planned buy goes to the Bench for review, and Selling periods are yours to define
- [Aug 26, 2026 · Pro](https://docs.tightly.io/help/releases/2026-08-26-pro): A reorder line shows its justification, and the desk is a reconciliation against every declared target
- [Aug 28, 2026](https://docs.tightly.io/help/releases/2026-08-28): A purchase order delivery says what remains, and a completed delivery reads quietly in ink
- [Aug 28, 2026 · Pro](https://docs.tightly.io/help/releases/2026-08-28-pro): Every account has a page of its own, and depth on the desk comes from your own trading
- [Aug 30, 2026](https://docs.tightly.io/help/releases/2026-08-30): A variant's page is a room of its own, and the warning glyph draws at icon size again
- [Aug 30, 2026 · Essentials and Pro](https://docs.tightly.io/help/releases/2026-08-30-essentials): Families is a page of its own, and the Join Desk lists the incoming products waiting for a family
- [Aug 30, 2026 · Lite and Essentials](https://docs.tightly.io/help/releases/2026-08-30-lite): The stock projection opens on items with a forecast
- [Aug 30, 2026 · Pro](https://docs.tightly.io/help/releases/2026-08-30-pro): The room's front door follows the season's stage, and the desk reads the engine end to end
- [Aug 31, 2026](https://docs.tightly.io/help/releases/2026-08-31): A teammate's permissions open from their row
- [Aug 31, 2026 · Essentials and Pro](https://docs.tightly.io/help/releases/2026-08-31-essentials): Skills has a home of its own
- [Aug 31, 2026 · Pro](https://docs.tightly.io/help/releases/2026-08-31-pro): Saving a forecast change inside a live commitment names the commitment and the day its buy locks
- [Sep 1, 2026](https://docs.tightly.io/help/releases/2026-09-01): Purchase orders can split a line into dated tranches, and every unit on order counts once
- [Sep 1, 2026 · Pro](https://docs.tightly.io/help/releases/2026-09-01-pro): The season is one thread: declare it, arm it, work the buy, run it week by week and close it with a receipt