All products

Prevent duplicate order updates with AI

Design a defensive webhook receiver for your own store that records authorised events and applies an order change only once.

Prevent duplicate order updates with AI when payment or order notifications can arrive twice or out of sequence. The order-and-webhook-reliability skill helps an agent check event authenticity, keep a durable receipt record and reconcile an uncertain status with the configured provider. Its local example is separate from a live payment service.

A provider may send a successful payment notification, then retry because it never received the store’s acknowledgement. The second delivery should not reduce stock again or send another receipt. If a later cancellation has already been recorded, an older notification should not silently put the order back into an earlier state.

What it does

  • Record an event before acknowledging that it was received.
  • Keep a stable event identity for duplicate detection.
  • Separate receiving an event from changing the order.
  • Compare stale or incomplete notifications with the authoritative provider state.
  • Test recovery after an interruption between receipt and processing.

Install and use

  1. Use an agent with an authorised staging integration, official provider documentation and test events. Node runs the local verification example. Keep production secrets in the store’s protected configuration.
  2. Ask it to model two deliveries of one test notification and identify which effects must occur only once.
  3. Check the order history and stock or receipt side effects before approving a production change.

FAQ

Source

Made by Naser Sadrmanesh. Original skill: order-and-webhook-reliability, published on GitHub under the MIT licence.

View on GitHub