Batches
A batch is a physical shipment of devices arriving at your facility — typically from an approved quote.
Where to find it
Admin: /process/batches
Portal: /portal/batches
API: /api/v1/batches
Batch lifecycle
| Status | Code | Meaning |
|---|---|---|
| Pre-Load | 0 | Created, devices not yet scanned in |
| Received | 1 | Devices arrived, ready for inspection |
| Inspection | 2 | Inspection in progress |
| Processing Complete | 3 | All devices inspected and graded |
| Escalated | 4 | Issue found — needs admin review |
Batch fields
referenceName— human-readable label (e.g. "Lincoln Elementary Spring 2026")sid— source ID (which client it's from)uid— user who created the batchdateExpected— ETAquantityExpected— how many devices expected
Workflow
- Create batch — set reference name, expected quantity, expected date
- Receive shipment — mark batch as Received
- Scan devices in — use mobile app or admin UI to scan IMEIs/serials into the batch
- Inspect each device — technician runs diagnostics, sets grade, uploads photos (see Device Inspection)
- Complete batch —
POST /batches/{id}/completeonce all devices are processed - Pay the client — based on the quote and actual grades received
Discrepancies
If quantityExpected ≠ actual device count, the batch may be flagged for escalation. Similarly, if graded value is significantly different from quoted value, admins review before paying.
Related features
- Device Inspection
- Quotes
- Mobile app intake workflow — scan devices on the go