Skip to main content
GullySystem
Retail

Sales Returns and Credit Notes for Footwear stores

Record customer returns and link their financial and stock effects.

Sales and Distribution

Does this function belong in your operation?

Use when supplied goods or billed amounts can require returns or credit adjustments.

A customer requests a return or credit.

A customer returns a pair that does not fit or has a fault. Staff record the reason and the size. The pair goes back on the shelf or to the claim list.

Bring the records the workflow depends on.

  • Original invoice
  • Returned quantities and reasons
  • Acceptance and stock-disposition rules

Outputs to check

  • Authorised return and inspection record
  • Stock-disposition statement
  • Credit or refund handoff

Follow the sales returns and credit notes workflow.

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

  1. 1. Register the request

    Identify the original sale, quantity and stated reason.

  2. 2. Authorise the return

    Apply the approved commercial and eligibility rules.

  3. 3. Receive and inspect

    Count returned goods and record their condition.

  4. 4. Decide disposition

    Separate saleable stock, repair, rejection and other approved outcomes.

  5. 5. Issue the adjustment

    Pass accepted quantities to credit or refund processing and reconcile the original balance.

Who uses the module, and who approves?

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

Counter staff

Finds the original sale, records the return reason and follows the authorised acceptance process.

Storekeeper

Counts what came back and says plainly what is fit to sell again.

Accounts assistant

Raises the credit note and sets it against the bill, so the ledger and the warehouse tell the same story.

Owner

Approves returns above a value, and reads the monthly reasons.

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.

Return exceeds sold quantity

Hold the excess for investigation before stock or credit posting.

Goods damaged on return

Record condition and approved disposition separately from saleable stock.

Invoice already settled

Route the approved credit to an account balance or refund process without duplicating payment.

Can this work independently?

Returns need the original sale or an approved exception reference. Inventory records accepted quantities and condition; accounting issues credits and manages refunds. A return request does not prove goods arrived, and receiving goods does not automatically authorise a full financial refund.

Systems and records it connects with

  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Stock: Item-location quantities and authorised stock movements.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Quality control: Inspection results and authorised hold or release decisions.

Configure, test and introduce the workflow.

  • We trace a return from gate to ledger. You show recent cases, and a written flow is sent back.
  • Reasons and time limits are agreed. You approve the list used in the screens. The note is matched to your invoice series and tax details. Accounts proof a sample.
  • Saleable and damaged bins are set up. The storekeeper tries both paths. Returns start here on an agreed day. The owner receives a monthly count.

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.

  • Credits do not exceed authorised returns.
  • Damaged stock is distinguished from saleable stock.
  • Balances reconcile with the original invoice.
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 sales returns and credit notes?

Use when supplied goods or billed amounts can require returns or credit adjustments. A customer requests a return or credit.

What should we bring to the requirements discussion?

Bring anonymised examples of Original invoice; Returned quantities and reasons; Acceptance and stock-disposition rules. 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. Record customer returns and link their financial and stock effects. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Consumer obligations, tax treatment and refund policy require your adviser-approved rules.

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. Credits do not exceed authorised returns. Use this check when reviewing the first working version.

Talk to us

Discuss sales returns and credit notes 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