One record. Every document you send.

ProductZephyr is deliberately narrow: it turns product data into the documents your clients receive, and it stores that data properly so that it can. Everything below is in both plans.

Exports in the three formats a sales team actually uses

Generated in the background, from one template and from the typed product repository described further down this page.

PDF — a single multi-page document with native, selectable text.
Images — high-resolution renders delivered as a ZIP.
PowerPoint — one slide per page, ready to present.
Long documents are rendered in chunks and merged, so a 300-page document is not a special case.
Files stay downloadable for 30 days, on every plan — and they share the storage allowance with your photographs, so a document you no longer need is one click from being room again.

Export profiles, so a routine stops being a procedure

The German price list and the US product sheet become a saved object, not something a colleague has to remember how to produce.

Save a product selection, a language, a currency, a unit system and a template together.
Re-run the profile when the data changes instead of answering six questions again.
Apply a discount level to a profile, so a distributor tariff is a setting rather than a second spreadsheet.
Each run records the rates it applied, so an old file can still be explained.

Languages, currencies and units, handled at render time

The same stored value, presented the way each market expects to read it — which is what makes one record enough for every market.

Values stored per language, with a fallback to a language that actually has content.
Numbers and prices formatted for the reader — separators, decimals, currency placement.
Measurements stored with their unit and converted to whatever the document asks for.
A rate you set, or the European Central Bank’s reference rate of the day — with the rate used recorded on each export.

A template editor built for documents, not slides

Fixed A4 geometry, blocks where you put them, and a preview that is the export.

Blocks: free text, reusable shared text, a product field, an attribute table, an image, a shape.
Rich text with real typographic control.
Conditional pages — a page with nothing to say about a product is dropped from that document.
The editor preview and the exported file come from the same renderer, so what you place is what ships.

A product repository that knows what it holds

Everything above works because the data is typed: formatting is a property of the value, rather than something re-decided in every document.

Categories, with a product free to belong to several of them.
Attributes typed as text, rich text, number, price, measurement, yes/no, date or list.
Decimal count, currency and default unit configured on the attribute itself.
A Ctrl+K search across everything in the workspace.

Your photographs, held here, without hosting them yourself

A product document is mostly pictures, and pictures have to live somewhere. If yours are on a disk in the office, this is the part that decides whether any of the rest is usable.

Upload a photograph straight onto a product, in the formats a camera and a phone produce.
Every image is re-encoded on the way in, which strips the location data a phone writes into a photograph taken in your workshop.
One picture can serve every language, and a language that needs its own — a packshot with printed text on it — can have one.
Photographs travel inside the document itself when it is rendered, so a file that generated correctly cannot lose an image later.
If your images are already published somewhere you are happy with, keep them there: a URL still works, and nothing here asks you to host the same file twice.

Import and round-trip through Excel

Because part of your catalogue will always be maintained in a spreadsheet, and that is fine.

xlsx, csv and ods, in both directions.
Rows matched on ID first, then on SKU — an export you edited comes back as updates.
The attribute reference itself travels the same way.
Photographs come in with the sheet: a .zip beside it, and the file’s path written in the cell.
A mapping step you confirm before anything is written.

A workspace your team can share safely

Separation that holds at the database level, not just in the interface.

Three roles, so a colleague who should read cannot overwrite.
Invitations by email, and access revoked by deactivating an account rather than deleting its history.
Each customer gets an isolated database schema — not a shared table with a column bearing your name.

The fastest way to evaluate it is with your own products

Tell us what you sell and which document costs you the most time. We will set the workspace up around that document.

Open a workspace or ask for a demo