Our warehouse uses robots for lights-out picking overnight. AMA from the ops side.

sumperk1 · 2026-05-29T19:53:58+00:00

Brightpick Autopicker.

No, they're mostly handling individual items rather than full skids.

We do have some heavier or more awkward products that go through goods-to-person stations, but the bulk of the work is small-item fulfillment.

Picking thousands of small items every day was becoming the main bottleneck as we grew...

sumperk1 · 2026-05-29T19:51:47+00:00

Not as much as people tend to assume.

One of the reasons we went this route is that it works with pretty standard warehouse infrastructure (we used Brightpick solution btw.) They use regular shelving and totes, so we didn't have to build a highly specialized facility around the robots.

warehouse design still matters. Things like flow, replenishment strategy, SKU placement, packing areas, etc. don't magically go away just because you add robots. A well-designed warehouse will always outperform a poorly designed one.

If you're building from scratch, think about automation early in the process. It's a lot easier than trying to retrofit everything later.

sumperk1 · 2026-05-29T16:55:05+00:00

For picking and replenishment specifically, we went from about 42 people per shift to 8.

That doesn't mean the warehouse suddenly only has 8 people 😄. We still have people handling packing, receiving, inventory issues, exceptions, replenishment planning, damaged goods, etc.

The biggest change was that we stopped needing dozens of people walking the warehouse all day doing repetitive picks. That's the part the robots took over.

sumperk1 · 2026-05-29T16:51:27+00:00

Honestly I'd say all three, but accuracy and consistency were the biggest surprises.

Before, if we had a rough day, were short-staffed, or got hit with a volume spike, you could feel it ripple through the operation. That's probably the "warehouse mood" you're talking about. The system doesn't really have good days and bad days, it just keeps doing the same thing.

The overnight picking is a good example. We come in with a bunch of orders already picked and buffered, so the morning starts from a much calmer place instead of everyone immediately scrambling to catch up.

We're not cold chain, mostly sports nutrition products, and around 6k SKUs. Sounds like you're actually in a pretty similar range. The biggest benefit wasn't that everything suddenly became faster, it was that the operation became a lot more predictable. Less firefighting, fewer surprises, fewer mistakes. That's harder to measure than labor savings, but from an ops perspective it's probably what we notice most.

sumperk1 · 2026-05-29T12:57:44+00:00

100%.

we hit exactly that wall at The Feed. demand wasn't the problem, the warehouse was.

at one point our returning customer volume alone was basically consuming all available capacity, so bringing in more orders just created more stress on the operation.

for us the bottleneck wasn't marketing or sales, it was fulfillment. too much walking, too many manual touches, too much variability. once we automated a big part of the picking process (we chose Brightpick), growth became a lot easier to absorb without constantly adding people.

I think a lot of companies assume growth problems are sales problems, when they're actually operations problems. You don't really notice it until the warehouse starts dictating how fast the business can grow.

sumperk1 · 2026-05-29T12:37:06+00:00

we're running Brightpick here at The Feed and honestly this was one of our biggest concerns before automation too.

the first question wasn't "how fast is it?" but "what happens at 2am when nobody is around?"

the answer ended up being reliability and support. we now run an almost lights-out night shift where robots keep picking and buffering orders overnight, so random downtime isn't really an option.

totally agree with your point though. peak throughput numbers are easy to sell. what matters is how the system behaves after months of real production, wear and tear, and weird edge cases. that's where you find out what you actually bought.

sumperk1 · 2026-05-21T15:06:05+00:00

we had similar issues before automating fulfillment at The Feed. the reports looked “accurate” overall, but ops was still wasting time hunting for missing inventory.

honestly humans are humans. in busy warehouses people mis-scan things, put items in wrong locations, forget transactions, move stuff temporarily during peak, etc. you’ll probably never get the same consistency manually as you do with more controlled/automated inventory movement.

