Building a SKU Tracker You Can Actually Trust

A SKU tracker tells you how much of each specific stock item you hold, where it is and how much is available to promise. For a product with sizes, colours or pack options, that means tracking the exact variant—not relying on a total for the whole product range.

The practical goal is to answer “do we have the blue medium?” without phoning the warehouse or comparing several dashboards. But a useful answer needs more than a screen. The record must distinguish physical stock from reservations, unavailable units and the quantities published to channels.

This guide explains what to track, how movements should change the balance, where barcode scanning helps and how to introduce a tracker the team can trust. The same principles apply whether you use a controlled spreadsheet, standard inventory software or a custom system.

Availability needs to reflect the exact item ordered, the stock that can fulfil it and any commitments already made.

Key Takeaways

• Track each distinct stock item separately, including relevant size, colour, pack and unit differences.
• Keep location and stock state visible. A business-wide total does not prove stock is usable or accessible for a particular order.
• On hand and available are different quantities. Reservations and restrictions determine what you can safely promise.
• Maintain a traceable movement history, with defined rules that avoid deducting the same units twice.
• Scanning helps identify items and capture work, but does not independently verify every quantity or prevent every error.
• Central stock control still needs channel synchronisation and recovery. Standard and custom systems should both be tested against real exceptions.

In this guide:

• 1. Define What a SKU Tracker Tracks
• 2. Separate On-Hand Stock From Available Stock
• 3. Model Variants, Packs and Bundles Correctly
• 4. Calculate Balances From Recorded Movements
• 5. Use Barcode Scanning as Part of the Workflow
• 6. Connect Channels Without Double-Counting Stock
• 7. Compare Spreadsheet, Standard and Custom Options
• 8. Pilot a Catalogue You Can Reconcile
• Frequently Asked Questions
• How OpsMavix Can Help

1. Define What a SKU Tracker Tracks

A SKU is an internal stock-keeping identifier. It distinguishes an item you need to manage separately from other stock.

A tracker can be part of an inventory platform rather than a separate product. Its value is in the catalogue model, movement records and availability rules it makes accessible.

Track the Exact Item

For a T-shirt range, blue-medium and blue-large may be separate stock items. A parent product total can help summarise the range, but should not determine availability for a specific variant.

The range has 25 available units, but none is blue-medium. Accepting a blue-medium order from the parent total would promise a different item from the one the customer selected.

Use Stable Identifiers

Give each distinct stock item an unambiguous internal identifier. Maintain mappings to supplier references, channel variants and barcode identifiers where needed.

A SKU and a barcode are not necessarily the same thing. Multiple identifiers may refer to the same internal item, and a packaging barcode may represent a different quantity from an individual-unit barcode.

Shopify’s product-detail guidance distinguishes SKUs and barcodes and recommends unique SKUs for effective tracking.

Keep Parent Totals for Their Proper Purpose

A product without variants may need only one stock item. Products with separately stocked variants need separate balances, while parent-level reports remain useful for analysis.

2. Separate On-Hand Stock From Available Stock

A physical quantity is not automatically a sellable quantity. Units may be reserved, damaged, awaiting inspection or otherwise restricted.

Shopify’s inventory-state documentation illustrates this distinction through on-hand, available, committed, unavailable and incoming quantities. Other systems may use different names, so agree the definitions in your own workflow.

A Location-Level Example

Suppose a SKU has stock in two locations:

The example uses on hand minus reserved minus unavailable. If the business applies safety buffers, channel allocations or other restrictions, the published quantity may be lower.

An order needing eight units may require split fulfilment or a transfer, even though the business has ten available overall. Location matters as well as quantity.

Do Not Count Incoming Stock as Present

An open purchase order can inform planning, but its units are not physically on the shelf. If you accept preorders or backorders, display and manage those commitments under explicit rules.

Similarly, stock in transit should remain visible without appearing at both the sending and receiving locations as immediately usable.

Show the Age of the Record

A central view can be current only to the last successful update it received. Include refresh times and unresolved failures where they affect decisions.

If a location has pending offline movements, staff should know that its balance needs caution rather than assume the screen is fully current.

3. Model Variants, Packs and Bundles Correctly

Size and colour are familiar variants. Packs and kits introduce another issue: one sellable item can depend on several physical units or components.

Distinguish a Pack From Its Contents

A six-pack may be held as a separately stocked item, or assembled from six individual units when ordered. Those models change stock differently.

If a receipt of five six-packs is posted as five single units, you understate stock. If it is posted as 30 packs, you overstate it. Document units and conversion rules before connecting feeds or scanners.

Worked Example: Shared Components

Assume a bundle needs two units of component A and one of component B. Component A has 18 available units and B has seven.

The limiting component is B, so the components support seven bundles under these assumptions.

