Laundry POS software that knows the order, not only the sale

A generic till does not know the jacket

A point of sale records that money moved. A laundry counter also has to know which garments or which bag the money belongs to, whether the work is still in processing, and whether the customer already paid part of it. Shops that keep a cash register on one side and paper tickets on the other lose the link. The ticket gets lost, the price on the ticket does not match the book, and the ready clothes sit on the rail while the till has already forgotten them. EaziTags is the store system for that counter. It is not a generic point of sale, and the product says so: it is for drop-off garment and laundry-lot work.

Calling it laundry POS software is fair only if “POS” means the front desk can take the order and the payment in one place. It does not mean a card terminal, a grocery scan, or a hotel charge to a room.

The sale is the order

The sequence is customer, order, garments or laundry lots, services and prices, tags, processing, payment, ready notification, then collection or delivery. Payment is a step in that sequence, not a separate product. Staff can take the full amount or a partial amount. The remaining balance stays on the order. A receipt or an invoice can be produced from that record.

There is no card gateway. If the shop takes cards, that charge happens outside EaziTags. What the software keeps is the amount recorded against the order, and the amount still unpaid. Reports list sales, payments, outstanding balances, and orders. That is the end-of-day question: what came in, what was collected, and what is still open.

Finding the sale again

A retail receipt is hard to connect to a garment three days later. EaziTags search is by customer, order, or tag. The tag is the QR on the piece or the lot. The person at the desk can start from the customer’s phone number or from the tag in their hand. The ready rail is the queue of orders waiting for collection, which is a different list from the list of balances still open. An order can be ready and unpaid, paid and not ready, or both settled. The unpaid-orders article is about keeping those states apart.

Prices come from services priced by piece, kilogram, pound, or bag. The price copied onto the order stays there. The till does not re-price yesterday’s jacket because today’s book changed.

Who touches the till

Front Desk is a role of its own, next to Owner, Manager, Processing, and Driver. Processing updates the work. The desk takes the order and the money. A driver sees the pickup and delivery job list rather than the whole catalog. More than one location can run under one owner, with each shop’s data kept separate.

Customer notices are part of the same order: email when it is created, email when it is ready, and a WhatsApp message the staff send with a tracking link. The customer never gets a login. They open a page. That is as much a part of the counter as the receipt, because the next visit starts with “is it ready?”

What this is not, and where to read the rest

EaziTags will not pretend to be every retail POS feature. No card gateway is included. It is not the system for industrial linen or hotel laundry. It is the browser on the counter PC, laptop, or tablet, for a staff of about 2 to 15 people at a location, one shop or a few locations under the same owner.

The feature page lists every capability in one place. Wash-and-fold and dry-cleaning pages split the order into the lot and the piece. Product engineering is the Core Bracket practice that builds a multi-tenant product this way, and EaziTags is the product that came out of that work.

At the end of the day the desk should be able to answer four questions from the same order: who the customer is, what was accepted, where that work sits, and how much money is still open. A laundry POS that cannot answer all four is still a cash register beside a notebook. EaziTags is built so those four answers are fields on the order, not a reconciliation someone types up after close. Search by tag is what makes the fourth answer possible when the customer is holding the ticket and not their name.