Navigation Menu: Resolve & Sync

• Web Portal: Resolve & Sync: Review Mismatches
• Web Portal: Resolve & Sync: Complete RFID Tasks
• Web Portal: Resolve & Sync: Update Partner Counts via Sync
• Web Portal: Resolve & Sync: Update Partner Counts Manually

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 process involves determining what is accurate by manually reviewing each one. Upon review the user has three options which can be selected: trust RFID count, trust Partner count, or perform a manual count:

• 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.

A Resolution in Simple RFID is the process of investigating discrepancies between scanned RFID counts and expected on-hand quantities from a partner system. It involves reviewing each mismatch, assigning a reason, and completing the needed actions 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 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 .

Resolution Workflows

Discrepancies move through two workflows depending on what correction is required:

Pending Actions (RFID Actions)

The RFID inventory must be adjusted to reflect physical inventory, either increasing or decreasing counts. This may include printing and applying new tags, performing Add scans to register items, or performing Archive scans to remove tags from inventory.

Ready to Sync / Ready for Correction (Update Partner Inventory)

This flow accounts for when the partner system on-hand inventory must be updated up or down.

• With an integration enabled, this tab appears as Ready to Sync, allowing corrections to be sent directly to the partner system.
• If the audit was created using a spreadsheet, the tab will be called Ready for Correction, where an inventory correction file can be exported and uploaded into the partner system.

---

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

Reviewing Mismatched Products

• Choose the products you wish to resolve by clicking the checkbox on the far right.
• Next, click the "Resolve" button to apply a reason.

---

Apply a Reason to Group and/or a Single product

Mismatched Products are grouped as: Under Expected and Over Expected. Once a reason has been applied containing the correct discrepancy adjustment, and Resolved, Pending Actions and Sync / Update tasks are created.

Here are a few of the reasons for an item being Over & Under Expected, along with the associated required Action:

Common Reasons for Over Expected

• Duplicate Tags on Items - Action: Remove extra tags and perform Archive scan to remove them from the RFID count.
• Extra Items Received - You scanned more items than you expected and need to increase your partner to match.
• Unlogged Incoming Inventory - You scanned new items but didn't update your partner on hand inventory.
• Incorrect Adjustment - You scanned more items than you expected. To fix you'll increase the partner quantity to match with the scanned count.

Common Reasons for Under Expected

• Incomplete Purchase Received - Fewer items arrived than ordered. Decrease the partner quantity to match with RFID counts.
• Purchase Not Received - You updated your system with expected inventory that was never delivered. Decrease partner quantity to match with RFID quantity.
• 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 - Reduce partner quantity to correct to match with RFID scans.

When to apply Reason for Over / Under Expected

Generally you'll use the associated reason for over/under expected counts. For example, if an item is under expected, you'll want to use an associated "Under" reason.

To Resolve a mismatch, you need to give it a Reason. Depending on the reason you give it, it will require a specific Action.

There are two different ways you can add a Reason:

1. Group Reason: To apply the same reason for all selected products, use the "Add reason to group" selector.

2. Single Reason: Give a reason for a specific product. The single reason option allows the user to apply both over and under expected reasons to a product.

Multiple reasons can be applied to a single product. This may include applying the opposite reason to its over/under status. This may be needed to properly account for discrepancies. Understand that applying a "Over" expected reason to an "Under Expected" count will create a greater difference to the mismatched count which must be accounted for to resolve the mismatch.

---

Web Portal: Resolve & Sync: Complete RFID Tasks

After mismatched products have been reviewed in the Resolution Center, each product may require one or both of the following:

• RFID Actions – RFID-related tasks that must be completed before the Audit is finalized. These actions may include Printing RFID tags, performing an Add Scan, or performing a Remove Scan to bring the RFID inventory into alignment with the verified physical inventory.
• Partner Corrections – Inventory adjustments that update the quantity in the connected partner system (such as Shopify or Apparel Magic) to match the verified inventory count determined during the Audit.

RFID Actions

Each Pending Action identifies the RFID operation that must be performed to bring the RFID inventory into alignment with the verified inventory count. To view additional details about a specific action, hover over the ? icon in the Action column.

Pending Actions may include the following:

• Ready to Print – Displays the products and quantities that require new RFID tags to be printed and encoded. If the required print job has already been completed, you can locate the existing print job and associate it with the Pending Action instead of printing the tags again.
• Ready to Scan (Add or Remove) – Displays the products and quantities that require an RFID scan to update the RFID inventory. Depending on the action, you will either:
  • Add Scan – Scan RFID tags to add items to the RFID inventory.
  • Remove Scan – Scan RFID tags to remove items from the RFID inventory.

Note: To update RFID inventory, use the mobile app to perform Add scans (to increase the RFID count) or Archive scans (to decrease the RFID count). Printing actions must be completed from the Pending Actions page or by the associated print job generated for the action.

Coming Soon: The next version of the mobile app introduces a dedicated Pending Actions tab that consolidates all required RFID actions into one place. Instead of switching between multiple screens, users will be able to view and complete Add, Archive, and print actions from a single workflow. Here's a preview.

---

Web Portal: Resolve & Sync: Update Partner Counts via Sync

Update Partner Inventory

If you are auditing data from a spreadsheet or non-integrated source, follow these instructions.

• If you manually created your audit the name of this tab will be Ready for Correction.
• If you are auditing data from an integrated source the page will be called Ready to Sync.

Ready to Sync

For integration users the page is called Ready to Sync.

Ignore

Use the ignore button to remove items from the Ready to Sync list without making a change to the partner quantity.

Web Portal: Resolve & Sync: Update Partner Counts Manually

If you are using a 3rd party source to audit, this article walks through the final step in the process--updating the partner system via spreadsheet import.

Partner Corrections

Now that you have reviewed your mismatched products, generated RFID tasks, and identified products which require an inventory correction you can export a spreadsheet with the corrections for upload into your third party source.

Including Corrections in Exported Sheet

Generate a spreadsheet containing corrections in two ways:

• Click on the checkboxes on the right, then click Export Corrections to include specific records
• Click the drop-down arrow, then click "Export all" to include all records in the export

• Inventory corrections are generated as a spreadsheet.
• Sheet is exported,, then upload into partner system.

Product Correction Export

• Take the correction sheet and upload it into your partner system

Mark as Corrected

Once partner system has been updated the user "Mark(s) as Corrected" to indicate that the partner system has been updated.

History tab

Click on the History tab to view the products which have been updated. They will be marked as "Corrected."