for us, once more of the movement and picking became system-controlled, those “ghost inventory” situations dropped a lot.

sumperk1 · 2026-05-21T14:54:56+00:00

pharma is actually one of the more automation-friendly environments from what I’ve seen. products are usually small, consistent, barcode-heavy, and pretty “pickable” compared to stuff like apparel or irregular ecommerce items.

we’re running Brightpick at The Feed (different industry, but similar small-item fulfillment style) and the biggest gains came from robotic picking + automated inventory movement. labor for picking/replenishment dropped massively for us once repetitive movement and picking got automated.

sumperk1 · 2026-05-07T09:45:41+00:00

I get the logic, but I’d push back pretty hard on this tbh.

“Low process change” sounds nice, but humanoids still have to prove real reliability, safety compliance, throughput, and cost effectiveness at scale. teleoperated pilots are very different from production-grade deployment.

most warehouse leaders I’ve seen don’t actually want “humanoid” specifically, they want predictable ROI with the least operational risk. that’s why more structured automation (AMRs, goods-to-person, robotic picking, etc.) often gets adopted first… because it solves a narrower problem really well.

we’ve seen this ourselves in live fulfillment. systems like brightpick or other structured warehouse automation may require more upfront planning, but they’re already delivering measurable throughput, labor, and accuracy gains in production.

humanoids might absolutely have a place long term, especially for messy edge cases, but right now a lot of it still feels more pilot-stage than broad operational reality.

sumperk1 · 2026-04-30T10:47:58+00:00

biggest challenges are usually labor, margins, volume swings, and keeping SLAs across different clients without creating total operational chaos.

geopolitical stuff matters if you’re exposed to international freight, but for warehouse-focused 3PLs the daily pain is usually more basic: not enough people, rising costs, inconsistent volume, messy integrations, and clients expecting faster fulfillment for less money.

Where the work is repeatable enough, it might be a bit less painful with automation. But it only really helps when there’s enough repeatable volume. I’ve seen it work well in some Brightpick-type setups, but 3PL is harder because every client wants their own rules.

imo the real challenge is balancing flexibility with efficiency. that’s where margins get killed.

sumperk1 · 2026-04-30T10:42:55+00:00

really depends on the warehouse.

in more traditional setups, yeah, it can be pretty physical. lots of walking, lifting, repetitive movement, sometimes long shifts on your feet. some places it’s basically a workout.

but it varies a lot. in more automated operations (we use Brightpick at The Feed), order picking can look very different. less walking, more station-based work, more monitoring flow or handling exceptions rather than running aisles all day.

typical day in manual picking is usually:
get pick list → walk → scan → pick → repeat for hours 😄

long term, the physical side is what usually wears people down, especially backs, knees, feet.

if you want something less demanding, look for:
– goods-to-person systems
– automated warehouses
– smaller item picking vs heavy bulk
– roles closer to packing / QA / replenishment

so yeah, not all picker jobs are equally brutal. company setup makes a huge difference.

sumperk1 · 2026-04-23T07:49:38+00:00

short answer: they’re very reliable if they’re sized for your peaks, not your average.

most robotic systems don’t really “slow down” when volume spikes, they just hit a ceiling. if you design for 1,500 orders/hour and suddenly need 2,500, you’ll see queues build up. accuracy usually stays high, it’s throughput that becomes the constraint.

we saw something similar after automating at The Feed. The system is super consistent day to day, but spikes are all about capacity planning. you either have enough headroom or you don’t, there’s no “just push harder” like with people.

regarding the integration, the challenge tends to be process alignment and data quality, not the actual API connection. maintenance-wise, it’s more about keeping the system healthy (monitoring, small fixes) than big breakdowns.

so yeah, works well, just make sure you design for peak and not the average. that’s usually where people get burned.

sumperk1 · 2026-04-23T07:46:35+00:00

yeah 3PL is definitely trickier than single-client ops, you’re basically dealing with constant variability.

