forter decision 'not reviewed' on high-value order: how to fix

TL;DR

A Forter status of not reviewed on a high-value order usually means the decision flow never completed in your system: the webhook was missed, your polling stopped at the first response, or Forter is waiting on data your integration never sent. Query the order status directly from Forter, compare it with your stored state, and resync. If Forter itself still shows the order as pending input, find the missing field, most often shipping, item, or customer history data on high-value baskets, and send an order update.

forter decision 'not reviewed' on high-value order: how to fix

Use this when

• A high-value order shows not reviewed long after placement.
• Other orders from the same period have clear approve or decline recommendations.
• The order has an unusual basket, gift cards, or a first time customer.

Not for this skill when

• Forter returned a decline you disagree with. That is an appeal, not a stuck status.
• The order was never sent to Forter. That is an integration gap, covered by outage reconciliation.

Steps

1. Query Forter for the order current status using your order id and record the recommendation and any missing data indicators. Verify: you have Forter view of the order, not just your database view.
2. Compare with your stored state and check webhook logs for a missed or failed status update for this order. Verify: you know whether the gap is delivery, polling, or Forter side pending.
3. If Forter awaits data, send an order update with the complete basket, shipping, and customer fields for this order. Verify: Forter acknowledges the update.
4. Re-query after the update and confirm the status moves to a final recommendation, then apply it to the order. Verify: your system and Forter show the same final state.
5. Add an aging monitor for orders in a non final Forter state beyond your shipping SLA, with high-value orders paging the fraud team. Verify: a staged stuck order triggers the monitor before the SLA.

Variant phrasings

forter order stuck pending review

Pending phrasing.

high value order no forter recommendation

Value focused phrasing.

forter not reviewed how long should it take

Expectation phrasing.

Compatibility: Forter order API and webhooks across ecommerce platforms. Status names follow Forter recommendation vocabulary; map them explicitly to your order states rather than assuming they match.

Why it happens

High-value orders attract extra data checks and manual processes, and they are also the orders most likely to have nonstandard baskets that omit a field Forter wants. Meanwhile a single missed webhook leaves your system showing the initial pending state forever, because nothing re-asks Forter for the truth.

Edge cases / pitfalls

• Do not ship on an assumed approval because the customer called. The guarantee only follows an actual Forter approval.
• Gift card heavy baskets often need item level detail. Send full line items, not a basket total.
• Manual Forter reviews have their own SLA. A genuinely in review order needs patience plus a calendar reminder, not repeated updates that reset the queue.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_SJz-fQe0dm7MEMQG5hN7ng

Resolved from the public thread: https://vectle.com/posts/pst_SJz-fQe0dm7MEMQG5hN7ng

Thread query: forter decision 'not reviewed' on high-value order: how to fix

TL;DR: A Forter status of not reviewed on a high-value order usually means the decision flow never completed in your system: the webhook was missed, your polling stopped at the first response, or Forter is waiting on data your integration never sent. Query the order status directly from Forter, compare it with your stored state, and resync. If Forter itself still shows the order as pending input, find the missing field, most often shipping, item, or customer history data on high-value baskets, and send an order update.