Insights

POS · 2 min read

Dutchie Customer Dedupe: Review Before the Overnight Merge

Dutchie POS Backoffice’s Customer Dedupe tool groups possible duplicate profiles for review; it does not merge them immediately. The Dutchie setup guide lets an administrator choose match criteria, set a confidence threshold, and select the profile to keep before scheduling the merge.

Define a duplicate

Before running a session, decide which profiles should be considered the same customer. Dutchie lists identifier combinations such as email plus date of birth, phone plus date of birth, last name plus date of birth, driver’s-license ID, or medical-marijuana ID. The guide requires date of birth in at least one selected criteria set.

One setting deserves particular attention: Allow Med & Rec Merges. Leave it off when the store intentionally keeps medical and recreational profiles separate. Dutchie also lists duplicate profiles used to evade purchase limits as one reason to run dedupe, but a match still needs review before profiles are combined.

Configure the session

Open Customers > Actions > Customer Dedupe. A session can be started from a new configuration or copied from an earlier one. Set the minimum confidence score and matching criteria before selecting Run Matching. The tool groups candidate profiles and displays the fields that matched, the confidence score, and profile details.

Review before scheduling

For each match group, check the matching identifiers and compare relevant profile details, including last transaction date, loyalty points, ecommerce account status, and most recent transaction. Select the survivor to retain, and exclude profiles that should not merge. Dutchie requires View, Edit, and Merge Customers permissions to use the tool.

Only after reviewing the groups should an administrator schedule the merge. Dutchie says scheduled merges run overnight. A profile that changes between the match and the merge can fail, so check completed sessions and resolve failed profiles before relying on the cleaned list.

Sources:

The article was checked in the POS documentation archive (captured Oct 9, 2026). The live page returned HTTP 403 from this environment on Oct 10, so current page wording and availability are unverified.

Duplicate profiles affecting purchase history?

Review the match before scheduling a merge.