> ## 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.
# List newly received inventory
> Review newly received inventory for channel readiness, pricing, listing submission, and provider-confirmed results.
## Goal
Find inventory that has recently entered AIM, review whether each item is ready for
the particular channel you intend to use, submit only the approved listing action,
and verify the provider result. A received item can be Available while a
post-receive step still keeps it out of Ready to list. Receiving and putaway can
participate in automation that has been set up, but neither workflow promises that a
marketplace listing was created.
**Who does this:** Listings or inventory operator. **Who else is involved:** A
receiving operator may finish pending receiving or putaway work; a catalog or
marketplace administrator may resolve channel mapping, condition, photos,
credentials, or a failed provider response.
## Before you start
* Confirm that receiving has created the inventory item and physical unit you
intend to review. If the item is still **Pending receiving** or **Pending
putaway**, finish or resolve that work first when your channel requires it.
* Confirm the receiving location and, where applicable, the item's sublocation.
Use the separate putaway or transfer workflow when the physical location needs
to change.
* Have the purchase order available if you need to review one intake. The
purchase-order filter uses unconsumed units attributed to the selected order;
it does not apply the full canonical active-unit definition or mean “every row
that once mentioned this order.”
* Confirm that you have the **Listings Control** access needed for the action.
Marketplace credentials and channel setup must be active for the location and
channel you select.
* Decide which channel you are reviewing. StockX, GOAT, and eBay listing
readiness are not interchangeable, and Shopify uses a separate quantity and
publication path.
**What this touches:** The review reads inventory items, physical-unit and
location state, ownership, condition, channel mapping, market data, hold
settings, and existing listing records. A preview or listing action records its
preview/task identity, pricing inputs, per-item outcome, and local listing state;
the workflow does not use listing submission as a substitute for receiving,
putaway, or an inventory correction.
## Keep these terms separate
| Term | What it means here | What it does not mean |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **Available** | The inventory pool AIM draws from when something sells. | It is not a promise that the item can be listed on every channel. |
| **Ready to list** | AIM's derived portion of Available after **Damaged**, still-processing, and quarantined inventory is held back. | It is not a provider listing and is not the same as each channel's sellable quantity. |
| **Pending receiving** | A received item still has a post-receive step, such as putaway, to complete. | It is not proof that the item is unreceived or ready for a listing. |
| **Marketplace sellable quantity** | For StockX, GOAT, and eBay, the channel quantity after the relevant eligibility rules and minimum hold. | It is not the Shopify quantity and is not a value to type into AIM. |
| **Shopify quantity** | A separate publication quantity based on available stock and Shopify blockers. | It is not the StockX/GOAT/eBay marketplace sellable quantity. |
| **Preview** | A proposed action with pricing and skip information for review. | It is not provider confirmation or a live listing. |
| **Confirmed listing** | A provider-terminal result matched to the relevant local listing state. | It is not the same as a submitted or queued request. |
## Steps
| Step | Where in AIM | What you do | What you should see |
| -------------------------------- | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 1. Open the candidate view | **Listings Control** | Open the listing-control view and sort by **Date Updated** to start with recently received candidates. Narrow by location, purchase order, brand, or quantity; on a consignment-enabled business, use the Ownership control's **All**, **Owned**, or **Consignment** choice when the review needs a smaller set. | Rows are grouped by variant and location. The purchase-order filter shows unconsumed units attributed to the selected order. |
| 2. Separate work from candidates | **Listings Control** | Use **Pending putaway only** when you need to find items still in post-receive work. Treat those rows as a work queue; finish the pending step and refresh before submitting a listing action. | Pending receiving counts are shown separately, and the row can appear even when the channel quantity is zero. |
| 3. Inspect the row | Variant and location details | Review Available, Ready to list, Damaged, pending receiving, minimum hold, ownership when the Ownership control is available, condition, location, and current marketplace cards. | You can tell why the row is a candidate, why it is not ready, or why an existing listing remains visible. |
| 4. Choose one channel path | Marketplace selection | Select only the channels you have checked. Apply the StockX/GOAT/eBay marketplace rules separately from the Shopify publication path. | The review is channel-specific: a row can be ready for one path and not ready for another. |
| 5. Review channel readiness | Eligibility and catalog details | Confirm ownership, condition, catalog identity, size mapping, required photos, active credential, and hold. Do not treat a positive Available number as a substitute for these checks. | Ineligible channels are skipped with a reason such as condition, missing mapping, missing photos, missing credential, no channel quantity, or below hold. |
| 6. Review pricing | Listing preview | Open the preview and compare current market data, asks, payout, margin, and any channel strategy. Add a custom price only when the preview allows it and the price is approved. | The preview has a preview-run ID and per-item pricing/skip information. Missing market data can remain an editable price decision; it is not an automatic price. |
| 7. Submit the reviewed action | Preview and approval controls | Approve only the item/channel combinations you intend. Submit the approved action. For eBay, follow the separate eBay Listings handoff rather than assuming this StockX/GOAT action submitted eBay. | A preview remains a preview until submission. A larger submission may return **Processing** with a task ID. |
| 8. Verify provider confirmation | Action status and listing details | Wait for the task/result status. Inspect every item and channel, then compare provider-terminal confirmation with the corresponding local listing state. | The result distinguishes success, partial, skipped, and error. A queued or submitted action is not reported as a live listing. |
## Channel readiness and ownership boundaries
### StockX, GOAT, and eBay marketplace paths
For these marketplace paths, use the marketplace sellable quantity: derived
Ready to list after **Damaged**, pending receiving, and quarantined units are
removed, less the minimum hold shown for that row. If the result is zero, or if the
item is at or below hold, the action is skipped even when Available is positive.
Then check the channel-specific prerequisites:
* **StockX:** the product and size need a usable StockX catalog/variant identity,
the condition must be accepted, and the location needs an active StockX
credential. Standard and Direct are separate listing types; review the type
and price shown in the preview.
* **GOAT:** the item needs an authoritative catalog and size mapping, accepted
condition, required GOAT photos when the preview asks for them, and an active
location credential. A missing catalog ID, size mapping, or photos is a
channel-specific skip, not a reason to change inventory quantities.
* **eBay:** this review path hands listing creation to the separate eBay Listings
surface. Use that surface's template, identity, condition, and provider
verification steps; do not describe the StockX/GOAT action as an eBay
submission.
On a business with consignment enabled, Listings Control shows an **Ownership**
control with **All**, **Owned**, and **Consignment** choices. When consignment is
not enabled for the business, that control is not shown; do not imply that these
choices are available. When the control is available, do not turn a consignment
row into an owned-marketplace claim or assume that a channel's owned inventory
rules apply to consignment. Follow the ownership boundary shown for the selected
channel and escalate when the row's ownership or the channel's eligibility
ruling is unclear.
### Shopify
Shopify is a separate publication path, not another marketplace target in this
workflow. Shopify quantity is resolved from available inventory minus Shopify
blockers (or the owned equivalents), includes **Damaged** retail units, and does
not subtract the marketplace minimum hold. Use the Shopify sync/publication
surface and its store-scoped mapping and verification state. Do not claim that a
StockX/GOAT/eBay listing action published a Shopify product or changed its
quantity.
## Pricing review and submission boundary
Review price before you approve a listing action. The preview can provide current
market asks, payout, margin, market-data timestamp, and skipped-item reasons. A
missing market-data result can be left for an explicit manual price when the
preview permits it; it is not a reason to invent a market price or to imply that
the provider has accepted one.
StockX and GOAT have different strategy and listing-type inputs. Review the
selected StockX Standard or Direct type, GOAT strategy, custom price, and any
hold/floor context as separate decisions. Inbound purchase-order pricing review
and marketplace repricing are also separate workflows: recording a unit cost or
printing a barcode does not submit a marketplace price, and a repricing workflow
does not stand in for a new listing submission.
The approval boundary matters:
1. **Preview** calculates a proposed action and identifies skips.
2. **Approve/submit** sends only the selected item/channel combinations.
3. **Processing** means the action has a task/status identity but is not a
provider-confirmed listing.
4. **Confirmed** means the provider's terminal result and the corresponding AIM
listing state agree for that item/channel.
## Variants
**Pending putaway or another post-receive step.** Use **Pending putaway only** to
find work, not to bypass it. Complete the supported putaway workflow, refresh
Listings Control, and recheck the row's pending receiving, Ready to list, hold,
and channel status before previewing again. Putaway records an existing unit's
location; it does not mint inventory or promise a listing. Automation that has been set up
may be triggered after clearance, but it remains subject to its own channel and
eligibility checks.
**Purchase-order review.** Filter by the PO when the intake is known. If a row is
not present, verify that an unconsumed unit is attributed to that PO and that the
business/location filters are correct. Do not add a made-up quantity or use an
old cost-layer association to force the row into the review.
**Owned inventory.** Confirm the owned quantity and channel eligibility for the
selected location. A hold reduces marketplace sellable quantity but does not
change Available; do not lower Available to represent the hold.
**Consignment.** On a consignment-enabled business, use the available Ownership
control and keep the channel boundary visible. When consignment is not enabled,
the All/Owned/Consignment control is not shown. Do not assume a consignment row
follows the owned StockX, GOAT, eBay, or Shopify path; use the supported channel
surface and escalate an ownership mismatch before approval.
**StockX Standard or Direct.** Treat Standard and Direct as separate listing
types. Review the selected type, catalog identity, credential, and price in the
preview. An existing listing of one type does not authorize silently creating a
duplicate of the other.
**GOAT mapping or photos missing.** Keep the row in the preview's skipped set,
resolve the catalog/size mapping or required photos on the appropriate surface,
then create a fresh preview. Do not retry the same missing-prerequisite action
as if it were a provider timeout.
**eBay.** Follow the eBay Listings handoff for templates, conditions, quantity,
and confirmation. A row may be visible in Listings Control while its eBay action
is managed on the eBay surface.
**Shopify.** Move to Shopify sync/publication review. Validate store-scoped
mapping and Shopify sync state independently; a marketplace listing result is not
Shopify confirmation.
**Partial batch.** Keep the task ID and preview-run ID. Use the same preview
identity only to inspect or resume in-progress, stale, or deferred work. After a
terminal partial or failed result, create a fresh preview containing only the
failed or skipped item/channel combinations. Never include already successful
combinations in that fresh preview.
## When it does not go to plan
| What you see | What it means | What to do | Where it is explained |
| ------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **Pending putaway** or another pending receiving count | The item is on hand but still blocked by post-receive work. | Finish the supported receiving/putaway step, refresh the row, and recheck Ready to list and channel readiness. | [Put away and locate stock](/operations/put-away-and-locate-stock) |
| Available is positive but the marketplace sellable quantity is zero | **Damaged**, pending receiving, quarantined, or hold units leave no channel quantity. | Correct the underlying workflow or approved inventory record when the evidence supports it; do not write a derived quantity or lower Available to model a hold. | [How the inventory numbers fit together](/concepts/inventory-numbers) |
| Condition is not eligible | The selected marketplace rejects the item's recorded condition. | Resolve the condition through the supported catalog/inventory path, then preview again. Do not submit that channel. | [Ready to list and channel sellability](/understand/channel-sellability) |
| Missing StockX catalog/variant identity or credential | StockX cannot build an eligible, authenticated listing for this item/location. | Resolve the catalog or credential, then create a fresh preview. | **StockX, GOAT, and eBay marketplace paths** |
| Missing GOAT mapping or photos | GOAT cannot prove the size/catalog or required listing media. | Resolve the mapping/photos on their supported surface and preview again. | **GOAT** |
| Existing active listing | The requested listing would duplicate an existing active listing for that marketplace/type. | Inspect the existing listing card. Do not submit another copy; use the separate repricing or delist workflow if that is the actual goal. | [Repricing](/operations/repricing) |
| Preview shows missing market data | The price decision lacks the expected market input. | Enter an explicitly approved custom price only when the preview allows it, or stop and resolve the data. Do not call the preview a confirmed listing. | **Pricing review and submission boundary** |
| **Processing** with a task ID | The action is queued or running, not confirmed. | Poll or refresh the action status. Keep the task and preview IDs; do not submit a duplicate while it is processing. | **Pricing review and submission boundary** |
| Partial, skipped, or error result | Some item/channel combinations did not become confirmed listings. | Read each per-item reason. For in-progress, stale, or deferred work, inspect or resume with the same preview identity. After a terminal partial or failure, create a fresh preview containing only failed or skipped combinations; never include successful combinations. Escalate provider/auth/rate-limit/timeout failures. | [What syncs and who wins](/understand/what-syncs-and-who-wins) |
| Provider authentication, rate limit, timeout, or temporary error | The provider has not confirmed the requested state. | Preserve the response and identifiers, follow the supported retry/backoff path, or escalate. Do not mark the local listing live by hand. | **What was recorded** |
| Shopify quantity or publication differs | Shopify uses a separate store-scoped quantity/publication path. | Review Shopify mapping and sync state there; do not retry a marketplace listing action to fix Shopify. | [What syncs and who wins](/understand/what-syncs-and-who-wins) |
A listing action is not an inventory adjustment. Do not lower Available to model a
marketplace hold, clear a pending workflow without completing it, or change ownership or
condition merely to satisfy a channel check. Use the supported receiving, putaway, catalog, or
inventory-correction workflow and preserve the listing preview/task identifiers.
A queued, processing, stale, or deferred action can already own the listing work. Check the
existing preview-run and task status first. Use the same preview identity only to inspect or
resume in-progress, stale, or deferred work. After a terminal partial or failed result, create
a fresh preview containing only failed or skipped combinations, never successful ones. Escalate
authentication, rate-limit, timeout, and temporary provider failures instead of treating them as
confirmed success.
## Fictional example
Northstar Kicks receives a fictional PO into **Main Warehouse** for two **Owned**
Bluebird Runner size 9 units. The operator opens **Listings Control**, sorts by
**Date Updated**, filters to the PO, and sees one unit with one pending putaway
step. The operator uses **Pending putaway only** as a work queue, completes the
fictional putaway, refreshes, and sees the pending count fall; no listing is
assumed from that change.
The remaining candidate shows one Ready to list unit, a minimum hold of one, and
an active StockX credential. The operator previews StockX Standard and GOAT
separately. StockX returns a price and margin; GOAT is skipped because the
fictional catalog mapping lacks the required size mapping. The operator approves
only the StockX row, submits it, waits for the task to reach a terminal result,
then checks the provider-confirmed StockX result against the local listing card.
The operator records the GOAT skip and resolves it separately rather than
submitting a duplicate or claiming that the Shopify storefront changed.
## Check it worked
1. Reopen or refresh **Listings Control** with the same location and PO filters,
plus the Ownership control when it is available for a consignment-enabled
business.
2. Confirm the submitted item/channel has a terminal action result and inspect
every skipped or error row. A partial result is not an all-success result.
3. Confirm the provider's terminal result and the matching local listing state
for the specific item, marketplace, credential/location, and listing type.
4. Confirm that a preview-only or still-processing row is not described as live.
5. For in-progress, stale, or deferred work, retain and use the preview-run ID
and task ID to inspect or resume the existing action. After a terminal partial
or failed result, resolve the exact failure and create a fresh preview with
only failed or skipped combinations; never include successful combinations.
6. If the intended channel was Shopify, verify Shopify's store-scoped mapping,
publication state, and quantity separately; do not use a StockX/GOAT/eBay
listing result as that proof.
## What was recorded
The action evidence includes the preview-run ID, selected marketplace and listing
type, pricing inputs, task ID when background work is used, and per-item success,
partial, skipped, or error results. After a non-dry-run action, AIM refreshes the
local Listings Control state. Keep the provider response and the local listing
record together: submission, **Processing**, and provider confirmation are
different states.
## Related
* [How the inventory numbers fit together](/concepts/inventory-numbers) — keep Available, Ready to list, pending receiving, and holds distinct.
* [Ready to list and channel sellability](/understand/channel-sellability) — compare StockX, GOAT, eBay, Shopify, and ownership boundaries.
* [What syncs and who wins](/understand/what-syncs-and-who-wins) — verify channel-specific direction and confirmation.
* [Put away and locate stock](/operations/put-away-and-locate-stock) — finish pending putaway without treating it as a listing.
* [Review pricing and print barcodes](/operations/review-pricing-and-print-barcodes) — keep inbound pricing review separate from marketplace listing price.
* [Repricing](/operations/repricing) — change an existing listing price through its own workflow.
* [Send and receive a purchase order](/operations/send-and-receive-a-purchase-order) — verify the intake state before listing review.
* [Choose an in-store purchase or purchase order](/operations/in-store-purchase-or-purchase-order) — choose the correct intake path first.