web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Answered

Expiration date deletion for package tracking for items

(4) ShareShare
ReportReport
Posted on by 35
Please, I need help with the scenario described bellow.
 
As we can maintain Serial, Lot, and Package Numbers in Item tracking, I've set up a tracking code as follow:
-Lot tracking: Lot specific tracking. Meaning traquing is required for all inbouds and outbounds
-Package tracking: just for sales, positive adjustments, negative adjustments and  transfers.
-Use Expiration dates and  strict expiration posting
 
The scenerio that is creating some disruption is explained here: I Assign Lot number and expiration date to items from production orders. At this point it is not required to assign package number.  The next step is to create a transfer order and post a shipment. In the transfer order it is requiered to assing a package number, so I select the lot number to ship and assign the package number. The issue here is that, when assigning the package number the expiration date auto delete and the expiration date field becomes uneditable. If the shipment document is posted, as expected, the item entry created has no expiration date. Nevertheless, when I undo de posted shipment document, the tracking line is updated with the expiration date. Simple said, I have to post the shipment, undo the sipment and post it again.
 
Is there any way that this could be a Buiness Central Bug or am I doing something wrong?
 
I have the same question (0)
  • Verified answer
    CA Vijay Krishna Profile Picture
    187 on at
    This looks very similar to a known BC bug reported in v21/v22: “Expiration date lost when package number added on transfer shipment.”  Microsoft fixed it in later cumulative updates. If youre on-prem or SaaS but behind on updates, upgrading could solve it.
    In Business Central item tracking, each tracking dimension (Lot, Serial, Package) has its own metadata and behaviour:
    • Lot Tracking carries the expiration date field.
    • Package Tracking does not directly maintain expiration metadata; instead, it inherits from the lot when properly linked.
    • When you add a package number after a lot/expiration is already applied, BC sometimes treats it as a new tracking line split. That can cause the expiration date field to reset, because the system assumes you’re defining a fresh tracking dimension record without an expiration. This is not intentional behaviour — it’s a side effect of how BC validates combined tracking dimensions.
    Workarounds / Options

    1. Tracking Code Setup Review
    • In Item Tracking Code, check the “Lot-specific tracking” and “Package-specific tracking” flags.
    • If Package is required only for outbound, consider enabling “Lot Expiration Date Required” (so the lot always pushes its expiration, even if package is added later).
    2. Tracking Policy in Transfer Orders
    • In Transfer Order Transfer Shipment Lines Item Tracking Lines, enter the Lot first, then add the Package.
    • Ensure you’re not overwriting the tracking line but extending it (sometimes users click New Line instead of editing the existing one).
    3. Use Item Tracking Line Inheritance
    • There’s a known pattern: expiration dates do not automatically “copy down” when adding a package.
      A customization or extension is often used to auto-fill the expiration date from the lot into the combined Lot + Package record.
     
  • Suggested answer
    Sahan Hasitha Profile Picture
    2,683 on at
    hi
     
    This issue matches a known BC bug (v21/v22) where expiration dates disappear when adding package numbers on transfer shipments. Microsoft fixed it in later updates, so upgrading may resolve it. The problem occurs because package tracking doesn’t directly store expiration metadata and sometimes resets the expiration when combined with a lot. Workarounds include reviewing Item Tracking Code setup, ensuring lot is entered before package on transfer lines, and using a small customization to auto-inherit expiration dates from the lot to the package.
  • CN-16091855-0 Profile Picture
    35 on at
    Thank you all for your replies. Just for the record, the issue is with on SaaS, Version W1 26.4. All your suggestions have been tested, and still have the problem, so I think I might apply some customization.
     
     
  • Suggested answer
    Rishabh Kanaskar Profile Picture
    6,231 Super User 2026 Season 1 on at
    This behavior is very likely a Business Central bug rather than a setup issue.
    Here’s why:
    You have Lot Tracking set up with Strict Expiration Posting, so the expiration date should always carry through once it’s assigned during production output.
    Assigning a Package No. on the Transfer Order should not wipe out the Expiration Date, both fields are part of Item Tracking Lines and should coexist.
    The fact that the Expiration Date reappears only after undoing and reposting is a strong indicator that BC is mishandling the tracking line data when the Package No. is added.

    Recommended actions:
    Verify you are on the latest cumulative update for your BC version. This issue has been reported in earlier versions and fixed in later builds.
    If you’re already up to date, log this as a support ticket with Microsoft, provide them with your steps to reproduce.
    As a temporary workaround, you can manually re-enter the Expiration Date after assigning the Package No. before posting (if editable in your version), or use a small customization to auto-fill the Expiration Date from the Lot record when Package No. is assigned.
     
    Thanks 
    Rishabh

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 1,869 Super User 2026 Season 1

#2
YUN ZHU Profile Picture

YUN ZHU 1,182 Super User 2026 Season 1

#3
Grigorios Mavrogeorgis Profile Picture

Grigorios Mavrogeorgis 1,109 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Microsoft Training Manuals

Product updates

Dynamics 365 release plans