Retail chain software: ERP, POS extensions or a custom build

An ERP gives you one item master, one ledger and purchasing across every store. It is strong at the back office. It bends slowly. Changing a rule often means a vendor change request.

Point of sale extensions grow from the till outward. They handle billing, returns, loyalty and daily cash up well. Stock transfers and supplier ordering tend to be thinner, and the reports lean on what the till saw.

A custom build starts from your process. It costs more time up front and gives you exactly the screens you use. Store managers see only their own transfers and counts. It is worth it only where the first two cannot represent your stock.

Watch what happens when a shirt sells out in one store and sits unsold in another. The system should raise a transfer request, record dispatch from the sending store and receipt at the destination, and flag any gap in between.

Replenishment needs a rule per item and store, set by a buyer who knows the catchment: minimum cover, pack size, supplier lead time and seasonal pattern. A chain of fast moving stores wants this automatic. A chain of few, expensive items wants a buyer’s approval on every line.

Ask each vendor to demonstrate a transfer where one carton arrives short. Then ask them to show who is notified. Their answer shows how honest the stock record stays.

A price change must reach every till on the same morning, and each store must prove it did. Promotions add layers: buy two get one, a city only offer, a loyalty tier price and an end date.

Test the awkward cases first. Bring real bills. A promotion that starts at noon, a return of an item bought before the price drop and a bill that mixes two offers all expose weak rules.

If your promotions are mostly simple, an ERP or till add-on will cope. If marketing runs different offers by store cluster every week, ask for a rules screen that marketing can use without a developer.

Shrinkage is stock that vanishes between receipt and sale: theft, miscounts, breakage and wrong scans. Cycle counts, variance reports by store and exception alerts on voids give you the early signal.

A jewellery chain needs a different answer. Each piece carries a tag, a gross weight, a net weight, a stone weight and often a hallmark record. Stock is counted by weight and by piece, and an old gold exchange adds a second inflow.

Generic item masters hold a quantity and a price. They do not hold a tag history, so weight loss on a ring between two counts goes unseen. A custom build can store the tag as the unit.

List the ten situations that cause most of your arguments between stores and head office. Run each through the three options on paper. Mark where each option handles it fully, partly or not. Ask the store managers to check your list.

Most chains find that an ERP or till extension covers eight of the ten. Build only for the remaining two, and connect that module to the main system so nothing is entered twice.

Next step: take your last three stock disputes to each vendor and ask them to replay them on a demo. Bring the original count sheets, transfer notes and credit notes so the vendor works from facts.