Risk analysis
Shopify Fraud Analysis Is Missing or Pending: What Your Team Should Do
Missing or pending Shopify fraud analysis should trigger a defined fallback, not an assumption of low risk. First determine whether the analysis is still processing, unavailable for this order type, or held in a third-party provider's system. Each situation needs a different next step.
The immediate operational priority is to keep the relevant fulfillment handoff from outrunning the review. That does not mean every order must wait indefinitely. It means the merchant should know why a recommendation is absent and apply an approved decision process for that situation rather than inventing a score.
Distinguish pending from unavailable
Record the exact message shown on the order. “Not available yet,” no recommendation displayed, and a third-party review status are not necessarily the same condition. Include the order type and payment provider in the note so the person investigating can check eligibility and source.
Shopify lists recommendation exclusions and pending-analysis troubleshooting in its fraud-analysis documentation. Use the current list for the store's setup. A test order or another excluded order type should not be treated as a production analysis failure merely because it lacks an ordinary recommendation.
If the message says analysis is pending, check again under Shopify's current guidance and record the new status. If a third-party provider is conducting review, check that provider's authoritative record. A lack of updates in Shopify does not prove the external review has finished.
Avoid translating an empty field into “low,” “passed,” or zero risk. In a spreadsheet or operations dashboard, use an explicit unavailable state with its known reason. That preserves the difference between a reassuring result and no result at all.
Pause the actual fulfillment handoff
Identify which system or person can dispatch the order. A note in support software is ineffective if the warehouse or fulfillment partner never sees it. Confirm that the hold covers the relevant items and that no automated or manual path will release them before the owner decides.
Use a hold record with order reference, item scope, current location, reason, review owner, next check time, and fallback deadline. Ask fulfillment to acknowledge the hold in its normal operating system. If goods have already moved, record that fact and escalate the changed situation.
Do not apply a blanket storewide stoppage when one order needs investigation unless the incident genuinely affects the broader process. Scope matters: a provider outage affecting many recommendations is a different issue from one ineligible order type.
Apply an explicit fallback
A fallback should specify the facts the merchant can review without the missing recommendation, who can decide, and what remains uncertain. It should not claim to reproduce Shopify's unavailable analysis. Use the supported order context and the store's ordinary decision rules.
| Situation | Appropriate next step | Incorrect shortcut |
|---|---|---|
| Analysis is still pending | Recheck and maintain the assigned hold | Marking the blank recommendation low |
| Order type is ineligible | Use the approved process for that order type | Waiting forever for a result that does not apply |
| Provider review is external | Check the provider's record | Assuming Shopify's unchanged display is final |
| Source problem is unresolved | Escalate with a timed merchant decision | Creating an unsupported score |
The merchant can use Shopify's fraud-review guidance to identify available context. Keep collection proportionate. A missing automated recommendation does not justify asking a customer to email a card photograph or security code.
A hypothetical warehouse cutoff
A hypothetical store receives an order shortly before its afternoon dispatch cutoff. The order displays pending analysis. The reviewer records the message and asks the warehouse to hold that order's parcel. The warehouse acknowledges the hold; the rest of the dispatch batch continues.
At the next check, the result is still unavailable. The owner establishes that the payment provider is conducting a separate review and assigns the payment lead to check the provider record. Because the customer-facing promise allows dispatch the following working day, the merchant keeps the parcel held until the next scheduled review.
If the order had been ineligible for a recommendation, repeatedly refreshing would not have solved the issue. The owner would instead apply the documented fallback for that payment or order type. The hypothetical example demonstrates why the reason for absence changes the workflow.
Close the missing-analysis item deliberately
The review ends when the recommendation appears and is interpreted, the authoritative provider status is obtained, or an authorized merchant completes the fallback decision. Record which of those occurred. Do not overwrite the original missing state without retaining the relevant timing if it explains a dispatch delay.
Check whether similar orders are repeatedly arriving without the expected information. If so, verify eligibility, integration behavior, and operational ownership before adjusting the process. The durable improvement is a clear route for each absence condition, with a fulfillment hold that actually works and a decision deadline that prevents orders from disappearing into limbo.
Explore how Lower Chargeback presents Shopify risk signals for merchant review.
Related reading in this collection:
- Shopify Fraud Analysis: Reading the Recommendation and the Individual Signals
- Shopify Chargeback Prevention: Build Controls Beyond Fraud Screening
- An Address Change After Payment: When to Reopen the Fraud Review