Overview
Receiving-Only Tracking lets you capture Lot Number, Expiry Date, or Production Date at the point of receiving — for traceability and audit purposes — without those values becoming inventory dimensions. This is useful for products where you want a record of what attributes were received, but don't need inventory split out by lot, expiry, or production date for picking, packing, or shipping.
When to Use It
Use Receiving-Only Tracking when:
You need an audit trail of Lot Number, Expiry Date, or Production Date for a product, but don't want inventory fragmented by that attribute
Downstream operations (picking, packing, shipping) don't need to require or scan that attribute
You currently leave a tracking attribute off entirely but want visibility into what was received, without the operational overhead of full tracking
⚠️ Receiving-Only capture is only available through the mobile PO receiving flow. The desktop Purchase Order screen, Cross-Dock Receiving, Return Order receiving, and the Open API receiving endpoint are not affected — they continue to work exactly as before, even for products with Receiving-Only flags set.
Prerequisites
Before setting up Receiving-Only Tracking, ensure:
Your user account has permission to create or edit products
You understand that a tracking attribute (Lot, Expiry, or Production Date) and its corresponding Receiving-Only flag cannot both be enabled at the same time for the same product
Step-by-Step Instructions
Navigate to Products and open the product you want to configure (or create a new one).
In the product drawer, go to Step 4. Advanced.
Open the tracking accordion for the attribute you want to configure: Lot/Batch Tracking, Expiry Tracking, or Production Date Tracking.
Locate the new Receiving-Only [Attribute] Tracking toggle inside that accordion.
Set Receiving-Only [Attribute] Tracking to Yes.
If the master tracking toggle for that attribute (e.g. Expiry Date Tracking) is currently Yes, the system will not let both be Yes at once — the master toggle is automatically reset to No, or the save is blocked, depending on which toggle you changed last.
Repeat for any other attribute (Lot, Expiry, Production Date) you want to mark Receiving-Only. Each of the three attributes is independent — enabling Receiving-Only on one does not affect the others.
Click Save.
Confirm: the accordion subtitle chip reflects the active tracking mode, and reopening the product shows your saved toggle state correctly.
Key Fields & Options
Field | Description | Notes |
[Attribute] Tracking | The existing master toggle for Lot, Expiry, or Production Date tracking | Enabling this tracks the attribute as a full inventory dimension |
Receiving-Only [Attribute] Tracking | New toggle that captures the attribute at receiving without tracking it on inventory | Cannot be Yes at the same time as the master toggle for that same attribute |
Resulting behavior by combination:
Master Tracking | Receiving-Only Tracking | Result |
No | No | Not tracked at all — no capture, no inventory tracking, no downstream requirement |
Yes | No | Full tracking (standard behavior) — captured, tracked on inventory, required downstream |
No | Yes | Receiving-only capture — captured at mobile receiving, shown on Receiving History report, not written to inventory, not required downstream |
Yes | Yes | ⚠️ Invalid — blocked with a validation error |
What Happens During Receiving
When a product with a Receiving-Only flag is scanned during mobile PO receiving, an input field for that attribute appears on the Select Product / Attributes screen, separate from any standard tracking fields. If the flag is set, entering the value is required to complete the receipt.
⚠️Expiry Date and Production Date must be entered and stored in the
yyyyMMddformat.
Once submitted, Receiving-Only values are recorded only in Receiving History and are not stored as inventory attributes. They do not create lot, expiry date, or production date dimension splits for the SKU.
Receiving-Only values appear as columns in the Receiving History report and are populated only when a value was captured during receiving. These values are also included when the report is exported to Excel.
If a receipt containing Receiving-Only values is cancelled from the Receiving History report, the associated Receiving-Only values are voided along with the receipt. This ensures that cancelled receipts do not leave behind active Receiving-Only data.
Common Questions & Edge Cases
Can I set both the master tracking toggle and the Receiving-Only toggle to Yes for the same attribute?
No. The two are mutually exclusive. Turning one on automatically turns the other off (or blocks the change), so a product can never have both active for the same attribute.
Does enabling Receiving-Only tracking for Lot Number also require it for Expiry Date or Production Date?
No. The three attributes are fully independent. You can mix and match — for example, standard Lot Tracking with Receiving-Only Expiry Tracking on the same product.
Will this affect receiving through the desktop Purchase Order screen, Cross-Dock, Return Orders, or the Open API?
No. Receiving-Only capture only applies to the mobile PO receiving flow. All other receiving entry points continue to work exactly as before, with no new fields or requirements, even for products that have Receiving-Only flags set.
Can integrators set these flags through the API?
Yes. The Receiving-Only Lot, Expiry Date, and Production Date flags are available on the Open API's product create, update, patch, and detail/list endpoints, so they can be set the same way as through the UI.
What happens if I import products via Excel with these columns?
Excel import validates the values as True/False. An invalid value in a Receiving-Only tracking column causes that row to be rejected with a validation message, while the rest of the file continues processing.
