Egocentric Retail Backroom Organization Data

Egocentric retail backroom organization data is real-world, first-person video of a person doing the work the catalog rows describe: sorting stock onto labelled racks and bins, breaking down cartons and clearing the aisles, and inspecting returned or damaged items and sorting them into the right bin. It is recorded from the operator viewpoint, with depth, 3D hand pose, contact events and frame-accurate action segments aligned on one hardware clock.

Retail backroom robot training data needs the decision behind each placement as well as the grasp, because stock is grouped by category and a damaged item goes to markdown, disposal or a returns bin. The site states no store, stock, process or loss detail for these rows, so this page says only what the rows say.

The site lists four rows for this topic in the Retail Store -- Back of House environment. Backroom Organization sorts stock onto labelled racks and bins, breaks down cartons and clears the aisles. Sort and organize backroom inventory using shelving racks and bins groups backroom stock by category, shelves it on racks and labels bins. Damaged-Goods Sorting inspects returned or damaged items, scans them and sorts them into markdown or disposal bins. Inspect and sort damaged goods using a handheld scanner and returns bins scans each damaged item, checks the condition and drops it into the right returns bin.

All four are rated Easy, use a head-mounted phone or multiview rig, and are listed as Ready to deploy. The environment describes the stockroom, receiving dock and backroom of supermarkets, apparel and general retail. A stockroom organization video dataset here means footage recorded to your spec for those rows. Tasks outside the list can be added to a spec.

Yes for sorting. Two rows cover damaged goods: one ends in markdown or disposal bins and one in a returns bin after a handheld scan and a condition check. That makes egocentric damaged-goods sorting and backroom inventory data a matter of choosing which rows go into the spec, and the sequence between them.

Counting is a different job. The site lists no counting row in a store environment, and its backroom rows sort and shelve stock rather than count it. If your policy needs a count step, say so in the written spec; it is scoped as an added task with its own accept criteria. The site does not state stock types, carton sizes or weights, rack layouts or label formats, so those are agreed in the spec and checked on a Spec Pilot.

The environment holds ten rows in total, all rated Easy and listed as Ready to deploy. Six sit beside the four above: Cart & Basket Retrieval, Price Tagging & Signage, Retail Stocking Back of House, Shelf Restocking & Facing, tagging and pricing merchandise with a pricing gun and label sheets, and unpacking and stocking shelves with a box cutter and stocking cart.

This page does not claim those six. A spec can pair backroom organization with a restocking row when your policy has to carry a carton from the rack to the shelf; the second table lists the rows side by side.

The returns processing page covers returns rows in a warehouse, a retail floor set and the front of house: opening returned parcels, inspecting, scanning and routing items. The inventory counting page covers two counting rows and says the store backroom rows sort stock rather than count it. The sorting task page is a task family across many sectors and lists the backroom rows among them. The grocery put-away page covers putting groceries away in a kitchen.

This page is the dedicated one for the store backroom: organizing stock on racks and bins and sorting damaged goods there. The third table sets the pages side by side.

A head-mounted phone records the first-person view of real work on site, and a multiview rig adds synchronized third-person angles when the spec asks for them. A wrist-mounted camera is available alongside the head camera for close-range detail. A stereo head rig is also offered where depth from a calibrated pair matters; the MCAP hub page describes it.

The site does not state a camera count, resolution or frame rate for these rows, the number of workers per site, or the location of the capture. Environment, access and schedule are agreed in the spec, and the site names no retailer, store or worker.

Each episode follows the Firsthand episode schema: ten streams synced under 2 ms, with head and wrist RGB, depth, 3D hand pose with per-joint visibility, contact and grasp events, and frame-accurate action segments. Hand pose tracks the grip on a carton or item, contact events mark when fingers meet stock or a bin, and action segments mark each step of a sort.

Object labels use the terms your spec sets. Item categories, scanner models, a task-completion label, force or tactile data and the markdown, disposal or returns rules are Not stated. They are defined in the spec if your policy needs them, and no safety, shrink, loss-prevention or compliance claim is made.

Delivery formats are RLDS, LeRobot and WebDataset, plus HDF5, zarr and Rerun .rrd, and MCAP is offered for stereo capture. The format table below sets each against what its official documentation states. The episode schema is the same as every other Firsthand collection, so a loader that reads another Firsthand dataset reads this one without changes.

Every batch is validated against signed accept criteria before it ships, with a reject log, and delivery is rolling, per validated batch.

Every episode links to a signed contributor release through a documented consent chain, and the consent record is part of the delivery. Faces, plates and screens are detected and irreversibly blurred at ingest, and a reviewer confirms the result before anything ships. The anonymization record is delivered with the data.

The site does not state a separate rule for other text in a stockroom, such as shelf labels, cartons or scanner displays, so this page does not claim it is blurred. Raise it in the spec if it matters.

Where coverage is already deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks, because vetting operators there is the bottleneck. The site names retail handling as an example of deep coverage but does not state coverage depth for the back-of-house environment itself, so the timeline is quoted against your spec before capture begins. The backroom rows are ready to deploy on a signed spec.

Custom retail data collection runs as custom collection at scale through a network of thousands of capture providers, for a consistent, recurring data flow to labs. On-demand top-ups run against the same spec and accept criteria after each training run. The site does not state a batch size or later-batch turnaround, so those are quoted against your spec.

You describe the backroom work, bins and sequence your policy needs. We turn that into a written spec covering tasks, environments, capture tier, annotation depth and accept criteria, then quote reach, timeline and price before any capture begins.

A Spec Pilot, a small and fast first batch, can prove the spec and accept criteria before you scale. Billing is per validated hour, a reject log ships with every batch, rejected items are recaptured at our cost, and every collection ships under a perpetual, buyer-owned commercial license.