Skip to main content
GullySystem
Retail

Business solutions for Footwear stores

Explore software for work such as “School shoes and sandals”. Review each business function below, including when it fits and what to check before implementation.

Footwear stores

How the business operates.

A shoe is never one item. It is a style in several sizes, two widths and three colours, and each combination is a separate box on a shelf.

Style, size and width grid

Hold each style with its sizes, widths and colours, and see what is on the shelf, in the back room and on order from one screen at the bench. Counts stay per box.

Size-run receiving

Receive a carton against its packing list and check each box label against the shoe it holds, flagging every box that does not match before it reaches the shelf. Short cartons are noted.

Barcode billing at the bench

The box label is scanned, the pair is billed, and the customer pays by cash, card or wallet at the bench. The size sold is deducted from the right shelf.

Fit returns and exchanges

Record a return with its reason, such as narrow, loose or a sole fault, and send the pair back to stock, to a repairer or to the supplier. Reasons add up by style.

Branch transfers by size

Ask another outlet for a single pair, track it while it is in transit, and receive it into the shelf that needs it, so the customer’s wait is known at the bench.

Season orders and markdowns

Build supplier orders from last season’s size curve, then mark down slow styles and odd pairs when the season closes. Nothing is guessed.

Supplier price and cost lists

Each brand’s wholesale rate, margin and recommended retail price are held by style. Buyers compare them across seasons. A cost change updates the shelf price after the manager approves it.

Shoe care and accessory sales

Polish, insoles, laces and socks are billed with the pair at the counter. The branch manager sees add-on sales by salesperson. Low accessory stock is flagged beside the shoe stock.

Staff sales and incentive targets

Daily pairs sold and add-ons are recorded for each salesperson. Managers set each salesperson’s target for the season. Incentives are worked out from the billed figures and returns.

Warranty and repair claims

Sole separations and stitching faults reported by customers are logged with the invoice and style. Staff send the pair to the brand and record the reply. Customers see the claim status.

The records that hold the operation together.

  • Style, size and width grid. Each style is a grid. Sizes, widths and colours sit in rows. The pairs on the shelf, in the back room and on order are shown against every cell, so a gap is visible at a glance.
  • Brand and supplier master. One card per brand and distributor. Price lists, pack sizes, return terms and the styles bought from each are held together, so a buyer can compare how a stiletto line and a loafer line performed.
  • Size-run receiving. Cartons are received against the packing list. Each box is scanned, and mismatched labels, short boxes and pairs with a scuffed vamp are set aside for the supplier with a note.
  • Barcode and price labels. A label per box carries style code, size, colour and retail price, reprinted whenever a price changes so the swing tag and bench scanner agree. A stale ticket is easy to find.
  • Bench billing. Scan the box and the pair is billed. Payment by cash, card or wallet is taken at the bench, and the receipt prints with the exchange terms so the customer knows the rule before leaving.
  • Fit returns and exchanges. Every return has a reason. Narrow, loose, pronation complaint, rubbing at the instep or a sole fault is recorded, and the pair is routed to the shelf, a repair bench or the supplier.
  • Branch transfers. Ask for one pair. The sending outlet picks it, the transfer shows as in transit, and the pair is received into the shelf of the outlet that asked once the box is opened.
  • Odd pair and display pair register. Mismatched shoes, window displays and damaged boxes are held apart from sellable stock, with a list for season-end disposal ready, so a single left espadrille never inflates the count.

Operational bottlenecks to check

Missing sizes are found at the counter

The grid shows plenty of a style, yet sizes seven and eight are gone. The customer learns this while a fetch from the back room comes back empty. The sale walks out with the customer.

Boxes and shoes do not match

A label says size nine and the shoe inside is a nine and a half. Counts drift from the first week. Nobody notices until a stocktake.

Returns for fit are not coded

A pair comes back because it runs narrow. The reason goes unrecorded, so the reorder repeats the same width.

Stock sits in the wrong branch

One outlet holds the last pair of a style in a size that another outlet is asked for daily. Transfers happen by phone call and memory. Sales are lost.

Follow the work across teams.

