MechanicRepeat the draft
Choose a tag, start date, and cycle length. The task finds matching source drafts and duplicates them on the configured cycle.
Use cases / Repeat business
Give repeat orders a repeatable starting point.
For a customer who orders the same items on a regular cycle, start the next order from a draft you’ve already prepared. Mechanic can duplicate selected draft orders and optionally send an invoice.
Start with a library task. Configure it for your store.
A repeat wholesale order
The next draft starts from an agreed order.
- Prepare the source draft
Add the recurring tag to a draft containing the intended items and customer.
- Set the cycle
Choose a cycle start date and the number of days between runs.
- Create the next draft
On a matching day, the task copies the source without its recurring tag.
Ready-made starting points
Choose how far the automation should go.
A repeat ordering workflow can stop at a draft for staff review, or include an invoice email for the customer. Decide which step belongs to your team and configure the task accordingly.
Follow up on invoices
The separate reminder task follows up after 24 hours, with optional daily reminders. Review its recipient rules before enabling customer emails.
Send an order PDF
For an order created with pending financial status and an email address, this separate task can send a PDF invoice from an HTML template.
Set it up in Mechanic.
Prepare one source draft
Use a test customer and the products you intend to repeat. Add the tag the task will search for, and make sure no unintended drafts share it.
Set the cycle and options
Enter the cycle start date and number of days. Leave automatic completion off if your team should review drafts. Turn on invoice sending only when you want customer email.
Test the next occurrence
Review the preview, permissions, and generated draft on a valid cycle day. Confirm products, pricing, discounts, terms, and email behavior before using real recurring orders.
A recurring draft is its own workflow.
This task duplicates draft orders. It does not create a subscription contract or automatically charge a stored payment method. Its optional completion setting can mark a new order as paid when the source lacks supported payment terms, so configure that deliberately. The task documentation explains which payment terms and discounts it carries forward.
Before you set it up
Can I run it manually?
Yes, but the task still checks the cycle date. A manual run is not a bypass for the configured schedule. Check the current cycle before using a manual run to test it.
Is a 30-day cycle the same as a monthly billing date?
No. The task uses a number of days, so a 30-day cycle can move between calendar dates. A specific day-of-month schedule requires different task logic.
Will the new draft become another recurring source?
The task leaves its search tag off the new copy. The tagged source draft remains the starting point for the recurring cycle.
Can this replace a subscription app?
It may fit repeat orders handled through drafts and invoices. Subscription contracts, saved-payment charging, subscriber portals, and other subscription features require a solution designed for that process.
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: