Ga naar inhoud

Ecommerce Inventory Cycle Counting: How to Build a Schedule That Catches Stock Errors

A customer orders the last item showing in stock, but your picker finds an empty shelf. Now you have to delay the order, offer a substitute, or issue a refund. The error may have started weeks earlier with a misplaced return or an unrecorded damaged unit.

An ecommerce inventory cycle counting schedule helps you catch those errors before they reach checkout. Instead of closing your operation for a full stocktake, you count small groups of products regularly, investigate differences, and correct the process that caused them. Here’s how to build a schedule your team can actually keep.

What is cycle counting in ecommerce?

Cycle counting is the practice of checking a portion of your physical inventory against your inventory records on a recurring basis. You might count a few high-value SKUs every week, slower-moving products once a quarter, and items with recent discrepancies more often.

For an online store, the goal is not simply to make the numbers in your system match the shelves. Accurate records help you avoid selling unavailable products, make better purchasing decisions, and spot issues such as missed receipts, picking errors, damaged goods, or returns put back in the wrong location.

A workable schedule has three parts: a rule for choosing what to count, a repeatable count procedure, and a way to investigate and track discrepancies. Without all three, counting becomes a recurring correction exercise rather than a way to prevent errors.

Build your cycle counting schedule in six steps

1. Define exactly what you are counting

Start with the smallest unit you need to control: usually a SKU at a specific storage location. A medium T-shirt in black and the same shirt in blue are separate SKUs. If you stock the black shirt in two bins, each bin needs to be checked before you can explain a location-level difference.

Include every place stock can sit: picking shelves, overstock, returns areas, damaged-goods areas, and any other location you manage. If you use a fulfillment partner, establish which counts you perform and which inventory reports or count procedures they provide.

Also define the quantity your team will compare. Physical on-hand stock is not always the same as available-to-sell stock. Open orders may reserve units, while damaged or quarantined items may still be physically present but unavailable to customers. Keep those statuses separate so a correct physical count does not create a new checkout error.

2. Group SKUs by risk, not just sales volume

A simple ABC approach gives you a starting point. Put your most important items in group A, moderately important items in B, and the remainder in C. Sales value or order frequency can help you sort them, but they should not be the only factors.

Move a SKU into a more frequent count group if it is expensive to replace, frequently returned, easily confused with another variant, stored in multiple locations, or associated with past discrepancies. A low-cost item that repeatedly causes canceled orders may deserve more attention than its sales value suggests.

Count groupTypical itemsExample starting frequency
A: High riskFast sellers, high-value products, or SKUs with recurring errorsWeekly
B: Moderate riskSteady sellers with occasional movement or errorsMonthly
C: Lower riskSlow movers with stable recordsQuarterly

These are starting points, not universal rules. If weekly A counts overwhelm your team, narrow the A group or count a manageable share of it each day. If a product causes repeated problems, increase its frequency even if it sits in group C.

3. Turn frequencies into a realistic calendar

Calculate the workload before assigning dates. If you have 40 A SKUs to count weekly across five working days, plan for roughly eight A SKUs per day. Add a share of your monthly and quarterly counts, then allow time to research differences. A schedule that accounts only for the minutes spent scanning products will quickly fall behind.

Choose a consistent counting window when movement is relatively low. For many stores, that is before daily picking begins. If orders, receipts, or transfers continue during the count, your team needs a clear cutoff: record what happened before the count and what happened after it. Otherwise, normal stock movement can look like a discrepancy.

A simple calendar might assign high-risk SKUs to short daily batches, one section of the B list to each week, and one section of the C list to each month. This spreads the work without leaving a large quarterly count until the final day.

4. Write a count procedure anyone can follow

Consistency matters more than an elaborate system. Give the person counting a SKU or location list and a clear method for recording the result. Where practical, have them count without seeing the expected quantity; this reduces the temptation to accept the system number after a quick glance.

  1. Confirm the SKU, variant, unit of measure, and storage location.
  2. Count the physical units, including any stock in overstock locations covered by the task.
  3. Keep damaged, returned, or quarantined units separate from sellable stock.
  4. Record the quantity and count time before changing the inventory record.
  5. Recount differences, preferably with a second person for material discrepancies.
  6. Investigate and approve any adjustment according to your team’s rules.

Bundles and multipacks need special care. A sealed pack of six is not six individual units available to sell unless your inventory setup and fulfillment process treat it that way. Write down the counting unit so different team members do not make different assumptions.

5. Investigate discrepancies before adjusting stock

Suppose your system shows 12 units of a product and your team counts 10. Before changing the record, check for orders picked but not yet marked fulfilled, recent receipts not entered, stock in another bin, pending returns, and damaged units set aside. Then recount the product.

If the difference remains, record both the adjustment and the likely cause. Useful cause categories include receiving, picking, returns, transfers, damage, product identification, and unknown. “Unknown” is acceptable when you cannot establish the cause; inventing an explanation is not.

Set an approval threshold that fits your business. For example, you might allow a supervisor to review all adjustments and require an additional check for high-value or repeated losses. The purpose is to keep an audit trail and make sure a mistaken count does not overwrite a correct record.

6. Review the schedule and fix recurring causes

Once a month, look beyond the number of counts completed. Which SKUs keep showing differences? Do discrepancies cluster around returns, a particular bin, or days when receipts arrive late? Use those patterns to change the workflow.

If similar-looking variants are repeatedly mixed, improve bin labels or separate their storage locations. If returned items are the problem, make the return inspection and restocking steps clearer. If one SKU has several unexplained differences, count it more frequently while you investigate.

Track a few measures your team can use, such as counts completed on schedule, SKUs with discrepancies, units adjusted, and repeated discrepancies by cause. A high count-completion rate is helpful, but fewer recurring errors is the stronger sign that your process is improving.

How to handle counts while orders are moving

You do not have to stop selling to cycle count, but you do need to prevent transactions from being mistaken for errors. If possible, count a bin when no one is picking from it. If that is not possible, note the count time and check any orders, receipts, transfers, or returns recorded around that time before making an adjustment.

For a small team using a spreadsheet, that may mean one person counts while another confirms recent movements. If you use inventory software, check how it handles count sessions, stock reservations, and adjustments before relying on an automated count workflow. The same principle applies either way: compare the physical quantity with the system quantity at the same point in time.

Common cycle counting mistakes to avoid

  • Counting everything equally: This spends too much time on stable products and too little on SKUs most likely to cause costly errors.
  • Correcting numbers without finding causes: An adjustment fixes today’s record but will not prevent the same receiving or picking mistake tomorrow.
  • Ignoring secondary locations: Stock in overstock, returns, or quarantine can make an accurate bin count look wrong.
  • Counting during uncontrolled movement: Orders picked or receipts shelved mid-count can create false discrepancies.
  • Letting the schedule become too ambitious: A short routine your team completes consistently is more useful than a detailed plan it regularly skips.

Start with a schedule you can maintain

You do not need to classify your entire catalog perfectly before beginning. Choose your highest-risk SKUs, assign a small daily counting block, and use one consistent procedure for recording and investigating differences. After a month, review what you found and adjust the frequencies.

Your next step is to list the products that have caused stockouts, refunds, or frequent manual corrections recently. Put those SKUs on a weekly count schedule first. The errors you uncover will show you where to improve the rest of your inventory process.

Veelgestelde vragen

How often should an ecommerce business cycle count inventory?

Count higher-risk SKUs more often than stable, slow-moving ones. Weekly counts for high-risk items, monthly counts for moderate-risk items, and quarterly counts for lower-risk items can be a practical starting point. Adjust the schedule based on discrepancies and the time your team can reliably commit.

Is cycle counting a replacement for a full physical inventory count?

Cycle counting can reduce your reliance on disruptive full counts, but whether it replaces one depends on your operational, accounting, and reporting needs. Ask your accountant or relevant advisor what records and physical checks your business requires.

What should you do when a cycle count does not match your records?

Recount the SKU, check all relevant locations, and review transactions around the count time. If the difference is real, document the adjustment and investigate its cause. Avoid changing the quantity simply to close the count task.

Can you run cycle counts with a spreadsheet?

Yes, especially with a smaller catalog. Record the SKU, location, expected and counted quantities, count time, difference, likely cause, adjustment, and reviewer. As order volume and locations grow, consider whether your current process still gives you a reliable view of stock movements.

Geef een reactie

Je e-mailadres wordt niet gepubliceerd. Vereiste velden zijn gemarkeerd met *

Secret Link