Questions worth answering before you pay.

The Chrome extension records each sale in your own show as it closes: auctions, Buy It Now, giveaways, and accepted offers. Each one lands in your dashboard grouped by buyer, so someone who wins six lots becomes one bundle instead of six line items.

Organization labels print through the print agent as those bundles form, each carrying a QR code. After the show you scan that QR at the pack station to pull up the buyer's whole haul and check it against the box in front of you.

It runs on whatnot.com and nowhere else. Its Chrome host permissions cover exactly three origins: whatnot.com, the HaulCall API, and the HaulCall login server. From your show it reads the sale type, buyer username, item title, price, and Whatnot's own order id, then sends those to your account.

It reads the realtime feed your Whatnot session already receives, and falls back to reading the page when that feed is unavailable. It never sees your Whatnot password. You sign in to HaulCall through a separate login window, and the extension holds a HaulCall token only.

Off Whatnot it captures nothing. Sale events waiting to upload sit in the extension's own storage on your machine until it delivers them.

The print agent prints to any printer your computer already knows about — Windows or macOS. You pick the target in Settings, Print agent, from the list the agent reports back. Rollo and Dymo units are what we verify against on real hardware.

Labels render in five sizes: 1x1, 2x1, 1x3, 2x3 (the default), and 4x6. The agent accepts PNG or PDF and hands the job to the printer driver, with the operating system's own print verb as a fallback when a driver rejects raw bytes.

The agent is a small tray app for Windows or macOS. It opens a WebSocket server on 127.0.0.1 port 47777 and prints the label images the web app hands it. That is its whole job.

A browser cannot send a job to a specific printer without opening a print dialog, and a dialog popping up every time a lot closes would wreck a live show. The agent is the piece that turns a rendered label into a silent print job.

The listener binds to loopback, so nothing outside your machine can reach it. Loopback by itself is a thin boundary, because any other program on the same computer could also connect, so the agent generates a random 6-digit pairing code at startup and shows it only in its tray menu. Until someone enters that code in HaulCall, the agent refuses print jobs. Listing printers and reporting status work without pairing, since neither changes anything. The pairing holds until the agent restarts.

Your shows, sales, bundles, and buyer roster stay in your account for as long as the account exists. A daily sweep then strips the fields that carry risk once they stop being useful.

After 60 days it clears the Whatnot order reference on a sale and any note you wrote on a buyer, while keeping the row and its totals so your analytics and buyer history survive. Prepaid shipping labels carry a buyer's name and address, so their PDFs and tracking numbers clear on the same 60-day clock. HaulCall encrypts those PDFs with AES-GCM while it holds them. Crash reports delete outright after 90 days.

Pack evidence photos are the exception: they sit in object storage and stay there, because their whole purpose is defending a dispute months later. Email [email protected] to delete your account and everything in it.

Card numbers never reach HaulCall. Stripe handles checkout and stores the payment method.

Every pack-station scan writes a timestamped record, and you can attach a photo of the packed box before you seal it. When a buyer opens a case, one click builds a dispute packet for that bundle: buyer and order details, the item list, the evidence photo if you took one, and the scan-by-scan trail. Timestamps render in UTC so the record reads the same to whoever reviews it.

The packet is built for Whatnot's item-issue refund flow rather than a card-processor chargeback. A refund-exposure queue ranks shipped bundles whose evidence is thin, meaning no photo, incomplete scans, or a buyer you flagged, so you can see the weak ones before a case opens.

You cancel from Settings, Billing, which opens the Stripe customer portal. Once Stripe reports the subscription ended, four things stop: capturing new sales, rendering labels, VIP insert cards, and postage matching. Those paths return a payment-required error until you subscribe again.

Everything else keeps working. Your shows, bundles, buyers, past sales, and analytics stay readable, the pack station still scans, and dispute packets for boxes you already shipped still build. Billing itself stays reachable, so resubscribing switches the paid paths back on.

A failed payment behaves the same way as a cancellation until the charge clears. Deleting your data is a separate request: email [email protected].