MechanicOrder CSV by email
Filter with a Shopify order search, optionally exclude previously tagged orders, and send the CSV as an email attachment. The task offers a nightly setting.
Use cases / Reports
Send Shopify order exports on a schedule.
Get the orders you need into a CSV and into your team’s inbox. Use a ready-made Mechanic task to email an order export on demand or nightly, with filters that match your workflow.
Start with a library task. Configure it for your store.
A nightly handoff
Tomorrow’s order list, ready to review.
- Choose the orders
Use an order search, such as unfulfilled orders.
- Build the CSV
The task writes a row for each line item.
- Email your team
The file arrives as an attachment for review or import.
Ready-made starting points
Start with the file your team needs.
A regular export can support a packing review, an operations spreadsheet, or a handoff to another team. Decide which orders belong in the file and who needs it before turning on the schedule.
Product CSV by email
This simple example emails product IDs and titles as a CSV. Use it as a starting point when you need a custom product export.
Inventory CSV backups
Use the dedicated inventory-export task when your workflow calls for a scheduled inventory file in Shopify’s CSV format.
Set it up in Mechanic.
Filter the orders
Add the order-export task and set its order search. Start with a small, known group so you can check exactly which orders and line items the file contains.
Set up the email
Choose the recipient, subject, body, and filename. Complete Mechanic’s email approval, review the task preview and permissions, then enable it for a manual test.
Turn on nightly exports
Open the test attachment and confirm the columns and values with the receiving team. Enable the nightly option once the file fits the workflow.
Decide what should appear in the next export.
For a fresh snapshot each night, keep every currently matching order eligible. For a handoff of new work, configure an export tag and exclude orders carrying that tag. The tag records task processing; it is not confirmation that an email arrived or a receiving system imported the file. Plan how you will handle corrections or a resend.
Before you set it up
Is there one row per order?
The order-export task produces one row per line item. An order containing several line items occupies several rows. Check this structure before importing the file into another system.
Can I change the columns or send to SFTP?
The ready-made order task emails its defined CSV columns. A different column layout, SFTP delivery, or a direct API handoff requires a custom task or a task-code change. Use the library task as a starting point for that work.
Does the task send an empty file?
The current order task sends its export email when the CSV contains line-item rows. If no eligible orders produce rows, there is no export email.
Can I export older orders?
Check the task’s requested access and the date range of your order search. Orders older than 60 days require additional order access. Test the intended range before relying on a recurring historical report.
How is this different from Shopify’s order export?
Shopify offers order CSV exports from the admin. This Mechanic task adds a recurring email workflow with configurable order selection. Its column layout is its own, so compare a sample with your existing export before switching.
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: