Bulk PODBatch recoveryPlan allowance

How to recover a partially completed POD batch

Download completed proofs, fix missing destination postal codes, and start held rows when your Provanza plan has room.

By ProvanzaPublished Updated 4 min read
Illustration of a support desk with a parcel and delivery records

Direct answer

Open the saved batch in Provanza. Download the files that are ready. Enter the destination postal code for rows marked Needs ZIP. Use Start on the on-hold banner when your workspace has room for more requests.

A duplicate row starts no second request. Use the original row for the proof. Check the batch before you retry other rows.

Provanza

Follow four fictional rows through a batch

Suppose your workspace has room to start two new requests. Submit these four fictional rows in the order shown. UPS A and GLS B start. GLS B can start with a blank postal code because the lookup can ask for it later. UPS C stays in the saved batch on hold.

The first successful proof for a parcel and carrier in your workspace counts toward the plan allowance. An in-progress request that could use allowance reserves a slot. When GLS B stops to ask for a postal code, that slot becomes free. UPS A uses one slot for its completed proof. Its duplicate uses none.

ProvanzaProvanza

Fictional batch after the first lookups

Input orderBatch outcome
1. UPS AStarted and completed. The original row has the available PDF.
2. UPS A againDuplicate. Provanza skipped the repeat.
3. GLS BStarted. The lookup requested the destination postal code. Open Needs ZIP.
4. UPS COn hold. Both slots were reserved at submission.

Download available proofs and the summary file

Choose Download ZIP on the batch page. Select the carriers to include. Turn on Include summary file (JSON) to add manifest.json. With UPS and GLS selected in the example, the ZIP has the available PDF for UPS A. The manifest describes all four rows, including the duplicate, missing postal code, and hold.

Use the manifest to match each selected row to its file or to the reason a file is unavailable. The ZIP and the manifest cover the selected carriers. Check the batch page for unassigned rows and rows from other carriers.

Provanza

Illustration of shipments from several carriers with files and exceptions in one batch
Download the files available now. Leave rows that need work in the saved batch.

Enter the destination postal code

Open Needs ZIP and save the recipient’s postal code for GLS B. If several rows have the same destination, use the batch postal-code action to apply one value. Set postal codes individually when destinations differ.

Saving a postal code can start a new attempt. The save itself uses no allowance. The attempt may need an available slot. If the app refuses the save because the plan has no room, apply the code again when there is room. That row stays in Needs ZIP.

Provanza

Start held rows when your plan has room

Use Start 1 entry in the on-hold banner to start UPS C once your plan has room. Provanza starts eligible held rows in batch order. If you use the freed slot to restart GLS B first, UPS C stays on hold until the plan has room again.

Keep using the same saved batch after the allowance resets or you upgrade. Batches with held rows stay available for 90 days from creation. Download completed proofs before they age out under your plan’s history limit.

Start applies to held rows. If a row needs a postal code, use Needs ZIP. For an eligible failed request, use Retry. The batch retry can also include not-found requests if you select that option. A retry leaves completed proofs in place.

Provanza

Official sources

  1. Provanza: Provanza API ReferenceAccessed
  2. Provanza: Carrier delivery evidence coverageAccessed

Ready to organize proof-of-delivery work?

Review Provanza plans or sign in to continue to your workspace.

Already on Provanza? Sign in

Get started