corvadex

FAQ

What distributors ask before automating order entry

What Corvadex is

Where it sits, what changes for your team, and what it's not

What does Corvadex actually do?

Corvadex reads the orders and quote requests your customers send you and enters them into your ERP. They can arrive by email, fax, text or phone, as PDFs, spreadsheets, scans, handwriting, or a few lines typed into a message. Every line is matched to a product in your catalog. Quantities, units and prices are checked, and anything questionable is flagged for a person. Your team reviews and accepts instead of typing and verifying manually.

Does it handle quote requests too?

Yes. A quote request goes through the same steps as an order. Every line is read and matched to your catalog, and priced from your ERP, including customer-specific pricing where your ERP has it. It then goes into your ERP as a quote or an estimate instead of an order.

What is different about quotes in Corvadex?

Only the ending. A quote goes into your ERP as a quote or an estimate instead of a sales order. When the customer accepts, you turn it into an order in Corvadex without retyping anything. If they don't, you cancel it.

Does Corvadex replace our ERP?

No. Your ERP stays exactly where it is and stays your system of record. Corvadex sits in front of it and does the data entry step. Nothing about how your ERP is set up, or how your team works inside it, has to change.

Do our customers have to change how they order?

No. They keep ordering the way they do now, by email, fax, text or phone, in whatever format they already use. The change happens on your side, not theirs. Asking customers to adopt a portal is the thing that usually fails, and it's not what this is.

Will this replace our order-entry team?

That is your decision, not something the software forces. Corvadex removes the typing and verifying, not the work that needs a person - talking to customers, chasing what is missing from an order, and the calls that are genuinely a judgment. Taking the keying away means the same team can handle more orders. Whether you use that to grow or to move people onto other work is up to you.

How is this different from the OCR or scanning tools we have tried?

Older tools read characters and fill in a template. They work until a customer changes their layout, and then somebody has to rebuild the template. Corvadex reads an order the way a person does, without a template per customer or per format, and then checks what it read against your actual catalog and your actual prices.

What happens when a customer sends a format we have never seen before?

Nothing special, and that is the point. There is no per-customer setup and no template to build, so an unfamiliar layout is just another order. If a customer redesigns their PO next week, nobody has to be told.

How is this different from the bigger order-automation platforms?

They are good products, built for very large distributors, and that shows up in two ways. Setup runs as a project with a services team behind it. And in most of them each customer's document layout is mapped in advance, so a new format means a request and a wait. Corvadex reads a document instead of mapping it, which is why there is no per-customer setup, and it's sized for distributors those platforms were not built for.

The longer version is on the Why Corvadex page, including when you should choose one of them instead. If you are weighing a specific one, ask and I will tell you where they are stronger.

Getting started

What you install, how orders reach Corvadex, how long it takes, and what is needed from you

What do we have to install?

Nothing on your team's computers. Corvadex is a website your team signs in to with their work accounts. If your ERP runs on a machine in your office, that one machine needs a small standard connector so the ERP can talk to the outside. Nothing custom, and nothing on anyone else's PC.

How do orders and quote requests get to Corvadex?

Mostly by email. Your team forwards an order to your private Corvadex address, so they choose exactly what Corvadex sees. If orders land in a shared inbox like orders@, you can have it forward them automatically later, once you're comfortable with that. Your inbox stays exactly as it is either way, and faxes that already arrive as email can be forwarded too.

Anything else goes in through the app: paste a text message, drop in a file, a scan or a photo, or dictate an order after a phone call. From there it's handled exactly like an email.

What about orders that come in by phone?

Your rep takes the call the way they do now. Afterwards they open Corvadex and say the order in one go, the way they'd read it back to the customer, or just type it in as a text. It becomes an order with every line matched to your catalog, the same as one that arrived by email. Nothing listens in on the call itself. Talking to a customer and to software at the same time makes a call worse.

Do you connect directly to WhatsApp, our fax line or our phone system?

Not yet. Email comes in through forwarding and everything else is entered in the app, which works without touching your phone or fax provider. I can build a direct connection if you need one, so if it would save your team real time, tell me what you use.

We get hundreds of emails a day and most are not orders. What happens to those?

Corvadex reads each forwarded email and works out whether it contains an order or a quote request. Questions about tracking, invoices, and general back-and-forth are set aside and never reach your ERP. If a single email contains several orders, they are separated and processed independently.

How does the team know when an order is ready?

Everything appears in the review queue as it arrives, and Corvadex can email whoever should be looking at them. Teams settle into different habits here - some keep the queue open all day, some work from the notification, and it matters more when several people share one inbox. I work this out with you during onboarding instead of making you fit one pattern.

How long does it take to go live?

Usually about two weeks once I have your past orders and access to your ERP. Most of that time goes into tuning the matching on your orders, not into installing anything. If your ERP is a bigger system I haven't connected before, it's closer to a month, and I'll tell you that up front rather than quietly running late.

