3 ms·
> - would waiting to print the receipt at the end cause a big slowdown vs printing as you ring items up? (I believe with most current systems, items can be adde
by RussianCow 7y ago
> - would waiting to print the receipt at the end cause a big slowdown vs printing as you ring items up? (I believe with most current systems, items can be added and removed, and they show up as 'add' and 'remove' line items, because it does print as you scan.)
Most (all?) stores I go to print the receipt at the end of checkout, and it takes maybe 3 seconds at most, so I don't think that's an issue.
I would also be concerned that the longer receipt length means that people will be less likely to actually read it. (I know I personally tend to gloss over really long/verbose receipts, but I take the time to look at ones that are more densely packed. Maybe that's just me though.)
- teej 7y agoIt takes 3 seconds to print because it doesn’t include any complex rendering (like a dynamic bubble chart) or need full state to determine how to print it. This design challenges a lot of assumptions that the current generation of receipt printers use.
- delinka 7y agoThat's the computer's problem, not the printer's. If rendering time really becomes an issue, it can start the rendering process while the humans are twiddling about with card reader terminals and making small talk.
- rtkwe 7y agoThe rendering itself isn't that large of a task and it'd all be done on the POS which has more than enough power to draw a couple circles. There's very little processing done on a thermal printer basically it's just decoding and drawing exactly what the source system tells it to. At most I'd expect it to add a second or two for the POS to do the calculations and send it to the printer.
- rubatuga 7y agoThe print time is proportional to the number of lines with pixels
- rtkwe 7y agoWatching the fast thermal printers in stores it's fluid enough it might just be directly related to length.