Functional overview of Validations and Postback fields
This document describes, in plain business terms, what happens automatically and what gets checked for each warehouse module (Receiving, Put-away, Picking, Movement, Production, …) when an operator uses the handheld scanner. It also explains which extra pieces of information the system shows on the scanner for each module, and why. It's the same information as the technical reference document, rewritten for a business/functional audience.
This describes the standard (out-of-the-box) setup for each module. A system administrator can switch individual checks on or off, or add extra information items, per warehouse location, using the “Create Default Validations” and “Create Default PostBack fields” actions on the Module Settings page.
How to read this: Each module has two parts. “Auto-fill & Check steps” lists what the system fills in automatically for the operator, and what it checks before letting the scan continue — in the order they happen. “Information shown on the scanner” lists the extra details, beyond the standard screen, that the operator sees for that module.
Why extra information is shown on the scanner
The handheld scanner shows a standard set of information for every scan — item, lot, bin, quantity, and so on. On top of that standard set, each module can be set up to show a few extra, process-specific pieces of information. For example: the expiration date the system recommends picking (to keep First-Expired-First-Out discipline), or whether a quantity still needs the operator's confirmation. This brings several benefits:
- The operator sees extra context relevant to the task at hand, without cluttering every scan screen with information that only matters for some processes.
- Some values are shown as “still to confirm” so the operator knows to double-check them, while others are shown as already accepted — avoiding unnecessary re-confirmation.
- Information captured earlier in a multi-step scan (like a chosen pallet type, or an answer to a lot attribute question) is remembered and carried forward, so the operator isn't asked the same question twice.
- Where a barcode already contains a particular piece of data (a GS1 code), a follow-up scan is automatically recognized and routed to the right field, without extra typing.
- Because this is configurable per module, new business needs (lot attributes, vendor lot numbers, packaging quantities, and so on) can be supported without changing the scanner app itself.
Modules covered
- Warehouse Receipt
- Direct Put-Away
- Warehouse Put-away
- Whse. Bulk Put-Away
- Warehouse Pick
- Whse. Bulk Movement
- Movement
- Ad Hoc Movement
- Prod. Output
- Prod. Consumption
- Adv. Prod. Consumption
- Warehouse Shipment
- Sales Return Order
- Transfer Receive
- License Plate Info
Warehouse Receipt
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 2 | Auto-fill | GetBinFromDoc | For Warehouse Receipt and Direct Put-Away, if no bin has been scanned, the system automatically fills in the receiving bin already set on the receipt. • This is a simple convenience default — it never blocks the process. | Yes |
| 3 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 4 | Auto-fill | GetQtyByTransportUOM | If an item has been scanned but no quantity entered, and the item is normally handled in full transport units (a full case or pallet), the system can default the quantity to 'one full unit'. • This saves the operator typing a quantity when they've clearly scanned a full-case/pallet barcode. | Yes |
| 5 | Check | ValidIdentifier | Checks that the system was actually able to make sense of the last scan (as an item, bin, pallet or lot). • If not, the operator is asked to scan again. | Yes |
| 6 | Check | HasBinValue | Checks that a bin has actually been determined before continuing. • If not, the operator is told a bin is required. | Yes |
| 7 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 8 | Check | ExistsOnDocument | Checks that the scanned item is actually part of the source document (the receipt, or the production order for advanced consumption). • If it isn't, the operator is blocked, or — for production, depending on the “Confirm Consumption not Included Item” setting on the WMS Configuration page — asked to confirm they really want to use an item that isn't on the plan. | Yes |
| 9 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 10 | Check | VerifyUnderDelivery | Intended to check for under-delivery on purchase receipts, but currently does not enforce anything — it never blocks a scan. | No — only available if Over/Under Delivery is licensed |
| 11 | Check | VerifyOverDelivery | On purchase-related Warehouse Receipts, checks whether the quantity being received would exceed what was ordered. • A small over-delivery within the allowed tolerance is let through; going beyond that, or receiving when nothing is left to receive, is blocked. | No — only available if Over/Under Delivery is licensed |
| 12 | Check | ValidateExpirationDate | Makes sure an expiration date is available when the item requires one, working it out automatically wherever possible rather than always asking. • On Warehouse Pick, not required for 'mixed content' bins, since those already allow different dates. • If no date can be worked out and none was scanned, the operator is asked to provide one. | Yes |
| 13 | Auto-fill | ResolveItem | On Warehouse Pick, when the operator scans an item barcode, the system looks up which item and quantity that represents. • If several products share the same barcode (a shared GS1 variant code), the operator is asked which one they mean. • If the barcode isn't recognized as any item, the operator is told no matching item was found. | Yes |
| 14 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 15 | Check | GlobalLotAttributes | For Warehouse Receipt, Direct Put-Away, Sales Return and Transfer Receive, when a lot is involved, prompts the operator for any company-wide lot attributes still needing a value — one question at a time. | Yes |
| 16 | Check | NonGlobalLotAttributes | Works the same way as the company-wide lot attributes check, but for attributes that are specific to this particular item. | Yes |
| 17 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
| 18 | Check | LPType | Determines — and, depending on the “Confirm License Plate Type” setting on the Module Settings page (or its override on the Warehouse Templates page for Pick/Movement), asks the operator to confirm — the type of pallet/license plate being used, based on the process (receipt, pick, movement, production, and so on). • Prevents the same physical pallet from ever being registered under two different types. • If confirmation is needed, the operator is asked; a mismatch with a previously registered type blocks the scan. | Yes, if License Plate Types are set up; otherwise No |
| 19 | Check | ValidateRequiredQuantity | A basic safety check used everywhere: the quantity being registered can never be zero. • If it is, the operator is told a quantity is required. | Yes |
| 20 | Check | RemainingQty | Checks that the quantity being registered doesn't exceed what's still outstanding to receive, pick, move or consume for this item. • The limit depends on the process — for production consumption, the “Allow over-consumption on Production Order” setting on the WMS Configuration page can allow going over; for picking or receiving, the Over/Under Pick or Over/Under Delivery add-on setup (where licensed) can allow it. • If the quantity is too high, the operator is told the maximum that can still be handled. | Yes |
| 21 | Check | ValueIsValidForLotNo | Double-checks a scanned 'lot number' to catch a mistake where the operator actually scanned a bin or item barcode. • If that happens, the operator is asked to confirm they really meant to use it as a lot number. | Yes |
| 22 | Check | LotInfoExists | Checks that the scanned lot has a proper lot record in the system (creating one automatically where allowed), and that it isn't blocked. • If lot information is required but missing, or the lot is blocked, the operator is told and can't continue with it. | Yes |
| 23 | Check | UpdateLotAttributes | Saves the lot attribute answers the operator gave into the item's lot record, so the information is stored and available for later use and reporting. | Yes |
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| LotNo | Shows the operator which lot number applies to this scan. • Especially useful when the lot was determined automatically, or when simply looking up a pallet's lot. |
| ExpirationDate | Shows the expiration date the system has determined for this item/lot. • Lets the operator see — and, where required, compare — the date instead of it staying hidden. |
| LastStep | Keeps track of where the operator is in a multi-step scan sequence. • Ensures the process continues from the right point once they answer a question, instead of starting over. |
| LPType | Shows the pallet type (e.g. pallet vs. case) the system has determined, and whether it still needs confirming. • Helps the operator see, and if needed correct, the pallet type before continuing. |
| LotAttributeID | Keeps track of which lot attribute question is currently being asked. • Ensures the operator's next answer is linked to the right question. |
| LotAttributeValueID | Keeps track of the specific value chosen once an answer has been matched to an existing option. • Keeps the scanner and the system in agreement about exactly which value was picked. |
| LotAttributeValue | Carries the operator's actual answer to the lot attribute question currently being asked. • This is what ultimately gets saved to the item's lot record. |
| LotAttributeSequence | Keeps track of where the operator is in a sequence of lot attribute questions. • Makes sure attributes are asked one at a time, in the right order, without repeats. |
| VendorLotNo | Only used when Lot Management is in use: shows the supplier's own lot number captured during receiving. • Keeps the supplier's lot traceable through receiving and put-away. |
| ProductionDate | Only used when Lot Management is in use: shows the manufacturer's production date captured during receiving. • Adds full origin traceability alongside the vendor lot number. |
| Overdelivery | Flags on-screen that this receipt was more than what was ordered, but still within the allowed margin. • Gives the operator visibility that more is being received than ordered, even though it's allowed. |
Direct Put-Away
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Auto-fill | LineResolver | On Direct Put-Away and Ad-Hoc Movement, long-pressing a line on the scanner loads everything already known about that line (bin, pallet, lot, expiration date, quantity) automatically. • Depending on the action, the system may pick the destination pallet automatically, or ask the operator to confirm one — especially for items that require pallet tracking. • If something required is still missing (bin, destination pallet), or the quantity is too high, the operator is stopped and told what's needed. | Yes |
| 2 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 3 | Check | ActionHandler | Recognizes when a scanned code is actually a special control/action code rather than an item, bin or lot, and handles it accordingly. | Yes |
| 4 | Auto-fill | GetBinFromDoc | For Warehouse Receipt and Direct Put-Away, if no bin has been scanned, the system automatically fills in the receiving bin already set on the receipt. • This is a simple convenience default — it never blocks the process. | Yes |
| 5 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 6 | Check | ValidIdentifier | Checks that the system was actually able to make sense of the last scan (as an item, bin, pallet or lot). • If not, the operator is asked to scan again. | Yes |
| 7 | Check | ExpirationDate | On Direct Put-Away and Warehouse Receipt, tries to determine the expiration date automatically — first from the barcode, then, if Aptean Expiration Management and Lot Management are both installed, from the “Expiration Date Calc.” setting on the item's Expiration Setup page (item-level setting first, falling back to the item-attribute-level setting when the item-level one is blank), then from the item's “Expiration Calculation” field — before asking the operator to enter one. | Yes |
| 8 | Auto-fill | GS1ExpirationDate | For Direct Put-Away and Warehouse Receipt, the system reads the expiration date directly out of the scanned barcode and converts it automatically. • This removes the need to type in a date that's already printed in the barcode. | Yes |
| 9 | Auto-fill | AutoCreateLotNo | For Direct Put-Away and Warehouse Receipt, if no lot number was entered, the system can generate one automatically — from the expiration date, or the next number in the item's lot series. • If a lot for that same item/expiration date already exists, it's reused instead of creating a duplicate. • This means lot-tracked items never end up without a lot number, even if the operator doesn't type one. | Yes |
| 10 | Auto-fill | GetQtyByTransportUOM | If an item has been scanned but no quantity entered, and the item is normally handled in full transport units (a full case or pallet), the system can default the quantity to 'one full unit'. • This saves the operator typing a quantity when they've clearly scanned a full-case/pallet barcode. | Yes |
| 11 | Check | RoundQtyPerTransUOM | On Direct Put-Away, rounds the scanned quantity down to whole transport units (whole pallets/cases only, no partial amounts), while also capping it to what's still expected on the receipt. • If rounding changes the quantity, the operator is shown the adjusted number and asked to confirm it. | Yes |
| 12 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 13 | Check | ValidateRequiredQuantity | A basic safety check used everywhere: the quantity being registered can never be zero. • If it is, the operator is told a quantity is required. | Yes |
| 14 | Check | GlobalLotAttributes | For Warehouse Receipt, Direct Put-Away, Sales Return and Transfer Receive, when a lot is involved, prompts the operator for any company-wide lot attributes still needing a value — one question at a time. | Yes |
| 15 | Check | NonGlobalLotAttributes | Works the same way as the company-wide lot attributes check, but for attributes that are specific to this particular item. | Yes |
| 16 | Check | LPType | Determines — and, depending on the “Confirm License Plate Type” setting on the Module Settings page (or its override on the Warehouse Templates page for Pick/Movement), asks the operator to confirm — the type of pallet/license plate being used, based on the process (receipt, pick, movement, production, and so on). • Prevents the same physical pallet from ever being registered under two different types. • If confirmation is needed, the operator is asked; a mismatch with a previously registered type blocks the scan. | Yes |
| 17 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 18 | Check | ExistsOnDocument | Checks that the scanned item is actually part of the source document (the receipt, or the production order for advanced consumption). • If it isn't, the operator is blocked, or — for production, depending on the “Confirm Consumption not Included Item” setting on the WMS Configuration page — asked to confirm they really want to use an item that isn't on the plan. | Yes |
| 19 | Auto-fill | ResolveItem | On Warehouse Pick, when the operator scans an item barcode, the system looks up which item and quantity that represents. • If several products share the same barcode (a shared GS1 variant code), the operator is asked which one they mean. • If the barcode isn't recognized as any item, the operator is told no matching item was found. | Yes |
| 20 | Check | ValueIsValidForLotNo | Double-checks a scanned 'lot number' to catch a mistake where the operator actually scanned a bin or item barcode. • If that happens, the operator is asked to confirm they really meant to use it as a lot number. | Yes |
| 21 | Check | LotInfoExists | Checks that the scanned lot has a proper lot record in the system (creating one automatically where allowed), and that it isn't blocked. • If lot information is required but missing, or the lot is blocked, the operator is told and can't continue with it. | Yes |
| 22 | Check | UpdateLotAttributes | Saves the lot attribute answers the operator gave into the item's lot record, so the information is stored and available for later use and reporting. | Yes |
| 23 | Check | ConfirmLPN | On Direct Put-Away, when a full transport unit is being put away for a pallet-tracked item, the system tries to generate a pallet number automatically; if it can't, the operator is asked to provide one. • Also re-checks the pallet isn't over its allowed capacity. | Yes |
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| SSCC | Shows the pallet/license plate number being used, including ones the system generated automatically. • Helps the operator see exactly which pallet this stock is being registered under. |
| Qty | Shows the quantity the system has worked out or suggested, and whether the operator still needs to confirm it. • Saves the operator re-entering a quantity the system already knows or calculated. |
| BinCode | Shows which bin the system has determined, and whether it's already confirmed. • Gives the operator a visual double-check that they're working with the right bin. |
| LastStep | Keeps track of where the operator is in a multi-step scan sequence. • Ensures the process continues from the right point once they answer a question, instead of starting over. |
| LPType | Shows the pallet type (e.g. pallet vs. case) the system has determined, and whether it still needs confirming. • Helps the operator see, and if needed correct, the pallet type before continuing. |
| RequiredQty | Shows how much quantity is actually expected on this line. • Lets the operator see at a glance if they're about to register less than expected. |
| DocumentLineNo | Keeps track of exactly which line of the source document this scan belongs to. • Makes sure the rest of the process keeps referring to the correct line, especially on Direct Put-Away. |
| ExpirationDateText | Shows the expiration date exactly as scanned from the barcode, before it's converted into a usable date. • Lets the operator double-check the original scan if the converted date ever looks wrong. |
| VendorLotNo | Only used when Lot Management is in use: shows the supplier's own lot number captured during receiving. • Keeps the supplier's lot traceable through receiving and put-away. |
| ProductionDate | Only used when Lot Management is in use: shows the manufacturer's production date captured during receiving. • Adds full origin traceability alongside the vendor lot number. |
| LotAttributeID | Keeps track of which lot attribute question is currently being asked. • Ensures the operator's next answer is linked to the right question. |
| LotAttributeValueID | Keeps track of the specific value chosen once an answer has been matched to an existing option. • Keeps the scanner and the system in agreement about exactly which value was picked. |
| LotAttributeValue | Carries the operator's actual answer to the lot attribute question currently being asked. • This is what ultimately gets saved to the item's lot record. |
| LotAttributeSequence | Keeps track of where the operator is in a sequence of lot attribute questions. • Makes sure attributes are asked one at a time, in the right order, without repeats. |
Warehouse Put-away
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 2 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 3 | Check | ValidIdentifier | Checks that the system was actually able to make sense of the last scan (as an item, bin, pallet or lot). • If not, the operator is asked to scan again. | Yes |
| 4 | Check | HasBinValue | Checks that a bin has actually been determined before continuing. • If not, the operator is told a bin is required. | Yes |
| 5 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 6 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 7 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 8 | Check | ValidateExpirationDate | Makes sure an expiration date is available when the item requires one, working it out automatically wherever possible rather than always asking. • On Warehouse Pick, not required for 'mixed content' bins, since those already allow different dates. • If no date can be worked out and none was scanned, the operator is asked to provide one. | Yes |
| 9 | Auto-fill | ResolveItem | On Warehouse Pick, when the operator scans an item barcode, the system looks up which item and quantity that represents. • If several products share the same barcode (a shared GS1 variant code), the operator is asked which one they mean. • If the barcode isn't recognized as any item, the operator is told no matching item was found. | Yes |
| 10 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
| 11 | Check | OutstandingQty | Checks that the scanned item genuinely has outstanding work on the current task (pick, put-away, movement or bulk task). • If it isn't actually expected here, the operator is told the item isn't on the document. | Yes |
| 12 | Check | RemainingQty | Checks that the quantity being registered doesn't exceed what's still outstanding to receive, pick, move or consume for this item. • The limit depends on the process — for production consumption, the “Allow over-consumption on Production Order” setting on the WMS Configuration page can allow going over; for picking or receiving, the Over/Under Pick or Over/Under Delivery add-on setup (where licensed) can allow it. • If the quantity is too high, the operator is told the maximum that can still be handled. | Yes |
| 13 | Check | ValueIsValidForLotNo | Double-checks a scanned 'lot number' to catch a mistake where the operator actually scanned a bin or item barcode. • If that happens, the operator is asked to confirm they really meant to use it as a lot number. | Yes |
| 14 | Check | PutAwayTemplateCheck | On Warehouse Put-away, enforces the location's put-away guidance rules — bin capacity (weight, pallet count, floor space), whether another item/pallet type already occupies the bin, and whether it's a preferred or empty bin for this item. • Some violations are hard blocked (e.g. exceeding capacity, wrong bin group); others simply ask for confirmation (e.g. an empty bin, or a different lot already there) — unless the system's own suggested bin is used, in which case no confirmation is needed. | Yes, if the “Put-Away Template Guidance” setting is enabled on the WMS Configuration page for this location; otherwise No |
Information shown on the scanner
No extra scanner information is set up for this module.
Whse. Bulk Put-Away
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Check | ActionHandler | Recognizes when a scanned code is actually a special control/action code rather than an item, bin or lot, and handles it accordingly. | Yes |
| 2 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 3 | Check | BulkPutAwayTemplateCheck | Extends the put-away guidance check to Bulk Put-Away, first making sure the whole batch of pallets belongs to a single item, a single pallet type and consistent lot handling, then applying the same bin rules as above. | Yes, if the “Put-Away Template Guidance” setting is enabled on the WMS Configuration page for this location; otherwise No |
| 4 | Check | RegisterBulkPutAway | On Bulk Put-Away, recognizes when what looks like an item scan is actually a bin scan, and treats it as confirming that bin for the whole batch. | Yes |
| 5 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 6 | Check | ValidIdentifier | Checks that the system was actually able to make sense of the last scan (as an item, bin, pallet or lot). • If not, the operator is asked to scan again. | Yes |
| 7 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 8 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 9 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 10 | Check | ValidateExpirationDate | Makes sure an expiration date is available when the item requires one, working it out automatically wherever possible rather than always asking. • On Warehouse Pick, not required for 'mixed content' bins, since those already allow different dates. • If no date can be worked out and none was scanned, the operator is asked to provide one. | Yes |
| 11 | Auto-fill | ResolveItem | On Warehouse Pick, when the operator scans an item barcode, the system looks up which item and quantity that represents. • If several products share the same barcode (a shared GS1 variant code), the operator is asked which one they mean. • If the barcode isn't recognized as any item, the operator is told no matching item was found. | Yes |
| 12 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
| 13 | Check | OutstandingQty | Checks that the scanned item genuinely has outstanding work on the current task (pick, put-away, movement or bulk task). • If it isn't actually expected here, the operator is told the item isn't on the document. | Yes |
| 14 | Check | RemainingQty | Checks that the quantity being registered doesn't exceed what's still outstanding to receive, pick, move or consume for this item. • The limit depends on the process — for production consumption, the “Allow over-consumption on Production Order” setting on the WMS Configuration page can allow going over; for picking or receiving, the Over/Under Pick or Over/Under Delivery add-on setup (where licensed) can allow it. • If the quantity is too high, the operator is told the maximum that can still be handled. | Yes |
| 15 | Check | ValueIsValidForLotNo | Double-checks a scanned 'lot number' to catch a mistake where the operator actually scanned a bin or item barcode. • If that happens, the operator is asked to confirm they really meant to use it as a lot number. | Yes |
Information shown on the scanner
No extra scanner information is set up for this module.
Warehouse Pick
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Check | ValidateTransportCode | On Pick, Shipment Load List and Movement, recognizes a scanned transport/dock/loading code and automatically turns it into the right bin selection. | Yes |
| 2 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 3 | Auto-fill | ScanDestinationLP | On Pick, Movement and Ad-Hoc Movement, when the operator scans a destination pallet, the system checks it's valid and usable for that purpose. • Depending on the situation, it may accept it straight away, ask for confirmation on a brand-new pallet, or reject an invalid one. • Scanning the same destination pallet again simply cancels the previous selection. | No (can be switched on manually) |
| 4 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 5 | Check | ValidIdentifier | Checks that the system was actually able to make sense of the last scan (as an item, bin, pallet or lot). • If not, the operator is asked to scan again. | Yes |
| 6 | Check | HasBinValue | Checks that a bin has actually been determined before continuing. • If not, the operator is told a bin is required. | Yes |
| 7 | Auto-fill | ResolveItem | On Warehouse Pick, when the operator scans an item barcode, the system looks up which item and quantity that represents. • If several products share the same barcode (a shared GS1 variant code), the operator is asked which one they mean. • If the barcode isn't recognized as any item, the operator is told no matching item was found. | Yes |
| 8 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 9 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 10 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 11 | Check | VerifyUnderPick | Intended to check for under-picking on Warehouse Pick, but currently does not enforce anything — it never blocks a scan. | No — only available if Over/Under Delivery or Over/Under Pick is licensed |
| 12 | Check | VerifyOverPick | On Warehouse Pick, checks whether the quantity being picked exceeds what's still outstanding. • A small overpick within the allowed tolerance is let through (and flagged for visibility); going beyond that is blocked. | No — only available if Over/Under Delivery or Over/Under Pick is licensed |
| 13 | Check | ValidateExpirationDate | Makes sure an expiration date is available when the item requires one, working it out automatically wherever possible rather than always asking. • On Warehouse Pick, not required for 'mixed content' bins, since those already allow different dates. • If no date can be worked out and none was scanned, the operator is asked to provide one. | Yes |
| 14 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
| 15 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes (runs a second time later in the sequence) |
| 16 | Check | Exp. Date Restriction | Enforces First-Expired-First-Out (FEFO) picking discipline by comparing the scanned date against the date the system expects the operator to pick. • Depending on the “Pick Expiration Date Restriction” setting on the Warehouse Templates page, a mismatch either requires the operator to confirm they're deliberately picking a different date, or blocks the scan and requires the correct (best) date. | No (can be switched on manually) |
| 17 | Check | DestLicensePlate | For items that require pallet tracking, checks a valid destination pallet has been set before the placement can complete. • If it's missing or invalid, the operator is told and asked to scan/confirm one. | Yes |
| 18 | Check | LPType | Determines — and, depending on the “Confirm License Plate Type” setting on the Module Settings page (or its override on the Warehouse Templates page for Pick/Movement), asks the operator to confirm — the type of pallet/license plate being used, based on the process (receipt, pick, movement, production, and so on). • Prevents the same physical pallet from ever being registered under two different types. • If confirmation is needed, the operator is asked; a mismatch with a previously registered type blocks the scan. | No (can be switched on manually) |
| 19 | Check | QuantityConfirm | Implements 'quick pick': proposes a calculated quantity to the operator and always requires their confirmation, rather than applying it silently. | No (can be switched on manually) |
| 20 | Check | ReasonCode | On Warehouse Pick and Warehouse Receipt, if the quantity registered is less than expected (a shortage), the operator must give a reason code explaining why. • This ensures every short pick or short receipt is documented for later review. | No (can be switched on manually) |
| 21 | Auto-fill | GetWhseItemQty | For bins set up for 'quick pick', if no quantity has been entered, the system proposes the outstanding quantity for this item — capped to what's actually in that bin. • The operator is always asked to confirm the suggested quantity before it's accepted. | Yes |
| 22 | Check | OutstandingQty | Checks that the scanned item genuinely has outstanding work on the current task (pick, put-away, movement or bulk task). • If it isn't actually expected here, the operator is told the item isn't on the document. | Yes |
| 23 | Check | RemainingQty | Checks that the quantity being registered doesn't exceed what's still outstanding to receive, pick, move or consume for this item. • The limit depends on the process — for production consumption, the “Allow over-consumption on Production Order” setting on the WMS Configuration page can allow going over; for picking or receiving, the Over/Under Pick or Over/Under Delivery add-on setup (where licensed) can allow it. • If the quantity is too high, the operator is told the maximum that can still be handled. | Yes |
| 24 | Check | ValueIsValidForLotNo | Double-checks a scanned 'lot number' to catch a mistake where the operator actually scanned a bin or item barcode. • If that happens, the operator is asked to confirm they really meant to use it as a lot number. | Yes |
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| ItemNo | Shows the operator which item the system has determined for this line. • Useful when the item was worked out from a bin/pallet/barcode scan rather than typed in directly. |
| LotNo | Shows the operator which lot number applies to this scan. • Especially useful when the lot was determined automatically, or when simply looking up a pallet's lot. |
| Qty | Shows the quantity the system has worked out or suggested, and whether the operator still needs to confirm it. • Saves the operator re-entering a quantity the system already knows or calculated. |
| BinCode | Shows which bin the system has determined, and whether it's already confirmed. • Gives the operator a visual double-check that they're working with the right bin. |
| ExpirationDate | Shows the expiration date the system has determined for this item/lot. • Lets the operator see — and, where required, compare — the date instead of it staying hidden. |
| LastStep | Keeps track of where the operator is in a multi-step scan sequence. • Ensures the process continues from the right point once they answer a question, instead of starting over. |
| LPType | Shows the pallet type (e.g. pallet vs. case) the system has determined, and whether it still needs confirming. • Helps the operator see, and if needed correct, the pallet type before continuing. |
| RequiredQty | Shows how much quantity is actually expected on this line. • Lets the operator see at a glance if they're about to register less than expected. |
| ReasonCode | Shows the reason the operator gave for a shortage on this line. • Keeps that reason visible during the session and stored on the line for later review. |
| SuggestedExpirationDate | Shows the expiration date the system recommends picking (the First-Expired-First-Out date). • Helps the operator compare what they're about to scan against what they should be picking. |
| MixedLicensePlate | Tells the operator the bin they're picking from contains more than one lot. • Warns them the pallet they pick may not be a single, uniform lot. |
| InternalProductVariant | Carries the internal product-variant code linked to a scanned barcode. • Lets a follow-up scan of the same barcode be understood automatically as the same variant, without asking again. |
| Overpick | Flags on-screen that this pick was more than what was outstanding, but still within the allowed margin. • Gives the operator (and later reporting) visibility of the overpick rather than it only showing up afterwards. |
Whse. Bulk Movement
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Check | ActionHandler | Recognizes when a scanned code is actually a special control/action code rather than an item, bin or lot, and handles it accordingly. | Yes |
| 2 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 3 | Check | RegisterBulkMovement | On Bulk Movement, during the 'place' step, recognizes when what looks like an item scan is actually a bin scan and treats it as confirming that placement bin. | Yes |
| 4 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 5 | Check | ValidIdentifier | Checks that the system was actually able to make sense of the last scan (as an item, bin, pallet or lot). • If not, the operator is asked to scan again. | Yes |
| 6 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 7 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 8 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 9 | Check | ValidateExpirationDate | Makes sure an expiration date is available when the item requires one, working it out automatically wherever possible rather than always asking. • On Warehouse Pick, not required for 'mixed content' bins, since those already allow different dates. • If no date can be worked out and none was scanned, the operator is asked to provide one. | Yes |
| 10 | Auto-fill | ResolveItem | On Warehouse Pick, when the operator scans an item barcode, the system looks up which item and quantity that represents. • If several products share the same barcode (a shared GS1 variant code), the operator is asked which one they mean. • If the barcode isn't recognized as any item, the operator is told no matching item was found. | Yes |
| 11 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
| 12 | Check | OutstandingQty | Checks that the scanned item genuinely has outstanding work on the current task (pick, put-away, movement or bulk task). • If it isn't actually expected here, the operator is told the item isn't on the document. | Yes |
| 13 | Check | RemainingQty | Checks that the quantity being registered doesn't exceed what's still outstanding to receive, pick, move or consume for this item. • The limit depends on the process — for production consumption, the “Allow over-consumption on Production Order” setting on the WMS Configuration page can allow going over; for picking or receiving, the Over/Under Pick or Over/Under Delivery add-on setup (where licensed) can allow it. • If the quantity is too high, the operator is told the maximum that can still be handled. | Yes |
| 14 | Check | ValueIsValidForLotNo | Double-checks a scanned 'lot number' to catch a mistake where the operator actually scanned a bin or item barcode. • If that happens, the operator is asked to confirm they really meant to use it as a lot number. | Yes |
| 15 | Check | ValidateRequiredQuantity | A basic safety check used everywhere: the quantity being registered can never be zero. • If it is, the operator is told a quantity is required. | Yes |
Information shown on the scanner
No extra scanner information is set up for this module.
Movement
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Check | ValidateTransportCode | On Pick, Shipment Load List and Movement, recognizes a scanned transport/dock/loading code and automatically turns it into the right bin selection. | Yes |
| 2 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 3 | Auto-fill | ScanDestinationLP | On Pick, Movement and Ad-Hoc Movement, when the operator scans a destination pallet, the system checks it's valid and usable for that purpose. • Depending on the situation, it may accept it straight away, ask for confirmation on a brand-new pallet, or reject an invalid one. • Scanning the same destination pallet again simply cancels the previous selection. | No (can be switched on manually) |
| 4 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 5 | Check | ValidIdentifier | Checks that the system was actually able to make sense of the last scan (as an item, bin, pallet or lot). • If not, the operator is asked to scan again. | Yes |
| 6 | Check | HasBinValue | Checks that a bin has actually been determined before continuing. • If not, the operator is told a bin is required. | Yes |
| 7 | Check | InvalidBinCodeCheck | On Movement, prevents an operator from registering stock into a bin the movement document has already designated as a different destination for that same item. | Yes |
| 8 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 9 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 10 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 11 | Check | InspectConsolidatedProdMovement | When Process Manufacturing and Inspection Status are both in use, and stock is being moved into production, checks the lot isn't on quality hold. • If it is, the operator is told the lot is blocked for consumption and the move cannot continue. | No — only available if both Aptean Inspection Status and Aptean Process Manufacturing are installed |
| 12 | Check | ValidateExpirationDate | Makes sure an expiration date is available when the item requires one, working it out automatically wherever possible rather than always asking. • On Warehouse Pick, not required for 'mixed content' bins, since those already allow different dates. • If no date can be worked out and none was scanned, the operator is asked to provide one. | Yes |
| 13 | Auto-fill | ResolveItem | On Warehouse Pick, when the operator scans an item barcode, the system looks up which item and quantity that represents. • If several products share the same barcode (a shared GS1 variant code), the operator is asked which one they mean. • If the barcode isn't recognized as any item, the operator is told no matching item was found. | Yes |
| 14 | Auto-fill | GetWhseItemQty | For bins set up for 'quick pick', if no quantity has been entered, the system proposes the outstanding quantity for this item — capped to what's actually in that bin. • The operator is always asked to confirm the suggested quantity before it's accepted. | Yes |
| 15 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
| 16 | Check | DestLicensePlate | For items that require pallet tracking, checks a valid destination pallet has been set before the placement can complete. • If it's missing or invalid, the operator is told and asked to scan/confirm one. | Yes |
| 17 | Check | LPType | Determines — and, depending on the “Confirm License Plate Type” setting on the Module Settings page (or its override on the Warehouse Templates page for Pick/Movement), asks the operator to confirm — the type of pallet/license plate being used, based on the process (receipt, pick, movement, production, and so on). • Prevents the same physical pallet from ever being registered under two different types. • If confirmation is needed, the operator is asked; a mismatch with a previously registered type blocks the scan. | No (can be switched on manually) |
| 18 | Check | OutstandingQty | Checks that the scanned item genuinely has outstanding work on the current task (pick, put-away, movement or bulk task). • If it isn't actually expected here, the operator is told the item isn't on the document. | Yes |
| 19 | Check | RemainingQty | Checks that the quantity being registered doesn't exceed what's still outstanding to receive, pick, move or consume for this item. • The limit depends on the process — for production consumption, the “Allow over-consumption on Production Order” setting on the WMS Configuration page can allow going over; for picking or receiving, the Over/Under Pick or Over/Under Delivery add-on setup (where licensed) can allow it. • If the quantity is too high, the operator is told the maximum that can still be handled. | Yes |
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| LastStep | Keeps track of where the operator is in a multi-step scan sequence. • Ensures the process continues from the right point once they answer a question, instead of starting over. |
| LPType | Shows the pallet type (e.g. pallet vs. case) the system has determined, and whether it still needs confirming. • Helps the operator see, and if needed correct, the pallet type before continuing. |
Ad Hoc Movement
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Auto-fill | LineResolver | On Direct Put-Away and Ad-Hoc Movement, long-pressing a line on the scanner loads everything already known about that line (bin, pallet, lot, expiration date, quantity) automatically. • Depending on the action, the system may pick the destination pallet automatically, or ask the operator to confirm one — especially for items that require pallet tracking. • If something required is still missing (bin, destination pallet), or the quantity is too high, the operator is stopped and told what's needed. | Yes |
| 2 | Check | ActionHandler | Recognizes when a scanned code is actually a special control/action code rather than an item, bin or lot, and handles it accordingly. | Yes |
| 3 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 4 | Auto-fill | ScanDestinationLP | On Pick, Movement and Ad-Hoc Movement, when the operator scans a destination pallet, the system checks it's valid and usable for that purpose. • Depending on the situation, it may accept it straight away, ask for confirmation on a brand-new pallet, or reject an invalid one. • Scanning the same destination pallet again simply cancels the previous selection. | No (can be switched on manually) |
| 5 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 6 | Check | HasBinValue | Checks that a bin has actually been determined before continuing. • If not, the operator is told a bin is required. | Yes |
| 7 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 8 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 9 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 10 | Check | ValidateExpirationDate | Makes sure an expiration date is available when the item requires one, working it out automatically wherever possible rather than always asking. • On Warehouse Pick, not required for 'mixed content' bins, since those already allow different dates. • If no date can be worked out and none was scanned, the operator is asked to provide one. | Yes |
| 11 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
| 12 | Check | LPType | Determines — and, depending on the “Confirm License Plate Type” setting on the Module Settings page (or its override on the Warehouse Templates page for Pick/Movement), asks the operator to confirm — the type of pallet/license plate being used, based on the process (receipt, pick, movement, production, and so on). • Prevents the same physical pallet from ever being registered under two different types. • If confirmation is needed, the operator is asked; a mismatch with a previously registered type blocks the scan. | Yes |
| 13 | Check | QuantityConfirm | Implements 'quick pick': proposes a calculated quantity to the operator and always requires their confirmation, rather than applying it silently. | Yes |
| 14 | Check | AdhocMvtTemplateCheck | On Ad-Hoc Movement 'place' actions, applies the same put-away guidance rules described above, but only where a Sub Module Template set to “Item Put-Away Templates” exists for Ad Hoc Movement at this location. | No — only available if a Sub Module Template set to “Item Put-Away Templates” exists for this location and module |
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| Qty | Shows the quantity the system has worked out or suggested, and whether the operator still needs to confirm it. • Saves the operator re-entering a quantity the system already knows or calculated. |
| BinCode | Shows which bin the system has determined, and whether it's already confirmed. • Gives the operator a visual double-check that they're working with the right bin. |
| ItemNo | Shows the operator which item the system has determined for this line. • Useful when the item was worked out from a bin/pallet/barcode scan rather than typed in directly. |
| LotNo | Shows the operator which lot number applies to this scan. • Especially useful when the lot was determined automatically, or when simply looking up a pallet's lot. |
| LPType | Shows the pallet type (e.g. pallet vs. case) the system has determined, and whether it still needs confirming. • Helps the operator see, and if needed correct, the pallet type before continuing. |
Prod. Output
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 2 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 3 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 4 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
| 5 | Check | ProdOutPutOverProduction | On Production Output, checks whether registering this output would produce more than the production order calls for. • Depending on the “Over-production” setting on the WMS Configuration page, over-production is allowed automatically, blocked outright, or requires the operator's explicit confirmation. | Yes |
| 6 | Check | LPType | Determines — and, depending on the “Confirm License Plate Type” setting on the Module Settings page (or its override on the Warehouse Templates page for Pick/Movement), asks the operator to confirm — the type of pallet/license plate being used, based on the process (receipt, pick, movement, production, and so on). • Prevents the same physical pallet from ever being registered under two different types. • If confirmation is needed, the operator is asked; a mismatch with a previously registered type blocks the scan. | No (can be switched on manually) |
Information shown on the scanner
No extra scanner information is set up for this module.
Prod. Consumption
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 2 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 3 | Check | HasBinValue | Checks that a bin has actually been determined before continuing. • If not, the operator is told a bin is required. | Yes |
| 4 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 5 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 6 | Check | RemainingQty | Checks that the quantity being registered doesn't exceed what's still outstanding to receive, pick, move or consume for this item. • The limit depends on the process — for production consumption, the “Allow over-consumption on Production Order” setting on the WMS Configuration page can allow going over; for picking or receiving, the Over/Under Pick or Over/Under Delivery add-on setup (where licensed) can allow it. • If the quantity is too high, the operator is told the maximum that can still be handled. | Yes |
| 7 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 8 | Check | LotInfoExists | Checks that the scanned lot has a proper lot record in the system (creating one automatically where allowed), and that it isn't blocked. • If lot information is required but missing, or the lot is blocked, the operator is told and can't continue with it. | Yes |
| 9 | Check | ValidateExpirationDate | Makes sure an expiration date is available when the item requires one, working it out automatically wherever possible rather than always asking. • On Warehouse Pick, not required for 'mixed content' bins, since those already allow different dates. • If no date can be worked out and none was scanned, the operator is asked to provide one. | Yes |
| 10 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
Information shown on the scanner
No extra scanner information is set up for this module.
Adv. Prod. Consumption
Auto-fill & Check steps
| # | Step type | Configuration name | What happens | Switched on by default? |
|---|---|---|---|---|
| 1 | Auto-fill | ResolveLPN | When the operator scans a pallet/license plate barcode, the system looks up everything already known about it — item, lot, expiration date and current bin — and fills that in automatically. • The exact behavior adapts to the task, e.g. loading the matching put-away line, or knowing whether stock is being taken from or placed onto that pallet. • If the pallet doesn't exist here, or holds more than one item/lot, the operator is told, or asked which one they mean. | Yes |
| 2 | Auto-fill | ResolveBin | When the operator scans a bin barcode, the system recognizes it and sets it as the bin being worked on. • For a 'mixed content' pick bin, or for Ad-Hoc/Direct Put-Away, it can also fill in the item, pallet and lot automatically from what's already known about that bin or pallet. • If the scanned code isn't a valid bin for this location, the operator is told the bin isn't used here. | Yes |
| 3 | Check | HasBinValue | Checks that a bin has actually been determined before continuing. • If not, the operator is told a bin is required. | Yes |
| 4 | Check | ItemValidation | Checks that the item involved is not blocked for use. • If it is, the operator is told and the scan cannot continue. | Yes |
| 5 | Auto-fill | ResolveQuantityfromAI | If no quantity has been entered yet, the system tries to read it directly from the scanned barcode (a weight or count encoded in it). • If the barcode doesn't provide a usable quantity, the operator is asked to enter one manually. | No (can be switched on manually) |
| 6 | Check | RemainingQty | Checks that the quantity being registered doesn't exceed what's still outstanding to receive, pick, move or consume for this item. • The limit depends on the process — for production consumption, the “Allow over-consumption on Production Order” setting on the WMS Configuration page can allow going over; for picking or receiving, the Over/Under Pick or Over/Under Delivery add-on setup (where licensed) can allow it. • If the quantity is too high, the operator is told the maximum that can still be handled. | Yes |
| 7 | Check | Tracking | Makes sure a required lot or serial number has actually been captured for this scan. • Skipped for 'mixed content' pick bins; on Warehouse Receipt, the scanned lot is compared against what's reserved on the purchase/sales/transfer order. • If several lots are possible, or a required one is still missing, the operator is asked to choose or enter one. | Yes |
| 8 | Check | LotInfoExists | Checks that the scanned lot has a proper lot record in the system (creating one automatically where allowed), and that it isn't blocked. • If lot information is required but missing, or the lot is blocked, the operator is told and can't continue with it. | Yes |
| 9 | Check | ValidateExpirationDate | Makes sure an expiration date is available when the item requires one, working it out automatically wherever possible rather than always asking. • On Warehouse Pick, not required for 'mixed content' bins, since those already allow different dates. • If no date can be worked out and none was scanned, the operator is asked to provide one. | Yes |
| 10 | Check | ValidateLicensePlate | The main pallet check: determines whether a pallet/license plate is required for this scan, and if so, checks a valid one has been provided. • It also checks quantity limits per pallet, prevents mixing the wrong lot onto a pallet, and (on purchase receipts) prevents scanning the same pallet twice. • If a pallet is required but missing, invalid, over capacity, or used incorrectly, the operator is told exactly what's wrong. | Yes |
| 11 | Check | ExistsOnDocument | Checks that the scanned item is actually part of the source document (the receipt, or the production order for advanced consumption). • If it isn't, the operator is blocked, or — for production, depending on the “Confirm Consumption not Included Item” setting on the WMS Configuration page — asked to confirm they really want to use an item that isn't on the plan. | Yes |
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| SourceLineNo | Keeps track of exactly which production order component line this consumption scan belongs to. • Used so a later correction can be linked back to the right line. |
| SourceSublineNo | Works together with the line reference above when a single component line has several tracked sub-lines (e.g. by lot) that need to be told apart. |
Warehouse Shipment
Auto-fill & Check steps
No default checks are set up for this module.
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| PackagingQuantity | Only used when Aptean Packaging is in use, on Warehouse Shipment: shows the packaging-level quantity needed for that integration. • Lets the packaging quantity be captured and shown separately from the normal quantity. |
Sales Return Order
Auto-fill & Check steps
No default checks are set up for this module.
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| LotAttributeID | Keeps track of which lot attribute question is currently being asked. • Ensures the operator's next answer is linked to the right question. |
| LotAttributeValueID | Keeps track of the specific value chosen once an answer has been matched to an existing option. • Keeps the scanner and the system in agreement about exactly which value was picked. |
| LotAttributeValue | Carries the operator's actual answer to the lot attribute question currently being asked. • This is what ultimately gets saved to the item's lot record. |
| LotAttributeSequence | Keeps track of where the operator is in a sequence of lot attribute questions. • Makes sure attributes are asked one at a time, in the right order, without repeats. |
Transfer Receive
Auto-fill & Check steps
No default checks are set up for this module.
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| LotAttributeID | Keeps track of which lot attribute question is currently being asked. • Ensures the operator's next answer is linked to the right question. |
| LotAttributeValueID | Keeps track of the specific value chosen once an answer has been matched to an existing option. • Keeps the scanner and the system in agreement about exactly which value was picked. |
| LotAttributeValue | Carries the operator's actual answer to the lot attribute question currently being asked. • This is what ultimately gets saved to the item's lot record. |
| LotAttributeSequence | Keeps track of where the operator is in a sequence of lot attribute questions. • Makes sure attributes are asked one at a time, in the right order, without repeats. |
License Plate Info
Auto-fill & Check steps
No default checks are set up for this module.
Information shown on the scanner
| Configuration name | What the operator sees and why it matters |
|---|---|
| LotNo | Shows the operator which lot number applies to this scan. • Especially useful when the lot was determined automatically, or when simply looking up a pallet's lot. |