Designed order documents for online stores, powered by the unchanged MIT-licensed Fullbleed engine. Developer preview; paid sales and marketplace listings are not live.
| Package | What is implemented | Distribution direction |
|---|---|---|
| Fullbleed Commerce for WooCommerce | Order summaries and packing slips, visual and HTML/CSS template editor, embedded logos, PDF previews, Studio design, local browser generation | Free entry plugin; no account, quota, watermark, or telemetry |
| Fullbleed Commerce Pro | Contrast and Quiet designs, up to 25 orders as a ZIP, automatic email attachments, customer account downloads, activity history and optional administrator failure alerts through a private renderer | Separate paid download, updates and support; proposed $79/year for one store, hosting separate |
| Fullbleed Commerce for Shopify | Visual and HTML/CSS template editor, three designs, native Flow actions, expiring document links, persistent activity/retry/revoke controls, authenticated previews and subscription checks | Studio $12 / 250 orders and Scale $29 / 1,000 orders per 30 days configured for development-store testing; paid launch pending |
Prices are not live offers. Shopify plan changes are verified on a development store; paid merchant purchases and marketplace listings are not live. The engine remains available independently under MIT; WordPress plugin code is GPL-compatible. See LICENSE.
| Studio | Contrast | Quiet |
|---|---|---|
 |
 |
 |
