Project description
We keep a small warehouse and a shop counter, and the price tags are still written out by hand. A storekeeper copies an article number from the screen onto a blank sticker, the sticker ends up on the wrong box, and by the end of the week two different goods are wearing the same code. Stock figures stop matching the shelves, the cashier phones the storeroom to ask what the item actually is, and every stock count turns into a day of arguing over scraps of paper.
What I want is a printing module built into the inventory system we already use. I tick goods in a list, or I take a whole incoming delivery document, press one button, and the printer gives me exactly as many stickers as the lines call for, each with a barcode and the fields we care about. If a sticker smudges or the tape jams, I want to reprint that single one instead of running the batch again. And I want a plain button right inside the item card, so a storekeeper who never opens a report can still print a label.
Three conditions are agreed before any code is written. The barcode format is settled with us in advance and checked on a live scanner at the till before launch: a code the checkout cannot read is worse than a handwritten tag. The label template is tied to one printer model and one tape width, so if we replace the printer or the tape the template has to be rebuilt as separate work, and that should be stated out loud in the estimate. The print log keeps nothing extra about staff: the time, the user who printed, and what was in the batch, and nothing beyond that.
What I expect to receive:
— selection of goods by list, by filter, or by a whole delivery document;
— barcode generation in the agreed format with a duplicate check before printing;
— several label sizes as templates, with field positions we can rearrange ourselves;
— batch printing in one press, with the right quantity per line;
— reprint of a single spoiled label without repeating the batch;
— a print journal with time, user and batch contents, searchable by date;
— a print button inside the item card;
— a short written instruction for storekeepers and a handover run on our own equipment.
What I want is a printing module built into the inventory system we already use. I tick goods in a list, or I take a whole incoming delivery document, press one button, and the printer gives me exactly as many stickers as the lines call for, each with a barcode and the fields we care about. If a sticker smudges or the tape jams, I want to reprint that single one instead of running the batch again. And I want a plain button right inside the item card, so a storekeeper who never opens a report can still print a label.
Three conditions are agreed before any code is written. The barcode format is settled with us in advance and checked on a live scanner at the till before launch: a code the checkout cannot read is worse than a handwritten tag. The label template is tied to one printer model and one tape width, so if we replace the printer or the tape the template has to be rebuilt as separate work, and that should be stated out loud in the estimate. The print log keeps nothing extra about staff: the time, the user who printed, and what was in the batch, and nothing beyond that.
What I expect to receive:
— selection of goods by list, by filter, or by a whole delivery document;
— barcode generation in the agreed format with a duplicate check before printing;
— several label sizes as templates, with field positions we can rearrange ourselves;
— batch printing in one press, with the right quantity per line;
— reprint of a single spoiled label without repeating the batch;
— a print journal with time, user and batch contents, searchable by date;
— a print button inside the item card;
— a short written instruction for storekeepers and a handover run on our own equipment.
Web programming Cash, Bank transfer
