Approving drop-offs
Working the queue, moving an appointment, and what each decision sends.
Drop-offs lists every request, with the ones waiting on a decision at the top.
What a row shows
The reseller, the warehouse, the manifest with quantities and values, anything they wrote, and — once they have been — the receipt and its drop-off number.
Approving
Press Approve… and a panel opens, seeded with the date they asked for.
| Field | Notes |
|---|---|
| Date | Change it if that day does not suit the warehouse. |
| Time | Optional. Leave it blank and the email says any time the counter is open. |
| Note | Sent to them verbatim. Use it for anything they need on arrival. |
Then Approve and email.
The email is the deliverable
Approving sends them the warehouse address, the receiver code, their manifest and the agreed slot. It is the thing they read in the car. If you moved the day, the email says the new day — so do not move it and tell them separately.
Rejecting
Reject requires a reason, and the reason is emailed verbatim. Its whole job is stopping someone loading a car, so write something they can act on:
That warehouse is not taking laptops until Monday. Request Hialeah instead, or send it Monday.
Their commitments are untouched by a rejection, and the email says so.
If the email fails
The approval still stands — an approval that emailed nobody is still an approval. The row shows a warning telling you to contact them directly rather than silently pretending it went.
After they have been
The reseller photographs the receipt and uploads it. The app reads the drop-off number and quantities and checks them against what you approved. If it matches, a submission opens carrying that number, and from there Inbound credits it like any other package.
Receipts that could not be read show on the row so you can follow up.