History
Received Booking History
Review previous booking batches, inspect audit text, and reopen exported results without leaving the received booking page.
Booking History
Reopen previous batches, inspect audit text, and regenerate CSV output.
0 booking(s) loaded
| Batch ID | PO Number | Generated At | Successful | Actions |
|---|---|---|---|---|
| Loading booking history... | ||||
Booking Detail
Audit text is shown exactly as returned by the backend.
Original IMEIs
Scanned IMEIs
Amended Audit
Excluded Audit
Workflow
Received Booking
Move through one clear step at a time: fill the batch details, scan devices with instant match feedback, then review mismatches first and matched devices second.
Step 1
Batch Setup
Fill the booking information and confirm the expected IMEIs.
Step 2
Scan Devices
Scan one IMEI at a time and see immediately whether it matched.
Step 3
Review & Submit
Handle mismatches first, then review the matched devices and submit.
1. Batch Header
Enter the shared batch details once, load the eligible ordered-stock records for the PO, and confirm the expected IMEIs before moving on.
Current stage
Fill batch details and load a PO to begin verification.
Choose from the currently available PO numbers returned by the booking availability endpoint.
Expected IMEIs
Paste the supplier list. Any whitespace format is accepted and duplicates are removed automatically.
0 unique
0 duplicates removed
Step 1 Summary
Keep the user focused on just the information needed to start scanning.
- Eligible Records
- 0
- Expected IMEIs
- 0
Readiness
Waiting for batch information and expected IMEIs.
2. Scan IMEIs
Scan or paste one IMEI at a time. Every scan is added to the list immediately with a match result.
The list on the right updates every time you scan. Duplicate scans are kept visible so the operator can understand exactly what happened.
- Scanned events
- 0
- Matched
- 0
- Not matched
- 0
Scan List
The newest scans appear first with an immediate status.
No scans yet
3. Review Mismatches First
The items needing attention stay at the top so the user always knows what must be resolved first.
Load and compare IMEIs to start resolving mismatches.
Expected IMEIs Not Matched
From step 1These IMEIs were provided in the expected list but do not currently have a matched or integrated scanned device.
Scanned IMEIs Not Found
From step 2These devices were scanned but are not in the expected list. Use the integration control below if the provider later confirms the mismatch.
| Expected IMEI | State | Replacement Scan | Action | Outcome |
|---|---|---|---|---|
| Move to step 3 to review mismatches. | ||||
Matched Devices
Everything below is already verified and ready at the bottom of the review step.
0 matched devices
Submission Summary
Keep the user aware of exactly what will be sent to the backend.
- Needs Action
- 0
- Ready To Submit
- 0
- Eligible records available
- 0
- Submission status
- Preparing
6. Results & Export
Successful export rows stay available even if part of the submission fails.
Total Rows
0
Successful Rows
0
Failed Rows
0
No booking submitted yet.
Quantity Check
PO quantity does not match
The selected PO and the devices ready to submit do not match.