Shipping labels & proof of delivery: protecting yourself on every sale

Most reseller losses that aren't pricing mistakes happen in shipping: a label bought against the wrong service, a missed ship-by window, or a “never arrived” claim you can't disprove. Each one is avoidable, and each one is cheaper to prevent than to argue after the fact.

The principle is simple — keep every shipping step attached to the sale that created it, so the label, the carrier, the pickup and the delivery proof all trace back to one order. That's how you stay defensible when something is questioned weeks later.

Defensible shipping starts one step earlier than the label — at the sale itself. When sales load into the Sales tab, each one carries a payout and can be assigned a carrier (UPS, DHL or DPD) right there, before any document is generated. That assignment is what threads the rest of the workflow together: the label, the pickup and the proof of delivery all inherit the carrier from the sale they belong to.

It sounds minor, but it's the difference between a connected chain and four disconnected tools. Assign the carrier on the sale and you never re-state it three more times, never mismatch a label to the wrong service, and always have the sale, the carrier and eventually the tracking sitting together. Account Sales pull live from your platforms and Inventory Sales from your own stock, so however a sale arrived, it enters the shipping flow already tagged with how it's going to move.

The label itself is built to survive a busy packing table. Each one carries indicators showing which page belongs to which label, plus a description with product name, style code and size, and a QR of the sale ID that the selling platform scans to process your sale faster. So the document isn't generic postage — it's tied to the specific order, which is what keeps a multi-box shipment from getting crossed.

Two helpers cut the per-parcel friction. Request Ship Extension (right-click a row) buys more time on marketplaces that enforce a ship-by window, turning a deadline you'd otherwise miss into one you've extended on purpose. And for mixed shipments — electronics, apparel and sneakers going together on StockX — the dialog supports bulk-shipping those item types in one run rather than forcing separate passes. The thread through all of it is that the carrier chosen on the sale flows into the label, the box, the pickup and the POD without re-statement — pick it once, and every downstream document agrees with it by default.

Confirmed sales land in the Sales tab with a carrier assignment (UPS, DHL or DPD) ready for the label step. The Label Dialog turns selected sales into shipping labels — thermal or standard — with the carrier and service already resolved, so you're not logging into each carrier portal to buy a label per order.

Two helpers cut the busywork per parcel: Auto Box sets packaging dimensions so you're not measuring every order, and Request Ship Extension buys time on marketplaces that enforce a ship-by window — which is exactly the deadline that turns into a penalty when missed.

At volume, the slow part of shipping isn't printing labels — it's deciding what goes in which box. The Label Dialog tackles that with an AI boxing algorithm: set your Box Settings (name, how many shoes fit, quantity), select the sales, and Auto Box groups them into proposed shipments for you to review and confirm. You can also build boxes by hand with the Bulk Creator when you want full control.

Each box then behaves like a first-class object. It carries its own status (Arriving, In Hand, Packed) and a calculated "ship this box by" date drawn from the earliest deadline among its contents — so the box itself tells you when it has to leave. For UPS shipments there's a built-in USS (Scanuss) integration: right-click a generated label and Send to USS to have scanning and dispatch handled. The point is that boxing, deadlines and dispatch live in the same dialog as the labels, so a packing session is one flow rather than a spreadsheet plus three carrier sites.

A label is one step; the parcel still has to move and arrive. The workflow follows the order through to the end:

1. Confirm the sale — it lands in the Sales tab with its carrier.
2. Generate the label in the Label Dialog, with Auto Box for packaging.
3. Schedule a UPS or DHL pickup when packed boxes are ready.
4. Download proof of delivery once the parcel moves.

Each stage hands off to the next without leaving the sale context, so nothing falls through a gap between tools.

A pile of labelled boxes still has to get collected, and doing that through carrier portals is its own tax on your time. The Schedule Pickup window books UPS and DHL Express collections directly — enter the address, package count and weight, and it generates a reusable template so the next booking is a date change rather than a re-type. Notably, RestocksAIO bypasses the UPS pickup fee, so collections scheduled through the tool are free.

Every booking lands in the My Pickups tab with its confirmation number, date, time window, location and a live status showing how long until the window closes. Per-row actions let you Track, Copy the confirmation, Remove, or Repeat — which pre-fills a new booking with the same carrier, address and package details. For an operation shipping regularly, that turns pickup scheduling from a recurring chore into a two-click habit, with a clean record of every collection in one place.

Proof of delivery only protects you if you actually have it, and pulling PDFs one at a time from carrier sites is exactly the kind of task that doesn't get done until a dispute forces it. The POD Downloader fixes that: paste a list of tracking numbers or tracking URLs, pick a carrier (Auto-detect works across a mixed batch), parse, and download every PDF into one folder. It supports UPS, DHL and DPD.

It's built for repeated, low-effort runs. The parser deduplicates by carrier and tracking, files already on disk show as Saved rather than re-downloading, and a second run only retries the rows that failed — so you can paste the same growing list across sessions cheaply. PDFs land in a Delivery PDFs folder named by tracking number, ready to archive. Pulling POD becomes a routine you run for every shipped batch, not a panic you do per dispute — which is the whole point of staying defensible.

Proof of delivery is the document that ends a dispute. When a buyer claims non-receipt, or a marketplace withholds a payout pending evidence, the POD is what closes it in your favour. Without it, you're arguing from memory against a claim — and you'll often lose.

Keeping the POD close to the sale and the invoice it belongs to also makes reconciliation cleaner: delivery evidence sits with the records it supports rather than scattered across carrier accounts.

The reason to run labels, pickups and POD inside one workflow isn't convenience for its own sake — it's that the alternative leaks. Four disconnected tools mean four places for an order to slip: a label bought but no pickup scheduled, a parcel shipped with no proof pulled. Keeping it in the pickup and POD flow alongside the documentation suite means each sale carries its carrier from confirmation through to delivery proof.

Protecting yourself on every sale isn't extra work when the proof generates itself from the order. It's the default.