An ecommerce dashboard template should keep order, payment and fulfillment states separate, then state the policy behind its work queue. This original dated snapshot qualifies two orders and six remaining units for a fulfillment review. It also preserves a canceled order's separate refund exception without performing or approving a transaction.
The native order/line workbook and source notes remain authoritative. The companion displays the dated order fixtures. Native spreadsheet files, formulas and import behavior remain separate checks.
Name the source and policy before the totals
This example is an invented four-order snapshot, source FIXTURE-EC01, as of October 13, 2026, at 12:00 p.m. UTC−04:00. It contains no actual store export, customer data or live carrier information.
Shopify's documentation separates order, payment, fulfillment and return statuses, and notes that canceled orders can still have work remaining. Adopt the independent-state model without treating this original workbook as a Shopify API schema or connected store view. Shopify: Understanding Order Statuses
Keep the original records visible:
| Order | Order state | Payment state | Fulfillment state | Hold | Ordered / fulfilled / remaining |
|---|---|---|---|---|---|
| O1 | Open | Paid | Unfulfilled | No | 3 / 0 / 3 |
| O2 | Open | Paid | Partially fulfilled | No | 5 / 2 / 3 |
| O3 | Canceled | Partially refunded | Not required | Not applicable | Not supplied; excluded from picking |
| O4 | Open | Pending | Unfulfilled | No | 2 / 0 / 2 |
The original policy Q1 requires Open, Paid, Unfulfilled or Partially fulfilled, explicitly No hold, and consistent positive remaining line units. This identifies a review queue, not permission to ship, capture payment or change an order.
Paid is a supplied status, not proof of delivery or a receipt inferred by this dashboard. Shopify's status description includes orders marked as paid; use separately supplied monetary records when reconciling cash. Do not invent captured amounts for O1 or O2 from the word Paid.
Explain why the qualified queue has six units
O1 satisfies Q1 and contributes 3 remaining units. O2 satisfies it and contributes 5−2=3. There are two distinct qualified order IDs and six remaining units.
O4 has two remaining units but fails Paid. It belongs in a payment-blocked review, not the Q1 queue. Counting O1/O2/O4's remaining units gives eight, but that is an open-work quantity across different payment states, not eight qualified units.
O3 is excluded from picking under its Canceled/Not required fields. That exclusion does not settle its payment exception.
| Original summary | Expected value | Inclusion rule |
|---|---|---|
| Q1 qualified order IDs | 2 | O1 and O2 only |
| Q1 remaining units | 6 | O1 3 + O2 3 |
| Payment-blocked remaining units | 2 | O4 only |
| Refund-difference review | USD 10 | O3's separate monetary record |
Keep the source date and Q1 policy beside these labels. Avoid a generic Ready badge that hides why an order was included or implies inventory, address, fraud, payment-provider and shipping checks have occurred.
Keep order counts separate from line totals
Use one order-header row per order ID. Use separate stable line IDs for quantities so a joined export cannot count the same order twice.
An original line fixture is:
| Line | Order | Ordered | Fulfilled | Remaining |
|---|---|---|---|---|
| L11 | O1 | 3 | 0 | 3 |
| L21 | O2 | 2 | 1 | 1 |
| L22 | O2 | 3 | 1 | 2 |
| L41 | O4 | 2 | 0 | 2 |
O2 has two lines but is one order. Its ordered total is 2+3=5, fulfilled total 1+1=2 and remaining total 1+2=3. These reconcile to the order summary.
Compute each eligible line's remaining units as ordered minus fulfilled. Require nonnegative whole quantities, fulfilled no greater than ordered, unique line IDs and matching order headers. Do not subtract an order-level fulfilled total from every line.
If order-level statuses are repeated on joined line rows, verify they agree before creating one header. Conflicting repeated values are an exception, not a reason to select whichever row comes first. Duplicate L21 is not another unit-bearing line.
O3's unsupplied picking quantities are not converted to zero. Its known exclusion makes those quantities irrelevant to Q1; its separate refund record remains available.
Preserve the canceled order's refund review
O3's original monetary record supplies captured USD 40 and refunded USD 30 for the same snapshot. Their arithmetic difference is USD 10.
Label this Amount difference requiring review. It is not an automatically owed refund, legal determination, approved payment or proof that another refund should be issued. A responsible reviewer must inspect the actual source and applicable decision before taking any action.
Retain fields for source reference, owner, proposed next step, actual decision and decision date. In this fictional workbook, actual owner, approval and completed action remain blank. A draft note can say Review O3 monetary reconciliation without claiming it was reviewed.
Do not net this difference into revenue, profit, tax, inventory or the fulfillment count. Do not infer a refunded line quantity from a dollar amount. Separate axes require separate evidence.
Make missing data visible in the affected metric
If O2's hold field becomes blank, Q1 qualification is unknown for that order. Withhold the complete qualified-order/unit totals and show the affected ID and missing field; do not silently drop O2 and present O1's three units as the complete queue.
If L22's fulfilled quantity is unknown, O2's remaining units cannot be reconciled. Preserve the supplied value as unknown, clear stale dependent totals and request the missing source. Blank is not zero.
If an unrelated field outside Q1 is missing, state which calculation it affects rather than withholding every known quantity indiscriminately. The complete supplied fixture has sufficient Q1 fields for its two/six result; real replacements require their own validation.
Maintain an exception ledger for duplicate IDs, conflicting statuses, missing policy fields, invalid quantities and source-age questions. A new dated source changes the snapshot and dependent totals; retain the previous source version rather than overwriting its history.
Let the review copy explain decisions
The HTML companion shows the dated summary, policy and rows. A native filter for Q1 qualified, payment blocked or refund review should disclose its scope. A displayed summary must say whether it covers the whole dated source or the filtered rows.
Opening an order detail can reveal its three states, hold, line calculations, source and proposed review task. These are read-only review actions. Do not place simulated Ship, Refund, Capture or Cancel buttons beside a static fixture.
Clear/reset can restore the original four-order demonstration and filters; it cannot change a store or erase real records. Actual workbook formulas, import validation, keyboard operation, production article width and 360 px layout remain later checks.
Copy this prompt to prepare the native workbook
Create one complete, self-contained US-English HTML companion for “Order review · EC01”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for All 4 orders; Q1 qualified; Payment blocked; Refund review; Restore original snapshot. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Prepare a complete original US-English ecommerce operations workbook/CSV design, separate formula/key sheet, exception ledger and optional later read-only HTML snapshot with manual tests. Reference https://help.shopify.com/en/manual/fulfillment/managing-orders/order-status for separate status axes and remaining canceled-order work only. Do not copy provider UI/API schema, connect a store, infer cash from Paid or make transactions.
Fictional source FIXTURE-EC01 as of October 13, 2026, 12:00 p.m. UTC−04:00. O1: Open/Paid/Unfulfilled, hold No, ordered 3/fulfilled 0/remaining 3. O2: Open/Paid/Partially fulfilled, hold No, ordered 5/fulfilled 2/remaining 3. O3: Canceled/Partially refunded/Not required, hold Not applicable; picking quantities unsupplied, not zero. Its separate captured USD 40/refunded USD 30 yields USD 10 difference for review only. O4: Open/Pending/Unfulfilled, hold No, ordered 2/fulfilled 0/remaining 2. No personal customer/store/carrier data.
Original Q1 review policy: Open AND Paid AND fulfillment in {Unfulfilled, Partially fulfilled} AND explicitly no hold AND consistent positive remaining line units. O1/O2 qualify: 2 distinct orders/6 units. O4 payment block: 2 units; O1/O2/O4 total 8 remaining units is not Q1-qualified. O3 excluded from picking but refund review remains. Q1 is review eligibility, not shipping/payment/stock/fraud authorization.
Native one-header-per-order table plus unique lines, quantities ordered/fulfilled/remaining: L11 O1 3/0/3; L21 O2 2/1/1; L22 O2 3/1/2; L41 O4 2/0/2. Reconcile O2 sums 5/2/3. Count distinct order IDs and sum unique consistent eligible line remainders. Require whole nonnegative units, fulfilled ≤ ordered, matching headers and consistent repeated statuses; duplicate/conflicting IDs create an exception, no first-row guessing or double subtraction.
Unknown Q1 hold or line quantity withholds complete affected totals and names missing ID/field; no blank→zero or silently reduced complete total. Unrelated missing fields affect only relevant calculation. Original complete fixture remains 2 orders/6 units. New source invalidates dependent results and preserves previous dated version.
O3 difference 40−30=10 is only an amount difference requiring review, not approved/owed refund/legal finding, revenue/profit/tax or unit count. Actual owner/decision/date/actions remain blank; proposed Review O3 monetary reconciliation labeled as proposal. No Send/Refund/Ship/Capture/Cancel controls, live API/store sync, customer records or fake approvals.
Workbook/source/key authoritative. Optional read-only HTML native filters for qualified/payment-blocked/refund review and order details reveal status/lines/source/policy/proposed task. Label filtered versus whole-source metrics; source/unknown changes clear stale totals. Reset demonstration restores original fixture/filters only, no real-record deletion. Test 2 orders/6 units, O4 block 2, O3 difference 10, O2 two lines/one order, duplicates/conflicts/unknowns, source versions and filter scope. Actual files/formulas/import/keyboard/production article width/360 px/print require tests; no artifacts/HTML/captures built now.
Finish separate optional NOS reading copy with an optional Explore NOS link without feature promises. No unverified workbook export, sync, private access, transactions, persisted records or working host controls.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# Ecommerce Dashboard Template: Separate Paid, Ready to Review and Fulfilled
The dashboard shows three open orders with unfulfilled work and labels eight units Ready to ship. One order still has a pending payment. Another order is canceled, so it disappears even though the supplied refund amount does not match the captured amount.
An ecommerce dashboard template should keep order, payment and fulfillment states separate, then state the policy behind its work queue. This original dated snapshot qualifies two orders and six remaining units for a fulfillment review. It also preserves a canceled order's separate refund exception without performing or approving a transaction.
The native order/line workbook and source notes remain authoritative. The companion displays the dated order fixtures. Native spreadsheet files, formulas and import behavior remain separate checks.
## Name the source and policy before the totals
This example is an invented four-order snapshot, source FIXTURE-EC01, as of October 13, 2026, at 12:00 p.m. UTC−04:00. It contains no actual store export, customer data or live carrier information.
Shopify's documentation separates order, payment, fulfillment and return statuses, and notes that canceled orders can still have work remaining. Adopt the independent-state model without treating this original workbook as a Shopify API schema or connected store view. [Shopify: Understanding Order Statuses](https://help.shopify.com/en/manual/fulfillment/managing-orders/order-status)
Keep the original records visible:
| Order | Order state | Payment state | Fulfillment state | Hold | Ordered / fulfilled / remaining |
|---|---|---|---|---|---|
| O1 | Open | Paid | Unfulfilled | No | 3 / 0 / 3 |
| O2 | Open | Paid | Partially fulfilled | No | 5 / 2 / 3 |
| O3 | Canceled | Partially refunded | Not required | Not applicable | Not supplied; excluded from picking |
| O4 | Open | Pending | Unfulfilled | No | 2 / 0 / 2 |
The original policy Q1 requires Open, Paid, Unfulfilled or Partially fulfilled, explicitly No hold, and consistent positive remaining line units. This identifies a review queue, not permission to ship, capture payment or change an order.
Paid is a supplied status, not proof of delivery or a receipt inferred by this dashboard. Shopify's status description includes orders marked as paid; use separately supplied monetary records when reconciling cash. Do not invent captured amounts for O1 or O2 from the word Paid.
## Explain why the qualified queue has six units
O1 satisfies Q1 and contributes 3 remaining units. O2 satisfies it and contributes 5−2=3. There are two distinct qualified order IDs and six remaining units.
O4 has two remaining units but fails Paid. It belongs in a payment-blocked review, not the Q1 queue. Counting O1/O2/O4's remaining units gives eight, but that is an open-work quantity across different payment states, not eight qualified units.
O3 is excluded from picking under its Canceled/Not required fields. That exclusion does not settle its payment exception.
| Original summary | Expected value | Inclusion rule |
|---|---|---|
| Q1 qualified order IDs | 2 | O1 and O2 only |
| Q1 remaining units | 6 | O1 3 + O2 3 |
| Payment-blocked remaining units | 2 | O4 only |
| Refund-difference review | USD 10 | O3's separate monetary record |
Keep the source date and Q1 policy beside these labels. Avoid a generic Ready badge that hides why an order was included or implies inventory, address, fraud, payment-provider and shipping checks have occurred.
## Keep order counts separate from line totals
Use one order-header row per order ID. Use separate stable line IDs for quantities so a joined export cannot count the same order twice.
An original line fixture is:
| Line | Order | Ordered | Fulfilled | Remaining |
|---|---|---|---|---|
| L11 | O1 | 3 | 0 | 3 |
| L21 | O2 | 2 | 1 | 1 |
| L22 | O2 | 3 | 1 | 2 |
| L41 | O4 | 2 | 0 | 2 |
O2 has two lines but is one order. Its ordered total is 2+3=5, fulfilled total 1+1=2 and remaining total 1+2=3. These reconcile to the order summary.
Compute each eligible line's remaining units as ordered minus fulfilled. Require nonnegative whole quantities, fulfilled no greater than ordered, unique line IDs and matching order headers. Do not subtract an order-level fulfilled total from every line.
If order-level statuses are repeated on joined line rows, verify they agree before creating one header. Conflicting repeated values are an exception, not a reason to select whichever row comes first. Duplicate L21 is not another unit-bearing line.
O3's unsupplied picking quantities are not converted to zero. Its known exclusion makes those quantities irrelevant to Q1; its separate refund record remains available.
## Preserve the canceled order's refund review
O3's original monetary record supplies captured USD 40 and refunded USD 30 for the same snapshot. Their arithmetic difference is USD 10.
Label this Amount difference requiring review. It is not an automatically owed refund, legal determination, approved payment or proof that another refund should be issued. A responsible reviewer must inspect the actual source and applicable decision before taking any action.
Retain fields for source reference, owner, proposed next step, actual decision and decision date. In this fictional workbook, actual owner, approval and completed action remain blank. A draft note can say Review O3 monetary reconciliation without claiming it was reviewed.
Do not net this difference into revenue, profit, tax, inventory or the fulfillment count. Do not infer a refunded line quantity from a dollar amount. Separate axes require separate evidence.
## Make missing data visible in the affected metric
If O2's hold field becomes blank, Q1 qualification is unknown for that order. Withhold the complete qualified-order/unit totals and show the affected ID and missing field; do not silently drop O2 and present O1's three units as the complete queue.
If L22's fulfilled quantity is unknown, O2's remaining units cannot be reconciled. Preserve the supplied value as unknown, clear stale dependent totals and request the missing source. Blank is not zero.
If an unrelated field outside Q1 is missing, state which calculation it affects rather than withholding every known quantity indiscriminately. The complete supplied fixture has sufficient Q1 fields for its two/six result; real replacements require their own validation.
Maintain an exception ledger for duplicate IDs, conflicting statuses, missing policy fields, invalid quantities and source-age questions. A new dated source changes the snapshot and dependent totals; retain the previous source version rather than overwriting its history.
## Let the review copy explain decisions
The HTML companion shows the dated summary, policy and rows. A native filter for Q1 qualified, payment blocked or refund review should disclose its scope. A displayed summary must say whether it covers the whole dated source or the filtered rows.
Opening an order detail can reveal its three states, hold, line calculations, source and proposed review task. These are read-only review actions. Do not place simulated Ship, Refund, Capture or Cancel buttons beside a static fixture.
Clear/reset can restore the original four-order demonstration and filters; it cannot change a store or erase real records. Actual workbook formulas, import validation, keyboard operation, production article width and 360 px layout remain later checks.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Review: a dated reading copy of the exceptions
Keep the native order/line workbook and source versions together. Use the companion to place Q1's six units beside the payment block and refund-difference review.
Verify actual formulas, filters, details and layout before presenting a working example. A saved snapshot does not refresh a store, ship an order or authorize a refund.
The useful dashboard identifies which source and policy make each next review necessary.