Web Portal: Resolve & Sync: Review Mismatches
This article describes the process of reviewing mismatched products generated in an inventory audit. Based on this review process tasks are created (RFID & Partner) to ensure all steps are completed.
What is the Review Mismatches Process?
The Review Mismatches page displays all Mismatched Products from your audits. The user has the ability to apply reasons for the mismatches which falls into three possible outcomes:
- Trust RFID count - If you trust your RFID it means:
- If the RFID count is greater than the Partner Count = increase Partner Count to match the RFID.
- If the RFID count is less than the Partner Count = decrease Partner Count to match the RFID.
- Trust Partner count - If you trust your Partner Count it means:
- If the RFID is greater than the Partner Count = Perform an "Archive" scan on tags to reduce RFID count to match Partner.
- If the RFID is less than the Partner Count = Print and/or scan tags to increase RFID count to match Partner.
- Trust Neither and perform a manual count. Of course you may need to physically inspect the items to identify the issue. In this case the physical count my differ from both the RFID and the Partner Counts. In this case tasks will be generated for both RFID and Partner.
- RFID - Do you trust that all items are tagged and accurately scanning? If so, you can choose this quantity. You may choose to trust the RFID count if you are afraid of overselling and want to ensure that partner quantity isn't inflated, as well is if your partner numbers are deflated and trusting the scanned count will increase the inventory quantity. Trusting the RFID Count means that all Tasks created will be "Partner Tasks."
- Partner - Do you trust the partner software expected count is correct? If so you can choose this quantity. You may choose to trust the partner count at the beginning of the process when you don't have any better data to go from. Trusting the partner quantity means that you are simply aligning your RFID counts to match the partner. Trusting the Partner count means that all pending actions will be "RFID Actions".
- Manual Count - For best accuracy choose this method. Why? Because neither the partner nor scanned quantity may be accurate. Performing a manual review ensures that the correct quantity is entered. Entering a manual count may mean that the product may require both RFID Actions and Partner Corrections.
To Resolve is the process of investigating the mismatched items from an Audit, assigning a reason for the mismatch, which generates tasks to fix the error and align both inventory records.
Assigning a Reason / Generating an Action
Each mismatched product must be assigned a Reason that accounts for why the RFID count differs from the expected quantity (e.g., missing tags, extra items, or incorrect tagging). Each Reason is linked to an Action, which defines how the discrepancy should be resolved.
Examples:
- If a product is scanned -5 less than expected due to products missing tags, the Reason would be Missing Tags. The Action would be to print the missing tags and perform Add scans to update the RFID count.
- If a product is scanned +5 more than expected, the Reason may be Items Double Tagged. The Action would be to remove the extra tags and perform Archive scans to remove them from the RFID inventory.
- If a product is scanned -1 below expected, and inspection confirms the RFID count is accurate, the Reason may be Shrink/Theft. In this case, no RFID adjustment is required; instead, the Action is to reduce the partner on-hand quantity.
Accessing the Resolution Center
Once an audit is completed, all mismatched products are moved to the Resolution Center. From there, users can access mismatches either:
- Directly from the audit by selecting Resolution Center, or
- From the left navigation menu by selecting Resolve & Sync
Steps
1. Review Mismatched Products
- Choose the product(s) you wish to review by clicking the checkbox(es) on the far right.
- Next, click "Resolve" to apply a reason.
2. Apply a Reason
Mismatched Products are grouped and displayed as: Under Expected and Over Expected. Below are a few of the common reasons for an item being Over & Under Expected, along with the associated required Action:
Common Reasons for Over Expected
Common Reasons for Under Expected
- New Inventory Not Tagged - Items exist in inventory but aren't tagged. Print new tags, then perform Add scan to add them to RFID counts.
- Incorrect Adjustment - Partner quantity is too high and must be reduce to match with RFID counts.
- Incomplete Purchase Received - Fewer items arrived than ordered. Decrease the partner quantity to match with RFID counts.
Group or Single Reason
Group Reason
Use the "Add reason to group" control at the top of the section to apply the same reason for all selected products.
- Choose Reason
- Click "Apply to Group"
Once Applied each Product card will show "Ready to resolve", if there is no remaining difference.
3. At the bottom click "Resolve" to generate the Tasks and clear the Mismatches from the list.
Single Reason
From the product card drop-down apply multiple reasons, which can be both over and under expected to a product.
PLEASE NOTE: Applying the opposite reason to a product (E.g.. Applying an Over reason for an Under Expected product will create a greater difference to the mismatched count which must be accounted for to resolve the mismatch.




