Request a feature

Tell us what would make Workflow Documents better. The more specific the goal, the better.

What makes a request easy to act on

You do not need to write a spec. A sentence is fine. But if you can, include:

• The goal - what you are trying to achieve in your store, not just the feature. "My warehouse needs a pick list sorted by shelf" tells us more than "add sorting".
• What you do today - the workaround you are using now, if any.
• Where it fits - the template editor, the data in templates, the Flow action, languages, branding, the API, or somewhere else.
• How often it matters - a daily annoyance and a once-a-year edge case get weighed differently.

An example of the document you want to produce always helps. Attach a sample or a sketch.

Good things to ask for

• A ready-made template you wish existed - see Create your first template.
• A field you need in a template that is not available yet - see Template variables and Liquid.
• A kind of document beyond orders, products and customers.
• A rough edge in the editor, the preview or the document history - see The template editor and Document history and downloads.
• Anything in the API or MCP surface - see Developer API and MCP.

Already possible?

A few things that already exist:

• The same document in several languages - see Templates in several languages.
• Your own fonts and colors, for all templates or for one - see Branding your documents.
• Generating documents from your own code - see Developer API and MCP.

What happens next

• We reply to confirm we have it, usually within a couple of business days.
• Related requests are grouped, so if others have asked for the same thing, yours adds weight.
• When something you asked for ships, we note it in the changelog.

Found a bug instead?

If something is broken rather than missing, use Report a bug - bugs are triaged ahead of feature requests. For anything else, Support lists every way to reach us.