Reference · built on requestOperator by FibricInventory & supply

Dead Stock

Finds items with no sales inside your window, prices the stock behind them, and proposes a markdown, vendor return, or write-down.

Request accessPricing ↗

About

Stock that has stopped selling still carries cost, occupies bins, and ages toward a write-off nobody has scheduled. Dead Stock reads on-hand quantity and unit cost per item and location from your ERP, the date each unit was received, and the sales history behind each SKU from your store or a sales table in your warehouse.

Every item with no sales inside the window you set is listed with units, value at cost, and days since the last receipt. For each one it proposes a markdown on the storefront, a return to the vendor, or a write-down of the carrying value. A buyer or controller approves each proposal, and the record kept shows the figures it rested on.

This is a reference listing. It documents what Fibric would read from Dead Stock and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • On-hand quantity, unit cost, and value per item and location from NetSuite or Business Central item records
  • Receipt dates on NetSuite item receipts and Business Central posted purchase receipts, to age each unit on hand
  • Order lines per SKU from Shopify or BigCommerce, or a sales table in Snowflake, BigQuery, or PostgreSQL
  • Variant price and compareAtPrice on Shopify products, so a markdown proposal shows the current price
  • The vendor on each item and the purchase order it arrived on, for a return-to-vendor proposal
  • Open vendor return authorizations, so the same units are not proposed for return twice

Proposed actions

  • Target capability: propose a markdown on a Shopify variant through productVariantsBulkUpdate, with the original price kept as compareAtPrice
  • Target capability: propose a NetSuite vendor return authorization for the units, with vendor, quantity, and value of the return
  • Target capability: propose a write-down as a Business Central revaluation journal line with a new Unit Cost (Revalued)
  • Target capability: propose a NetSuite inventory adjustment removing units that cannot be sold, with Adjust Qty By and a Memo

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Clear a season's leftovers

    Units with no Shopify sales inside the window are listed by value at cost. The buyer approves a markdown per variant, and the new price is written to Shopify with the original kept as compareAtPrice.

    With Shopify, NetSuite

  • Return slow stock while the vendor still takes it

    Items bought on returnable terms with no sales since receipt are proposed as a NetSuite vendor return authorization, with quantity and value filled in for the buyer to approve.

    With NetSuite

  • Write down aged stock before period close

    Business Central items past your age threshold, with sales read from Snowflake, are proposed as revaluation journal lines with a new Unit Cost (Revalued). The controller approves each line before posting.

    With Microsoft Dynamics 365 Business Central, Snowflake

Requirements

  • An ERP holding on-hand quantity and unit cost per item and location: NetSuite or Business Central
  • Sales history per SKU from a storefront or a warehouse table, covering at least the window you set
  • NetSuite with the Vendor Return Authorizations feature enabled, if returns to vendor are to be proposed
  • A buyer or controller named to approve each markdown, return, or write-down
Authentication
ERP credentials with item, receipt, vendor return, and journal permissions, plus a Shopify Admin API token with write_products for markdowns and read-only access to the sales table.

Limits

  • An item with no receipts inside the window is aged from its earliest receipt still on hand. No date is guessed.
  • A NetSuite vendor return authorization is non-posting. Units leave inventory only when your team ships the return.
  • A markdown changes the storefront price only. Marketplace prices are outside this listing.
  • A write-down is proposed as a journal line with its amount. Posting the journal stays with your controller.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Dead Stock ↗

Questions and answers

What counts as dead stock?
An item and location with units on hand and no sales inside the window you set, measured from store orders or your sales table. The window, a minimum value at cost, and any excluded categories are yours. Items below the minimum are listed but not proposed.
What does the approver see?
One card per item and location: units on hand, unit cost, value at cost, days since last receipt, last sale date, and the proposal with its figures filled in. The approver can change the markdown, the return quantity, or the write-down amount, or decline.
Does it change prices or post journals on its own?
No. Each markdown, vendor return, or write-down stays a proposal until a named approver accepts it. The record shows the figures it rested on, who approved, when, and the prior price or cost, so the change can be put back.
Ask about Dead Stock

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy