Overview
When the same item on the same order had been returned more than once, our deduplication step could keep the wrong record if any return event came in from Loop without a timestamp. We've corrected the logic so the legitimate, most recent return is always retained.
Issue
For items returned more than once on the same order, Daasity uses a deduplication step to keep only the most recent return record. If one of those return events arrived from Loop without a timestamp populated, the timestamp-less record could incorrectly win the dedup and replace the legitimate, more recent record — leading to slightly inaccurate historical return metrics for those orders.
Solution
We corrected the deduplication logic so legitimate, timestamped records are always retained over records missing timestamps. Historical data recalculates automatically with the release on May 5th.
What to expect
If any of your returns fit the pattern — same item, same order, returned more than once, with at least one return missing a timestamp from Loop — your historical return metrics may shift slightly after May 5th. The updated numbers will be more accurate. If your Loop data is clean and timestamps are populated, you won't see any change.
No action is required — the update rolls out automatically.