In a textile DC, a pick face rarely goes wrong in a dramatic way. A replenishment case of size L lands in the size M bin, a returned shirt goes back one slot over, and every picker after that trusts the location label. The WMS still shows one clean SKU, so the error surfaces later as a customer return or a count variance. Per-bin vision reads catch the mixed face before the next wave picks from it, and you can watch a bin read run in a 30-minute pick face demo.
Catch Mixed SKUs on the Pick Face Before Pickers Ship Them
iFactory reads every bin on the face, matching label, barcode and hangtag text plus colour and pattern cues against your slotting master. When a bin holds two SKUs, the location goes on hold and open pick tasks for it are blocked until a counter clears it.
Five Ways a Clean Pick Face Turns Mixed
Mixed faces are almost never theft or system failure. They come from ordinary handling at speed, where one wrong placement looks fine to the next person who walks past. Apparel and home textiles make it worse, because a style can run to dozens of colour and size variants that sit side by side and look nearly the same once folded. One warehouse guide notes that count mismatches often stem from incorrect putaway or mislabeled cartons rather than true shrinkage. Walk through your own handling points with our DC support team.
What the Camera Reads, and What It Cannot Tell Apart
Here is the honest part. Two polos of the same style and colour that differ only in size look the same when folded or polybagged. No model can reliably tell a folded M from a folded L by shape alone. So iFactory does not try to guess size from appearance. It reads printed identifiers, such as the barcode, size sticker, bag label or hangtag text, and uses colour and pattern only as supporting cues. Every read is then compared with the slotting record in your WMS. See how reads and cues combine in a bin-level walkthrough.
- Barcodes on polybags, hangtags and inner cartons where they face the camera
- Size stickers, bag print and hangtag text by OCR
- Colour and print against a reference image of each SKU
- Pack form: folded, hung, bagged or still in a carton
- Size, when no label or barcode is visible
- Very close shades, such as ivory against off-white
- Units hidden behind the front of a deep bin
- Quantity on hand, which stays a count task
A bin with no readable identifier is marked unverified, never clean. Colour or pattern alone can raise a soft flag but cannot block a task. A block needs a decoded identifier that conflicts with the slotting master, so pickers are not stopped on a guess.
The Per-Bin Read Against the Slotting Master
Each signal carries a different weight. A decoded GTIN is close to proof, because each colour and size variant normally has its own code. Colour is useful for spotting a stranger in the bin, but weak for telling close shades apart. The matrix shows how each signal is used. Weights are tuned to your labelling, so share sample bin photos with our vision support team.
A Held Bin With the Evidence Attached
Ops leads don't want a dashboard alert. They want to know which bin, which SKUs, what was read and what happened to the pick. iFactory answers in plain words and shows the bin image behind each hold.
From Mixed Read to Blocked Task in One Pass
The block only helps if it lands before the next picker arrives. Reads are taken after each putaway or replenishment into a bay, and on a fixed schedule for slow faces. A confirmed conflict puts the location on hold through your WMS integration, so open tasks for that bin stop rather than shipping the wrong size. Most WMS platforms offer some form of location hold or lock, and iFactory uses the one yours already has. Plan the hold rules in a WMS integration session.
Four Face States and What Each One Triggers
Vision checks identity, not quantity, so it does not replace the cycle count. What it changes is where counters spend their time. Instead of counting bins on a calendar and hoping to hit the mixed ones, the count list is pointed at faces the camera has flagged. Every adjustment then carries a cause, putaway, returns or breakdown, so the same mistake is fixed upstream. Ask our operations team how this fits your count programme.
What Every Held Location Keeps on File
A hold is only useful later if the record explains it. Each mixed face produces one record that links the image, the reads and the last tasks that touched the bin, so a supervisor can see whether the cause was a replenishment, a returns put-back or a breakdown. Request a sample exception export in a short demo call.
Three Mixed Faces, Three Different Fixes
These are illustrations, not customer cases. They show how the cause found in the record points to a different fix each time, which is the real value of a held bin over a silent mis-pick. Talk through faces like these with our slotting specialists.
Size the Cost of Mixed Faces With Your Own Numbers
We don't quote mis-pick rates, because they vary too much between DCs. Every input below is assumed, and the worksheet does nothing more than multiply them. Put your own count and returns figures in their place, or build it with us in a pick accuracy review.
Catching a face after two picks instead of eight cuts the middle line to a quarter on the same assumptions. Customer goodwill and chargebacks are left out on purpose. Include them only where your records back up a number.
Aisle Cameras, WMS Link and Edge Server, Delivered Ready
iFactory delivers per-bin vision as one package. Cameras are placed to cover your fastest pick faces, and a pre-configured NVIDIA AI server ships racked and ready with the read and compare models loaded, and bin images never leave the building. You rack it, plug in power and Ethernet, and the AI is live. Our deployment team can survey your first aisles.
- Pre-configured NVIDIA AI edge server, racked and ready
- Aisle cameras sized to your bay and bin layout
- Barcode, OCR and colour models trained on your SKUs
- Slotting master sync with your WMS
- Location hold and pick-task block integration
- Exception records with bin images and cause codes
- 24×7 remote monitoring of models and hardware
Pilot aisles chosen, cameras mounted, server racked and the slotting master connected.
Reads compared with counter checks, with no holds placed while weights are tuned.
Location holds and pick blocks go live, counters trained, count list linked.
Built for Textile DCs Where Variants Look Alike
iFactory sits between the aisle and your WMS. It doesn't replace slotting, counting or picking logic. It gives them a check they didn't have. Book a pilot planning call to see where it fits first.
What Textile DC Operations Leads Ask About Mixed Faces
Stop the Wrong Size Before It Is Picked
Read every bin against your slotting master, hold mixed faces and block their pick tasks, with the evidence on file. Delivered as one turnkey package, it is live on your aisles within 6 to 12 weeks.