This is a planning flow. Confirm the steps, owners and approval rules against your actual operation.

  1. 1. Ordering

    Ordering is built from the record. A supplier order is drawn up by style and size run, using last season’s sales by size as the starting point and the rejected widths as a warning.

  2. 2. Receiving

    A carton is opened against its packing list. Staff scan each box and compare the label with the shoe inside, and any mismatch, torn polybag or missing insole card is flagged before shelving.

  3. 3. Shelving and tagging

    Boxes get a barcode and a price. Then each goes to the shelf, the back room or the window display, with shoetrees and tissue paper left where the maker packed them.

  4. 4. Selling

    The cashier scans the box that was fetched. The pair is billed, and the size, width and colour sold come off that outlet’s count while the floor person who fetched it is credited.

  5. 5. Returns and transfers

    Returns carry a reason code. A pair goes back to the shelf, to a cobbler for a resole, or to the supplier, and pairs requested by another outlet are moved on a transfer note.

  6. 6. Season close

    Slow styles, odd pairs and broken size runs are listed together for markdown, and the final stock, including sandals and wellington boots, is carried forward to next season.

Roles and responsibility boundaries.

For owners

The shop in numbers. Pairs sold by style and size, stock held in each outlet, returns by reason and the markdown list for the season are read from one place on Monday morning.

On the shop floor

Check before fetching. A size is looked up across the shelf, the back room and other outlets before anyone climbs the ladder, and the screen shows what the customer tried last time.

At the cashier’s bench

One screen is enough. The cashier scans the box, bills the pair, takes payment and handles an exchange without opening a second window or walking to the manager’s desk.

For buyers

The curve decides. The buyer reads sales by size across seasons, with the widths that came back for fit marked, and the next supplier order is built from that, from nubuck boots to canvas plimsolls.

In the stock room

Receiving is the job. Staff open cartons, resolve label mismatches, move pairs between shelves and outlets, and keep odd pairs separate from the saleable rows, so the closing count matches the scanner.

Reports your managers need.

  • Pairs sold by style, size and width
  • Sizes out of stock in active styles
  • Fit returns by reason and style
  • Transfers requested, in transit and received
  • Odd pairs, display pairs and scuffed boxes
  • Sell-through by brand for the season
  • Slow styles and broken size runs for markdown

Connections to scope

  • Barcode scanner
  • Label printer
  • Card terminal
  • SMS
  • WhatsApp
  • Accounting export
  • Supplier price list import

Confirm data access, record ownership and the exchange method for each connection. Inclusion here does not mean every connection is available in a standard package.

Setup decisions and adoption risks.

Use these requirements to plan phases, data migration and user training. Agree the release sequence after reviewing your current systems.

Your size scales and widths

Half sizes, width fittings and children’s ranges are keyed exactly as each brand prints them on the box end, so a wide fitting never hides in a standard line.

Return terms

Your rules apply. Exchange periods, condition checks and reason codes follow the policy your store already tells customers, including how an outdoor-worn pair is treated.

Stock and price list loaded

Styles, sizes, barcodes and current counts arrive from your spreadsheet or billing export, and staff check them against the shelf, row by row, before the first sale is scanned.

Currency and tax settings

Shops selling across borders price shoes in the local currency, with the matching tax rate on every bill. Your accountant can test a few sample bills before the first sale.

Hosting and changes

We host it, so every outlet reads one shared stock count. Our staff also edit the brand and size lists for you whenever a new range arrives or a supplier changes its size scale.

Limitations to settle before implementation

  • A stall selling a few styles in a handful of sizes can manage on a counter register, with no size grid worth keeping and no second outlet to transfer from.
  • A footwear factory handling cutting, lasting and sole attachment will find a manufacturing system fits better than a retail one, because lasts and cutting dies are tooling, not stock.

Modules to consider first.

These functions connect to the operating model above. Confirm each one against the work your business actually runs.

Choose the operation you want to improve.

Use these activities to explain your scope. Your business does not need every function in the directory.

  • School shoes and sandals
  • Men's formal and casual shoes
  • Women's sandals, heels and flats
  • Sports shoes and sneakers
  • Floaters and monsoon footwear
  • Wedding and festive footwear
  • Kids' first shoes and growth sizes
  • Safety and work shoes
Talk to us

Start with the problem your team can describe.

Bring a sample record and show where information is copied, missed or waiting for approval. Scope the first useful change from there.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements