The oldest order is not the next order due for dispatch

List the accepted orders, not the oldest page

Start with the quantities the business still owes: accepted orders with outstanding line quantities, whether paid or covered by an authorized no-charge replacement, excluding only cancelled quantities and quantities already handed to a carrier. An order sorted to the top by creation date may be unaccepted, on hold, partially shipped with a remainder still due, or waiting on a buyer answer, and none of those states by itself makes it next or removes it. A partially shipped order stays in the population for its unshipped remainder, and an authorized no-charge replacement is outstanding work even though no payment accompanied it. Shopify's order-view documentation shows that payment status, fulfillment status, date and sales channel are independent filters; an age-sorted view says nothing about which of those conditions apply to each row.

Export or record the queue with the fields that matter for this decision: order reference, acceptance event, the shipping commitment in force when the order was taken, the outstanding quantities still owed, current fulfillment state, and any hold reason. Keep customer names and contact details in the store system; the worksheet needs references and facts, not identities.

Recover the commitment each order carries

For each accepted order, record the promise that accompanied it: the shipping statement shown at purchase, an individual date given in a confirmation, or the absence of any stated time. Orders taken under different commitments are not interchangeable in the queue. An order accepted last week under a two-day statement can be due before an older order accepted under a statement with no time, and an order whose buyer agreed in writing to a later date moves with that agreement, not with its creation date.

Where the commitment cannot be recovered for a particular order, mark it as unverified rather than assigning it the current website wording. A policy edited since the order was placed does not describe what that buyer was promised. Orders with unrecoverable commitments form their own group, to be prioritized conservatively and corrected in the storefront wording going forward.

Check holds and remaining work before ranking

A documented hold removes an order from the due-now ranking without erasing its commitment. Record each hold's reason and source: a payment-confirmation hold, a stock wait tied to an identified supply event, a buyer-requested pause, or an unresolved address question. An order held for a reason that has quietly expired belongs back in the ranking, so each hold needs a review point rather than an indefinite exemption.

Then record the work that stands between each order and handoff: quantities still to pick, a partial shipment already made whose remainder is still owed, or a dependency on goods not yet received. Two orders with the same commitment date are not equally due if one can be dispatched today and the other cannot move this week. The ranking should reflect the earliest commitment that can actually be met, with blocked commitments visible as blocked rather than silently overtaken.

Publish the queue logic and own the exceptions

Write the resulting queue as an ordered list with one line of reasoning per order: commitment date, hold status, readiness. When an older order is passed over, the record should already contain why, so support can answer a buyer from the same facts instead of improvising. When two commitments collide and capacity can meet only one, the choice and its reason belong to the fulfillment owner, recorded at the time, not reconstructed after a complaint.

Revisit the queue against new evidence: a supply receipt, a released hold, a buyer's reply to a delay notice. A queue built on Monday's facts is not a promise about Thursday's. Where a commitment will be missed regardless of ranking, that order leaves this worksheet and enters the delay-communication process with its own record; moving it down the list is not a substitute for telling the buyer.

If the storefront's stated commitments no longer match what the operation can meet, that mismatch is worth describing in a Prism consultation alongside any related processing question. Describe the platform and the commitment structure without sending the order list or customer details through the public form. Scope, responsibilities, fees and terms are confirmed before work begins.

Due-work queue table

Build one row per accepted order or per queue checkpoint, using real commitments and holds. The table is finished when every outstanding quantity in the population is either ranked with a reason or explicitly parked with a hold reason and a review point.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.