> ## Documentation Index > Fetch the complete documentation index at: https://docs.aimventory.com/llms.txt > Use this file to discover all available pages before exploring further. # Choose your path > Start with the job in front of you and open a current AIM destination for setup, receiving, listing, fulfillment, or investigation. Use the job, not the menu label, to choose a starting point. These paths lead to current AIM destinations and end with a result to verify; they do not assume that every channel follows the same sequence. ## Choose your job Finish the provider-specific approval or validation and check the connection result before relying on it. Record what actually arrived. If the box is partial, leave the remainder expected and continue with the stock workflow. Select the target channel, review the operation, and confirm the provider result rather than treating submission as success. Find the outbound work, use the applicable label or shipment artifact, and check the committed fulfillment result. Run or review a marketplace listing check and use its history as evidence for the next action. ## If you are starting from a state | What you have | Start here | What to verify next | | ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ | | An expected shipment or purchase order | [Receive incoming stock](/buying/purchase-orders) | Actual quantities, partial/remaining state, and the inventory workflow state. | | Stock that needs an offer decision | [Listings Control](/listings/listings-control) | Target channel, selected sizes, and the scoped provider result. | | A channel-native order | [The lifecycle overview](/start/lifecycle-overview), then [Fulfillments](/selling/fulfillments) when physical work is required | Source status, operational stage, and committed fulfillment evidence. | | A StockX or GOAT listing mismatch | [Sync Health](/listings/sync-health) | Check results and Report History before changing stock or retrying a cleanup action. | | A disagreement about channel numbers or authority | [What syncs, when, and who wins](/understand/what-syncs-and-who-wins) | Which channel owns each value and which surface is the applicable check. | ## Boundaries worth remembering * A connection being saved, or a local connection label being active, is not the same as provider-specific approval or validation. * A receipt records what arrived; it does not by itself prove that every unit is ready for every channel. * A listing action is applied only after the exact scoped provider result confirms it. Timeout, rate-limit, and temporary failure are not success. * An operational order stage preserves channel-native status. Do not use one channel’s status mapping for another channel. * Available and Ready to list are different inventory questions, and Reserved has already left Available. Use [How the inventory numbers fit together](/concepts/inventory-numbers) for the definitions. ## When the path stops being clear Do not force a count adjustment, retry an external action, or mark an order complete when the result is missing or contradictory. 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. For the full sequence and its non-linear entry points, read [The AIM lifecycle from Intake to Fulfillment](/start/lifecycle-overview).