Skip to main content
Pick, pack, and ship work is a chain of evidence, not one universal status change. First identify the order and the physical item, then record the pick, satisfy the packing checks that AIM shows, and verify the channel’s own shipment result. A pick or label can exist before the order is packed or shipped, and an AIM fulfillment status is not proof that a provider has accepted the parcel. Who does this: a fulfillment operator or picker/packer with access to the assigned location. Who else is involved: the person responsible for the channel account and the owner or manager who reviews an identity, permission, provider, or inventory exception.

Before you start

  • Open Fulfillments, or use Pick Mode for floor picking. Use Pick Runs when a saved batch is the work unit, and Pack Mode for the supported StockX and Alias packing path.
  • Confirm the business, channel-native order number and status, product and size, fulfillment location, and any unit, serial, item barcode, label, or tracking evidence already shown.
  • Make sure the channel account and the relevant AIM surface are Set up, and that your user has the applicable Pick or Pack permission and access to the selected location. A location selected by default is not a substitute for checking access.
  • For a serialized business, have the AIM serial label for the physical unit. For an item-level sale, have the supported item or variant barcode. Do not use a similar size, SKU, or box as a substitute for an identity match.
  • If the order is cancelled, returned, in an attention state, or has a credential or location mismatch, stop before picking or packing. Follow the named channel or inventory path instead of assuming that cancellation restores or relists stock.
What this touches: pick evidence, the optional saved pick-run item and label state, packing verification evidence, and—when the supported Pack Mode confirmation succeeds—the order’s AIM fulfillment state. A label or tracking value is separate evidence. This workflow does not promise a universal reservation change, inventory restoration, label, tracking propagation, provider shipment, or delivery result.

Keep the evidence separate

Steps

Assign the right physical item

Picking is an identity check. A serial scan must match the exact physical unit at the selected location. An item-level scan must resolve the supported item or variant barcode. When the scan reports a different location, another marketplace filter, no unpicked sale, or no serial/item match, stop and resolve the identity rather than choosing a similar pair. If you marked the wrong row or scanned the wrong code, use Undo or the supported unpick action, then refresh and repeat the identity check. If the exact unit is explicitly eligible for assignment to the sale, use the surfaced link or assignment result and verify the sale again. Do not silently overwrite another sale’s assignment. If ownership, consumption, or location remains unclear, preserve the evidence and escalate to the owner or manager.

Partial, missing, or wrong picks

Pack verification and labels

Pack Mode is currently the supported StockX and Alias path. Alias is represented as the GOAT channel in the underlying order path, but its label retrieval is still its own provider flow. The confirmation mode shown by AIM controls the evidence required:
  • Tracking: the tracking value must match the order.
  • Serial or item barcode: the scanned physical identity must match the order.
  • Both: satisfy both checks before confirming.
If a label is pending or fetching, refresh the label state and give the provider a few moments to respond. If it is failed, inspect the surfaced reason before using the supported refetch or rebuild action. Authentication, unavailable/not-ready, unsupported, rate-limit, and upstream errors have different next actions; an unsupported path is not fixed by repeated retries.
A generated or stored label, a tracking value, and an AIM FULFILLED result are separate pieces of evidence. Pack confirmation records the AIM packing result. Verify the channel’s own shipment or handoff status before telling a customer or teammate that the order shipped.

Channel variants

When it does not go to plan

Pick, pack, and ship evidence does not authorize an inventory adjustment. Do not use a cancellation, generic status edit, or manual quantity change to make Available, Reserved, a physical unit, a reservation, or a channel quantity look right. Use the named channel or inventory workflow and keep the original evidence for review.

Check it worked

  1. In the order or fulfillment row, confirm the selected business and location, the matched product/size and physical identity, the picked/packed evidence, and the current label and tracking result.
  2. For a saved run, confirm the picked and stored-label counts and leave any failed or unresolved rows visible for follow-up. A closed run is not proof that every row shipped.
  3. After a successful Pack Mode confirmation, confirm that AIM shows the recorded packing evidence and FULFILLED state. This is the AIM result, not the carrier or channel result.
  4. Open the channel/provider view and verify its native shipment or handoff status. For Shopify, check linked order and line-level fulfillment truth; for StockX, GOAT/Alias, eBay, and other channels, use the provider-specific status rather than a shared label assumption.
  5. If the provider has not confirmed shipment, leave the order in the appropriate unresolved state and escalate with the order number, channel, location, current AIM evidence, label state/error, tracking value if present, and the action already attempted.

What was recorded

AIM records pick and pack evidence with the order, including the actor/time and the matching serial, item, barcode, tracking, and verification details that the selected path accepts. A saved Pick Run retains its item and label state, and a stored provider label can be retrieved from the applicable label surface. Keep the channel-native status and provider error alongside that AIM evidence; neither a current row nor a label alone explains every prior action.

Fictional example

Northstar Kicks receives a fictional StockX order for one pre-owned “Harbor Blue” size 10 at the Main Warehouse. The operator opens Pick Mode, confirms the location and order number, and scans the AIM serial label on the exact pair. AIM records the pick, while the order remains separate from a packed or shipped result. The operator opens Pick Runs and sees the label move from fetching to stored, then opens Pack Mode. AIM shows the confirmation mode Both, so the operator scans the matching tracking value and the same pair’s serial label. The confirmation succeeds and AIM records the packing evidence with FULFILLED. Northstar then checks the StockX-native order status. If StockX still reports that the parcel has not been handed off, the operator does not call it shipped: the AIM pack result and the provider shipment result are recorded as separate evidence, and the order is escalated with the label/tracking details. If StockX confirms the handoff, the operator records that provider result as the final shipment verification.
Last modified on August 9, 2026