MakeFlow
For personalized-product shops

The paid order already knows what to make. MakeFlow makes it makeable.

Engraving, embroidery, print, signs and monograms arrive as line-item properties buried in Shopify. MakeFlow turns each paid line into a single production packet, proves it with the customer, and batches approved work by material, machine and colour.

No install needed for the preview. Works with any options app that writes line-item properties.

Production desk · Today

In queue

12

Awaiting proof

5

Ready

7

#1048

Walnut keepsake box · A. Rivera

Approved

#1049

Team polo × 12 · M. Chen

Awaiting proof

#1050

Brass award plate × 8 · J. Okafor

Revision

Batch ready to release

Laser · Walnut · Natural — 3 jobs, 5 pieces

Free preview

Drop a Shopify order export. See the queue.

This is the real MakeFlow engine running in your browser. Nothing is uploaded, nothing is stored, and no account is needed.

The daily tax

Customization is captured beautifully. Then someone opens forty orders by hand.

A paid order holds the buyer's text, font, colour and artwork — spread across properties, an email, a screenshot and a file link. To make the item, staff re-key that into a job ticket, chase approval, then mentally regroup the day's work by machine and material. Every handoff is a place a paid order breaks.

1 by 1

Opening orders to find the personalization

Values live in the order, not in a production view. Staff click through to read them, then type them again.

By email

Proof approval that evaporates

Screenshots and replies mean no version history, no audit trail, and no way to know what was approved.

Setup tax

Jobs run in the order they were opened

Without grouping, a laser or an embroidery head is re-set for every item instead of once per material.

Remakes

The most expensive mistake

A misspelled name found after engraving costs the item, the shipping and the customer.

How it works

Connect once. Release every morning.

01

Capture becomes instruction

Paid lines and their properties are mapped through a template into one packet: text, font, colour, placement, artwork and quantity, in the order the operator needs them.

02

The customer proves it

A calm, branded proof page shows exactly what will be made. Approve or request a change. Every version is timestamped and kept, so "what did they approve?" is never a guess.

03

Approved work batches itself

Released jobs group by material, machine and colour. Print the batch as work packets, export the table, and run the day in setups rather than in order numbers.

Built for the bench

One engine, the right packet for each craft.

Open the desk
Pricing

Priced per production line, not per seat.

Start on the free preview. Move to a paid desk when the queue is yours. Cancel anytime.

$29/mo

Up to 100 production lines a month.

  • Packets, proofs and version history
  • Batch release and print sheets
  • CSV import and export
Start free
Most shops

$49/mo

Up to 500 production lines a month.

  • Everything in Workshop
  • Unlimited packet templates
  • Shopify order sync
  • Branded proof pages
Open the desk

$99/mo

Up to 2,000 production lines a month.

  • Everything in Studio
  • Multi-store and multi-team
  • Priority support
Talk to us later
Common questions

Before you connect it

MakeFlow is deliberately narrow. It does one handoff — captured customization to released production — and refuses to become another dashboard.

More support →
What does MakeFlow actually produce?

A production packet per personalized line: the source order, the captured values mapped to your instructions, the artwork, the proof state, and a batch it can be released with. The output is work, not a report.

Does it replace my product options app?

No. Keep whatever captures customization at checkout. MakeFlow sits after the paid order and reads the line-item properties that app writes, so it stays neutral across vendors.

How do customers approve a proof?

You send a secure link. The customer sees the item and its details, then approves or requests a change. Each round is a new version; nothing is overwritten, and the approval is timestamped.

What if a required field is missing?

The job is flagged rather than silently run. Missing values are shown in the packet and in the queue, so a paid order is never discovered at the machine.

Does it talk to my machines?

Not in this version, deliberately. It prints and exports exactly what an operator needs; machine integrations are a later question, not a prerequisite.

Run tomorrow's personalized orders from one calm queue.

Start with the free preview. When the queue is yours, release your first batch the same day.