RakeScan

Scanning in dead zones

field guide · scouting without a signal

The best sales are in the worst buildings. Library basements. Steel barns on the county fairground. Estate houses at the end of a gravel road, one bar flickering on a tower you can almost see. Scout long enough and you learn the pattern: book density and signal strength travel in opposite directions.

This guide covers what actually kills the signal, what a dead zone costs you when your app needs the network to function, and the queue pattern that turns "no bars" into a non-event.

RakeScan holding three scans in the on-device queue with no signal, then resolving them into verdicts once the connection returns
the offline queue draining · real capture, release build

Where the signal dies, and why

Basements. Concrete floors, rebar in the walls, earth on three sides. Friends-of-the-Library sorting rooms tend to sit below grade because that's the cheap floor space — and cheap floor space is where book sales live. You lose signal on the stairs and get it back on the sidewalk.

Metal buildings. A steel-skinned warehouse is a passable Faraday cage. Surplus depots, thrift outlets, fairground exhibit halls — the venues big enough to host a serious sale are exactly the structures that shrug off the towers.

Rural sales. An estate sale past the last subdivision often hangs on one distant tower, and on sale morning every phone in the line leans on it at once. You can hold three bars and still get nothing. Congestion fails slower and uglier than a true dead zone, because each request keeps almost finishing.

What a dead zone actually costs

Not data. Position.

A bag-day library sale or a well-run estate sale is a positional game. The good shelf gets read once, early, by whoever is standing in front of it; the window on any section is measured in minutes. (More on working that clock in the library sale guide.)

Now run the request-first loop in that room: scan, watch a spinner, hold the phone higher, walk to the door, scan again on the sidewalk, walk back in. Every trip out is paid twice — once in minutes, once in the shelf you left. The scout next to you didn't leave. An app that needs the network per scan quietly converts every dead zone into a line for the exit, and puts you at the back of the real one.

The offline queue pattern

The fix is not a bigger antenna. It's a design decision about where a scan is recorded first.

  1. Write to the device first. The scan — ISBN, timestamp — is committed to local storage the instant the barcode fires. The network is not consulted before the record exists.
  2. Hold a queue. Unresolved scans wait on-device, in order.
  3. Drain on reconnect. When signal returns, the queue resolves itself — no button to press, nothing to re-scan.

Under this pattern the network is an accelerant, not a dependency. A request-first app treats a dead zone as an error state. A queue-first app treats it as latency.

How it works in RakeScan

RakeScan's rule is scan first, sync later. Every scan lands in the on-device ledger before anything touches the network, so losing signal halfway down the stairs changes nothing about the motion: aim, fire, next book. Queued scans resolve on their own the moment you're back in coverage, and each one comes back as a full verdict — BUY or REJECT with the WHY trace, the used and new offer ladders, the live rank. Online, a fresh ISBN resolves at a 1.3 s median, measured on the shipping build. There's a real capture of the queue on the homepage: airplane mode on, scans stack up; airplane mode off, they resolve into verdicts.

Be clear about the ceiling, because it decides how you work the room: a queue records, it does not answer underground. In a dead zone you're scanning blind. The honest play is a pending pile — pull anything plausible, keep it loose, sort at the door when the queue drains. What resolves BUY goes in the bag. What resolves REJECT goes back — except that RakeScan checks every reject against BookToCash, the buyer behind the app (100,000+ books bought since 2019), so some put-backs come back with a cash offer and go in the box anyway.

Resolved verdicts carry the full ladder, FBA/FBM split included, so sidewalk sorting is a read, not a guess. See FBA vs MF for used books for how to read that split, and the gating guide for why a clean-looking hardcover can still resolve REJECT for your account.

Pair a scanner; keep your eyes on the shelf

A Bluetooth or USB scanner in wedge mode — wedge meaning it types like a keyboard, so any scanner works — compounds with the queue. Online, sound and vibration carry the verdict so you never look down. Offline, there's no response to wait for at all, so the scanner sets the pace instead of the network. A bin of uniform paperbacks in a metal building is exactly where this combination earns its keep.

A dead-zone routine

The offline queue is in the app now, free during the invite-only beta — and you can run one book through the verdict engine on the homepage first. Get early access

Get in the next batch.

Free during the beta on Android and iPhone. No card, no ads — a human sends the invites.

You're on the list. Invites go out in small batches to the email above.
The list is briefly unreachable. Email [email protected] and we'll add you by hand.