What it is
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 is what that account then sold to shoppers, by door and by week, from the account's own report. Tightly keeps the quantities separate: orders are not consumer sales. For each account one side or the other drives its demand, and the word under the demand figure says which.
An unreported week is absent, never zero. When an account's file has no row for a week, Tightly does not know whether nothing sold or nothing was sent, and it refuses to guess.
How Tightly decides it
Sell-in arrives through Record a booking on the account and through Order intake: an upload, an order by email, over EDI, or on Pro from the buyer portal. Sell-out arrives as the account's own file, landed on Sell-out intake; a week that came in by email says so.
Before the first import, record the week end, locations, currency, tax treatment and full or sparse file coverage. Sell-out intake asks after preview; Setup → How their sell-out reads asks the same.
A missing row cannot be interpreted the same way for both file types. An import without the account's reporting rules is refused. A person chooses the account; Tightly does not infer it from the file.
A sales forecast is a third reading: expected consumer sales for a product and variant, by door and week. It can use measured selling evidence or quantities entered by the account executive or buyer. Where there is no usable history, a person enters the expected units and chooses an offered selling pattern and door distribution. The pattern shapes that estimate; it does not supply measured demand or turn missing actual sales into zero. Forecast inputs opens the selected pattern’s available source and coverage evidence.
The words on the face
On Sell-out intake an account is Reporting, Gone quiet or Never reported; a week with no track is a week not reported, and its hover reads "Not reported, not a zero."; Last reported is a date or Never. A declaration reads back in the words recorded: the file covers individual stores, distribution centres, not stores, or the whole account, with no store breakdown; prices are including tax, before tax, or tax treatment unknown; and every product is listed, every week, or only products that moved are listed.
Under a demand figure on the account's Book, sell-out means a predecessor of the product, as this account reported it, measured it, and sell-in means the account has reported nothing the engine can use and the brand has no level either, so its orders are the evidence; look-alikes and from the brand name the other two sources. On Accounts, where an active Commitment declares the season, the word under Demand is sell-out where the account's sell-out measures that season and sell-in where it does not.
Reported sales names its reporting window. Missing sales, stock-only reports and failed reads stay distinct; none proves that the account never sent a file. Retry reports retries a failed read.
What you can do about it
Chase the file: on Sell-out intake the row menu's Chase the sell-out file opens a note in your own mail naming the missing weeks, and on the account's Performance work area the same button opens Sell-out intake and prepares the chase note for that account. Land it with Import a file. An account with no recent sell-out and no feed shows a No sell-out tile with Import sell-out, which opens Ask. Where an account will never report, read its book as sell-in: record its orders as they come and the demand figure stands on them. Where the brand has its own level for a product, that row reads from the brand instead.
An account's own tills are Sales. A buyer's seat in a brand's portal is a separate relationship view: Sales planning shows the shared forecast and allows proposed changes where permitted. Reforecast follows All variants or your selected variant; Reported forecast keeps the grades from that account's reported doors separate.
Select the Commitment, account and product to build its door forecast. Source checks identifies missing inputs; a reviewed planning calendar permits no-report planning without inventing reporting conventions. Trend opens the forecast chart. Attention offers corrections for served missing evidence or constraints, without turning unknown stock into a shortage. Prepare buy carries that saved forecast and revision into Tightly Connect → Accounts → Buy plan. The buyer portal offers Buying plan. Preview deliveries with recorded prices, currency, stock, receipts, closing targets and supply, resolve missing inputs and obtain forecast approval, then Create draft orders. On the buyer portal, Review order shows its product, Commitment, delivery, unit price, total and store allocations before Confirm order. Drafts link agreed quantities to the forecast; forecasts remain separate from sell-in orders. An account can also send an order through the existing order intake without a sell-out plan; an unlinked order remains an order.
The account’s Sell-out view is one page: Doors and Styles split the weekly grid, with Coverage and All sell-out beneath.
Delivery review separates forecast demand, proposed order units and closing stock. Compare decisions and permitted What if previews remain comparisons; explicit review, approval and order confirmation remain separate actions.