The default options are all bad
- ✕
Build it yourself: 3–6 weeks of wrestling docx libraries, fonts, PDF conversion, and storage.
- ✕
Send users to an external tool: you lose the transaction and the brand experience.
- ✕
Buy an enterprise platform: $2k/mo minimum and a six-week procurement cycle.
- ✕
Hack together a Google Docs copy-paste: fragile, no authentication, no multi-tenancy.
How it works
- 1
Design the template
Upload a Word or Google Docs template once. Your team can iterate on the design without you redeploying.
- 2
Drop in the embed
An <iframe> pointing at your SheetMergy embed URL, secured with a per-customer token.
- 3
postMessage the data
Your app sends the row data via postMessage. The embed renders the document and offers download / email.
Embeddable, white-labeled, scoped
Branded embed
Style-matched to your product. No SheetMergy branding in the default view.
Token-scoped
Each customer or session gets a signed token — no shared keys, no cross-tenant leaks.
postMessage API
Push data into the viewer in real time; get status events back. Integrates cleanly into any SPA.
Download + email + storage
Users download a PDF/DOCX, email it to themselves, or hand it off to your storage via webhook.
Multi-tenant by design
One embed, many of your customers. SheetMergy keeps data and templates isolated per token.
Fast-ship ready
From empty project to working PDF in an afternoon. No library fight, no PDF sizing rabbit hole.
Embed questions
- Can we white-label the UI?
- Yes — colours, logo, and accent styling are configurable per workspace. No SheetMergy chrome by default.
- Is it secure for our customers?
- Per-session signed tokens scope the embed to one customer, with configurable TTL. Origin allowlists + CORS enforced per token.
- What about content we don't want SheetMergy to see?
- Data stays in the request — not persisted by default. You can flip on storage when you want history.
- Pricing?
- Credit-based per document generated. No per-embed seat license.