Skip to main content
The AIM lifecycle is a practical way to choose the next job: Intake → Stock → List Management → Sales → Fulfillment. The labels are operational workspaces, not a universal event vocabulary. A stock receipt and a channel order can enter the spine at different points, and each channel keeps its own status and eligibility rules.

​
How the stages connect

The stock branch starts with an expected shipment and may reach List Management once inventory is eligible for the relevant channel. The order branch can enter Sales directly. The diagram does not say that every channel uses every stage; it shows where an operator can look for the next operational job.

​
Starting states and ending states

There are two useful starting states:
  • Expected stock: a purchase or shipment is expected, but expected contents are not the same as physical receipt. Receiving records what actually arrived; a partial receipt leaves the remainder expected.
  • A channel order needing work: a provider has supplied a channel-native order status that AIM must interpret in its operational context.
The lifecycle ends for this overview when the applicable stage has a verifiable result: a receipt or inventory state is recorded, a provider confirms a listing action, an order reaches a completed or cancelled/returned outcome, or the work is held in attention until a person can review it. Attention is not a synonym for pending; an unknown or unsafe-to-interpret status belongs there rather than being silently put into a fulfillment queue.

​
Stage by stage

​
Where this appears in AIM

Use these current surfaces to inspect the handoff described by each stage. Access to a surface still follows your AIM permissions. The stage descriptions intentionally stay at the handoff level. How the inventory numbers fit together, Product, inventory, listing: what each one is, and Sales, reservations, and allocation own the detailed definitions that operators need inside those stages.

​
One example, carried through

Meridian Kicks expects six fictional pairs of the Jordan 4 “Black Cat,” size 10. Five arrive. At Intake, the operator records five and leaves one expected. In Stock, the operator checks the size, location, and processing state; a remaining processing, putaway, or location hold can keep the five out of a channel offer while that work is unfinished. Once the relevant channel rules allow an offer, List Management sends the selected action and waits for the provider-confirmed result. When one pair sells, Sales keeps the source status with its operational interpretation. Fulfillment then picks and packs the selected pair, uses the applicable shipment artifact, and checks the committed result; a cancellation or mismatch stops the pending work until it is reconciled.

​
Where the channels differ

The boundary between Stock and List Management is channel-specific. AIM’s own inventory inputs are not one universal published quantity: a marketplace feed and a store channel can apply different eligibility, ownership, workflow, and location rules. Read Ready to list and channel sellability before comparing numbers across channels. The Sales boundary is also channel-specific. Channel-native orders do not share one mapping from source status to pending, in transit, completed, cancelled, or attention. Queue eligibility can differ from the external lifecycle, so do not infer a pick/pack decision from a status label without its channel context. The Fulfillment boundary is about custody and evidence. Where a flow uses a reservation, check it alongside the selected unit, committed status, and audit history before treating physical work as complete. What syncs, when, and who wins explains channel authority and inbound/outbound differences; Sales, reservations, and allocation explains the order-side relationships.

​
Verification at every handoff

Use the evidence that belongs to the stage:
  1. After Intake: check actual received quantities and the partial/remaining state.
  2. After Stock: check the item or size, location/condition, and adjustment history before correcting a surprising number.
  3. After List Management: check the exact channel, account scope, listing or operation result, and provider confirmation.
  4. After Sales: retain the channel-native source status and its operational stage; unknown or conflicting interpretation is attention.
  5. After Fulfillment: check the committed shipment/fulfillment event and the available audit history before treating the order as complete.
Verification is not the same as reading one badge. Inventory and fulfillment history are event-backed, external listing actions require provider confirmation, and channel order states preserve source detail. If the applicable evidence is absent, do not fill the gap with an assumption.

​
Safe escalation

Stop before adjusting a count, retrying an external mutation, or marking work complete when the status or result is missing, contradictory, or outside the channel boundary described above. Use the AIM Assistant’s thumbs-down feedback and choose Contact support; the ticket includes your question, the answer, the conversation ID, and the page. A timeout or unknown status is not permission to force success.

​
Common misconceptions

“Every receipt is ready to list.” Receipt records what arrived; post-receive authentication, quality, putaway, workflow, and location gates can still keep a unit out of a channel offer. “Every sale follows Intake, Stock, and List Management first.” A stock path commonly moves through those stages, but an existing channel order can enter Sales directly. “Submitted means applied.” A listing intent or submitted operation is not an applied provider result until the exact scoped external response confirms it. “One number and one status rule work everywhere.” Inventory publication and order interpretation vary by channel. Keep the channel and source status with the result you are investigating.
Last modified on August 9, 2026