INSIGHTS / CRM AUTOMATION

CRM Quotations Approved Twice? Prevent Duplicate Orders

When a quotation approval button, callback or automated reminder runs twice, one accepted quote can become two sales orders. A robust CRM separates approval intent from document creation and makes the workflow safe to retry.

Share this guide

In this guide

How one approval becomes two orders

A customer receives an online quotation, clicks Approve and sees a confirmation screen. The sales team later discovers that the CRM created two orders or issued two invoices. This can happen without the customer deliberately approving twice.

Browsers retry requests, users double-click buttons and integrations resend events after timeouts. An approval email might also contain a link that someone opens more than once. If the system treats every request as permission to create a new order, ordinary network behaviour can produce duplicate business documents.

A dependable CRM must recognise that approving an existing quotation is a state transition, not an unlimited order-generation command.

Start with the business rule

Define what approval actually means. Does it accept a specific quote version and total? Does it reserve stock, start a project, generate a sales order or request a deposit? Can a salesperson amend the quotation after sending it? What happens if the customer approves an old version?

The data model should distinguish the quotation, each revision, the approval record and any downstream document. A stable quotation ID on its own is not enough when the contents may change before acceptance.

For example, quotation Q-104 may have version 2 with a total of R12,500. If the customer opens an old approval link for version 1 after staff have revised the price, the system should not quietly accept the newer amount. It should show the correct version or require a new approval.

Do not rely on the disabled button

Disabling the Approve button after the first click improves the interface, but it is not a concurrency control. Two requests can reach the server before the browser receives the updated page. A mobile device may retry after a dropped connection, or a customer may open the email on a second device.

The server must check whether the quotation version is still approvable and whether an approval has already been recorded. That check and the state change should happen atomically, ideally inside a database transaction where the relevant rows are locked or updated conditionally.

If the quote was already approved, the endpoint should return the existing approved outcome rather than trying to approve it again.

Give the approval event one durable identity

When a quote becomes approved, create a durable event or approval record with a uniqueness constraint tied to the exact quotation version and intended action. The database, not a PHP variable or temporary session flag, should prevent duplicate approval effects.

A practical system might record approval_id, quotation_id, version_id, approved_at, actor_id and source. It should also record the accepted total and enough immutable context to show what the customer agreed to, subject to the company's privacy and retention practices.

Use a separate unique business reference for downstream order creation. An order-generation worker should ask whether an order already exists for this approved quotation before creating another.

Separate approval from document creation

The safer workflow is to commit the approval once, then enqueue the next business actions: generate an order, email the customer and notify the salesperson. That separation prevents a slow accounting API from keeping the customer's approval request open until it times out.

The queue worker must also be idempotent. A unique constraint can enforce one sales order per approval event, while external systems require an integration mapping and reconciliation checks. The customer-facing response can state that the quote was accepted even if non-critical follow-up work remains queued.

Do not claim the accounting invoice has been issued until the external provider confirms it. If invoice creation times out, mark its state as uncertain and investigate before sending another create request.

Treat expired links and permissions carefully

An approval URL should carry an unpredictable token scoped to a specific quote or version. Decide whether authentication, a one-time confirmation step or another verification method is appropriate for the commercial risk involved.

Avoid exposing guessable sequential identifiers as proof that the visitor is authorised to approve a quotation. Apply expiry rules where appropriate, and make revocation possible when the sales team withdraws or replaces a quote.

Email link scanners sometimes open links automatically. That is another reason not to treat a simple GET request as a final irreversible approval. A link should open a review page; an explicit POST confirmation should record the acceptance.

Preserve the audit trail

When an approval turns into a sales order, staff should be able to trace the entire chain. The CRM ought to show the approved quote version, when approval happened, the actor or channel, the downstream order identifier and any errors.

If the customer claims they approved only once, a useful log will show whether the server received two identical requests and that the second was ignored safely. This is far better than removing a duplicate order and hoping there is no related invoice, stock reservation or email.

Where credit terms, signatures or legal enforceability matter, agree on the business's required evidence and acceptance process with appropriate advisers. Software event logging alone does not settle every contractual question.

Test the failure scenarios that matter

Place the same approval request twice, submit simultaneous requests and retry after a simulated network timeout. Open an old quote link after a revision, approve through two devices and interrupt order creation halfway through.

The expected result is one recorded acceptance for the intended version and, where business rules require it, one corresponding order. Notifications may need their own idempotency controls. Verify that a repeated queue job does not send duplicate deposit instructions or create duplicate projects.

Also test a rejected quote, a withdrawn quote and an expired link. Invalid transitions should return clear explanations without modifying records.

Make exceptions visible to staff

A CRM administrator needs a queue of approved quotations whose downstream work has failed or is awaiting reconciliation. Show the relevant quote, stage, retry count, last error and next action. Do not silently overwrite a failed stage with a generic Complete flag.

Operational reporting should distinguish quotes awaiting a customer decision from approved quotes awaiting internal fulfilment. That visibility prevents teams from manually recreating records because they assume the automation did not work.

Account for human changes after approval

Approval is not always the end of a quotation workflow. A customer may request one additional service after approving, or the sales team may discover that the quoted delivery date is no longer possible. Decide whether that requires a new quotation revision, a variation order or another documented process. Do not allow staff to edit the accepted quote in place without leaving evidence of what changed. This protects both the business and its customer when a later invoice does not appear to match the original approval. The CRM should show the accepted version prominently and guide staff towards a controlled amendment rather than encouraging ad hoc corrections in free-text notes.

When custom CRM development makes sense

Off-the-shelf quotation systems may already have appropriate duplicate protection. The risk increases when businesses attach bespoke scripts, a separate invoicing package, stock control and a customer portal to the approval event.

Digital4Front builds custom CRM and workflow systems around real operational rules. If one customer action is triggering duplicate orders, invoices or project records, we can map the state transitions, introduce safe database constraints and make downstream integrations reliable. The goal is a clear approval experience and a traceable result, even when requests are repeated.

Found this useful?

RELATED SERVICE

Need help applying this to your business?

Explore our crm development service, or tell us about the process you want to improve.

CRM Development ↗Discuss your project ↗
WhatsApp us