These are actual Fullbleed PDF renders with synthetic order data. Generate the
PDFs locally with npm run examples.
Open a sample store in your browser. Try the free editor and download real PDFs from two fictional orders without an account, payment or store connection. The sample store is temporary; export your template to keep it. The walkthrough includes an actual sample PDF and explains the automated workflows.
Download the free plugin from the
WooCommerce preview release.
Use a staging store. Install WooCommerce, then upload
fullbleed-commerce-0.1.6.zip in WordPress Plugins. Open
WooCommerce → Fullbleed documents, enter a numeric order ID, and generate a
PDF. An order edit screen also has a Create Fullbleed PDF link.
To evaluate Pro, upload the unchanged fullbleed-commerce-pro-0.1.2.zip after the base plugin. Select orders
on the Orders screen and choose Create Fullbleed PDFs, or enter comma-separated
IDs in the document form. Pro's workflow and design code ship separately from the
free plugin. There is no license lock in the free package.
WordPress hosting does not need Node, Python, a PDF service, or custom fonts. JavaScript, fonts, and the WebAssembly engine are served by the merchant's own WordPress site. Authorized staff read an order over WordPress's authenticated REST API; rendering occurs in a dedicated worker in that browser. This plugin sends no customer data to Fullbleed and stores no generated documents.
Back up your staging store and export your templates first. Upload the new free ZIP through Plugins > Add New > Upload Plugin, then choose Replace current with uploaded. If you use Pro, replace its ZIP next using the compatible pair listed in the release notes; the base is upgraded first. Free and Pro may have different version numbers. Do not delete the plugins to update them.
Saved summary and packing-slip templates, their revisions, and existing automation settings are retained. An enabled automation remains enabled after an upgrade; check its connection and one synthetic order before returning to normal use. The release verification records the upgrade checks and which configurations were exercised. The preview still has no automatic updater.
Version 0.1.6 updates browser and server rendering to Fullbleed 2.5.22 through Node package 0.4.1. Numbered sections in custom templates now restart their step counters correctly. Saved HTML/CSS stays intact; review the PDF preview after an engine update because corrected layout can change the output. The engine update record covers the saved-template comparison, numbered care instructions and release checks. Pro 0.1.2 is unchanged.
Version 0.1.5 serves the editor's icons from the installed plugin and removes the external stylesheet fallback. The local asset verification checks template editing and PDF downloads with off-site requests blocked.
Version 0.1.4 corrects font loading in the visual editor inside WordPress Playground and gives typography values and unit menus room in the style panel. The engine, PDF rendering and saved template content are unchanged. The editor verification records the reproduced failure and the browser checks.
Version 0.1.3 updates the engine to 2.5.8, including compact embedded fonts and corrected font-family selection. Saved HTML/CSS remains intact, but regenerated PDF bytes can change. Review your saved designs on staging after upgrading. The private WooCommerce renderer and Shopify server now use a separate process for each PDF. A failed render child can return a document failure without ending the HTTP server; the original native-crash investigation remains open.
Version 0.1.2 keeps summary totals and the closing note together in built-in designs and newly created starter templates. Existing saved designs retain their own CSS. To apply this pagination rule to a previously saved built-in summary, add the following in its HTML/CSS editor, preview a long order, then save:
.totals { break-after: avoid; }
.footer { break-before: avoid; }In WooCommerce, choose a document type and select Customize selected document. In Shopify, open Template studio. Each document type has its own saved template.
Use the visual editor to move blocks, edit text, insert fields, and style type, spacing, colors and borders. Switch to HTML / CSS to paste static markup or print styles. Upload an embedded PNG/JPEG logo, preview a PDF using an authorized order, then save. Export/import JSON backups, load a starter, or restore the built-in design. The free WooCommerce plugin includes this editor.
Order fields such as {{order.number}} are escaped text. Repeated item and totals
blocks expand for each order; prices are copied from the platform. Templates
control their own paper and print CSS. The visual canvas is a layout aid; the
Fullbleed PDF preview is the check for final typography and pagination.
See the template guide for fields, loops and supported input.
WooCommerce Pro can attach the saved order-summary design to selected existing transactional emails through an optional server renderer. It can also add an Order summary PDF action to My Account so buyers retrieve their own eligible orders without staff assistance. Both features start disabled and reuse the saved template. Failed rendering preserves the original email or account page and records a merchant-visible error. See the WooCommerce automation guide. Store operators and agencies can use the private renderer deployment for an HTTPS proxy, credential provisioning, bounded container resources, maintenance and rotation. It runs on infrastructure the operator controls; it is not a hosted plan.
Fullbleed activity shows the latest email-attachment and customer-download results, a failure filter, recovery guidance and native order links. Successful retries clear stale failures. It reports PDF preparation, not customer receipt. See the activity and retention details.
The 0.1.1 Pro preview includes opt-in administrator failure summaries, with hourly checks, one mail attempt per 24 hours and a link to recovery guidance. They need working WordPress scheduling and email; they never resend customer mail. See failure alerts.
Shopify adds Create order summary link and Create packing slip link to Flow. Enable automation, connect an order trigger, and use the returned private link in your next workflow step. Jobs survive restarts, duplicate events reuse the same job, and transient failures have bounded retries. Review activity, retry preparation, revoke one link, or pause all automation in the app. See the Flow setup and reliability contract. The order-arrival recipe automatically prepares both PDFs and saves private links and expiry times on the Shopify order. It is verified with an actual synthetic order trigger and browser downloads. Watch the recorded Shopify walkthrough for a saved custom template, the Flow workflow and document activity. The branded-origin verification retains the current install, download, pause and uninstall evidence.
These are development integrations. Customer delivery, production hosting, privacy operations and paid lifecycle validation remain launch gates. The privacy request workflow now captures encrypted exports and tracks merchant handling independently of paid-plan access.
Running a WooCommerce store or building one for a client? Start with the free sample store, then describe the document task you want to automate. Tell us what should trigger it, who needs the document, and whether you can run a private renderer or need managed hosting. Shopify developers can describe a Flow workflow for a development store.
The first evaluation covers a saved design, one normal order, one long order, and what happens when rendering fails. Keep tests on staging with fictional data. The request is public and does not purchase a service or reserve a launch date. For a private inquiry, contact Fullbleed.
The development toolchain and Shopify container use Node.js 26.10.0. Node 24.21.0
has an intermittent native rendering failure under investigation; see
runtime evidence.
After an install with --ignore-scripts, run npm run setup:playground before
using WordPress Playground. Its pinned file-locking dependency needs a local
build on Node 26 when no matching prebuilt binary is available (Python, make
and a C++ compiler on Linux). This is development tooling, not a dependency
added to the Fullbleed engine or the distributed WordPress plugin.
The rendering integration uses the published Fullbleed Node 0.4.1 package,
containing engine 2.5.22, pinned to its npm version and lockfile integrity.
Server rendering requires a normal Node host that permits child processes.
The existing admission limits cover child lifetime, including cancellation and
failure cleanup. Each request pays for a new process and WASM startup; this is
fault containment, not a security sandbox or a production capacity guarantee.
Its render promise settles after the worker exits, so the automation renderer
and Shopify limits hold their capacity slots through worker cleanup, including
cancellation and failed renders. The integration tests exercise those paths with
actual PDF workers. The separate native failure investigation remains open.
npm ci --ignore-scripts
npm run build
npm test
npm run examples
npm run packoutput/examples contains real PDFs, PNG previews, and hashes. dist contains
installable plugin ZIPs and SHA-256 sums. Source and build instructions accompany
the base ZIP; the add-on's complete readable JavaScript and sources accompany Pro.
Run a disposable local test store (downloads WordPress and WooCommerce):
npm run dev:wordpress -- --pro --hpos
python tools/check-wordpress.pyThe HTTP verification script uses Python requests. The store binds to
127.0.0.1:9475. Credentials are synthetic local-test data: admin /
fullbleed-local-test. Never use that fixture script or password on a merchant
site. Omit --pro --hpos to test the free package with legacy order storage.
The 0.1.1 preview uses numeric plugin versions and retains the
staging-preview limitations below. It includes the Fullbleed 2.5.6 text-extraction
correction for customized bold type and packages the opt-in Pro failure alerts.
Plugin archives use the version in each plugin's PHP header and matching readme;
the private integration package and this Playground demo use the same version.
npm run pack rejects invalid directory versions or mismatched
metadata. Directory submission and approval are separate from automated checks.
See docs/verification.md for checks and gaps. Node generation, the browser-worker runtime, DOM workflows, WordPress authentication, and actual WooCommerce order reads are checked separately. DOM simulation is not a real Chrome/Safari test or Shopify approval.
The native rendering investigation retains the unresolved Linux crash evidence and documents reproducible, bounded diagnostic runs. Passing repetitions do not establish that the intermittent crash is fixed.
The 0.1.1 release evidence records identical Windows/Linux archives, 45 shared tests and six visually inspected designs. Chrome, Playwright Firefox and Playwright WebKit each pass 36 staff, customer and alert checks on Linux. Windows Chrome passes 26 staff/customer checks with matching PDFs. Native WordPress passes strict Plugin Check and 12 Chrome checks.
Upgrades from the published alpha.3 ZIPs preserve templates, revisions and enabled automation in both order-storage modes, while new alerts stay disabled. The native renderer and private SMTP inbox pass 72 checks, including queued delivery, failure alerts and explicit recovery. The release includes the detailed evidence archive. External mail deliverability and merchant-host scheduling still require staging acceptance. Historical alpha.3 results remain separately identified.
This preview produces order summaries, not fiscal invoices. It preserves store display amounts and does not calculate tax, create invoice numbers, or reconcile refunds. Refunded orders are rejected. Shopify edited orders are also rejected. Pro includes opt-in development integrations for existing WooCommerce email attachments and customer account downloads through an optional server renderer. See the automation setup and limits. Automatic missing-attachment retries, license updates, checkout, multilingual font selection and production hosting remain unimplemented.
Limits: 250 items/order, 30 PDF pages, 30 seconds per render, 25 orders and 50 MiB of PDF bytes per Pro batch. Unsupported characters fail rather than silently dropping glyphs. Validate the layouts on representative merchant orders before production use.
The proposed paid value is merchant workflow, original document design, updates, and support. The first launch leads with WooCommerce; Shopify reuses the same document layer. Product care cards, gift inserts, and form-to-PDF integrations are later options after the first merchants show demand.
The production product plan now makes native automation the paid product's central value: WooCommerce email and order workflows, Shopify Flow, customer downloads, fulfillment batches and visible failure recovery. It distinguishes development milestones from the requirements for a paid launch.
The launch budget is $50 total. Shopify's paid registration invoice totals $19, leaving $31 before metered hosting charges. The attended Railway staging test has accrued less than one cent of reported resource usage. Compute is stopped between tests, with its persistent volume retained. Usage and actual charges are recorded in docs/launch-budget.json. More than $50 requires explicit user approval.
Before selling: complete real-browser and staging-store checks; finalize support, delivery/update, privacy and refund terms; connect a sales account; test purchase, download and renewal behavior; and verify the paid product against merchant needs. For Shopify, complete protected-data and browser tests, verify platform billing, deploy the app, then submit it for review. The Partner connection, development app and installation already exist. See shopify/README.md for the precise status and app development instructions.
Checked October 2, 2026; recheck before launch.
- WordPress.org permits GPL-compatible free plugins and separate externally sold add-ons. It prohibits trialware or locking functional code already included in a directory plugin. Official plugin guidelines.
- Shopify App Pricing is the default for supported new public-app billing models; subscription state must be verified server-side using the Partner API. Official billing documentation.
- Shopify lists a $19 one-time App Store registration fee per Partner account. Official distribution fees.
- There are established paid competitors. At the check date, Order Printer Pro listed $10/month for its first paid tier, and a WooCommerce PDF invoice/builder product listed $49/year. This supports testing a paid workflow product; it does not prove demand for Fullbleed or justify a revenue forecast. Shopify listing, WooCommerce listing.