The paid order was revised after its pick list was exported

Freeze the authorized revision and every released version

Start with the order as it now stands after the authorized edit: who approved the change, when, and exactly which items, quantities or addresses changed. Preserve the pre-edit contents as well, because the pick list was generated from that earlier state and the comparison needs both sides.

Then enumerate every instruction the warehouse received: each exported pick list, batch file, integration push or printed sheet, with its reference and export time. An order can appear on a consolidated batch pick list as well as its own document, and withdrawing one while the other circulates leaves the obsolete contents in play.

Do not rely on the current order screen to tell you what the warehouse holds. The screen shows the present; the pick list shows what the warehouse was told. This investigation lives in the gap between those two records.

Do not assume the integration saw the edit

Shopify's documentation on editing orders warns that some apps do not recognize order edits, and that a removed item can remain in a fulfillment app and still ship. That is a documented possibility about connected apps, not proof about your particular warehouse integration — but it means the default assumption must be that the edit did not propagate until a record shows otherwise.

Look for the acknowledgment in the system that produced the pick list: a re-import of the order, a revision flag, a new pick-list version, or an explicit sync log entry. If the fulfillment system has no record of the revision, treat the released instruction as live and the goods as at risk of being picked to the old contents.

A store edit also does not update the payment record by itself. If the revision changed what the buyer owes or is owed, that consequence is a separate reconciliation between the store and the payment provider. This page decides which physical instruction the warehouse follows; the money follows its own evidence.

Diff the instruction lines against the authorized order

Compare the released pick list line by line with the authorized revision: items removed, items added, quantities changed and any address change that affects the parcel. Each difference is an instruction the warehouse holds that no longer matches the order it is supposed to fulfill.

Classify the state of the physical work for each affected line using the warehouse's own records: not yet picked, picked, packed or handed over. A removed item already picked is a physical unit sitting in a tote that needs a return-to-stock or hold disposition. An added item may need new stock allocated and its own availability checked rather than assumed.

Where the pick list covers several orders in one batch, scope the withdrawal precisely. The instruction to withdraw concerns this order's lines, not the whole batch, and the warehouse needs the unaffected lines to keep moving.

Supersede the obsolete version explicitly

Issue the correction as a versioned event the warehouse can act on: the superseding pick list or revision reference, the explicit withdrawal of the earlier version, and the disposition for any units already picked to the old contents. An email saying the order changed is not a version withdrawal; the warehouse needs to know which document to stop using.

Obtain the warehouse's acknowledgment against the withdrawn reference, and confirm which version the pack-out will complete. Where a third-party fulfillment service controls the work, the acknowledgment comes from that service's own system or contact, not from an internal note.

Name the authorizer. The person who approved the order edit, the person who may direct the warehouse and the person who owns any payment adjustment may be three different roles. Record each decision with its owner so a later audit can see who instructed what.

Record the version decision before the parcel moves

The closed record answers: what the authorized revision changed, which pick-list versions existed, which were withdrawn, which version the warehouse acknowledged and completed, what happened to units picked to the old contents, and which payment consequence was handed to which owner. If the same integration repeatedly misses order edits, that recurrence is a configuration question for whoever maintains the connection, with this order as the documented example.

If the recurring failure means the storefront or its order flow cannot be trusted to propagate revisions, that is a website question you can describe to Prism: the platform, the editing and fulfillment systems involved, and the observed sequence, without order exports or customer records. Scope, responsibilities, fees and terms are confirmed before any work; each live order's instruction decision stays with your authorized staff.

Pick-list version control sheet

Use one copy per revised paid order. Enter actual references, times and findings. The warehouse completes only the acknowledged superseding version; the sheet never assumes a store edit reached the fulfillment system.

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.