Prepared with AI assistance and reviewed for clarity, relevance and unsupported claims.
Duplicate customer order requests create an awkward decision: should staff prepare one purchase or two? A customer might submit a website form, then send the same details on WhatsApp because they want reassurance. Another customer might deliberately order two identical gifts.
For a Moroccan merchant handling enquiries across channels, similarity should trigger a check, not an automatic merge. The useful distinction is between recognising a possible duplicate and having enough evidence to treat two requests as one purchase.
1. Separate customer identity from purchase identity
Even when two messages come from the same person, they do not necessarily describe the same order. Repeat purchases, gifts for different recipients and additions to an earlier order can all look similar.
The reverse also occurs: one person submits a form while another household member sends the follow-up message. A shared telephone number or delivery address is a clue, not proof of a single buyer or purchase.
Maintain a reference for each incoming request and a separate reference for each confirmed order. Several requests may eventually link to one order, but preserve their origins. Guidance on matching customer identities across channels helps keep this identity question separate from the order decision.
2. Compare meaningful clues and contradictions
Use a small evidence checklist rather than a rule such as “same phone number means duplicate”. Compare the actual purchase details and identify anything that points towards two different intentions.
- Existing reference: does the message explicitly mention the form or order number?
- Items: do product references, variants and quantities match?
- Fulfilment: are the recipient, delivery address or pickup arrangement the same?
- Timing: did the second request follow the first, or could this be a later purchase?
- Purpose: does the customer say “following up”, “another one” or “replace my earlier request”?
- Contradictions: are there different gift notes, dates, recipients or quantities?
Normalising obvious formatting differences can make comparison easier: spaces in a telephone number should not hide a possible match. However, do not overwrite original values or assume that a differently spelled name belongs to the same person.
Timing and identical products are supporting clues. An explicit reference and a clear statement of intent are stronger evidence. No numerical confidence score should replace reviewing a meaningful contradiction.
3. Ask a question that does not lead the customer
Consider this hypothetical example: a cosmetics merchant receives a website form for one gift set with a greeting card. Shortly afterwards, a WhatsApp message requests the same set for pickup and asks whether the card can be included.
The matching set and card suggest a follow-up, but the customer might want a second gift. Staff should clarify before either combining the requests or preparing two sets.
Staff: “You mentioned submitting a gift-set form earlier. Is this message about that same purchase, an additional gift set, or a change to the first request?”
Customer: “The same purchase. I only wanted to check the card.”
Staff: “Thank you. We will keep one request for one gift set and include the card request for review. This clarification does not yet confirm availability.”
If the connection between channels is uncertain, ask the customer to provide their reference before disclosing details from another record. Do not send a stranger the recipient name or address merely because their message looks similar.
4. Review downstream work before combining records
Customer clarification settles intent, but staff must still inspect what has already happened. One request may already have generated a preparation task, payment record or delivery instruction.
- Open both request records and their source messages.
- Record the evidence that they concern one purchase.
- Check whether either has become a confirmed order.
- Inspect preparation, payment and fulfilment activity separately.
- Select the authoritative order record and retain links to both requests.
- Close the redundant request with a reason and reviewer name.
- Check that no duplicate task remains active downstream.
If two parcels are already being prepared, merely closing one enquiry is insufficient. Notify the person controlling preparation and obtain acknowledgement. If there are two payment records, route them for appropriate review rather than deleting one or promising an automatic refund.
Keep an audit note instead of erasing the second request. It explains why a later message has no separate order and makes a mistaken consolidation easier to investigate.
5. Use a hold state when intent remains unclear
If the customer has not answered, label the new request “possible duplicate — clarification needed”. Assign a reviewer and a next check. Do not silently cancel an already confirmed order while waiting.
Where appropriate, pause only the additional preparation action whose legitimacy is uncertain. Tell the customer what remains pending. If a dispatch deadline is approaching, a responsible staff member must decide whether to call, hold the extra request or follow the merchant’s documented exception procedure.
The trade-off is real: cautious review can delay a genuine second purchase, while automatic merging can remove it entirely. Equally, treating every message as a new order can create unnecessary preparation. The right default is a visible, owned exception rather than a hidden assumption.
6. Automate candidate detection, not purchase intent
A first automation can collect matching clues, flag likely pairs and present the original messages together. AI-generated summaries remain suggestions: they can miss a phrase such as “another one” or misread a quantity change.
Before connecting tools, define the workflow triggers and states, including who can release a hold and how a mistaken combination is reversed. Test with deliberate repeat purchases as well as obvious duplicates. A process that finds duplicates but blocks legitimate orders is not ready.
To discuss this review workflow with FlowAgent, explore custom n8n automation and share the channels and order records you need to reconcile.