Item blocking and variants: retiring items cleanly and keeping variants under control

Implementation · 8 min read

Every assortment accumulates dead items: last year's model, the colour nobody bought, the variant created for a promotion that ended months ago. Left alone, they keep appearing in lookups, keep getting reordered by habit, and keep polluting counts and reports. Blocking is Business Central's retirement tool — but flipping the toggle first and tidying up later is how stores end up with blocked stock they cannot sell, open documents that fail, and staff who route around the block. Retire in order: sell through, close the loose ends, then block in stages.

Blocking is a sequence, not a switch

The block itself takes seconds. Everything around it is the real work, and the sequence matters because each block type closes a different door:

1. Stop the inflow. Block purchasing first, so no new stock arrives while the store is trying to retire the item — and deal with anything already on order.
2. Sell through what remains. Keep sales open while usable stock exists. A block on production, for example, is explicitly useful when a newer model replaces an old one but the remaining stock should still be sold.
3. Close the loose ends. Resolve open documents, returns in flight, and planning settings (below) before the final block.
4. Block sales last. Only when stock is gone — or deliberately written off — does the sales block go on.
5. Review before anything more drastic. A blocked item keeps its history: ledger entries, past documents, and reporting continuity. That history is worth money at audit and tax time; treat deletion thinking with suspicion and a blocked, documented item as the normal end state.

Clean data is the point of the exercise. Retiring an item properly removes it from daily work without removing the record of what happened — the same discipline as keeping unknown or messy data out of the system in the first place, applied at the end of an item's life instead of the beginning.

Know exactly what each block does

Two behaviours surprise staff who have not read the documentation. First, returns are exempt: customers can return blocked items, and the blocking settings do not apply to return orders and credit memos. A sales block is not a returns policy — if the store wants to refuse a defective item, that is a management decision, not a system setting. Second, copied documents quietly change: when a new document is created with Copy Document from an older one, blocked lines are excluded and a notification lists the excluded lines. A repeat order copied from last season will simply arrive without the retired item — correct behaviour, but staff should read the notification instead of assuming the copy is complete.

The all-blocks combination has a specific documented use: blocking an item from being posted in any kind of transaction suits an item with a known defect, where selling remaining stock is precisely what must not happen. Defect first, sell-through never — that is the one case where the staged sequence collapses into a single immediate block.

Retire an item cleanly, in order

1. Confirm it is really dead. Check recent sales and current stock. An item with stock is a sell-through project; an item with no stock and no movement is a quick retirement. Do not block on a hunch.
2. Stop replenishment. Search for Items, open the item, and turn on Purchasing Blocked. If the item is production-blocked as part of the retirement, also change its replenishment method so it stops appearing in planning: blocked items can still show lines in the requisition and planning worksheets, but the action to create orders from them cannot be carried out — stale worksheet lines are just noise until the method changes.
3. Clear open business. Receive or cancel outstanding purchase orders, fulfil or close open sales commitments, and process returns already in flight. Blocking mid-flight documents creates the error messages staff then blame on the block.
4. Sell through or write off the remainder. Markdown, bundle, or return stock to the shelf with sales still open. Whatever cannot be sold leaves through the store's normal adjustment process, so the final stock figure is honestly zero.
5. Apply the remaining blocks. On the Item Card, turn on Sales Blocked (and Service Blocked where service work applies), and set the Production Blocked field if production use is in scope.
6. Verify like a cashier. Try to add the item to a sales document — the system should refuse with a blocked message. Then process a test return path mentally against the real returns desk process, remembering returns still work by design.

Variants: one item, controlled differences

Variants exist to keep the product list under control when many items are almost identical and differ in a single characteristic, such as colour. One item with six colour variants is one item to price, describe, and report — with the difference carried in the Variant Code, which is specified on sales and purchasing document lines. The alternative, six near-duplicate items, multiplies every maintenance task by six.

Variants are maintained from the item card: choose Variants and list them on the Item Variants page. Discipline rules that keep them an asset instead of a swamp:

• One axis of difference per item. Colour or size is manageable. Colour times size times edition is a combination explosion — dozens of variants, most of which will never sell, each one a stock-keeping and counting obligation.
• Keep the difference in the variant and the attributes, not the description. Variants inherit the item's attributes, and variant-specific values can be adjusted or removed on the Item Variant Attribute Values page; the Update Variant Attributes action on the Item Card force-syncs attributes from the item to its variants. Colour belongs in an attribute on the variant — stuffing "black, summer" into descriptions is what makes reporting and template reuse painful later.
• Every live variant needs its own scannable identity. A variant staff cannot scan distinctly will be sold as whichever variant the till finds first, and variant stock becomes fiction within a month.
• Name variants for the shelf, not the supplier. Staff-facing codes that a new hire can decode beat cryptic vendor abbreviations that only one person understands.

Prune variants without breaking history

Variant retirement follows the same staged logic as item retirement, one level down. From Items, open the item, choose Variants, and work per variant:

1. Sell through the variant's stock first, with the variant still selectable. A variant with stock and a sales block is a markdown problem created by the office.
2. Block purchasing for the variant so it stops being reordered while the parent item lives on.
3. Then set the variant's blocks — the Blocked, Sales Blocked, Service Blocked, and Purchasing Blocked checkboxes, plus the Production Blocked field where relevant. Blocking one variant leaves the item and its sibling variants fully sellable, which is exactly the granularity variants exist to provide.
4. Leave the variant in place, blocked. Its history — what sold, when, at what stock — stays attached to the item's record. A future buyer asking why the range was pruned gets an answer from data, not from memory.

For new items, the discipline can start at creation: production blocking can be set on the Item Template page so items created from the template inherit the setting. Templates are how a one-off clean decision becomes the default for every item created afterwards.

What success looks like

Pick one retired item and test it the way the store will meet it. Searching and selecting it on a new sales document fails with a blocked message. It no longer appears as orderable in purchasing or planning. Its stock is zero by sale or by adjustment, not by wishful thinking. A customer return of the same item can still be processed. And its variants — if it had any — are individually blocked or individually alive, never a mixed mystery. When all five hold, the item is retired: invisible to daily work, intact in history.

FAQ

Does blocking an item stop customer returns? No. Blocking settings do not apply to return orders and credit memos; customers can return blocked items by design.

Should remaining stock be sold before or after blocking? Before the sales block, after the purchasing block. Selling through remaining stock is an intended pattern — it is the stated reason to production-block an old model while its stock still sells.

Why does a blocked item still appear in planning worksheets? Worksheet lines can still be generated for blocked items, but the orders cannot be created from them. Change the item's replenishment method to remove it from planning altogether.