Questions worth answering before you pay.

HaulCall reads your sales from an open Whatnot show tab in Chrome, signed in to your HaulCall account — your own broadcast page on extension 0.4.0 and later, or the whatnot.com/live/... viewer tab on earlier versions.

From that tab it records each sale in your 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.

Streaming from the Whatnot phone app puts your desktop on whatnot.com/dashboard/live — extension 0.4.0 and later reads sales straight from that page, nothing else needed; on an earlier version, watch your own show as a viewer in a second Chrome profile (or on a second computer) signed in to HaulCall instead.

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. We have verified it on real hardware with a Rollo 4x6 and a Rongta RP425 (2x1 and 2x3 rolls); other thermal label printers with a standard Windows or macOS driver should work too.

The item label prints the buyer's username, the item title, the price (or "Giveaway"), the show name, the time of the sale, and the big buyer number, with the pack-scan QR beside them. If you would rather have just the code, choose QR only under Settings, Print agent, Label stock, Item label. The 1x1 and 1x3 sizes fit only the QR and buyer number either way.

What prints during a show is your print mode, in the same Settings page. One label per item prints an item label for every sale. One label per buyer prints a single box label the first time each buyer wins. Both prints the item label for every sale plus that box label, so a buyer's first win comes out as two stickers: that is the box label, not a duplicate. It carries the buyer number, username and show, for the outside of the box.

On Windows, set the label printer's default paper size to your label stock (2 x 3 in, for example) in the printer's preferences. If the size is not in the list, add a 2.00 x 3.00 in form under Print server properties, Forms, then pick it. The agent looks for a paper size in the printer's own list that matches the label; when it cannot find one, the printer's default paper is what the label lands on, and a wrong default shrinks the label onto a bigger page.

Labels render in five sizes: 1x1, 2x1, 1x3, 2x3 (the default), and 4x6. Everything HaulCall prints goes out as a PNG through the printer's own driver, including prepaid shipping labels, which are rasterized from their PDF first. The agent's PDF lane is no longer used for printing: it spooled raw bytes past the driver, and a Rollo in ZPL emulation answered that by printing a configuration page instead of the label.

Yes. Settings, Label designer lets you drag each field (buyer username, buyer number, item title, price, show name, sold-at time, sale type, order number, your own text) where you want it, resize it, change its font size, and hide what you don't need. Each label size keeps its own design, and five starting layouts include the default one, QR only and a big buyer number.

Beside the canvas is the label as the print server renders it, and a test-print button sends one to five sample labels to your printer. The designer refuses a QR too small to scan and warns when text won't fit. Until you save a design, labels print in the default layout.

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. You can delete your account and everything in it yourself, from Settings, Account in the portal; email [email protected] if you would rather we did 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 separate from cancelling: do it yourself under Settings, Account, or email [email protected].