FAQ

What does Corvadex actually do?

Corvadex reads the purchase orders your customers email you and turns them into complete orders in your ERP. It handles PDFs, spreadsheets, scans, and orders typed into the body of an email. 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 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 emailing the same address, 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 not our call to make.

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.

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 get to Corvadex?

You add a forwarding rule on the inbox where orders already arrive, pointing at your own private Corvadex address. Nothing about how mail reaches you changes. A copy is simply forwarded on, and your original inbox stays exactly as it is.

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. Questions about tracking, invoices, and general back-and-forth are set aside and never become orders. If a single email contains several orders, they are separated and processed independently.

How does the team know when an order is ready?

Orders appear in the review queue as they arrive, 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. We work this out with you during onboarding instead of making you fit one pattern.

How long does it take to go live?

Around two to three weeks, starting from the point where we have a connection to your ERP and a batch of your real past orders. Most of that time goes into tuning the matching against your own orders, not into installation. If your ERP is one we have not connected to before, we tell you up front and plan for longer rather than quietly running late.

What do you need from us?

A connection to your ERP - your catalog and customer list are pulled from there and kept up to date, so there is nothing to export by hand. Thirty or more real past orders, different formats and customers, the messier the emails the better, since those are the ones worth tuning on. And a call to walk through how orders reach you today and how your team handles them, because that is what the setup gets built around. Smaller decisions, like what should be fixed automatically and what should be flagged for a person, we can settle in text.

How accurate is it?

It depends on your orders, so we measure it on yours. Before anything goes live we run your real past orders through the system and you see exactly what it got right and where it needed help. That number, on your own order mix, is the one worth trusting. Not a percentage on a website, produced from documents you have never seen.

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

It works harder before it asks. A line that does not 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 are separate from matching, and they are yours to configure. Unit conversions, date formats, a price that differs from your records - for each kind, you decide whether it's applied automatically or warned and held for someone to look at. What actually reaches a person is genuine ambiguity: two products that both fit, a quantity that cannot be read, a line with nothing to match on.

Does anything reach our ERP without someone approving it?

Not unless you decide it should. Corvadex starts in Copilot mode, where every order is reviewed and accepted by a person before anything is sent. Later you can let clean orders pass on their own and keep review for the rest. That is a setting you control, and you move it one step at a time.

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.

Which ERPs do you work with?

Corvadex is early, and each ERP connection is built deliberately. Most connect directly. QuickBooks Desktop goes through Conductor, an established US company that specializes in exactly this. Tell us what you run and we will tell you within a day whether it's possible to connect and what connecting would involve.

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. Nothing is charged before we have confirmed the connection is possible.

What exactly gets created in our ERP?

Whatever your team creates today. 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. Two companies on the same ERP often work differently, so we settle it when we set up the connection: which document, which fields it needs, and what should happen when one incoming order spans several vendors and has to become several documents.

What if our ERP has no API?

Then we say so before you pay. Some systems genuinely have no usable connection path, and no amount of goodwill changes that. We will tell you what we find, and if it's not workable today we will keep you on the list for when it is.

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.

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 requires our cooperation.

Could Corvadex damage or delete something in our system?

Corvadex creates orders. 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 order emails you forward, and the parts of your ERP needed to turn them into orders: your catalog, your customers, your pricing, and your past orders (where it helps matching). Everything on the ERP side other than creating orders is read only. We do not read your inbox generally, only what your own forwarding rule sends us.

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, ours or anyone else's, and they are not shared with other customers. We do 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.

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 closed beta. What does that mean for us?

A small number of customers, each onboarded personally, at pricing locked for a year below what it will later be. It also means that the connection to your ERP may be built as part of your onboarding, that what you ask for is prioritized, and that you deal with the person building it rather than a support team. There is a written scope and a money-back guarantee behind all of that, so it's not something you have to take on faith.

Why would we go first instead of waiting?

Because the terms are better and the risk is capped. You get a rate locked for a year that later customers will not get, the product bent around how you actually work rather than the other way round, and a guarantee that returns your money if it does not do the job. You can also start with nothing connected to your ERP, which means the practical downside of trying is some of your time and none of your systems.

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.

What does it cost?

Pricing is per order processed, billed as one clean monthly figure. Unlimited seats and users. It tracks the work taken off your team, rather than the number of people in it. We quote it on a call once we know your volume and what your usual orders look like.

Is there a setup fee?

Not for early customers. The first payment covers setup and your first month live. During setup we build the integration with your ERP if it does not exist yet, load your catalog, run your past orders through the system, and tune matching to your customers' habits.

What are we committing to?

Nothing long. You pay monthly and can stop whenever you like. The rate is locked for twelve months - it protects you from later increases without obliging you to stay. Everything agreed goes in writing before any work starts: what will be built, what it costs, how long it takes, and what happens if it does not work.

What if our order volume changes?

We adjust together on the same per-order basis instead of renegotiating. If volume drops, the monthly figure drops too.

What if it does not work?

Once we have everything needed - the payment, your sample orders, and the ERP connection - if your orders are not processing correctly within three weeks, you get the payment back. We only keep money for a working system.

How do we start?

Email me. The first conversation is fifteen minutes about how orders 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.