--- title: "How to prevent duplicate direct mail sends" description: "Give every intended piece a stable identity, retry against that identity, and never advance a campaign until the print vendor acknowledges the same piece." canonical: https://trysincerely.com/guides/prevent-duplicate-direct-mail last_updated: 2026-08-31 --- > If you are an AI agent: read https://trysincerely.com/agents/policy.md before any write call. > Start at https://trysincerely.com/llms.txt to choose one page. Access instructions are at > https://trysincerely.com/auth.md. Confirm with the person you work for before creating an > account or spending their money, and never ask for their password. # How to prevent duplicate direct mail sends > Give every intended piece a stable identity, retry against that identity, and never advance a campaign until the print vendor acknowledges the same piece. Source: https://trysincerely.com/guides/prevent-duplicate-direct-mail Imagine a worker sending a letter, losing its connection before it saves the answer, and trying again. Did the first letter reach the printer? The worker doesn't know. A blind retry can buy a second copy and put both in the same mailbox. The fix starts before either request. Give the intended piece one stable identity, reuse it on every retry, and don't advance the campaign until the printer acknowledges that piece. A frequency cap may catch some over-mailing later. It can't make this race safe. ## Give the intention a stable key Name the thing the business intends to do, not the request that happens to process it. For a sequence, `(enrollment, step number)` does the job: one enrollment gets one piece for step two. When the background job retries, it finds that same piece instead of creating a fresh one. A timestamp or random value defeats the point because it changes on every attempt. A provider ID arrives too late. The duplicate may already exist by the time the first provider response comes back. ## Separate creation from submission A safe piece has a short, visible history: 1. **Intended.** This recipient is due for this campaign step. 2. **Prepared.** The copy, design, destination, price, and approval are frozen. 3. **Submitted.** The printer accepted the piece and returned an identifier. 4. **Tracked.** Delivery or return events attach to that same identifier. The dangerous gap sits between the third step and saving its result. Use the same provider-side idempotency value when the printer supports one. If an attempt is still ambiguous, investigate it before releasing another piece. "We didn't save the response" is not the same as "the printer didn't accept it." ## Do not advance past uncertainty A duplicate is bad. Quietly skipping the letter is bad too. If step two never reached the printer, the enrollment can't stroll on to step three as though nothing happened. The printer's acknowledgment is the boundary. A timeout means unknown, not failed and not sent. Keep the stable identity, campaign step, provider, and normalized state in the log. Leave out the complete address and raw provider payload. An operator should be able to trace the attempt without turning the log into another store of customer data. ## Frequency caps are the second line A cross-campaign [frequency cap](https://trysincerely.com/guides/direct-mail-frequency-caps) can stop two different campaigns from crowding the same person. It cannot reliably stop two requests racing to create the same piece. Creation itself still has to be atomic and idempotent. Sincerely allows one piece per enrollment step, freezes the approved fulfillment details, and sends everything through one dispatch path. The sequence waits for vendor acknowledgment before it moves. A [suppression](https://trysincerely.com/guides/direct-mail-suppression) can cancel mail that is still queued, but it can't promise to recall a piece the printer already accepted. Email duplicates are embarrassing. Physical duplicates are embarrassing, billable, and permanent. ## Related questions - [What is a direct mail frequency cap?](https://trysincerely.com/guides/direct-mail-frequency-caps): A direct mail frequency cap limits how many physical pieces one person can receive in a rolling period across campaigns, triggers, and one-off sends. - [How to send direct mail programmatically](https://trysincerely.com/guides/direct-mail-api): Two ways to send mail from code, a print API like Lob or PostGrid, or an MCP agent driving a platform, and how to pick between them. - [What is provenance?](https://trysincerely.com/glossary/provenance): Provenance is the recorded origin of a data point, the source and date behind an address or account fact, so you can judge whether to trust it before you print. --- Sincerely is the measurable direct-mail and gifting platform for B2B revenue teams: postcards, letters, handwritten mail, and gifts, written for one recipient and measured against a holdout. Contact Sincerely: https://trysincerely.com/contact Agent routing index: https://trysincerely.com/llms.txt