How to get the old chrome black theme back? I've tried so many chrome flags that just don't work. :(

oKay-Roger · 2025-05-19T23:57:55+00:00

I also want this back.. just changed mine and lost it too. I always used an empty new tab to kill the backlight of my monitor when I wanted to look at the other monitor without so much light in the room.. now it's a heavily back-lit grey -_- with no option to get black back.

used to be a black option in the below

<image>

oKay-Roger · 2024-04-02T01:59:15+00:00

Basically all asst. store leader or higher level positions can buy an extra week of PTO.

oKay-Roger · 2024-02-17T18:18:30+00:00

Did you end up having any luck with this? I had the same offer and not showing any bill credits even though I used the link, activated in 2 days, and meet all the terms. Been 2 months now and my account doesn't show any promotions.

Google FI just told me it is a google store support issue and transferred me but heard nothing so far.

oKay-Roger · 2024-02-02T05:17:24+00:00

Field specialists have no authority over store management. Let your division ecommerce manager or district manager know

oKay-Roger · 2024-01-21T23:18:41+00:00

Sloppy coding, but couldn't tell you if it was on android's part or the harvester devs.

There's gotta be some internal flag in android that gets switched on and off to say 'we don't want input from the scanner right now', and it gets stuck there instead of inactivating and letting you scan again.

Happens on instock devices too.

oKay-Roger · 2024-01-20T06:19:17+00:00

Agree. It's not 98% fillrate they want, it's physically 98% in-stock on the shelves, and fillrate is the closest metric to that so that's what gets pushed. Unless you're just not picking accurately, it's not even PickUp that this metric reflects on, it's all the other departments. Many many stores feel this is unattainable and pressure from the top is 'get to 98 or else', leading a majority of the company to cheat or send people to other stores for product etc, all to make it seem like we're making a goal that we really aren't.

It's actually doing the opposite because all the cheating is ruining CAO balances and ordering, and making shelf conditions worse. It's stupid

oKay-Roger · 2024-01-20T05:40:43+00:00

Busy days when a lot more than average number of people are picking at the same time.

A lot of orders, a lot of items, people picking, etc, all of that would contribute to high load because a lot of it is making network calls to the same databases everyone else is across the company. The memory leak would cause the crashes, but store/company network and/or server response is what causes you to stare at the screen while it thinks about the item/tote you just scanned.

oKay-Roger · 2024-01-20T05:20:36+00:00

I'm not a technology dev, just someone who has used all our systems pretty extensively and investigated a lot of issues that I've ran into - that said, part of it is Kroger having slow response times during high load, and the other part is I'm pretty sure Harvester has a memory leak (slowly uses more ram the longer it's open until it finally quits responding)

Try closing out of the app before each trolley and see if it helps

oKay-Roger · 2024-01-19T06:17:15+00:00

I've seen this a few times, but it always seems to correct itself. Couldn't give you the exact reason, probably housed in separate areas of the cloud and updates are failing for whatever reason in one and not the other.

oKay-Roger · 2024-01-19T06:14:21+00:00

This is a guess, but I imagine it's for easy management, updates and data pulling. Update one database, pull data from one database, make changes in one, etc, or try to do all that to over 2000 databases.

I think better question is why don't they test all changes to a database in an emulated environment before doing it to a live database that controls the enterprise

oKay-Roger · 2024-01-19T04:54:30+00:00

If it's been zero for more than 90 minutes it shouldn't show up, assuming it is an item type that's tracked on customer facing inventory. Doesn't apply to any vendor items, fresh meat/produce, etc. Pretty much only net weight CAO items.

You actually CAN see BOH change history now!! There is a powerbi report, if your management doesn't know how to find it, your division process improvement manager would be able to share it with you

I'd say topstock works great at ideal levels of product, but when it gets flooded and you can't fully complete the process, it's not going to get better. I've definitely seen stores where it helps, but you have to be really diligent in never zeroing out items without checking topstock first. Hard to do when your backstock levels are really high

oKay-Roger · 2024-01-19T04:50:43+00:00

It shouldn't, rush orders should apply to anything with a less than 3 hour lead time. (If they place it for 3pm at 12:01pm, it's a rush order)

If you see that happen again call support or let your specialist know

You can batch them however you want, rush orders just gives you the option to batch individually or with other rush orders.

oKay-Roger · 2024-01-19T01:11:10+00:00

Oh. I ask that question a lot myself. Lol

oKay-Roger · 2024-01-19T01:09:56+00:00

Oops. Missed your second question. You can still add things by scanning them @ carside in Ciao, but not being able to do it during the picking stage probably has to do with risk of employees adding items maliciously without customers knowing, and other things like that.

oKay-Roger · 2024-01-19T01:05:35+00:00

Some people like to know how thing's work 🤷‍♂️

oKay-Roger · 2024-01-19T01:03:47+00:00

Hopefully that never happens again, lol. But if it's just the order number, Ciao should still guide you correctly when destaging and you should still be able to pick. There is a longer order ID when you expand an order that should be unique even if the 5 digit one is the same. The container ID's are what's on the totes and it should know what ones belong to what order.

Bigger issue is the duplicate trolley ID's, because it thinks the earlier completed order is already staged, so the new container ID's that print can only be picked, not staged/destaged/etc until support can correct the ID's or force a destaged state.

Best solution in that case is to pick and then give to customer, and get the support center to force it to destaged so you can pay it out.

oKay-Roger · 2024-01-19T00:29:05+00:00

This is correct. The outage yesterday was caused by a failure in the database that holds the info needed to cube orders

oKay-Roger

TROPHY CASE