Article summary
Deduplicate the Zalo submission without losing store ownership. Use an example with seven store records and five unique numbers to reconcile the export and delivery sheets.
Store A has four rows, Store B has three, and two numbers appear in both. For the same registration check at the same point in time, that makes five unique inputs. Store A still receives four rows and Store B receives three. The submission count and delivery counts answer different questions.
Keep a map before removing duplicates
Give the example numbers labels. Store A has A, B, C, and D. Store B has B, D, and E. Keep the original store and row reference on each source record. The combined submission contains five full numbers. B and D appear once there and twice across the source records.
Store the numbers as text and keep both the original and the verified, normalized form. When two entries resolve to the same complete number, include that number once. If only the trailing digits agree, leave the incomplete entry with the store for review. Where the stores have different permissions, confirm which records are eligible to be combined before building the submission.
Run one check and return two files
Build a TXT file of the combined numbers and run one AppShai Zalo registration check. Download the Excel output and match it to each store's records by the complete number. The result for B can go back to both rows for B. Filter by store before handing out the files.
If D has no clear result, the submission has one number to investigate. The stores have two rows waiting for a status. A reconciliation can say “four of five unique numbers have clear results” and “two of seven store rows are pending.” Adding up the store rows alone would count the same missing result twice.
If the stores need observations from different dates, preserve both run dates and handle the requests separately. A combined submission works when both stores can use the same task and observation time.
