Retail POS Guide: Barcodes, Returns, Stock and Shift Close

Build a useful demonstration basket

Bring an existing barcode, an item with size or colour variants, a multipack, a promotional item and any product requiring a different tax treatment. Have the owner approve the catalogue and tax setup. Confirm how the proposed software represents units and packs so a sale reduces the correct stock quantity.

Demonstrate a scan failure, item lookup, permitted price override and manager approval. Check the customer-facing total and receipt. If the store has several locations, identify whether prices, stock and user permissions are shared or location-specific.

Test returns rather than assuming them

1. Complete a sample basket using the provider’s test process.
2. Return one item with its receipt and inspect the payment and stock changes.
3. Demonstrate an exchange with a different balance.
4. Show the store’s approved procedure for a return without a receipt.
5. Confirm who may approve a refund or override and where it appears in the audit trail.

Define how damaged or unsellable returns affect inventory. A refund does not always mean the item should return to available stock.

Confirm the complete hardware configuration

List the exact register, payment device, scanner, cash drawer, printer and network connection for each lane. Confirm compatibility for every model and connector. If you sell weighted products, specialised tenders or regulated items, require a specific demonstration rather than relying on a general retail feature list.

Use the store checkout checklist for a fuller operating review and the Clover^® comparison when evaluating that platform. Hardware ownership and the selected software plan belong in the written proposal.

Reconcile the shift and protect historical records

Compare cash, card, refunds, voids and discounts with employee activity. Then reconcile processor batches with deposits, allowing for fees and timing differences. Decide who handles a cash variance, missing deposit or inventory discrepancy; these may require different support providers.

Before changing systems, export the catalogue, prices, stock and required history. Document how gift cards, store credits and old receipts will be honoured. Test imports, permissions and first settlement before cancelling the previous service. Compare processing and POS costs separately, including subscriptions, paid apps and equipment obligations.

Choose the catalogue structure before importing products

Identify the unit the store actually sells. A product may have size or colour variants, a pack size and a separate supplier identifier. Similar display names should not force cashiers to guess which stock record belongs to the item in front of them.

Decide which system owns the SKU, barcode, description, price and available quantity. If several applications can edit the same fields, establish the direction of updates and an owner for resolving conflicts. A successful first import does not establish how later changes will stay consistent.

Clean a representative sample before loading the whole catalogue. Resolve duplicate items, inconsistent units and missing identifiers, then test scanning, receiving and returning those products. Confirm whether any required variant, bundle or pack relationship needs a particular plan or application in the proposal.

Make receiving as testable as selling

A stock system is only useful when deliveries and corrections are recorded accurately. Demonstrate receiving a normal shipment and a shipment with a shortage, extra item or damaged product. Inspect the quantity available for sale after each action.

Decide who may create a new item, change a cost or price, approve a discrepancy and adjust a stock count. Staff need a documented correction route rather than creating a second product whenever a barcode is wrong. Keep a clear owner for the catalogue.

If purchasing, supplier management or specialised tracking is important, list those requirements separately. A general quantity-on-hand feature is not proof that the software supports every purchasing or stock-control task. Require a demonstration of the exact record and report the store needs.

Design promotions without confusing the cashier

List the offers you actually run: a product markdown, a bundle, a quantity offer or a permitted customer discount. Ask the vendor to demonstrate each and explain how overlapping promotions behave. An employee should not have to invent a manual price adjustment to reproduce an advertised offer.

Check the receipt, tax configuration and return result for the discounted basket. Have the owner approve the rules and involve the appropriate adviser where tax treatment needs review. The POS should implement the approved configuration consistently, not determine the store’s policy by default.

Restrict overrides and exceptional discounts to the intended roles. Inspect the audit trail and the report used to review them. The aim is a clear operating process, not a report that produces unexplained numbers after a busy shift.

Give gift cards, credits and exchanges their own tests

Gift cards and store credits create balances the business needs to honour. Demonstrate issue, partial redemption, remaining balance and the treatment of a return. Confirm whether the proposed functions are native, application-based or dependent on a separate provider arrangement.

For an exchange, show both a higher and lower replacement price. Inspect the payment difference, inventory movement and customer receipt. A stock transfer and a payment refund are separate actions unless the actual integration handles them together.

Before migration, export outstanding gift-card and store-credit records and agree how they will be used after the change. Do not assume the new POS can import every historical balance. Retain the required previous reports and test sample liabilities before the old service is retired.

Keep online and in-store inventory from competing

If the store sells online, identify which platform publishes product information and which controls available stock. Document the fields that synchronise, the direction of updates and any delay. A payment gateway connection does not automatically provide catalogue or inventory integration.

