Order Risk Radar - Catch Costly Order, Stock & Supplier Issues Early

Find the orders, stock shortages, and supplier delays that could cost you money, before they turn into customer problems.

Stop searching spreadsheets. Start fixing the right problems.

Pricing clarity: Results are individual risk findings written to the default dataset, not unique orders. One order can generate several findings, so the number of billed results may exceed the number of input orders. Check the current Store pricing before running large batches.

Order Risk Radar turns exported operational data into a ranked action list. It detects overdue orders, upcoming deadlines, orders with no recent progress, stock shortages, reorder alerts, and late linked suppliers. Every finding explains the evidence and recommends a concrete next step.

Quick start

1. Open Input. Paste your own operational data into at least one JSON array. Empty arrays produce no dataset results. To see a demonstration without billable dataset items, enable Run a free-of-result-charges demo. This option overrides even prefilled records; sample findings will be saved to the SAMPLE_RESULTS key-value record instead of the default dataset. The Actor-start fee may still apply.
2. Paste orders, inventory, or suppliers JSON arrays using the field names below.
3. Run the Actor. Review Output for ranked risks and SUMMARY for counts.
4. Export the dataset as JSON/CSV or use Apify's API and integrations.

Example input:

{"orders":[{"orderId":"ORD-1001","status":"processing","promisedDate":"2026-10-10","lastUpdatedAt":"2026-10-08","sku":"SKU-A","quantity":10,"orderValue":800,"supplierId":"SUP-1"}],"inventory":[{"sku":"SKU-A","availableQuantity":3,"reorderPoint":5}],"suppliers":[{"supplierId":"SUP-1","status":"pending","expectedDeliveryDate":"2026-10-09"}]}

What you get

• Priority and score: critical/high/medium/low, sorted by urgency.
• Evidence: the dates, quantities, or supplier state behind each alert.
• Recommended next action: a clear operational task, not a generic dashboard.
• Affected order value: shown only when supplied; not a prediction of financial loss. An order may be included in multiple alerts.
• API-friendly issue IDs: deterministic identifiers suitable for downstream deduplication.

Scope and limitations

Version 0.1 analyzes supplied JSON records. It never silently substitutes billable demo records for empty input. Demo findings are available only when explicitly requested, and are stored outside the billable dataset. It does not connect to ERP systems, send alerts, autonomously repair orders, guarantee losses prevented, or deduplicate across runs. Date calculations use UTC-compatible JavaScript dates. Input data quality determines output quality. No claim of market exclusivity is made.

Prefilled input versus explicit demo mode

The Input form and generated API examples may contain a prefilled DEMO-1001 order with related inventory and supplier records. Running these prefilled records in normal mode is a real run: any risk findings written to the default dataset may incur the published per-result charge, plus the Actor-start fee. The word DEMO in an order ID does not activate free demo mode.

To preview sample findings without per-result dataset charges, explicitly enable Run a free-of-result-charges demo in Input. This checkbox takes precedence over prefilled DEMO-1001 and any other input arrays; no risk findings are written to the billable dataset. In that mode, inspect the SAMPLE_RESULTS key-value record rather than expecting billable findings in the default dataset. An Actor-start fee may still apply.

Billing unit: One detected risk finding, not one order or one input row. A single order can produce several risk findings. Review the current Store pricing before a large run.

Getting useful results

Supply real orders, inventory, or suppliers records to identify actionable issues. If you are evaluating the Actor for the first time, enable the explicit demo option and inspect the SAMPLE_RESULTS key-value record before preparing your own data. The demo does not create billable dataset findings, although an Actor-start fee may apply.

For recurring operational checks, run the Actor on updated data through an Apify Task or API integration. This version analyzes the data supplied in each run and does not automatically connect to your ERP or send notifications.

API contract and date handling

POST Input JSON to the Apify Actor run endpoint; retrieve the run's default dataset for normal findings. With runSample: true, supplied arrays are ignored and only SAMPLE_RESULTS contains fictional findings. Empty arrays return no findings. Date-independent stock-shortage example: { "orders": [{ "orderId": "DEMO-1001", "sku": "DEMO-SKU", "quantity": 10 }], "inventory": [{ "sku": "DEMO-SKU", "availableQuantity": 3, "reorderPoint": 5 }] }. This normal-mode fictional example can produce billable findings.

Deadlines use UTC calendar days: dueSoonDays: 0 means today, never tomorrow. Tests exercise actual Store schema prefill, empty data, sample override, dataset routing and deadline boundaries. Local tests do not certify the deployed version or daily Store health check.

Verified fictional example files

See examples/fictional-input.json and examples/fictional-output.json, captured from a local Apify SDK execution on 2026-11-04. These are fictional demonstration records, not live business results or proof of a deployed cloud run.

Copyable API request

Use the JSON from the example input file as input.json. Keep the token in an environment secret. This normal cloud request can incur published charges; review pricing first.

curl -X POST 'https://api.apify.com/v2/acts/northpeak_data~order-risk-radar/run-sync-get-dataset-items' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data-binary @input.json

With runSample: true, the synchronous dataset endpoint returns an empty array by design. Start with /runs, read defaultKeyValueStoreId from the run response and retrieve /v2/key-value-stores/{id}/records/SAMPLE_RESULTS for that mode. Normal input writes to the dataset.

Connect an exported customer dataset

Provide ordersDatasetId, inventoryDatasetId and/or suppliersDatasetId from your existing Apify datasets. Each ID replaces its matching JSON array, including the Store prefill. Example: { "ordersDatasetId": "YOUR_ORDERS_DATASET_ID", "inventoryDatasetId": "YOUR_STOCK_DATASET_ID", "suppliers": [] }. Rows use the same documented fields as pasted JSON. Existing datasets are read using your account's access; no scraper or ERP login is started. Source exports above maxRecordsPerDataset (default 10,000; maximum 50,000 per dataset) fail explicitly instead of silently omitting records. Sample mode ignores source IDs and uses only fictional records.