Multi-Outlet Stock for Footwear stores
Keep outlet stock separate while supporting controlled transfers.
Does this function belong in your operation?
Use when physical stock is held across several selling outlets.
Goods move between outlets or staff need another outlet's availability.
A missing size 8 at one branch is found at another and sent by transfer. Branch managers see pairs by size across stores. Transfers are signed in at receipt.
Bring the records the workflow depends on.
- Outlet and item list
- Stock by location
- Transfer approval rules
Outputs to check
- Outlet availability view
- Transfer dispatch and receipt record
- Combined stock reconciliation
Follow the multi-outlet stock workflow.
Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.
Who uses the module, and who approves?
Keep responsibilities distinct even when one person holds more than one role.
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.
Can this work independently?
This requires item identifiers and balances for each outlet. A standalone transfer register can coordinate moves, but actual stock records must acknowledge both dispatch and receipt. POS and warehouse links update movements; viewing another outlet's stock does not reserve it.
Systems and records it connects with
- Stock tracking and alerts: Item-location quantities and authorised stock movements.
- Point of sale billing: Counter sales, tender records and authorised returns.
- Warehouse management: Storage locations, picking instructions and count results.
- Transport documents: Consignment details and authorised movement-document references.
Configure, test and introduce the workflow.
- We list your shops, stores and who runs them. You provide current stock and rate lists. A diagram of how stock should move comes back.
- Balances are loaded outlet by outlet. A manager signs off on each list. Request, dispatch and receipt are tried between a pair of shops. Notes from staff reshape the screens.
- Local rates and offers are entered where they differ. You review them against shelf prices. Remaining shops join in turn. Owners see combined and separate figures together.
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.
- Transfers debit and credit the correct outlets.
- Unreceived goods remain in transit.
- Outlet totals reconcile with the combined stock view.
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.
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. 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. 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. 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. 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. 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. 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 multi-outlet stock?
Use when physical stock is held across several selling outlets. Goods move between outlets or staff need another outlet's availability.
What should we bring to the requirements discussion?
Bring anonymised examples of Outlet and item list; Stock by location; Transfer approval 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. Keep outlet stock separate while supporting controlled transfers. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.
What is outside this module?
Recorded stock is not a reservation or promise of availability without the relevant workflow.
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. Transfers debit and credit the correct outlets. Use this check when reviewing the first working version.
Related functions for footwear stores.
Discuss multi-outlet stock 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
- We review your brief and the systems you already use.
- We clarify the workflow, missing information and the work to consider first.
- The proposed scope sets out the deliverables, responsibilities and dependencies.
- 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