What do you need from us?

Three things. First, 10-20 real past orders and quote requests from different customers, plus your catalog. The messier the better, because those are the ones worth tuning on. Second, access to your ERP, and someone on your team who will actually use Corvadex. Third, a call where you walk me through how orders reach you and how your team handles them today, since that's what the setup is built around.

The smaller decisions, like which fixes should happen automatically, we can sort out over email.

Accuracy and mistakes

What happens on a hard order, what happens when it's wrong, and how it gets better

How accurate is it?

It depends on your orders, so the honest answer comes from yours. Before anything goes live, I set Corvadex up and tune it on your past orders, so by the time your team uses it, it already knows your catalog and how your customers write. How it does on your orders is the number worth trusting, not a percentage on a website measured on documents you've never seen.

What happens when it's not sure about a line?

It works harder before it asks. A line that doesn't match your catalog directly is checked against what that customer has sent before, then against patterns learned from their past orders, then by name and description, and finally by an agent that searches your catalog and that customer's history. Asking a person is the last step, not the first.

Fixes work separately from matching. The safe ones - unit spellings, dates written in words, a missing ship-to - are fixed automatically, and the original is kept so you can undo it. Prices and quantities are never changed on their own: a price that's off your price list or a quantity under the minimum gets flagged for someone to apply or keep. A few things, like a line with no match, block the push until someone sorts them out. You can change what each check does.

Does anything reach our ERP without someone approving it?

Not unless you want it to. At the start, someone on your team accepts every order before it goes in. Once you trust it, you can let orders with no issues go straight through, and anything flagged still comes to a person. That's your call, whenever you're ready for it.

Can it get something wrong that nobody notices?

The realistic failure is a misread - a smudged digit on a scan, or a handwritten line that could be read two ways. A few things make that hard to miss. It never invents a product: a line either matches something in your catalog or is held for a person. The fields it was least sure about are marked, so attention goes where the risk actually is.

The original document sits beside the order while it's reviewed, so checking a quantity that looks odd takes a second rather than a search through your inbox. And every order keeps the source document, what was extracted from it, what changed and who accepted it, so if something does slip through you can see exactly where it happened.

What if it picks the wrong product?

You correct it in the review screen, and the correction is remembered for that customer. Next time the same part number or description arrives, it matches directly. Corrections are how the system learns your catalog, so the work is never wasted - it's the mechanism, not a workaround.

Does it handle scans and handwriting?

Yes. A scan or a photograph is converted to text first, then processed exactly like any other order, and handwriting is read the same way. Where a document is genuinely hard to read, that shows up as low confidence on the affected fields.

Does it get better over time?

Yes, and specifically for you. Every accepted match records what a customer calls a product against what you call it, and repeated patterns turn into rules. The first orders from a new customer might need some help. After that, most lines match on their own. That knowledge is about your catalog and your customers, and it stays yours.

Your ERP

Which systems Corvadex writes to, what gets created in them, and what happens when yours is not one of them

Which ERPs do you work with?

Most of them, including older ones. Cloud ERPs usually connect through their own API. On-premise systems connect through a standard connector on the machine that runs them. QuickBooks Desktop goes through Conductor, an established US company that specializes in exactly this. Green-screen, AS/400 and other systems without an API take more work, but there is usually a way in.

Two companies on the same ERP can run very different versions of it, so each connection starts with a discovery. You tell me what you run, I look at how it's set up, and you find out whether and how Corvadex can connect before anything is agreed.

Do you already have this working on our ERP?

Possibly not. Early customers get the integration built around their setup as part of onboarding, that is the trade for going early, along with pricing locked for a year and direct access to the person who builds it.

What exactly gets created in our ERP?

Whatever your team creates today. For orders, some distributors open a sales order, some go straight to an invoice, some raise a purchase order to their supplier with the end customer as the ship-to, and some start from an estimate. Quote requests become a quote or an estimate, whichever your ERP uses. Two companies on the same ERP often work differently, so we settle it when I set up the connection: which document, which fields it needs, and what should happen when one order spans several vendors and has to become several documents.

What if our ERP has no API?

That's more common than you'd think, and it rarely rules anything out. Green-screen, AS/400 and other older systems can usually be connected another way. It's more work, so it starts with a discovery where I find the way into your system. If there's genuinely no way in, I'll tell you.

Does anything change inside our ERP?

No schema changes, no migration, no new fields for anyone to maintain. Corvadex creates the same documents your team creates today. It does not restructure anything that is already in there, and your existing reports and processes carry on working.

Access, security, and your data

Who you are granting access to, what that access can do, and where your data goes

Who are we actually granting access to?

For QuickBooks Desktop, the connection is authorized to Conductor, an established US company whose whole business is this connection, through QuickBooks' own Web Connector. For other systems you generate credentials yourself, inside your own account, and hand over only what is needed.