Test the last unit being purchased online while a cashier sells the same product. Observe stock reservation, order status and the exception process if both orders cannot be fulfilled. Decide who contacts the customer, approves a refund and corrects the stock record.

Include a partial shipment, pickup cancellation and damaged return in the test. Use the ecommerce workflow guide to review checkout, fulfilment, refunds and settlement. Assign support ownership for the connector so a failed update does not become an unresolved argument between the web and POS vendors.

Separate cashier tasks from management access

Define what a cashier, supervisor and owner may do. Normal sales, price changes, refunds, exports and account administration do not necessarily require the same access. Use individual accounts where supported and test the permissions with the actual roles.

At shift change, confirm how the drawer is assigned, counted and handed over. Decide who approves a variance and how the explanation is recorded. Shared drawers may need a different review process from individually assigned tills; establish that operating decision before relying on employee reports.

Prepare the access-change process for a new employee, a lost device or a departing staff member. The owner should know how access is removed and which records remain available for review. A convenient shared administrator login can undermine an otherwise well-designed checkout.

Plan for the payment that does not complete cleanly

Test a decline, interrupted connection and uncertain result using the provider’s supported methods. Teach staff to check transaction status before retrying. A frozen screen, absent receipt or interrupted notification does not by itself prove the first attempt failed.

Record the device, time, amount and transaction reference without copying card details. Give staff the support route for a device problem, payment-status question and software fault. Agree who updates the customer and who approves the next step.

Confirm a practical fallback and its conditions before opening the new lane. Do not assume offline acceptance is included or that a personal device can substitute for the approved setup. Include power, network, device replacement and receipt handling in the continuity plan.

Compare the economics of the whole store configuration

Gather card volume, transaction count, average ticket, refunds and sales-channel mix for the same period. Keep cash sales separate when calculating an effective card-processing rate. Use those assumptions consistently across proposals.

Then add POS subscriptions, paid apps, ecommerce connectors, equipment, accessories, setup, catalogue work and training. Ask whether each charge is per device, location or account. Review ownership, cancellation and replacement terms alongside the advertised price.

A hypothetical extra ten cents per transaction adds $400 at 4,000 transactions, before any percentage or fixed charges. That illustration is not a Process Rite rate. It shows why a smaller-ticket retailer should compare the complete pricing model rather than a single percentage. Use the pricing framework to organise the actual written offers.

Use closeout reports to explain differences

Compare sales, refunds, voids, discounts and tenders for a defined shift. Inspect which employee performed the relevant action and how corrections are recorded. A useful report should help the manager understand the difference rather than encourage an unexplained adjustment to the total.

Reconcile card transactions to the provider’s batches or payouts, then match the net amounts to bank deposits. Keep timing, fees, refunds and adjustments visible. Gross sales and net deposits will not necessarily match on the same calendar day.

Assign each unmatched item an owner and next action. A missing catalogue update, stock discrepancy and missing deposit are different problems. Support is more effective when the store can supply a clear reference and expected result without sending unnecessary customer or card information.

Approve a migration plan before replacing the register

Export products, prices, stock and the history the business needs. Agree the opening-stock method and verify sample items after import. Include tax categories, users, permissions and receipt configuration in the sign-off rather than treating the catalogue file as the entire setup.

Document how old receipts, deposits, gift cards, store credits and unresolved refunds will be handled. Review the previous service’s cancellation and equipment obligations. The new provider may not be able to access the old transaction history.

Train staff on returns, price errors, uncertain payments and shift close, then test a realistic busy period. Review the first completed shift and settlement before retiring the previous arrangement. Clover’s retail overview and inventory documentation are product references; the exact devices, plan, applications and implementation still need to be specified for your store.

Score the demonstration with a receiving-to-return exercise

Use one illustrative product through its full stock life rather than demonstrating unrelated screens. Receive a pack, sell the approved unit or pack quantity, apply a permitted promotion and return one damaged item. Ask the employee to inspect the remaining available stock after each action.

Then introduce a barcode error. The manager should correct the intended record without creating a second product that divides the sales and stock history. Check whether the fix reaches every required device and, where relevant, the website. Document any synchronisation delay and the operating response.

At the end, compare the physical scenario with the stock report, sales report and payment record. The available quantity should reflect what can actually be sold. The refund should appear in the payment report, and the damaged item should follow the store’s approved disposition rather than silently returning to saleable stock.

Give competing vendors the same exercise. Record whether each action is included, requires another application or remains manual. Ask the vendor to identify the exact software plan and configuration used so a demonstration feature does not disappear from the eventual quote.

Finally, have a cashier and supervisor perform the scenario under their own proposed permissions. A technically capable catalogue can still be unsuitable if routine staff cannot complete the work or if every correction requires unrestricted administrator access. Use those results to define training, support and the unresolved acceptance criteria.