Validation in ItemCodes and SerialNumbers in WMS and SFS
We are pleased to announce the addition of new validation rules for Item Codes and Serial Numbers in our Warehouse Management System (WMS) and Ship from Store (SFS). These new rules will help ensure that the codes you scan/ enter are accurate and consistent, reducing errors and improving efficiency.
Key Features
Improved Accuracy for Item Codes:
Ensures Item Codes follow specific patterns, such as:
Starting with certain characters or digits.
Matching parts of the SKU, like style or size.
Being of a specific length or format.
Enhanced Validation for Serial Numbers:
Similar checks as Item Codes to ensure Serial Numbers are correctly formatted and consistent.
User-Friendly Configuration:
Easy-to-use interface to set up and test these validation rules.
Benefits
Reduced Errors: Fewer mistakes when entering Item Codes and Serial Numbers.
Better Consistency: Ensures codes follow your brand's specific patterns.
Improved Efficiency: Saves time by catching errors at the point of entry.
Assumptions
Validation rules will be defined and applied at the client level.
SKU master data will be used for rule definitions.
Out of Scope
Current validations do not extend to using Purchase Order (PO) data or Box data. Future updates may include these elements.
Implementation Notes
Rules can be configured to be case-sensitive as required.
Prefix and suffix validations based on variable fields from SKU master data.
Support for complex barcode patterns like "INCREFF{SKUCode}{numeric value}".
Examples
Pattern Validation for ItemCodes:
First X characters are digits or not digits.
First X characters must match a specific field from the SKU master (e.g., style, size, color) followed by Y digits.
Combination of digits and characters in specified sequences.
Exact length and specific string patterns.
Sample patterns include:
Length exactly 10 characters, all digits.
Exactly “abc” string at the start, followed by X digits.
Pattern Validation for ItemSerialNumbers:
Similar rules as ItemCodes, with additional patterns like:
ItemSerialCode = ItemCode + String “abc”.
Setting the Serial Code Rules
Go to Serial Code Rules-> Edit Rules.
Click on Add Rule.
Add the Rule
To set the Actions, go to Actions Tab.
Choose the Action and Params.
Add the conditions from Condition tab.
On Saving, the condition would be displayed. More conditions can be added.
Setting the Item Code Rules
Similar to Serial code rules, Item Code Rules can be set.
FAQs
What specific validation rules are being applied to the External Serial Codes and ItemCodes?
The validation rules involve checking the format of ItemCodes and External Serial Codes. These include patterns like ensuring the first X characters are digits or not, matching the first X characters to a part of the barcode or other SKU master data fields (style, size, color), and combinations such as a specific length or a predefined string followed by digits.
How do these validation rules improve or change the existing functionality?
These rules reduce errors in capturing and mapping ItemCodes and Serial Numbers by ensuring they follow a consistent and correct pattern, thus improving data accuracy and reducing the likelihood of mismatches or errors.
Are there any specific scenarios or use cases that these validation rules address?
The rules are applied at various entry points like item creation (GRN), returns, and wherever items are being created. They ensure that the scanned values adhere to specific patterns required by different brands.
Who are the primary users affected by this feature?
The primary users are warehouse and store operations teams who handle item entries, returns, and inventory management within the WMS (Warehouse Management System) and SFS (Store Fulfillment System).
How does this feature impact the overall system performance or workflow?
The feature ensures higher accuracy in data capture, reducing the need for manual corrections and improving overall workflow efficiency. It does not significantly impact system performance but enhances data integrity.
Are there any dependencies or prerequisites for this feature to work correctly?
The validation rules are set at the client level and may use SKU master data. The system should have access to accurate and up-to-date SKU data for these rules to function correctly.