Can we revoke access?

At any time, in one step, from your side. For QuickBooks Desktop that means removing the connection in the Web Connector, for other systems it means revoking the credentials in your own account. None of it needs anything from Corvadex.

Could Corvadex damage or delete something in our system?

Corvadex creates orders and quotes. It does not edit or delete existing records, and it does not restructure anything. If that is still more than you want to take on in week one, start without connecting the write side at all. Check the next question.

Can we run it without connecting the write side at all?

Yes, and it's a good way to start. Orders are read, extracted and matched, and you watch them come through the app while your team carries on exactly as they do today and nothing is written to your ERP. You turn the write side on when the results have earned it, on your schedule.

What data does Corvadex touch?

The emails you forward, whatever your team enters in the app, and the parts of your ERP needed to process orders and quotes: your catalog, your customers, your pricing, and your past orders (where they help matching). Everything on the ERP side other than creating orders and quotes is read only. Corvadex never reads your inbox, only what you forward to it.

Do you use our data to train AI models?

No. Your orders and your catalog are used to process your orders and to improve matching for your account. They are not used to train models, Corvadex's or anyone else's, and they are not shared with other customers. Corvadex does keep records of how orders were processed, so failures can be found and fixed - those stay internal and are used for nothing else.

Where is our data stored?

On servers in North America, encrypted in transit and at rest. Your data is tied to your own account, and no other customer can see it.

Who at Corvadex can see our orders?

Today, one person: me, and only to run your onboarding and fix problems. As that changes, access will stay limited to people who need it to support you.

Is there a record of what happened to an order?

Every order keeps the original document, the values that were extracted from it, every change with the reason for it, and who accepted it and when. It's usually a better record than a manual process.

About Corvadex

Who builds it, what going early actually means, and what happens if Corvadex is not here

Who is behind Corvadex?

I am Denys Bondarenko, a software engineer, and I build and run Corvadex. I do the onboarding, the ERP integrations and the support myself, so the person who answers your email is the one who can fix it. There is more about me and why I am building this on the about page.

Corvadex is in private beta. What does that mean for us?

It means I onboard you myself. I set Corvadex up on your past orders, connect your ERP and tune the matching to your customers, and that onboarding is free. Then you use it on your real orders for a month before paying anything.

It also means the connection to your ERP may get built as part of your onboarding, what you ask for gets built first, and when something's off you talk to the person who built it, not a support team. The price after the free month is agreed in writing before we start, and it's locked for a year, below what later customers will pay.

Why would we go first instead of waiting?

Because the terms are better and there's little to lose. Onboarding is free, and you use Corvadex on your real orders for a month before paying anything. Your rate is locked for a year at a level later customers won't get, and the product gets bent around how you work rather than the other way round. You can even start with nothing written to your ERP, so trying it costs you some time and nothing else.

What happens to us if Corvadex goes away?

I do not plan to go anywhere. But in practice, if Corvadex disappeared tomorrow, it would matter less than you might expect. Your ERP is the system of record and keeps working exactly as it does now. Corvadex sits in front of it, so if it disappeared tomorrow your team would go back to typing, and nothing would be lost or need rebuilding. Your data is yours and exportable at any time, and you pay monthly, so there is nothing to unwind.

Pricing and terms

How it's priced, what you are committing to, and what happens if it does not work

What does it cost?

It's a monthly price based on how many orders and quote requests you process, with unlimited users. It follows the work taken off your team, not the number of people on it. I quote it on a call once I know your volume and what your orders usually look like.

Is there a setup fee?

Not for early customers. Onboarding is free, and so is your first month live. That covers setting Corvadex up and tuning it on your past orders, loading your catalog, and building the connection to your ERP if it doesn't exist yet. The one exception is an old system with no API, where connecting is real extra work. That gets its own price after a discovery, before you commit to anything.

What are we committing to?

Not much. Before we start, we agree in writing on what it costs after the free month, what gets built and how long it takes. After the free month you pay monthly and can stop whenever you want. The rate is locked for twelve months, which protects you from increases without tying you in.

What if our order volume changes?

Every three months the price follows your actual volume, up or down, and you get notice before it changes. Nothing stops working if you go over, and if volume drops, so does the bill.

What if it does not work?

Then you don't pay. I set Corvadex up on your past orders first, and if it turns out not to be a fit for your orders, we stop there, before anything gets built. After go-live you have a month on your real orders before any billing starts, and you can cancel any time after that.

So you can try it absolutely for free and risk-free for a month before committing to anything.

How do we start?

Email me. The first conversation is fifteen minutes about how orders and quote requests reach you today and what your ERP is, and you will know by the end of it whether this is worth either of our time.

Still have a question?

If something is unclear, or your situation is not covered, email me directly for more details

Denys Bondarenko

Denys Bondarenko, Founder

I answer every email and onboard every customer