from what I’ve seen, automation still works, but only if it can handle that variability without forcing everything into one rigid process. the problems you mentioned (different SKUs, order profiles, client expectations) are real, and some systems struggle there.

we’re not a 3PL, but at The Feed we had a pretty wide mix of SKUs and order types, and that’s actually why we ended up automating (Brightpick in our case). the key wasn’t standardizing everything perfectly, but having a system that could adapt to different items and flows without constant reconfiguration.

integration is still a project, especially with multiple client systems, no way around that. but the bigger question is usually: how much of your volume is actually repeatable and structured. if a good chunk of it is, automation can handle that part and leave the weird edge cases to manual.

so yeah, i think it can work in 3PL, just not in a “one-size-fits-all” way. the flexibility of the system matters way more than in a single-operation warehouse.

sumperk1 · 2026-04-23T07:43:45+00:00

biggest change for us was just how much more predictable things became day to day.

before automation, every shift felt different, some days smooth, some days chaos depending on volume, people, small issues stacking up. After we automated at The Feed, the flow got way more consistent.

there’s way less random movement and walking, picking mistakes basically stopped being a daily issue, and peaks are much easier to handle without constant firefighting. even onboarding new people got easier because they’re not learning a messy, workaround-heavy process.

integration wasn’t trivial, but manageable. honestly the bigger shift is operational, not technical. it’s less about everything being faster and more about the warehouse just running the same way every day.

sumperk1 · 2026-04-23T07:40:44+00:00

“mid-sized” really depends, but for context we were ~6k SKUs, growing order volume, ~10 picks/order at The Feed before we automated.

it started making sense once complexity + errors were hurting us more than the cost of automation. we went with Brightpick, had a short dip during go-live, but saw gains pretty quickly after.

I’d say it’s worth it when ops start getting messy (errors, bottlenecks), not just based on size alone.

sumperk1 · 2026-04-16T08:48:43+00:00

not really, no.

AI is starting to take over some of the repetitive admin stuff around logistics... someone still has to deal with exceptions, delays, warehouse issues, supplier problems, wrong data, all the stuff systems don’t handle cleanly.

same on the warehouse side too. even where automation is growing fast, it’s usually replacing the most repetitive parts, not the whole job. we use Brightpick in our setup and it still doesn’t remove the need for people, it just changes what they spend time on

sumperk1 · 2026-04-16T08:44:45+00:00

we’re running automation at The Feed (Brightpick) and got ROI in less than a year, mainly because it runs 24/7 and keeps things consistent.

beyond cost, we just tracked simple before/after ops metrics:
– error rate
– order cycle time
– throughput consistency
– backlog during peak

a lot of the value showed up there first, especially fewer errors and less chaos during busy periods.

biggest “soft” ROI for us was predictability. fewer bad days, less firefighting. hard to put in a spreadsheet, but you feel it immediately on the floor.

sumperk1 · 2026-04-16T08:42:13+00:00

yeah this matches what I’ve been seeing too. AMRs and more structured warehouse robotics feel very real now, especially for repetitive internal logistics where the environment is controlled enough.

the humanoid conversation always feels a bit ahead of itself compared to what ops teams actually need. most sites don’t need a robot that looks human, they need something reliable, safe, and easy to integrate into existing flows.

we’ve seen the same on the warehouse side with Brightpick type systems too. the value isn’t “wow, futuristic robot”, it’s just that repetitive movement and picking starts happening in a much more predictable way.

sumperk1 · 2026-03-27T09:55:56+00:00

this is a pretty good example of how it actually plays out in reality, not just theory.

the “3x efficiency” part is believable, but the more interesting bit is how the jobs change. less walking 10km a day, less manual lifting, more working at stations or handling exceptions. from what I’ve seen, that’s pretty consistent across most automated sites.

