When a catalogue count is not a stock count

An imported catalogue can tell you that records exist. It cannot, by itself, tell you how many units are physically present, correctly identified, ready to sell, or safe to promise to a customer.

That distinction sounds simple, but it is easy to lose when a dashboard presents one large number beside a reassuring progress indicator. A source may contain 5,000 products, listings, releases, or collection entries while the business has fewer Stock items, more physical copies, incomplete matches, or quantities that are unavailable for sale.

The answer is not to force the numbers to agree. It is to give each number a clear meaning and make the differences reviewable.

One screen can contain three different counts

Catalogue reconciliation becomes easier when three questions are kept separate:

These counts may be related, but they are not interchangeable. A catalogue record describes an identity or source entry. A Stock item represents something the business controls. Sellable quantity is a decision derived from the current operating state.

When those meanings are collapsed into one total, the interface can create confidence without evidence.

Why the numbers legitimately differ

One record may represent several physical units

A product catalogue often stores one record for a product or release. The warehouse may hold five copies. Conversely, a source collection may contain repeated entries for the same identity while the Stock catalogue groups or separates them according to condition, location, cost, or fulfilment needs.

Record count and unit count therefore answer different questions. Neither is wrong; the mistake is presenting one as the other.

A match does not prove availability

An imported record can be matched to a Stock item that currently has no sellable quantity. Units may be allocated to open orders, in quarantine, awaiting inspection, reserved as a buffer, held at an unavailable location, or already sold on another Channel.

Identity is necessary for stock control, but identity is not availability.

Condition can change the commercial offer

Two physically similar items may need separate Stock records because their condition, packaging, edition, grading, or completeness differs. A catalogue identity can help describe what the item is, but the operator still needs to confirm which physical copy is being offered and on what terms.

Identifiers may be incomplete or ambiguous

SKUs, barcodes, catalogue numbers, external IDs, titles, and variants are not equally reliable. Exact identifiers can support a strong match. Similar names can produce plausible but unsafe candidates, particularly when editions, bundles, sizes, or regional versions differ.

A good reconciliation workflow distinguishes an exact result from a candidate that still needs judgement. It does not turn uncertainty into a match simply to improve the percentage.

The source may describe something the business no longer holds

External catalogues and collections can contain history, duplicates, archived offers, or entries that have not yet been reconciled with physical stock. Importing them is useful evidence. It is not a warehouse count.

What goes wrong when the counts are blended

Overselling becomes easier

If every imported entry is treated as available stock, Channels can receive quantities that the warehouse cannot fulfil. The resulting cancellation is not just a data problem; it is a broken customer promise.

Progress looks better than the operation

A single percentage can hide the difference between “imported”, “identified”, and “ready to sell”. A team may believe a migration or connection is complete while hundreds of ambiguous records still need review.

Review work disappears

Mismatches are operational work. They need a visible queue, a reason, and a safe next action. If a system silently creates Stock, guesses a match, or removes differences from the headline total, it makes the dashboard tidier by making the underlying position harder to trust.

Corrections become destructive

When imported facts and Stock ownership are mixed together, a later refresh can overwrite values that the business deliberately reviewed. Clear boundaries make it possible to refresh source evidence without rewriting the operating record.

A practical reconciliation workflow

1. Preserve the imported evidence

Keep the source identity, import time, connection, and useful catalogue facts visible. The team should be able to explain where a record came from before deciding what it means for Stock.

2. Match strong identifiers first

Start with exact external IDs, barcodes, and controlled SKUs where their contracts are understood. Normalise formatting carefully, but do not broaden an exact match into title similarity simply because the exact path found nothing.

3. Put uncertain records into review

Ambiguous, missing, conflicting, and duplicate evidence should remain visible as review work. Show the candidate facts that support a decision, then ask the operator to confirm, create, correct, or leave the record unresolved.

4. Create Stock deliberately

A new Stock item should represent an intentional operating record, not a side effect of importing a catalogue. The create step should collect the fields the business needs to identify, locate, value, and manage the item while preserving the approved source facts.

5. Calculate sellable quantity separately

Once identity and Stock coverage are understood, availability can be calculated from the stock model: physical balance, allocations, buffers, locations, quarantine, returns, and Channel-specific rules. That quantity can change without changing the underlying catalogue identity.

6. Reconcile again after change

Imports, warehouse movements, sales, returns, and manual corrections all change the picture. Reconciliation is strongest when the system re-reads the current state after each reviewed action rather than relying on a stale batch summary.

Not every blank should block the workflow

Honest reconciliation does not mean making every optional field mandatory. A missing descriptive attribute is different from a missing identity or an unknown quantity. The workflow should distinguish what is required for a safe action from what would merely enrich the record.

Core questions usually include:

• Do we know which product or variant this is?
• Do we know which physical units the business controls?
• Do we know their current location and availability state?
• Can we explain the quantity being offered on each Channel?

Optional catalogue facts can remain blank or await later review without pretending they were assessed. The important rule is that missing enrichment must not be confused with missing operational evidence.

What a trustworthy dashboard should show

A useful reconciliation surface does not need a complicated chart. It needs labels that preserve meaning.

• Imported: the number of source records or copies currently held.
• Covered: the number represented by reviewed Stock identities.
• Needs review: missing, ambiguous, duplicate, or conflicting coverage.
• Excess Stock: Stock evidence beyond the imported source count, where relevant.
• Sellable now: the quantity that remains after operational availability rules.

The interface should also state the unit behind each number. “Records”, “products”, “copies”, “Stock items”, and “units” are not stylistic variations. They are contracts with the operator.

The ChannelWeave approach

ChannelWeave keeps imported catalogue evidence separate from the Stock records used to operate the business. Where a connected catalogue is compared with ChannelWeave Stock, imported totals, Stock coverage, and items needing attention remain distinct rather than being presented as one number.

Strong identifiers can support exact reconciliation. Ambiguous candidates remain reviewable, and reviewed catalogue values can be retained as Reference facts without turning every optional attribute into a blocker. Stock quantity and Channel availability continue to follow the inventory workflow rather than being inferred from the existence of a catalogue entry.

The aim is not to make every count match. It is to make every difference understandable, reviewable, and safe to act on.

For the wider stock-control model, read the multichannel inventory ownership playbook. To see why product facts increasingly matter beyond conventional search, read why clean catalogue data matters in AI search.

Final thought

A catalogue count tells you how much evidence arrived. A Stock count tells you what the business has identified and chosen to manage. Sellable quantity tells you what can be promised now.

Keep those answers separate. The dashboard may show more than one number, but the operation will gain something more valuable: confidence that each number means what it says.