AIWorkDex
Ecommerce Practice

Prepare and reconcile a subscription dispatch wave

Create a dated dispatch view that separates future, due, overdue, blocked, and completed subscription orders.

Preparation
One setup session followed by a review for each dispatch wave.
Difficulty
Moderate
Task
Build a subscription dispatch queue
Back to the Task: Build a subscription dispatch queue

Before you start

Get what you need before you start

  • Confirm the actual subscription types, billing states, fulfilment schedules, promised dispatch dates, and cancellation rules.
  • Gather pending subscription orders, inventory, locations, address holds, payment exceptions, and customer-contact exceptions.
  • Use an organisation-approved ChatGPT workspace. Before upload, remove names, addresses, emails, phone numbers, payment data, credentials, and external order references; keep a secure reconciliation key separately.
  • Identify the owner for the wave and the person who approves stock release.

Steps

Work through the method

Use the listed inputs and tools. Check the evidence when you need to verify a step.

  1. Classify every pending order

    Export the minimum pending-order fields, remove the listed identifiers, and store the secure reconciliation key outside the upload. First classify each order as pay-per-delivery or prepaid. Then assign it to future, due, overdue, blocked, or completed from the correct fulfilment path and schedule. Keep uncertain orders in a review queue.

    Why it matters: A dated state prevents future orders from blending into work that should ship now.

    Input
    Pending subscription orders, schedule records, fulfilment state, and approved dispatch dates.
    Output
    A de-identified dispatch table with due wave, state, evidence link, and review flag.
    Tools in this stepShopifyChatGPT data analysis

    Evidence for this step

  2. Check and reserve wave stock

    Group due orders by SKU and location. Compare required, available, reserved, damaged, and incoming stock. Apply the approved reservation process and route every shortage.

    Why it matters: A clean order list cannot produce a complete wave when stock is missing or reserved elsewhere.

    Input
    The due queue, product quantities, inventory by location, reservations, and incoming stock evidence.
    Output
    A stock-ready list and shortage queue with owner, customer route, and next decision date.
    Tools in this stepShopify

    Evidence for this step

  3. Approve the dispatch queue

    Remove future, cancelled, refunded, payment-blocked, address-blocked, customer-contact, and stock-short orders from bulk fulfilment. Lock the due set and record the approver.

    Why it matters: The approval gate stops a bulk action from shipping an order that needs another decision.

    Input
    The classified table, stock-ready list, order exceptions, and subscription terms.
    Output
    A locked due queue, separate exception queues, count, quantity total, and approver.
    Tools in this stepShopify

    Evidence for this step

  4. Fulfil and reconcile the wave

    Fulfil only the locked queue. Reconcile planned orders and quantities against labels, fulfilment records, inventory changes, failed actions, and remaining due orders before closing the wave.

    Why it matters: A final reconciliation detects missing, duplicate, failed, or premature fulfilment while the wave can still be corrected.

    Input
    The locked queue, fulfilment and label results, inventory movements, and exception log.
    Output
    A signed wave record with matched totals, unresolved orders, exception owners, and next dispatch date.
    Tools in this stepShopify

    Evidence for this step

Success checks

Check the result before you finish

  • Every pending order has a documented future, due, overdue, blocked, completed, or review state.
  • Required stock, available stock, reservations, shortages, and affected orders reconcile before release.
  • The locked queue excludes every known payment, address, cancellation, refund, stock, and contact exception.
  • Planned orders and quantities match fulfilment, labels, inventory movements, failures, and remaining due work.

Failure modes

Watch for these problems

  • AI infers a dispatch date from order age. Restore the documented subscription schedule and review uncertain rows.
  • Future and due orders share one bulk action. Stop and rebuild the locked queue.
  • Stock is counted without reservations. Reconcile all commitments before release.
  • The closing totals differ. Keep the wave open and trace every missing or duplicate order.

Tools

Choose the tools you need

Sources

Read the sources behind this practice

Check what each source supports and where the advice has limits.