• 0 Posts
  • 10 Comments
Joined 2 years ago
cake
Cake day: July 2nd, 2023

help-circle

  • Dude, you can make a barcode of anything with literally a Microsoft word font, and you can scan with a phone. They can keep the same item IDs for heaven’s sake - I work for a manufacturer, and we wanted to add barcodes literally just for our own internal inventory counting (no on site POSs, less structured warehouse given nature of work). Our internal item codes have letters and symbols in them, like 25WIDGET-01.

    I was able to tweak the label printing template to add an additional line of the same item code in barcode font with the right open and close symbols added (/25WIDGET-01/) and then when we do inventory, we use a really cheap app that let me put together a scanning form that lets the user scan the code, converts it back to the string, and then lets them input a quantity, and sends it back to a master excel document without needing to manually transcribe written inputs or risking employee typos or visually misidentifying the item as 26WIDGET-01 instead. We also no longer have to have one group of counters scour the entire disjointed warehouse looking for every single location one of “their” items might be and hope they found all of them while other groups chaotically do the same - your group is assigned to scan EVERYTHING in this section. If you find something without a label you report it. No more crazy margin math, no more “oops I didn’t think I’d find boxes of our hottest seller in the storage trailer”, no more 30 paper copies of a form.

    Our total organizational cost to use this system in 2 countries and half a dozen locations was about 12 man hours of my completely underpaid time and about $30 per location per inventory in app fees on existing company phones.

    We made no changes to our ERP. It reduced inventory time, recounts, and mistakes by ~50%. Employees LOVED not having to waste time trying to exactly copy longass random strings for our weirder items or the “gotcha” items. Our vendors don’t barcode for us either - we do it on receiving, because we already have to label the items with our internal code anyway.

    And we’re doing a TON of custom manufacturing - often items that literally may never be sold under that code again - with large volume orders, we’re not asking cashiers to manually enter everything for stocked items sold repeatedly at small volume. We’re literally ONLY using this for inventory and get no other benefits. Their excuses are such hot bullshit it’s crazy.

    Barcodes also literally have nothing to do with discounts - as above, they are literally just a way of storing a string visually. Not exaggerating to call them a font meant to be read by computers. If you are storing pricing in a computer anywhere, and not making cashiers enter THAT manually as well, then the only difference between barcodes and not is that with a barcode they scan the item code into the computer and without they manually type it?

    And if the only place they store pricing is on the item sticker, that is a system so fucking vulnerable to fraud both internal and external it’s CRAZY. For an organization of their size??? No way.








  • I literally work with ~750,000 line exports on the daily on my little Lenovo workbook. It gets a little cranky, especially if I have a few of those big ones open, but I have yet to witness my hard drive melting down over it. I’m not doing anything special, and I have the exact same business-economy tier setup 95% of our business uses. While I’m doing this, that little champion is also driving 4 large monitors because I’m actual scum like that. Still no hardware meltdowns after 3 years, but I’ll admit the cat likes how warm it gets.

    750k lines is just for the branch specific item preferences table for one of our smaller business streams, too - FORGET what our sales record tables would look like, let alone the whole database! And when we’re talking about the entirety of the social security database, which should contain at least one line each in a table somewhere for most of the hundreds of millions of people currently living in the US, PLUS any historical records for dead people??

    Your hard drive melting after 60k lines, plus the attitude that 60k lines is a lot for a major database, speaks to GLARING IT incompetence.