Email order capture For the customers who will never log in

Somebody on your team is retyping orders that already arrived in writing

A PDF, a spreadsheet, an order typed into an email. Vision reads it, matches every line to your catalogue at that customer’s prices, and hands you a finished order to approve. Nobody retypes anything.

Book a 30-min demo Start free trial

Live product, your order flow, no slide deck. · Trial: 14 days, no credit card needed.

What your customers send, and what you get. Four documents that have nothing in common — and one order with every line matched, at that customer’s own prices.

What actually happens

From their inbox to your order list, with nobody typing

Four things happen, and your customer notices none of them. They keep sending exactly what they sent last month.

They send what they always send

To your Vision address. No portal to join, no format to learn, no conversation about changing how they order.
It reads the whole message

The attachment and the email around it, as one thing — including the line that corrects the other.
It matches every line to your catalogue

Their wording, their item number, their barcode — against your products, at that customer’s own prices.
You get a finished order

What they wrote sits beside what it found, so checking a line takes two seconds.

The two that document scanners get wrong

If a person could open it and work out the order from it, so can Vision. These two are worth showing, because they are where reading the attachment on its own falls over.

The email corrects the attachment

Their spreadsheet says 5 × Ridge Knit. The line they typed above it says “make that 10 this week”. Vision reads the message and the file as one thing, so the order says 10. Anything that treats the attachment as the order and the email as packaging ships 5 — and nobody finds out until the delivery lands.
The order is a photo of somebody’s handwriting

The pad snapped in the stockroom, a scan of a printed sheet, the napkin somebody wrote an order on at the trade show. It reads the handwriting, matches each line to your catalogue, and prices it for that customer.

Everything ordinary too: PDFs, Word files, spreadsheets whatever order the columns are in, a range plan sent as a deck, a screenshot, or a zip with several orders inside it.

The part nobody publishes

When it gets one wrong

Every system that reads a document gets some of them wrong, including this one. Any vendor who will not tell you what happens next is asking you to find out in production. So here is what happens next.

The one line it could not place, said out loud on the line itself — with what the customer actually wrote still on screen, so a person settles it in seconds.

Nothing reaches your ERP until a person says yes

…unless you decide otherwise, and you can. Fully automatic for everyone, automatic only for the named customers you trust, or every order reviewed by hand, forever.

Most brands start with everything manual, then let the two or three senders whose documents are always clean go through on their own. Either way the consequence is the point: a mistake is something your team catches on a screen in seconds — not a wrong quantity in your warehouse, or a credit note three weeks later.

It flags the line, not the order. Marked against the wording it came from — six clean lines and one that needs you is six lines you never look at.
Correcting it is a search box. See what they wrote, search your catalogue, pick the product. No ticket, no rule to write, nobody from us involved.
You can always say no. Reject the order outright, or strip the lines that would not match and accept the rest — rejecting is a button, not a support conversation.
Nothing fails silently. A file it cannot read at all — corrupted, or never an order — shows up on your action list as not processed. No silent errors.

Before it reaches you

What has to be true for an order to go through on its own

If you let orders through without review, this is what they have to satisfy first — and every one of these is a number you set rather than a judgement we make. An order that fails any of them stops and waits for a person, with the reason on it.

The checks are yours to set, and they are checks rather than adjectives — including how far a price on their document may drift from the price you agreed.

When their price is not the one you agreed

A customer orders at last season’s price. Nobody notices, it ships, and the gap turns up at invoicing three weeks later — as an argument, a credit note, or lost margin.

So you set how far off a price may be, as a percentage, a cash amount, or both. Inside that, the order goes through. Outside it, it stops and shows both prices side by side.

Order value. A floor and a ceiling. Nothing enormous goes through unseen, and neither does a €4 order that is probably a mistake.
Line count. A document that reads as two hundred lines when your customers order twelve is a document that was read wrongly.
Quantity. Catches the extra zero, which is the single most expensive typo in wholesale.
Per customer, if you want. The buyer who has sent the same clean spreadsheet for nine years does not need the same suspicion as a new account.

Being honest about setup

No template per customer — but not no setup either

Every product in this category says “template-free”. Here is the accurate version, in two lists.

What genuinely needs nothing

No template, map or rule — not per customer, not per layout.
They change their format? Nothing to redo.
Nothing for your customer to install, join, or even notice.
No developer, at any point.

What actually takes work

Your catalogue, in Turis, with the codes your customers use. The real job — and the same one the storefront needs.
A new sender’s first orders: the odd line matched by hand, once.
Ten minutes on approval rules with whoever owns pricing.
The ERP connection — ours to make, part of onboarding.

The honest summary: the work is in your product data, not in teaching it to read. The go-live checklist →

The only demo worth having

Bring the worst order you receive

Not a sample. Not a clean one. The PDF from the customer whose format changes every quarter, the spreadsheet with the merged cells, the email where the order is three lines of prose in the middle of a paragraph about something else.

We run it on the call, in front of you, having never seen it. You will know inside thirty minutes whether this works on your documents — which is a different and far more useful thing than knowing it works on ours.

Book a 30-min demo

Bring the document. If it does not read, we will tell you that on the call rather than after you have signed.

Before you ask us

Mostly about what happens when it goes wrong

Which is the right thing to ask. Anyone evaluating a system that reads documents has already pictured it failing.

What is the accuracy?

We are not going to give you a percentage, and the reason is worth two sentences. Any figure we publish is measured on our documents rather than yours, and the number that matters is how it reads your customers’ worst PDF. What we can tell you is the thing that actually protects you: nothing is written to your ERP until a person approves it, unless you decide otherwise. Bring us a real order and you will have a real answer in thirty minutes.

What happens when it reads something wrong?

The line is flagged on the line, against the wording it came from, and the order waits. You point it at the right product in a search box and carry on. Nineteen good lines and one bad one is nineteen lines you never look at.

Can orders go through without anyone approving them?

Yes, if you want. Fully automatic, automatic only for named customers, or every order reviewed by hand forever. Automatic orders still have to pass the limits you set — order value, line count, quantity, and how far a price may differ from the one you agreed.

What if a document is unreadable?

It appears on your action list as not processed. It does not fail quietly and it does not disappear — you will know it needs a person rather than discovering the order was never placed when the customer rings.

Our customers correct the order in the email. Does that get lost?

No. Vision reads the message and the attachment as one thing, so a line like “only 10 of the Ridge Knit, not 20 as on the PO” is applied to the line it refers to. The order you approve shows the quantity it used, with the original still beside it, so you can see the correction was caught rather than take it on trust.

Do our customers have to change anything?

No, and that is the point. They keep sending what they have always sent, to an address that reaches Vision. Nobody has to tell them, and nobody has to be persuaded.

Do we need a storefront as well?

No. Vision runs perfectly well on its own, and plenty of brands start here because it is the channel they cannot control. If you later want the customers who would log in to do so, that is B2B Storefront.

What about handwritten orders?

A photographed or scanned handwritten order is the hardest thing in this category and we would rather show you than claim it. Send us one of yours — that is precisely the document worth bringing to the call.

What does it cost?

From €199/mo, priced by how many documents it reads. No setup fee and no commission. The full ladder →

See it with one of your own orders

Send us a real purchase order — a messy one, ideally — and we’ll show you what Turis does with it on the call.

Book a 30-min demo Start free trial

Live product, your order flow, no slide deck. · 14 days, no credit card needed. · No commission on your sales, ever.