NetSuite Lot Expiry and FEFO Picking Requirements

A workable first-expiry-first-out process selects the earliest-expiring lot that is eligible for the customer's requirement, then verifies that the warehouse actually picks it. Recording an expiration date is only the starting point. Allocation, minimum remaining shelf life, inventory status, and physical picking must agree.

Before configuring FEFO in NetSuite, identify the execution layer: native lot records, NetSuite WMS picking rules, the FEFO Lot Assignments SuiteApp, or a third-party solution. Their capabilities and supported transaction paths differ. Do not assume one setting governs every sale, transfer, return, and production movement.

Define eligibility before sorting by expiry

Write the rule in business terms. Which date matters: dispatch, expected delivery, or the customer's receipt? How many days of remaining life must be left? Are there customer-specific thresholds? Who may approve an exception?

Include quality and inventory status. The earliest-expiring lot may be quarantined, already assigned elsewhere, or unsuitable for the customer. A valid FEFO decision filters out ineligible stock before choosing among the remaining lots.

Use a documented rule for missing or disputed expiry dates. Do not let a blank value silently become “never expires” or the earliest possible date. Quality should decide the permitted treatment, and the application should make the exception visible.

Distinguish the NetSuite components

NetSuite lot records can store expiration dates and track lot quantities through purchasing and sales. This provides the inventory identity needed for expiry control. It does not, by itself, prove that every transaction route enforces the business's shelf-life policy.

The FEFO Lot Assignments SuiteApp supports scheduled commitment and lot assignment, as well as an order-fulfillment assignment mode. For expiry-controlled items, assignment uses expiry; otherwise it can use FIFO. Customer shelf requirements and minimum fulfillment needs are relevant in its supported assignment flow.

NetSuite WMS also has its own picking configuration. Confirm installed features, SuiteApp prerequisites, current release, and compatibility before choosing the mechanism. A custom FEFO script or external WMS should be documented as that solution, rather than described as universal native NetSuite behavior.

Build a representative lot test set

Use at least three lots with different expiry dates, plus one unavailable lot and one missing-date exception if applicable. Give them different bins and realistic quantities so the test exercises selection as well as sorting.

Test sufficient and insufficient eligible stock. Add an order requiring more than the earliest lot contains, a customer with a stricter shelf-life requirement, and a shipment delayed after allocation. Include a lot that expires during transit if customer acceptance is measured at delivery.

Record the expected lot and quantity breakdown before running the process. This lets the reviewer distinguish a legitimate bypass of an ineligible early lot from a genuine FEFO failure.

Hypothetical shelf-life decision

Assume an order is expected to reach the customer on November 10. The approved policy requires 30 days of remaining shelf life at delivery. Lot A expires November 25, Lot B expires December 20, and Lot C expires January 15.

Lot A expires first but has only 15 days remaining at the assumed delivery date, so it does not satisfy this customer's rule. Of the eligible lots, B is the first-expiring choice. If B has 40 units and the order needs 60, the proposed selection is 40 from B and 20 from C, subject to commitments and other controls.

Now the delivery estimate moves to December 1. B has only 19 days remaining and becomes ineligible under the same policy. A lot assignment made earlier should therefore be reviewed before dispatch.

The example illustrates a decision rule, not a guarantee that every NetSuite configuration calculates shelf life from the delivery date. Prove how the selected application represents the reference date and threshold, or implement an approved control for the gap.

Verify receiving data before blaming picking

Inspect expiry capture at receiving. Confirm the supplier's label, date format, lot identity, and the recorded value. Ambiguous day-month formats and reused lot names can create selection errors that appear to be warehouse-rule failures.

Preserve a clear relationship between supplier lot information and any internal lot identifier. If multiple receipts use the same lot, establish who may change its expiry data and how existing stock is affected. A correction to one shared lot record can influence more than the latest receipt.

Test barcode and manual entry routes. A handheld may read a date while a manual receipt leaves it blank. Both flows need a defined response. Do not fabricate an expiry date simply to complete a required field.

Follow the lot through picking and shipment

Compare recommended, assigned, picked, and shipped lots. Those can diverge when an operator substitutes stock, a bin is empty, or another transaction changes availability. Record substitutions with their business reason and approval where required.

Verify that the warehouse can physically distinguish lots. Mixed bins, damaged labels, and poorly separated cases can defeat an accurate system recommendation. A second confirmation at packing may be appropriate for a high-consequence product, but it should be designed around the actual risk and workload.

Test the supported reversal and repick route. If a lot is rejected after picking, the inventory and assignment records must match the returned physical goods before a replacement lot is used. Simply editing the final lot field can leave the earlier movement unexplained.

Decide what happens at expiry

Define how expired stock becomes unavailable and who owns review, return, or disposal. An alert is useful only if someone acts on it. An automated status change needs tested scope, timing, failure handling, and authorized override behavior.

Keep operational expiry control separate from financial write-off policy. An item can be physically held while finance evaluates the appropriate accounting treatment. Quality, legal, or regulatory specialists should establish any industry-specific requirements; a FEFO configuration alone does not establish compliance.

Include returns. A returned lot may meet its original shipment rule but fail the remaining-life requirement for resale. Reinspect its condition and eligibility before it re-enters the selection pool.

Accept the process using exception evidence

A good acceptance pack shows the rule, configured mechanism, expected selection, actual selected lots, physical scan evidence, and final shipment. Include tests that correctly refuse or divert an unsuitable lot, not only clean examples that succeed.

Review unsupported transaction types and custom entry channels explicitly. If a production issue, cash sale, or external warehouse route is outside the chosen solution's scope, document the separate control. Avoid a broad “FEFO enabled” sign-off that hides those gaps.

For account-specific design, CuriousRubik's NetSuite support services can be approached with the eligibility policy and representative lot test set. The aim is a verifiable lot-selection process, with appropriate quality and finance approval where relevant.

Frequently asked questions

Does entering an expiration date automatically enforce FEFO everywhere?

No. The date supports lot identification, while assignment and picking depend on the configured application and transaction route. Verify the FEFO Lot Assignments SuiteApp, WMS rules, custom logic, or third-party solution actually used.

Should the earliest-expiring lot always be picked?

Only if it is eligible. Quarantine, existing commitments, customer shelf-life thresholds, and other approved restrictions can exclude it. FEFO should select the earliest-expiring lot within the eligible population.

Is FEFO the same as FIFO?

No. FEFO prioritizes expiry, while FIFO prioritizes receipt or inventory sequence under the relevant process. An earlier-received lot can expire later than a newer receipt, so the policies can choose different physical stock.

What if shipment is delayed after lots are assigned?

Recheck eligibility against the approved reference date and remaining-life requirement. A lot that was acceptable when allocated may no longer qualify at dispatch or expected delivery. Record any substitution and its approval.

Can a FEFO setup prove regulatory compliance?

No. It is one operational control. Applicable requirements, quality procedures, validation, records, and exceptions need review by the responsible specialists. Test the system against those approved requirements rather than treating a feature label as certification.