Skip to main content
GullySystem
Retail

Barcodes and Labels for Footwear stores

Connect scannable labels with the correct items and variants.

Retail and POS

Does this function belong in your operation?

Use when physical items benefit from scanning or printed identification.

An item needs identification at receipt, counting or sale.

Each box is labelled with style, size, colour and price. The counter scans the box at billing. Reprinted labels follow a mark-down so the shelf shows the new price.

Bring the records the workflow depends on.

  • Item and variant codes
  • Barcode formats
  • Printer and scanner requirements

Outputs to check

  • Item-code and label definition
  • Printed-label batch record
  • Scan-validation exception list

Follow the barcodes and labels workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Select the item

    Confirm the item or variant that the code identifies.

  2. 2. Assign the code

    Check format and prevent ambiguous active mappings.

  3. 3. Prepare the label

    Set the approved printed fields and layout.

  4. 4. Print and verify

    Test readability on the agreed printer and scanner.

  5. 5. Use in transactions

    Confirm scanning selects the correct record before relying on it for billing or counts.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Store assistant

Receives stock, prints labels, and sticks them before the goods reach the shelf.

Counter staff

Scans the label, checks the selected variant and reports an unreadable or incorrect code.

Owner

Reviews scan exceptions and count differences before approving changes to item identification.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Code maps to two variants

Stop use of the ambiguous code and resolve the item mapping.

Label unreadable

Reprint from the approved definition and verify the agreed scanner can read it.

Price changes after printing

Use the documented relabelling or checkout rule so the printed and transaction prices are reviewed.

Can this work independently?

Labels need an item or asset identifier and compatible printing and scanning arrangements. Billing, receipt and counting systems use the scanned value to select a record. Printing a code does not create a stock movement, establish authenticity or satisfy every product-labelling requirement.

Systems and records it connects with

  • Product management: Item identifiers, units and controlled variant definitions.
  • Point of sale billing: Counter sales, tender records and authorised returns.
  • Stock tracking and alerts: Item-location quantities and authorised stock movements.
  • Label and thermal printers: Agreed label formats and hardware-tested print output.

Configure, test and introduce the workflow.

  • We look at items, current labels and your printer. You supply a stock list. You get back a note on which codes exist and which are missing.
  • Codes are agreed on paper. You approve how item and variant codes are built before any printing. A sample label is cut to size. A few stickers come back to hold against real stock.
  • Counter staff scan a small batch at billing and at a rack count. Slow scans get noted. So do wrong codes. Remaining items are labelled in groups while the unlabelled list shrinks on screen. Training at each counter closes the work.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Codes retrieve the correct variant.
  • Duplicate active codes are detected.
  • Printed labels are readable on the agreed hardware.
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.

See the full industry workflow, reports and implementation plan →

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.

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.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  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.

Industry reports to connect with

  • 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

Questions before implementation.

When should footwear stores consider barcodes and labels?

Use when physical items benefit from scanning or printed identification. An item needs identification at receipt, counting or sale.

What should we bring to the requirements discussion?

Bring anonymised examples of Item and variant codes; Barcode formats; Printer and scanner requirements. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Connect scannable labels with the correct items and variants. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Industry numbering standards and mandatory product-label requirements need separate confirmation.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Codes retrieve the correct variant. Use this check when reviewing the first working version.

Talk to us

Discuss barcodes and labels for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

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