We've updated how certain rejected orders appear in the Rejected Order Reasons section of your Orders Analytics tab. Specifically, orders that were in a payment retry cycle and subsequently superseded by a Send Now action will now surface with more detail than before, previously showing “NA”.

What is a "810" Rejection Code?

When a subscription order fails due to a payment issue, Ordergroove automatically retries it based on your store's retry settings. If a Send Now action is triggered on a subsequent order for the same subscriber while a retry is still in progress, Ordergroove automatically rejects the retrying order to prevent a duplicate shipment from going out. This is expected platform behavior and it protects your subscribers from being charged or shipped twice.

Previously, these rejections appeared with limited detail:

• In Orders Analytics, the rejection code and text appeared as N/A
• In the API, Order.rejected_message appeared as {}

What’s changed:

• Rejection Code: Instead of N/A, the Rejection Code field now displays 810, making it immediately clear why the order was rejected.
• Rejection Text: Instead of N/A, the Rejection Code field now displays "Order superseded by Send Now"
• API Response: Instead of {}, the Order.rejected_message field now returns: {'code': '810', 'message': 'Order superseded by Send Now'}

What to Expect:

The Rejected Order Reasons table in the Orders Analytics tab reflects these new formats immediately.

If your team exports rejection data or uses it in a data pipeline, you will see the updated rejection code and message appear.

No action is required within the Ordergroove platform. You can view this table in Data > Analytics > Orders.

Questions?

If you have questions or notice unexpected behavior in your data, reach out to your CSM or to the support team.