A wholesale or product catalogue is sent to a small number of named people, over and over, with the details changing constantly. That combination is what makes the usual delivery awkward: a large file arrives in a buyer’s inbox, they download it if the size allows, they pinch and zoom their way around it on a phone, and the version they keep is frozen at the moment you sent it. Meanwhile you have no idea whether it was opened. If your catalogue already exists as a web page — generated, exported from a design tool, or built from your product data — you can hand over an address instead of a file, and the whole thing behaves differently.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML file or ZIP bundle, or click to choose.
Single file or ZIP. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
Upload the catalogue as a self-contained HTML page, or zip the folder if the images and styles sit alongside it, and you get a link back in seconds. It opens in the browser on any device with nothing to install — which matters here more than in most delivery cases, because buyers open things on phones between meetings, and a page reflows where a print-shaped document doesn’t.
The link is a 32-character unguessable address carrying a noindex tag, so trade pricing doesn’t surface in a search for your brand. Put a password on it when the terms are account-specific, and an expiry when the pricing is only valid for a season — both free on a registered account. Different buyers can hold different links to different versions, which is the ordinary reality of wholesale and awkward to do with files.
When prices move, replace the file at the same address. Everyone you already sent it to sees the current catalogue next time they open it, without you reissuing anything or hoping nobody quotes from the old one. You can see how many times a link has been opened, which is a straightforward answer to the question every rep actually has after a send: did this land anywhere.
A self-contained HTML page, or a zip containing the page and its images and styles. That’s the honest boundary and it’s worth stating plainly: this hosts web pages, so a PDF or an InDesign file is not what you upload. Many catalogues are already produced as web pages, generated from product data, or exported to HTML from a design or catalogue tool — those work directly. If yours only exists as a print document today, converting it is a real piece of work, and worth costing before you plan around this.
Because of where it gets opened. A print-shaped document assumes a page-sized screen; buyers open things on phones, and pinch-and-zoom is a poor way to compare six product variants. A page reflows to the screen it lands on, keeps text as selectable searchable text, lets a buyer jump to a category instead of scrolling through forty pages, and doesn’t need to be downloaded before any of that starts. For a catalogue that’s finished and being archived, a PDF is entirely reasonable. For one that’s being browsed and revised, it isn’t.
Yes, by publishing more than one document. Each catalogue is its own link, so an account with negotiated terms gets its own address with its own password and expiry, and it can’t be reached from any other. There’s no shared directory anywhere on the service, so nothing links one buyer’s catalogue to another’s. What this isn’t is a login system with per-account pricing rules — it’s one document per audience, which for most wholesale relationships is exactly the right amount of machinery.
Replace the file at the same address and the link everyone is holding shows the new catalogue. This is the part that’s genuinely difficult with files: once a price list is in a buyer’s downloads folder, you can’t reach it, and the only defence is an email asking people to please use the new attachment. Keeping one address per buyer means the current version is the one they open, and the stale copy stops being a live document the moment you replace it.
It’s the default here. The address is long and unguessable, it carries a noindex meta tag and an X-Robots-Tag header, and there’s no public gallery to browse. Trade pricing turning up in a search for your brand name is a specific and unpleasant category of problem — it reaches your retail customers and your competitors at the same time — and the defence is that the page is never listed and never linked, so the only way anyone reaches it is because you sent it to them.
You see how many times the link was opened, which answers the follow-up question honestly without overstating itself. It tells you the page was loaded; it doesn’t tell you which products someone looked at or how long they stayed. Detailed analytics come with the paid plans. Used sensibly, a view count is a prompt — the buyer you sent this to a week ago hasn’t opened it, so the follow-up call has a purpose beyond checking in.
The per-file ceiling is 10 MB on a free account, 25 MB on Solo ($4.99/mo) and 50 MB on Studio ($14.99/mo). Catalogues are image-heavy, so this is the constraint worth planning around. Sizing product photography for screens rather than print usually cuts a bundle dramatically, and it makes the catalogue load faster on the mobile connection a buyer is actually using — so the ceiling tends to push you toward a better experience rather than away from one.
On paid plans the page carries no branding of ours, and Studio serves it from your own domain, so both the address and the page read as yours. For a catalogue that matters more than for an internal document — it’s a sales artefact going to a buyer who is forming an impression of how organised you are, and an address on your own domain is part of that impression.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.