DTC technology × growth systems — built to compound.
DTCUP / FIELD NOTES / OPERATE

Keep Inventory Accurate from Warehouse Shelf to Website

Keep physical stock, commitments and website availability in agreement. Plan cycle counts, investigate differences and fix the processes that create inventory errors.

Published Jul 11, 2026Updated Sep 21, 20268 min read
Jack Hu
Jack Hu

7 years of experience building and operating brand websites, specializing in website development, paid advertising and SEO. Built a brand website from launch to US$10 million in annual sales.

The Short Answer

Define each quantity by item, location, condition, unit and time. Trace receiving, picking, transfers and returns, then count a controlled scope with an explicit method for movements during the count.

Investigate differences before an approved adjustment, protect the customer promise while uncertainty is unresolved, and verify the downstream website quantity. Review recurring causes and consistent accuracy definitions so counting improves the process rather than merely resetting numbers.

Key takeaways

  • Physical stock and sellable availability answer different questions.
  • A count needs a clear scope, time and treatment of concurrent movement.
  • Investigate and approve differences, then verify every affected stock destination.
  • Fix recurring causes instead of relying on repeated manual adjustments.

An inventory number is useful only when the team knows what it means. Twenty units in a warehouse might include products already promised to customers, damaged returns and stock waiting for inspection. Treating all twenty as available can create a customer problem even if the physical count is correct.

I would build inventory accuracy around three questions: what is physically present, what condition and commitment apply to it, and what quantity should the website offer for sale? Counting matters, but so does the movement between those states. A monthly correction cannot compensate for a process that creates new errors every day.

This guide explains a practical operating routine for a brand working with its own warehouse or a fulfillment partner. The examples are fictional and the controls should fit the actual products, systems and responsibilities involved.

Agree which number answers which question

Write down the stock definitions used by the warehouse, commerce platform and planning sheet. Do not assume two columns called “available” subtract the same reservations or include the same locations.

For example, Shopify's inventory-state guidance distinguishes on-hand, available, committed, unavailable and incoming quantities. This is a concrete platform example, not a universal vocabulary for every warehouse system. Map the equivalent definitions in your own setup before comparing totals.

For a fictional product, suppose the location physically holds 100 units. Fifteen are committed to orders and five are held for quality review. Under a simple model where those groups do not overlap, 80 remain available. Another 40 traveling to the warehouse do not become received stock merely because the purchase order exists.

Record the unit of measure too. A carton containing six products is not one sellable unit unless the customer buys the carton. Variant, pack size, location and condition are part of the stock record, not optional notes.

Assign an owner for the definitions. When a new marketplace, bundle or warehouse is added, review the mapping before connecting its quantity feed. A consistent-looking dashboard can still be comparing different concepts.

Find where the record can fall behind reality

Follow one product from receiving through storage, picking, dispatch and any return. At each step, identify the physical movement, the required record and who confirms it. Include damaged items, samples, replacements and transfers between locations.

Common questions are straightforward: when is an incoming delivery counted as received, who confirms a partial shipment, and where does a returned item wait before it can be sold again? If the team cannot answer consistently, the next discrepancy is already being prepared.

Use a short movement record:

Event Physical evidence Record to reconcile
Supplier receipt Counted product and condition at receiving Accepted quantity by item and location
Order dispatch Confirmed picked and shipped items Fulfilled quantity and remaining commitment
Customer return Actual item received and inspected Return status, condition and stock decision
Location transfer Dispatch from one location and receipt at another Stock in transit and accepted destination receipt
Damage or sample use Identified units and approved reason Appropriate removal or unavailable state

Do not use a convenient stock adjustment to conceal a missing receipt or unrecorded transfer. It may make today's total match while destroying the evidence needed to explain tomorrow's problem.

Count a controlled scope at a known time

Cycle counting means checking selected stock regularly rather than relying entirely on an occasional full count. Choose a scope that someone can finish and reconcile: specified items, bins or locations with clear boundaries.

Give more attention to items with frequent movement, costly discrepancies, confusing variants or recent process changes. Also include some less active stock so the program does not ignore forgotten locations. There is no universal daily or monthly frequency that suits every business.

Record the count time and handle movements during the count explicitly. The operation might temporarily control movement in the selected area, or use a supported process that reconciles concurrent receipts and picks. Agree the method before starting; otherwise the physical count and system snapshot may describe different moments.

Microsoft's cycle-counting documentation illustrates separate stages for creating count work, recording quantities and reviewing differences. It also notes that open counting work in that configuration does not automatically block the associated inventory. Check your actual system's behavior rather than assuming that opening a count freezes stock.

Use clearly identified products and locations. Where practical, have the initial counter record what they observe without being led by the expected quantity. A recount should resolve uncertainty, not simply repeat the system's number until the report looks correct.

Investigate a difference before approving an adjustment

First verify the basics: correct product, correct variant, correct location, correct unit and comparable timing. Then inspect recent movements. A discrepancy may be an unposted receipt, a pick in progress, a duplicate transaction or stock stored in the wrong place.

Imagine a fictional system balance of 50 units and a physical count of 44. Six units were moved to a packing area shortly before counting. If the count covered only the storage bin while the system balance covered the whole location, reducing total stock by six would create a new error. Clarify the scope before changing the record.

