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.
Use cases / Documents
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
Use the supported Shopify admin action to trigger the task.
The configured HTML and Liquid produce the PDF document.
The library task sends it to the email address on the order.
Ready-made starting points
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.
Generate and email a PDF for orders sent to Mechanic through Shopify admin action links. Configure the HTML template, email copy, and attachment name.
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.
Start with a demonstration that places product titles and images in a PDF. Extend the template and data for the catalog you need.
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.
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.
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.
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.
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.
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.
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.
It generates and emails a document. Payment collection and any accounting or invoice requirements belong to the surrounding business process.
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: