Alert: Potential ReFID Mismatch Encountered While Running the POS Sync

Overview

This alert is triggered when T.M.A.S. attempts to pull POS data using the Location IDs configured in T.M.A.S., but one or more of those IDs do not exist or cannot be found in your POS system.

T.M.A.S. uses the Location ID mappings you have entered to request sales, transactions, and other POS data.
If a POS location ID is missing, invalid, or no longer active, the POS may:

• Return no data at all
• Return partial data (depending on the POS provider’s behavior)
• Reject the request entirely
• Because each POS system handles invalid location IDs differently, sync results may vary.

Why You Received This Alert

During the sync, T.M.A.S. submitted the list of Location IDs configured for your POS integration.
One or more of the following occurred:

• The ID does not exist in the POS anymore
• The ID was changed or renamed in the POS
• The ID was removed because the store closed
• The ID was mistyped or not changed from default in T.M.A.S. when the location was created
• The POS account no longer includes that store
• The POS system returned only partial data and flagged the mismatch

The alert indicates that at least one Location ID in T.M.A.S. did not match any known POS location.

Important: Behavior Varies by POS Platform

Depending on your POS provider, the results of a mismatch differ:

Some POS systems return no data if any ID is invalid

• The entire sync may fail
• T.M.A.S. may receive no updates for all locations

Some POS systems return partial data for valid IDs and skip invalid ones

• Stores with correct IDs sync normally
• Stores with incorrect IDs are silently ignored or flagged

Some POS systems return errors only for the mismatched ID

• Only one location stops syncing
• All others continue as expected

Because each POS API behaves differently, this alert does not always mean that all POS data failed — only that at least one location ID was not recognized.

How to Fix the ReFID Mismatch

To resolve the alert, verify that the Location IDs configured in T.M.A.S. match exactly the IDs in your POS system.

Step 1 — Identify Which Location Failed

Check:

• The alert message
• The Sales reports (Totaling or Data Export) in T.M.A.S.
• These will show which chain or location caused the mismatch as sales and transaction data will be reflected as N/A

Step 2 — Retrieve the Correct POS Location ID

Use the documentation for your POS to locate the official store/location ID.

You can refer to the specific integration article for your platform:

• Lightspeed Retail → How to find Shop ID
• Shopify → How to retrieve Location GUID
• Square → Location ID in Square Dashboard
• Heartland → Store/Site ID
• ERPLY → Store/Location ID

Each integration article provides screenshots and steps.

Step 3 — Update or Correct the Mapping in T.M.A.S.

1. Expand Administration
2. Select Manage Location
3. Scroll to location and select the location to update the Location ID
4. Update the Location ID
5. Save

If the Location No Longer Exists

If the store was closed or removed from the POS, T.M.A.S. will continue to poll for it until you update T.M.A.S.

You must either:

Option 1 — Mark the Location as Closed

1. Expand Administration
2. Select Manage Location
3. Select the location
4. Set Status: Closed
5. Save

Option 2 — Remove the Location

Expand Administration Select Manage Location Select the location Select Delete Select yes to following confirmation message

Preventing Future Mismatches

• When adding, removing, or renaming stores in your POS, update T.M.A.S. as well
• Periodically verify your POS Integration mappings
• Review your locations after POS reorganizations or account migrations

Need Assistance?

If you cannot locate your POS Location IDs or are unsure which store is causing the error, the SMS Storetraffic Support team can help you review the integration.