Four shops, one plant, and a jacket nobody can place
You run three high street receiving shops and a plant on an industrial estate. Each afternoon a van collects bags from the shops and brings back finished work from the day before. At the plant, bags are opened, items sorted by process, cleaned, finished and bagged again for their home shop.
A customer at your second shop is told their jacket is not back yet. The shop thinks it went to the plant. The plant thinks it came back. The van driver cannot remember. The bag list, if there was one, was a handwritten count of items, not a list of tickets.
Two days later the jacket turns up at your third shop, hung under the right ticket number for the wrong branch.
The same thing happens in the other direction. A bag from one shop is opened at the plant and an item is missing from the count, but by then the van has gone, the shop has closed for the day, and nobody can say whether it was ever put in the bag.
Handover counts, not handover records
Transfers between shops and plant are usually counted, not recorded. A bag has twenty items, the plant counts twenty, and everyone is happy until one of those twenty is the wrong twenty.
- Ticket numbers are not unique across shops, so similar numbers collide.
- The van's manifest is a count of bags, not a list of items.
- The plant cannot see which items are due back at which shop when.
- Returns are bagged by shop by eye, and one bag looks like another.
- Shops have no view of the plant, so they phone to ask.
Lost items, phone calls and blame between sites
Items lost in transfer are hard to find because nobody knows which stage they reached. Shops and plant spend time ringing each other, and the relationship between shop staff and plant staff sours when each side thinks the other lost it. Customers at the shops are told vague answers, and promised dates slip without notice.
How we build transfer tracking between shops and plant
- Every ticket gets a shop code in its number or tag, so an item's home shop is never ambiguous.
- When a bag leaves a shop, staff scan the items into it and the system creates a manifest: bag number, shop, ticket and item list.
- At the plant, the bag is scanned in and items are checked against the manifest. Differences are flagged straight away, while the van is still there.
- As items are finished, they are scanned into outgoing bags for their home shop. The system warns if an item is put in the wrong shop's bag.
- At the shop, the returning bag is scanned in and items are matched to their tickets and slots.
- Each shop can look up any ticket and see its last scan: at the shop, in the van, at the plant, or back.
| Handover | What is recorded |
|---|---|
| Shop to van | Manifest per bag with ticket list |
| Van to plant | Scan in, checked against manifest |
| Plant processing | Optional scans by process stage |
| Plant to van | Outgoing bag per shop, wrong-shop warning |
| Van to shop | Scan in and slot assignment |
If your point of sale runs all your branches from one system, we connect to it. If each shop has its own till, we use the ticket data from each and the shop code keeps them apart.
Shops and plant working from the same picture
A shop assistant can answer a customer's question without phoning the plant. The plant manager sees which items are due back where, and what is running late. When a manifest does not match, the gap is caught at the dock rather than a week later at the counter.
Is this your business?
- You have more than one receiving shop feeding a plant.
- Transfers are counted, not listed.
- Items have ended up at the wrong shop.
- Shops ring the plant to ask about orders.
- Ticket numbers can repeat across branches.