Skip to main content
GullySystem
Retail · Software for footwear stores

Hold every shoe as a style, size, width and colour, down to the last pair in the box.

Footwear stores sell one style in a dozen sizes, and a missing size is a lost sale. The footwear product keeps stock by style, size, width and colour, covering the pairs on the shelf and in the back room, and fit-related returns. Supplier orders follow the size run that actually sold.

At a glance

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

Pairs are recorded as the shop assistant fetches them, by style, then size, then colour. Returns, transfers and supplier orders follow the same grid, so a gap in one size shows before a customer asks for it.

How the work runs today

Cartons arrive from a brand or a distributor as a size run, with a packing list that rarely matches what is inside. Staff open every carton, check each box label against the shoe, and place the pairs on the shelf or in the back room. Each box carries a barcode, a style code and a retail price.

The sales floor fetches sizes all day long, and a customer tries three pairs, buys one and leaves two behind on the bench for someone to carry back. Returns come back for fit, a loose sole or a wrong colour. Fetching never stops.

Orders for the next season go out months ahead, based on a size curve that the buyer keeps in a notebook. Slow styles are marked down at season end. Odd pairs, display pairs and boxes with the wrong shoe inside pile up in a corner.

Where it breaks

What goes wrong for footwear stores without a proper system.

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 leaves with her.

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.

What the software does

What we would build for footwear stores.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

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.

Before you talk to a supplier

A requirements checklist for footwear stores.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for footwear stores.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

Footwear Store Management Software

Style, size and width stock, bench billing, fit returns, branch transfers, odd pairs and season orders for footwear stores.

See the product
Solutions inside

The business modules footwear stores use most.

Each one is also available on its own, or inside a system built for you.

How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, accounting reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Common questions

Questions footwear stores ask before they call.

Can one style hold sizes, widths and colours at once?

Yes. A style carries every size, width and colour as its own line with its own barcode. Counts are kept per line, so a shortage in size eight shows before a customer asks for it.

What happens to an odd pair or a display pair?

Each is held as a separate line, flagged as odd or display, and kept out of the sellable count until a person moves it back. Both appear on the markdown list at season end.

Do we need it for a single small shoe shop?

Maybe not. A shop with a few styles can manage on a counter register. The grid starts to matter when several sizes run short across weeks, and the owner can judge that from the shelf.

Can we load our current price list and stock?

Yes, from a spreadsheet or your billing export. The owner or manager checks the imported styles and sizes against the shelf before billing starts on the new system. A short list of exceptions is expected.

What happens after I share my requirements?

An engineer reads what you send and replies within one business day. We then look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough. You get a short written summary ordered by priority, with no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. That first review settles the scope, and the cost goes into a written proposal before any work starts.

Category

Part of a wider group.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

  • No obligation
  • A reply within one business day
  • Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements