Running a stock take in WINTOUCH POS/ERP means freezing sales, counting physical stock against the system, and posting variance adjustments in a single controlled sequence — not a once-a-year scramble with a clipboard. This guide covers the exact steps, when to schedule full counts versus cycle counts, and what actually causes stock discrepancies in 2026.
- WINTOUCH POS/ERP handles both full stock takes and rotating cycle counts for inventário de stock WINTOUCH workflows in 2026.
- Freeze sales and receiving before counting — mixing live transactions into a count is the top cause of bad variance data.
- Enter counted quantities into WINTOUCH and let the system calculate variance before you post any adjustment.
- Barcode scanners cut manual entry errors versus paper count sheets and speed up multi-location counts.
- Businesses on Primavera or Cegid ERP can reconcile WINTOUCH stock adjustments through API integration.
Why this matters
An inventory audit that isn't structured turns into wasted labor and a stock ledger nobody trusts. Retailers and restaurants running WINTOUCH POS/ERP in 2026 need a repeatable count process because stock accuracy feeds directly into reorder alerts, margin reporting, and SAF-T compliant invoicing.
Get the sequence wrong and adjustments end up hiding theft, spoilage, or receiving errors instead of surfacing them. A stock take that skips the variance review step is just a number reset, not an audit.
How to run a stock take in WINTOUCH
- Schedule the count and lock the register. Pick a low-traffic window and block new sales for the counted categories, or store-wide for a full stock take.
- Pull the current stock list. Export on-hand quantities by category, location, or supplier so counters work from an accurate starting sheet.
- Count the physical stock. Scan each SKU with a handheld barcode scanner instead of writing numbers on paper — it removes a full layer of transcription error.
- Enter counts into WINTOUCH. Input the scanned or manual counts against each stock list line so the system calculates the difference automatically.
- Review the variance report. WINTOUCH ranks discrepancies by value — work top-down, not alphabetically, so the biggest exposure gets checked first.
- Post the adjustments. Once reviewed, commit the change so stock levels, cost of goods, and reorder thresholds update immediately.
- Investigate flagged SKUs. Pull sales history and receiving records for items with an unusual variance before writing anything off as shrinkage.
- Log the audit and set the next date. Full counts run once or twice a year; cycle counts rotate through high-value or high-turnover SKUs weekly or monthly.
Skip step 5 and you're just resetting numbers, not auditing them. A stock take without a signed variance review isn't an audit — it's a guess with extra steps.
Full stock take vs cycle counting
| Full stock take | Cycle counting | |
|---|---|---|
| Frequency | 1-2 times per year | Weekly or monthly rotation |
| Store impact | Requires closing or heavy scheduling | Runs during normal trading |
| Best for | Year-end reconciliation, audits | High-turnover or high-value SKUs |
| Labor | High, concentrated | Low, spread out |
| Verdict | Do it for annual reconciliation | Do it for ongoing accuracy |
Most retailers running WINTOUCH POS/ERP in 2026 use both: a full count for year-end books, cycle counts to catch problems between them instead of finding out in December.
Why stock discrepancies happen
- Manual entry errors — typos and miscounts on paper sheets, largely solved by scanning instead of writing.
- Theft or shrinkage — the variance category that should trigger investigation, not automatic write-off.
- Receiving errors — accepting the wrong quantity from a supplier without checking the delivery note against the system.
- Damaged or expired stock not written off — items still sitting in the system after they've left the shelf.
- Uncaptured transfers — stock moved between locations or storerooms without a matching adjustment.
- SKU or barcode mismatches — similar products with swapped barcodes throw off counts for two SKUs at once, not one.
Do I need to close the store to run a stock take?
No — cycle counting lets you audit sections of your inventory while the store stays open, which is why most WINTOUCH POS/ERP users reserve full closures for the annual count only. Freezing sales for the specific counted category, rather than the whole register, keeps the rest of the floor trading normally.
Can WINTOUCH sync stock counts with Primavera or Cegid ERP?
Yes — businesses running Primavera or Cegid alongside WINTOUCH can connect WINTOUCH POS to Primavera ERP via API so posted stock adjustments reconcile with the accounting side automatically instead of requiring a manual export.
How does cloud WINTOUCH differ from on-premise for audits?
Cloud deployments centralize the stock list across every terminal in real time, which matters for multi-location counts. Businesses still running local installs can review the process to migrate from on-premise POS to WINTOUCH Cloud before their next full stock take.
Set up WINTOUCH for your next audit
Get WINTOUCH POS/ERP configured for stock takes and cycle counts.
One last thing
Most businesses treat the annual stock take as the whole audit and skip cycle counting the rest of the year — that's backwards. A weekly cycle count on your top 20% highest-value SKUs catches receiving errors and shrinkage within days instead of months, and it makes the once-a-year full count a formality instead of a 12-hour scramble. If your 2026 stock take turns up a variance you can't explain by receiving records or sales history, treat it as a shrinkage signal first and a data-entry error second — not the other way around.
FAQ
What is a stock take in WINTOUCH POS/ERP?
A stock take in WINTOUCH POS/ERP is a physical count of inventory reconciled against the system's recorded stock levels, with variances reviewed and posted as adjustments. It can cover the full store or a rotating subset of SKUs.
How often should you run inventory audits?
Run a full stock take once or twice a year and cycle counts on a weekly or monthly rotation for high-value or high-turnover SKUs. Relying on the annual count alone leaves discrepancies uncaught for months.
Can you run a stock take without closing the store?
Yes, cycle counting lets you audit specific categories or sections while the rest of the store keeps trading. Full stock takes usually need a closed register or a heavily scheduled low-traffic window.
Is WINTOUCH Cloud different from on-premise for stock audits?
WINTOUCH Cloud centralizes stock data across every terminal and location in real time, which simplifies multi-location counts compared to reconciling separate on-premise installs manually.
Does WINTOUCH integrate with Primavera or Cegid for stock reconciliation?
Yes, WINTOUCH POS can connect to Primavera or Cegid ERP through API integration so posted stock adjustments reconcile with the accounting ledger without a manual export step.
What causes most stock discrepancies in retail?
Manual entry errors, receiving mistakes, theft or shrinkage, and uncaptured transfers between locations account for most stock discrepancies. Barcode scanning during counts removes the transcription-error category entirely.
Do barcode scanners actually improve inventory audit accuracy?
Yes, scanning each SKU removes manual transcription errors that paper count sheets introduce, especially across large SKU counts or multi-location stores.
Should you post stock adjustments immediately after counting?
No, review the variance report first and investigate flagged SKUs before posting. Posting unreviewed adjustments can hide theft, damage, or receiving errors instead of surfacing them.