If a recount and movement review confirm a real difference, document the reason as far as it is known. “Unknown after review” is more honest than inventing a damage explanation. Keep the original count, expected balance, recount, related movements, proposed adjustment and approving person together.

Set approval boundaries appropriate to the business. An unusual or material adjustment may need someone separate from the counter to review it. The aim is a traceable correction with an accountable owner, not an administrative obstacle that leaves customers buying unavailable stock indefinitely.

Address the customer promise while investigating. If confidence in a product's sellable quantity is low, the responsible team needs a temporary selling or allocation decision. Do not leave that decision implicit in an inaccurate number.

Make warehouse and website changes agree

Name the system that owns the physical stock record and the system that determines the offer to customers. Document how reservations, unavailable stock and location eligibility affect the quantity sent between them.

Check both normal updates and exceptions. What happens if a stock message is delayed, an import fails or the same adjustment is received twice? Who sees the problem, and how do they verify the current state before repeating an update?

For a discrepancy investigation, compare the same item, location, definition and timestamp. Repeatedly overwriting the warehouse from the website, then the website from the warehouse, can create a loop in which neither team knows which record is authoritative.

After an approved correction, verify the downstream result. Confirm that the appropriate quantity reaches the commerce system and relevant channels, while committed orders remain accounted for. A successful adjustment in one screen is not proof that every selling destination has updated.

Treat bundles carefully. If several offers consume the same component, their availability must reflect that relationship. Do not count the same physical item as independently available in every bundle merely because each has a separate product page.

Measure recurring causes, not just the final accuracy percentage

Choose a consistent accuracy definition and keep its denominator visible. A measure based on item-location records matching exactly differs from a measure based on absolute unit differences. Neither should silently become the other in a monthly report.

In a fictional count of 100 item-location records, 92 match exactly. That gives 92% exact-record accuracy for that sample. It does not establish 92% accuracy across the whole warehouse, particularly if the sample deliberately focused on troublesome items.

Also review the size and consequence of differences. One missing high-value product and one extra low-value accessory do not cancel each other operationally just because the net unit difference is zero. Track meaningful causes, affected orders and repeated locations alongside the headline measure.

Look for the work that prevents recurrence: clearer labels, an earlier receiving confirmation, a better return inspection queue or a corrected integration mapping. Counting more often helps discover errors sooner; correcting their source helps stop producing them.

Start with one manageable counting routine

Select a representative area and agree the definitions, timing and movement controls. Train the people involved using the actual products and devices. Perform the count, review differences and follow approved corrections all the way to the website.

At the first review, ask whether the team completed the process and resolved the important discrepancies. If the count generated a growing review queue, fix ownership or scope before expanding it. Unresolved count work is not the same as accurate stock.

Then extend coverage according to the observed risks and available capacity. Keep a clear route for a support or warehouse colleague to request an extra check when an order exposes a problem.

My recommendation is to connect the counting routine with everyday receiving, dispatch and returns reviews. Inventory accuracy becomes dependable when those processes leave clear evidence. It should not depend on one experienced person remembering which spreadsheet adjustment explains the number.

Questions about inventory accuracy

Should every discrepancy immediately change the website quantity?

Not automatically. Confirm the product, location, unit and timing, and investigate relevant movements. Separately decide how to protect the current customer promise while uncertainty is resolved. Apply an approved correction through the defined source system and verify the downstream result.

Can our fulfillment partner own the counting process?

Yes, if responsibilities and evidence are clear. Agree what is counted, how movements are controlled, who reviews differences, which adjustments need approval and how results reach the brand. Delegating the task does not remove the need to understand recurring problems or customer impact.

Does an accurate physical count mean we can sell every unit?

No. Some units may already be committed, damaged, awaiting inspection or in a location that cannot fulfill the order. Translate the physical count into sellable availability using the actual stock states and operating rules.

Explore the warehousing guides, fulfillment provider selection and inventory planning guide for the connected stock and operating decisions.

Sources

  1. learn.microsoft.com — cycle-counting
  2. help.shopify.com — inventory-states

Still have a question?Ask the DTCUP Community ↗

FAQ

Questions related to this insight.

Clear scope, practical constraints and direct answers for the decision ahead.

Should every discrepancy immediately change the website quantity?

Not automatically. Confirm the product, location, unit and timing, and investigate relevant movements. Separately decide how to protect the current customer promise while uncertainty is resolved. Apply an approved correction through the defined source system and verify the downstream result.

Can our fulfillment partner own the counting process?

Yes, if responsibilities and evidence are clear. Agree what is counted, how movements are controlled, who reviews differences, which adjustments need approval and how results reach the brand. Delegating the task does not remove the need to understand recurring problems or customer impact.

Does an accurate physical count mean we can sell every unit?

No. Some units may already be committed, damaged, awaiting inspection or in a location that cannot fulfill the order. Translate the physical count into sellable availability using the actual stock states and operating rules.

Leave a Reply

Your workspace

Selected services

DTCUP / YOUR NEXT PERSPECTIVE

Stay curious.
Stay connected.

Ideas for the work behind growth—websites, brands and the apps that connect them.