Reference · built on requestOperator by FibricInventory & supply

Lot Rotation

Projects which lots will expire before they sell, from lot dates and sales rate, and proposes a pick-order change, markdown, or disposal.

Request accessPricing ↗

About

A lot with an expiration date is a clock. Lot Rotation reads each lot's on-hand units and expiration date, the order in which your system picks lots, and the rate the item sells per day. It projects the date each lot runs out at that rate and compares it with the date the lot expires.

Lots that will not clear in time are listed with units, value, and days remaining. For each it proposes moving the lot ahead in pick order, a markdown to lift the sales rate, or disposal once the lot is past use. A quality or inventory manager approves. Nothing is picked differently, repriced, or scrapped until then.

This is a reference listing. It documents what Fibric would read from Lot Rotation 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

  • Lot numbers with expiration dates and on-hand units from NetSuite lot numbered items, Business Central item tracking, or Odoo lots
  • Odoo Expiration Date, Best Before Date, Removal Date, and Alert Date on each lot
  • The pick order in force: NetSuite FEFO Lot Assignments, Business Central Pick According to FEFO, or an Odoo FEFO removal strategy
  • Units sold per day per item from Shopify or BigCommerce orders, or from ERP sales orders
  • Lots already assigned to sales order lines, so a lot promised to a customer is not proposed for markdown
  • Required shelf life per customer, where NetSuite FEFO Lot Assignments stores it

Proposed actions

  • Target capability: propose assigning an earlier-expiring lot to open sales order lines through NetSuite FEFO Lot Assignments
  • Target capability: propose turning on Pick According to FEFO for a Business Central location, or Strict Expiration Posting on the item tracking code
  • Target capability: propose a markdown on the item's Shopify variant price until the lot clears, with the original kept as compareAtPrice
  • Target capability: propose an Odoo scrap order for a lot past its date, with Product, Quantity, Lot/Serial Number, and Source Location filled in
  • Target capability: propose a NetSuite inventory adjustment removing an expired lot, with the lot number under Serial/Lot Numbers 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

  • Move a short-dated lot to the front

    NetSuite shows a lot expiring before its units clear at the current Shopify rate. Assigning it to open sales order lines through FEFO Lot Assignments is proposed, respecting the shelf life each customer requires.

    With NetSuite, Shopify

  • Mark down before the removal date

    An Odoo lot reaches its Alert Date with units still on hand. A Shopify variant markdown is proposed until the lot's Removal Date, and the original price is proposed back afterwards.

    With Odoo, Shopify

  • Scrap what is past use, with a record

    Lots past their Expiration Date in Odoo are proposed as scrap orders with lot and quantity filled in. In NetSuite the same lots are proposed as an inventory adjustment with the lot number and a Memo.

    With Odoo, NetSuite

Requirements

  • Lot tracking with expiration dates: NetSuite Lot Numbered Items, Business Central item tracking codes with expiration, or Odoo Lots & Serial Numbers with Expiration Dates
  • Sales history per item to measure the daily rate, from a storefront or the ERP
  • A rule for what counts as at risk: days of cover short of expiry, or a value threshold
  • A quality or inventory manager named to approve each proposal
Authentication
ERP credentials with item tracking, lot, and adjustment permissions (a NetSuite REST integration, a Business Central OAuth app, or an Odoo API user), plus a Shopify token with write_products for markdowns.

Limits

  • A lot posted without an expiration date cannot be projected. It is listed as undated, not assumed.
  • Business Central picks by FEFO only for items with a warehouse tracking code at locations with the toggle on. Elsewhere pick order stays manual.
  • Sales rate is measured per item, not per lot. Two lots of one item share a rate.
  • Disposal is proposed as a scrap order or an adjustment. Physical removal and any regulated disposal record stay with your team.

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 Lot Rotation ↗

Questions and answers

How does it decide a lot is at risk?
On-hand units in the lot divided by the item's daily sales rate gives days to clear, counting lots ahead of it in pick order. If that runs past the expiration date less the margin you set, the lot is at risk. Both dates are shown.
What is put in front of the manager for each lot?
Per lot: units, value at cost, expiration date, projected clear date, and the proposal chosen, whether a pick-order change, a markdown with its price, or disposal. The manager can switch the proposal, edit the price, or decline.
What record is left, and can it be undone?
Each approved action records the lot, the dates and rate it rested on, who approved, and when. A markdown keeps the prior price for restoring. A scrap or adjustment is recorded as posted, with the reversing entry described.
Ask about Lot Rotation

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