Your first stock count: moving a real shop into inventory software

The first inventory import sets the starting position from which future sales, purchases, returns, and transfers will move. If the starting quantity is a guess, an accurate checkout cannot repair it. The shop may faithfully record every new sale and still be unable to explain the shelf.

Pick a cut-over date and a manageable scope. Start with the products the pilot location actually sells. A small, reconciled catalog is more useful than a large file containing duplicates, uncertain units, and stock assigned to the wrong branch.

Clean the product list before counting. Give each item a stable SKU or other product code, a recognizable name, a selling unit, a location, and a selling price. Keep barcode values as text so leading zeros survive spreadsheet imports. Keep a pack of twelve distinct from one piece unless the system's unit conversion has been configured and tested.

Treat a blue medium shirt and a blue large shirt as different variants when the shop needs separate availability. Avoid creating three versions of the same item because different attendants used different names. Keep an import mapping that shows which old record became which product.

• Product or variant identity: a unique, stable code.
• Name and unit: something the cashier can recognize and count.
• Location: the shop or storage area holding the quantity.
• Selling price and documented cost information, kept distinct.
• Counted quantity, count time, counter, and review notes.

Count when trade is quiet or pause stock movements in the area being counted. If the shop must keep trading, record sales, receipts, and transfers during the count window and agree which side of the cut-over they belong to. Counting a shelf while another person replenishes or sells from it creates an avoidable difference.

Work by physical area so the same item is not counted twice. Mark completed areas and separate damaged, returned, reserved, and consigned goods. A customer return waiting for inspection should not automatically be included as saleable stock. Record its condition and let the reviewer decide its treatment.

Record the physical count, then compare it with the old notebook, spreadsheet, or system. A second count is useful for expensive items and large differences. Do not show counters the expected quantity if doing so will turn the exercise into confirming a number rather than observing the shelf.

For example, an old sheet lists 30 pieces of an item. The first count finds 27 and a recount also finds 27. Review recent sales, unrecorded receipts, damage, and transfers. If one branch sent three pieces to another, the issue may be location attribution rather than a loss. Keep the count and explanation even when the difference remains unresolved.

Existing stock at cut-over should use the product's opening-stock workflow. A delivery received after cut-over should use the normal purchase or receiving workflow. Entering both an opening quantity and a purchase for the same goods doubles the stock and can duplicate its financial effect.

The quantity is not the same as the value. Use documented cost information and have the responsible bookkeeper review the opening financial treatment. Do not use selling price as cost simply because it is the only number available. Keep uncertain cost information on a review list rather than inventing a precise margin.

Zemba has a dedicated opening-inventory workflow with an owner authorization check and a location-specific quantity. Its import path distinguishes creating a product from recording opening inventory. Use that distinction during implementation rather than treating any stock increase as interchangeable.

Import a small sample and inspect it. Check product codes, variants, prices, quantities, locations, and rejected rows. Compare the resulting product and quantity totals with the approved count. Resolve duplicate codes and unit mistakes before loading the remaining file.

Then follow one item through a test sale, its payment, the reduced stock quantity, a receipt, and the relevant owner view. If a return is part of the shop's routine, test that too. Check that a cashier sees the correct location and that an authorized reviewer can trace the movement. Use clearly separated practice data; remove or reverse it through the product's supported workflow before trading on the live opening position.

An opening count is the beginning of control. Record deliveries, sales, transfers, damage, and returns when they happen. Once the initial position is stable, count small groups of important or frequently moving items on a regular schedule instead of waiting for one disruptive annual count.

Give each difference a reason and reviewer. A pattern of wrong pack sizes requires a unit fix; a pattern of transfers missing at the receiving shop requires a handover fix. Repeatedly adjusting quantity without changing the underlying habit only resets the same problem.

Bring the cleaned product file, named locations, an approved opening count, a list of staff roles, and one person who can resolve setup questions. Choose the first products and cut-over together with the implementation lead.

The first milestone is simple: the owner, cashier, and reviewer agree on the starting stock, record real movements, and can explain the remaining quantity. Add more catalog depth and locations after that loop works.