Skip to content
Mechanic

Use cases / Documents

Make the document fit the workflow.

Generate a PDF from Shopify data, shape it with HTML and Liquid, and send it when your workflow calls for it. Mechanic gives developers control over the data, the document, and what happens next.

Start with a library task. Configure it for your store.

A document from an order

Choose the order. Send the right details.

  1. Send an order to Mechanic

    Use the supported Shopify admin action to trigger the task.

  2. Render your template

    The configured HTML and Liquid produce the PDF document.

  3. Email the attachment

    The library task sends it to the email address on the order.

The example requires the order to have an email address. Custom recipients or routing require task changes.

Ready-made starting points

Three useful places to begin.

Use an existing task to learn the shape of the workflow, then decide what your document needs. A custom specification sheet, product catalog, or order summary may need different data and delivery rules from a standard invoice.

Order documents on demand

Generate and email a PDF for orders sent to Mechanic through Shopify admin action links. Configure the HTML template, email copy, and attachment name.

Invoices for pending orders

Generate a PDF invoice when an order is created with a pending financial status and an email address. The task also offers a delay option.

A product catalog example

Start with a demonstration that places product titles and images in a PDF. Extend the template and data for the catalog you need.

Set it up in Mechanic.

  1. Define the document

    Choose the data, recipient, and trigger. Start with a library task whose behavior matches, and identify any extra fields or routing that need code changes.

  2. Build the template

    Edit the HTML and Liquid template. Use the PDF generator’s layout options and test realistic data, including long names and orders with several items.

  3. Verify the delivery

    Complete email approval and review the task preview. Test with an order and inbox you control, then inspect the generated attachment before enabling routine sends.

Learn how to install and configure a library task →

Your business rules can shape the output.

A developer can query additional Shopify data, include relevant metafields, group items, or decide which document to generate. The PDF generator renders HTML, CSS, and JavaScript; email actions support file attachments. Those capabilities let the document become part of a custom workflow, with the task code defining the behavior.

Before you set it up

Is this a visual invoice designer?

These tasks use HTML and Liquid templates. Choose Mechanic when a developer needs control over document logic and the surrounding workflow. A dedicated invoice app may be a better fit for a standard template managed entirely in a visual editor.

Can I use Shopify Order Printer templates?

Templates can be adapted for Mechanic, but check their Liquid variables and data access. Review the template against the task’s actual data and test its output before using it with customers.

Can a Shopify Flow workflow start document generation?

Flow can send an event to Mechanic through its official connector. A developer can configure a task to receive that event, retrieve the required data, and generate and deliver a PDF. That requires connecting and adapting the task; the examples do not install a Flow workflow automatically.

Does the invoice task charge the customer?

It generates and emails a document. Payment collection and any accounting or invoice requirements belong to the surrounding business process.

PDF generator reference · Connect with Shopify Flow

Make it work for your store.

Open the task to see its options and instructions. Use the library version as it is, or work with a developer to adapt its Liquid code for your workflow.

More workflows to explore: