POS inventory management: keep shop stock accurate

A checkout can update stock when a product sells, but accurate inventory needs more than sales. Deliveries, returns, transfers, damage and physical counts must reach the same records. Start by deciding which system holds the stock figure you trust and how every movement gets there.

If you use separate checkout and operations software, write down what passes between them. A nightly file import and a live connection behave differently. Staff need to know when a balance was last updated before promising a customer that an item is available.

How does a POS update stock?

In a configured product-based checkout, a completed sale can reduce the balance for the item and location. A sale of two blue mugs should reduce blue mugs by two, not all mugs or the stock at another store. The software needs the correct product, quantity, location and transaction status.

Ask the provider to show how it treats orders awaiting payment, reservations, cancellations and returns. Do not assume that every number labeled stock means units ready to sell. Shopify's inventory-state guide distinguishes on-hand, available, committed, unavailable and incoming quantities.

POS product variants

Give each separately tracked size, color or pack its own clear identity. A single item called T-shirt cannot tell you whether the missing unit is a small green shirt or a large white one. Decide which distinctions staff need before importing a catalog.

For a worked example, a shop sells tea as individual tins and sealed six-packs. If a six-pack is a separate stocked product, scanning it should reduce that product by one. If it is a bundle of individual tins, the system needs a supported rule to reduce tins by six. Test the chosen model rather than relying on the name.

Barcode mapping in a POS

Scan real packaging during setup. Confirm the product description, size and price, then inspect which stock record changed. A barcode that reads successfully can still point to the wrong item. Keep internal product codes distinct from the barcode value when your system uses separate fields.

The product-code guide helps organize those identities. Check duplicate codes before a count: Shopify's stock-count documentation notes that a barcode assigned to multiple products causes a scanning error in that workflow.

POS stock reconciliation

Choose one product, one location and a defined period. Reconcile physical on-hand units, keeping reserved or unsellable units separate if your software uses those states. A useful quantity bridge is:

Closing stock = opening stock + receipts + restocked returns + transfers in − sales − transfers out − removals.

Here is a fictional week for one mug SKU:

The expected closing count is 40. If staff count 38, investigate the two-unit gap before changing the record. A count adjustment records a correction; it does not explain the cause. Keep the reviewed count and the explanation together.

Why is my POS stock wrong?

Check timing first. A delivery waiting to be entered or a sale waiting to sync can explain a difference. Then check product identity, location, pack size and duplicate entries. Review voids and returns separately because money moving back to a customer does not prove stock came back.

Use a short investigation order:

1. Recount the exact item, including the stockroom and set-aside goods.
2. Confirm the report period, time zone and location.
3. Match recent receipts and transfers with physical movements.
4. Review sales, returns and canceled transactions.
5. Record the reason and authorize any correction through your normal process.

The stock-discrepancy guide covers follow-up when the difference remains unexplained.

Handling returns in inventory

Separate the financial refund from the stock decision. A saleable return might go back on the shelf. A damaged return might need a separate unsellable balance or a recorded removal, depending on the system. A refund without a physical return should not add a unit to saleable stock.

Test each case in your provider's approved training workflow. Give staff a written rule for who inspects the item, chooses the outcome and approves an exception.

Multi location POS inventory

Keep location names consistent across connected systems. A transfer out of Shop A is not a customer sale, and stock in transit may not be available at Shop B. Decide who records dispatch, who confirms receipt and what happens when quantities differ.

Test a transfer from start to finish before rolling out to another shop. A correct business-wide total can hide an incorrect balance at both locations.

POS sales CSV imports

A file import needs stable transaction references and a clear cutoff so repeated or overlapping files do not deduct stock twice. Check whether the file contains one row per item, per transaction or per payment. Those formats are not interchangeable.

headoffis can review up to 100 completed sale lines per import, matching products by SKU or barcode and using whole units and USD unit prices. Repeated products within a transaction need stable line IDs. Keep the POS source name and line mapping consistent; exclude refunds, canceled or unpaid orders, weighted items and order totals. It does not calculate tax or discounts for imported sales.

Before confirming, check that those sales were not already deducted through manual entries or a newer physical count. This is a reviewed file workflow, not automatic live POS synchronization. See the sales help guide for the surrounding sales workflow.

Does a POS replace stock counts?

No. It records the movements it receives. A count checks the goods that are physically present. Use the cycle-counting guide to plan small checks and the stocktake tool to prepare a standalone count. Investigate repeated differences so the next count starts from a better process.

← All posts