If three bundles are accepted and reserve their components, six units of A and three of B become committed. Remaining availability is 12 A and four B, supporting four additional bundles.

Those components may also be sold individually or used in another kit. All relevant commitments need to affect the shared pool.

Shopify documents a component-based approach to bundle availability. Verify the behaviour of your specific bundle setup, locations and stock settings.

Treat Preassembled Kits Differently

If components are physically assembled into a stocked kit, the assembly transaction may consume components and create finished-kit stock. Subsequent kit dispatch should not consume those same components again.

The correct model follows what happens physically and how your system records it.

4. Calculate Balances From Recorded Movements

A tracker needs an explainable opening position and the events that change it. Those events can be captured manually, through scanning or by integration.

Repeatedly overwriting a balance without keeping the reason makes investigation harder. A movement history lets the team follow how the total was reached.

Agree Which Event Changes Which Quantity

A reservation changes availability. A transfer changes location. A dispatch reduces stock under the chosen fulfilment model. A return may initially increase stock awaiting inspection rather than available stock.

Picking and dispatch should not both reduce the same balance independently if they represent stages of one outbound movement.

Worked Example: One Location’s Balance

Consider a SKU beginning with 30 units at a warehouse:

The returned unit may be unavailable until inspected. The transfer should have a corresponding in-transit or receiving record, rather than disappear from the wider operation.

This table explains on-hand stock at one location. Reservations and restrictions need their own consistent state changes to calculate availability.

Record Enough Evidence

Retain item, quantity, unit, location, reference, time, responsible user or process, and correction reason where appropriate.

If a count finds a difference, investigate and approve the adjustment. A movement history improves traceability, but it does not guarantee that every physical event was recorded correctly.

For the accuracy problem in more detail, see why stock never matches the system.

Movement records, reservations and channel mappings should follow the same agreed stock model.

5. Use Barcode Scanning as Part of the Workflow

Barcode scanning is a capture method. It can identify an item or location quickly and reduce transcription errors when supported by validation.

A barcode inventory system may already include SKU records, movement handling and reporting. The scanning and tracking functions do not have to be separate products.

Verify the Relevant Details

A picking workflow may ask the operator to confirm location, item and quantity against an order. A receiving workflow may identify the item and record accepted quantity, batch or condition.

Scanning an item barcode confirms an identifier. It does not necessarily count the units in a carton, prove the condition or establish which batch is being used.

The workflow needs to capture those details where they matter.

Design the Record and Capture Together

Define identifiers, locations, stock states and movement rules, then test the scan steps against them. You can develop those parts together rather than insisting on a universal hardware-first or software-first sequence.

If staff cannot identify the right unit or complete an update reliably, improve that step before trusting the resulting balance.

Provide a Controlled Fallback

Unreadable labels, damaged scanners and connection problems will occur. Give users a practical fallback with validation and a visible record.

An awkward workaround can push staff back to notes that never reach the system. A fallback that bypasses every check can create a different error.

6. Connect Channels Without Double-Counting Stock

A channel is a sales destination, not necessarily another physical holding location. Adding together Shopify, Amazon and eBay listing quantities can overstate the stock available if they all draw from the same shelf.

Map Listings to Stock Items

Maintain the relationship between the internal SKU, channel listing or variant, fulfilment location and pack quantity. Do not rely on product titles alone.

Keep separate stock pools separate. Units physically held in a marketplace fulfilment network may not be immediately usable by your own warehouse.

Choose Shared Availability or Channel Allocation

Two channels can legitimately publish availability from one shared pool. That does not mean the quantity exists twice, but competing orders can arrive before updates propagate.

For scarce stock, the business may use buffers or allocate quantities to channels. If six units are divided into four for one channel and two for another, the allocation can reduce competing claims while potentially limiting sales in the busier channel.

Choose the trade-off deliberately and adjust it using demand and fulfilment evidence.

Design for Update Failures

Custom software still exchanges data with external platforms. It needs to handle delays, duplicates, missed events and failed updates.

Shopify’s webhook documentation describes delivery limitations and the need for reconciliation. Ownership of the integration does not remove those external constraints.

Track the last accepted publication, pending updates and failures. Reconcile periodically and prevent duplicate notifications from creating duplicate reservations or deductions.

For the wider workflow, see reducing overselling across Shopify, Amazon and eBay.

7. Compare Spreadsheet, Standard and Custom Options

A spreadsheet can track variants and movements. Standard inventory systems can provide traceability and central availability. A custom build can also fail if the design or capture process is weak.

Assess the configured workflow rather than assuming the product category determines accuracy.

Improve What Already Works

If the problem is inconsistent identifiers or an unrecorded return, correcting the workflow may be more valuable than changing software.

If current software already supports variant-level inventory, investigate configuration, mapping and adoption before replacing it.

Build for a Specific Gap

