Playbooks
One job, start to finish
Each playbook walks a real workflow end to end, with the assumptions stated so you can check the arithmetic. Worked examples, not customer testimonials — we are new, and we would rather show the working.
Worked examples
One job, followed all the way through
Each playbook states its assumptions so you can check the arithmetic — the working, not a testimonial.
The Monday recountA morning for about 400 itemsA whole floor, patchy signal, two counters, one live count — start to finish, with the arithmetic stated so you can check it.Outcome: One reconciled count of a full floor, in the browser, same morningEvery client's stock, in one clean importAbout 20 minutes of setup, then minutes per clientA group per client, and a TXT file shaped column-for-column to a legacy importer that has never heard of the cloud.Outcome: A per-client stock file your old system imports without complaintRestock once, update every channelOne count, then about 10 minutes per channel the first timeOne physical count, then one correctly-shaped CSV per marketplace — using column order as the mapping tool.Outcome: A bulk-upload file per sales channel from a single countCounting stock held in more than one placeOne pass per placeGroups, place names, and a pass-per-place workflow — plus a plain statement of what FieldScan does not model, so you can decide if it fits.Outcome: Clean counts across a storefront, a back room and a van
The individual features behind these live in the guides, and what connects to what is on Integrations.