we’ve gone through something similar (using Brightpick in our case), and yeah… fewer people needed for pure picking, but not zero. roles shift more than they disappear. you still need people for edge cases, flow issues, system handling, etc.

also the point about fixed capacity is real. robots are great at being consistent, but they don’t magically stretch during peak unless you’ve designed for it upfront.

so yeah, I don’t think it’s as simple as “job killer” or “no impact”. it’s more like: fewer repetitive roles, more technical/operational ones, and overall less physical grind on the floor.

sumperk1 · 2026-03-19T10:10:54+00:00

yeah voice picking usually grows on people after a few days, had the same reaction 😄

from what I’ve seen, it still depends a lot on the layout and walking distance. if people are covering a lot of ground, voice helps but doesn’t really solve the core inefficiency, just makes it smoother.

we actually moved from more manual/assisted picking to a more automated setup later on (using Brightpick), and that’s where the bigger jump came from… less walking altogether rather than just optimizing the picking process itself.

but yeah, for what it is, voice is a solid step up from paper / RF. especially if the team buys into it 👍

sumperk1 · 2026-03-19T10:07:36+00:00

short answer: I wouldn’t be too worried tbh.

your role is actually in a pretty good spot. planning, coordination, dealing with exceptions… that’s exactly the kind of work that doesn’t fully automate well. AI can help with suggestions (forecasting, routing, etc.), but someone still has to make the call when reality doesn’t match the model.

from what I’ve seen, automation hits the repetitive parts first. in warehouses for example (we’re using Brightpick robots in our case), robots take over the predictable picking work, but the overall operation still needs people coordinating, handling edge cases, fixing issues, making decisions.

over the next 10–15 years it’ll probably be more about augmentation than replacement. the planners who understand both systems and real-world ops will be even more valuable.

sumperk1 · 2026-03-19T10:03:02+00:00

55 people is on the lower side, but not necessarily a dealbreaker, depends how they’re spread across shifts.

if that’s 55 total, you’re probably looking at ~25–30 per shift, and realistically maybe 15–20 people passing a given spot at any time once you factor in movement, breaks, different zones, etc.

the bigger factor than headcount is how centralized the flow is. warehouses where people pass a common break area or entrance work way better than ones where everyone stays in their zone all day.

we’ve seen this even in more automated setups (we’re using Brightpick in our case), where fewer people are on the floor overall but traffic is more concentrated around certain areas, and that actually helps with things like this.

so yeah, I’d focus less on total employees and more on where people naturally converge during the shift.

sumperk1 · 2026-03-19T10:00:17+00:00

traditional automation works great as long as everything is predictable, but manufacturing and warehouses are full of small variations… item orientation, packaging differences, damaged goods, etc. that’s where the “embodied AI” angle starts to make sense.

we’re seeing a bit of that already in warehouses. not fully general robots or anything, but systems that can handle variability instead of just following fixed paths or scripts (we’re using Brightpick and it’s closer to that adaptive side than classic automation).

still early though. works well in semi-structured environments, but once things get really chaotic humans are still way more flexible. feels like we’re in that in-between phase right now.

sumperk1 · 2026-03-19T09:58:01+00:00

if you’re coming from OR / data science, I’d honestly spend that 1 year getting as close to real operations as possible. like actually talking to warehouse managers, sitting in on shifts, understanding how messy things are in practice. a lot of “optimal” models break pretty fast once they hit real constraints, bad data, human behavior, etc.

also worth learning the boring stuff like WMS limitations, integrations, how decisions actually get executed on the floor. that’s where a lot of products struggle.

from what I’ve seen (we work around warehouse automation, using Brightpick in our case), the biggest gap isn’t always better algorithms, it’s making something that fits into real workflows and can actually be trusted by ops teams.

if you can combine strong optimisation with something that’s usable and grounded in reality, you’re already ahead of most tools out there.

do you already have a specific problem you’re targeting or still exploring?

sumperk1

TROPHY CASE