Understanding your Orderflow analytics

Analytics answers what Orderflow did for your store after an order was created. It is not Shopify sales or revenue reporting.

Open Analytics in the sidebar. Choose 7 days, 30 days, 90 days, or a custom range. Every number on the page uses that range unless it is labeled as current (for example, proofs waiting now).

The page is meant to be scanned quickly:

1. How much Orderflow handled
2. How much work it automated
3. Roughly how much time it saved
4. Whether orders are moving through your statuses
5. How customers are responding to the features you actually use

You will not see a card for every Orderflow feature. If this store has never turned on Proof Review, Request Information, Collect Info, or marketing opt-in, those modules stay off the dashboard so unused tools do not look broken.

Date ranges

Numbers cover the range you select. A percent change vs the previous period only appears when that earlier period also has data. If the previous period is empty, we hide the comparison instead of inventing a trend.

Orders managed

Orders Orderflow touched in the range — status updates, proofs, information requests, or automations. Each order is counted once, even if Orderflow recorded it under more than one id. This is not the same as Shopify’s new-order count.

Fulfillment time

Average and median fulfillment time are Shopify order created → first fulfillment (or the order closed date if that is all we have). Median only appears after we have stored individual fulfillment times.

That is how long fulfillment took. It does not mean Orderflow made fulfillment faster.

On-time rate is fulfilled orders that finished on or before their Orderflow Ship by date. We only calculate it when both dates exist.

If you see Not available yet or Not enough data, we do not have enough qualifying completed orders in this range. Imported history may be missing an exact fulfillment timestamp. Those orders are left out of the average rather than guessed.

Time in status

Workflow performance uses your status names and recorded status changes. Another shop’s stages will look different.

The highlighted Longest stage is the status with the highest average time among statuses with enough visits. Bars and the status pie use your status colors. Bars are relative to that longest average. Visits is how many times orders entered that status, not unique orders.

If an order never changed status in the range, we cannot invent how long it sat there.

Proofs, requests, and marketing

These cards appear only when the feature is set up on a status or was used in the range.

• Approval rate uses customer decisions only (approved vs revisions requested). Pending proofs are not failures. Proofs closed because an order was fulfilled without a response are not customer approvals and are not merchant approvals.
• Closed without response appears only after this automation has run in the selected range.
• First-pass approval is approvals on version 1.
• Request Information completion is requests sent in the selected range versus those same requests completed.
• Collect Info is counted separately and never mixed into that percentage.
• Marketing conversion is successful new subscribers ÷ eligible prompts shown. Customers already on your Shopify list are not prompted.

If a rate says Not enough data, we do not have both parts of that calculation yet.

0 means the feature was in play and nothing happened (for example, prompts shown and nobody subscribed). That is different from a feature that is off.

Automations

Automatic status changes, ship-by dates, reminders, and Orderflow-handled proof / information / marketing work. Manual updates you make yourself are not counted as automation. Categories with no activity in the range are hidden.

Estimated time saved

This is an estimate, not a timesheet.

We multiply automatic tasks by conservative minutes (for example a short status change versus sending a proof). The breakdown shows which kinds of work added up. It is meant to describe repetitive admin Orderflow took off your plate — not measured employee hours.

Trends is a line for the range you picked — orders managed, automated actions, or another series you choose.

Tap the i next to a metric for the short definition, or open this article for the full explanation.

Why a metric might be missing

• The feature is not set up on any status
• Nothing happened in the selected range
• We started recording that detail after the range began
• The two sides of a rate do not belong to the same group of orders

Not enough data is better than a misleading 0% or a percentage over 100%.