Custom development may be appropriate for unusual bundle rules, shared stock across B2B and retail, or unsupported location and channel connections.

A custom inventory system should address those gaps with acceptance criteria. It should not be sold as a guarantee against future discrepancies.

Compare Total Cost

Include setup, data cleanup, migration, training, recurring charges and remaining manual work. Verify savings with measured incidents or effort rather than assuming all cancellations disappear.

Confirm code or licence rights, data exports, administrator access and support. Custom ownership depends on the contract and handover, and does not remove ongoing costs.

Shared responsibilities and visible exceptions help the team keep catalogue and stock records current.

8. Pilot a Catalogue You Can Reconcile

Start with a bounded product group that includes representative variants, locations and selling rules. Include at least one awkward example, such as a shared-component bundle or a restricted return.

Establish the Baseline

Clean duplicate identifiers, map channel variants and label locations. Confirm opening stock and reservations.

If work continues between the count and go-live, capture the intervening movements. A correct physical count can become an incorrect opening position if dispatches are omitted.

Test End-to-End Events

Include:

• A receipt in a different packaging unit.
• An order that reserves a variant.
• A cancellation and reservation release.
• A pick followed by dispatch.
• A transfer between locations.
• A return held for inspection.
• A bundle competing with an individual component sale.
• A failed update and a duplicate notification.

Check the result in the central record and each relevant channel. A successful message is not sufficient if it updates the wrong variant or location.

Measure Whether Trust Improves

Track count differences, late movements, manual checks, unmapped listings and unresolved channel failures. Define acceptance criteria before declaring the pilot complete.

An operations dashboard can show those exceptions and freshness indicators. It should not make provisional data look final.

Expand With a Support Plan

Assign owners for catalogue changes, count review and integration failures. Document how corrections work and retire conflicting stock writers deliberately.

A focused pilot may provide useful visibility in weeks where scope and data are ready. Multiple channels, complex bundles and data cleanup can extend the timeline with either standard or custom software.

Frequently Asked Questions

What is a SKU tracker?

It is a record or system that tracks quantities for distinct stock items, with the locations and states needed to determine availability. It may be a spreadsheet, a function of an inventory platform or a custom workflow.

Should I track products or variants?

Track separately stocked variants as separate items. Parent-product totals remain useful for reporting, but should not determine whether a specific size, colour or pack is available. A product without variants may need only one stock item.

Is a SKU the same as a barcode?

Not necessarily. A SKU is your internal stock identifier; a barcode is a machine-readable identifier used in capture. Map each barcode to the correct item and packaging unit so scanning changes the intended quantity.

What is the difference between on hand and available?

On hand describes physically recorded stock. Available reflects the units your rules allow you to promise after reservations and restrictions. Incoming or in-transit stock needs separate treatment rather than being assumed ready to ship.

Can one unit be offered on several channels?

Yes, channels can publish views of a shared stock pool. Updates and reservations need to be reliable, and concurrent orders can still create risk. Buffers or channel allocations may be appropriate for scarce stock.

Does barcode scanning guarantee the count is correct?

No. It can reduce identifier-entry errors and support validation, but quantities, condition and movements still need to be recorded correctly. Physical checks and exception review remain necessary.

Can standard software provide a traceable SKU tracker?

Yes. Many inventory platforms support variant records, movements and reservations. Evaluate the actual configuration and interfaces. Custom development is worth considering when an important requirement remains poorly served.

Why do stock figures change unexpectedly?

Investigate unrecorded movements, incorrect units, duplicate events, conflicting writers, reservations and adjustments. A movement and integration history can help explain the change. Unexpected figures are not proof that every packaged system is a black box.

How do I start without replacing everything?

Choose a representative product group, clean identifiers and agree stock rules. Test movements and channel updates against known results. Keep suitable tools and add configuration or connections before considering a wider replacement.

How OpsMavix Can Help

OpsMavix builds focused inventory automation systems for growing businesses with stock rules and connections their current setup cannot handle reliably.

We start with the catalogue, locations and movement process, then assess how availability reaches the channels. That helps distinguish a variant-mapping problem from missing capture, inconsistent reservations or an integration gap.

OpsMavix can help you:

• Define distinct stock items, variants and packaging units.
• Map channel listings to the right internal records.
• Separate on-hand, reserved and unavailable quantities.
• Connect receipts, transfers, returns and dispatches.
• Design scanning and correction workflows.
• Make failed updates and discrepancies visible.
• Plan pilot testing, documentation and support.

For multichannel sellers, eCommerce inventory automation can connect the agreed stock authority to Shopify and other supported channels. The aim is reliable, explainable availability with visible recovery when a connection fails.

Bring an oversold variant, a bundle discrepancy or a stock total you cannot explain to an Operations Leak Audit. We will map where the record diverges from the work and which changes could improve it.