A workplace from customer orders, without people

Customer orders

The customer's order arrives by email as a PDF, and someone retypes it line by line.

Arhivix takes the order attached to an email from the mailbox you connect and reads its header and its lines with the order document type you set up. Once it is read, an order that meets your condition goes for approval, a person on your team confirms the values next to the original, and every order is a row in a register you build and export to Excel or CSV. Entering the sales order stays in your ERP.

How the process runs through Arhivix.

Arhivix does every step below today.

  1. The order type

    Works today

    You set up an order document type once: header fields such as the customer, the order number and the requested delivery date, and a Table field for the lines, with columns such as item code, description, quantity and unit. The Type assistant proposes the fields from sample orders you drop in, you review the proposal before applying it, and you test the type on a document and publish it.

  2. Intake from the mailbox

    Works today

    You connect the mailbox where orders arrive, a Gmail account with a label or a filter, or a shared mailbox in Microsoft 365 with a folder, and link it to your published order flow. From the moment you turn the source on, the attachments of every new message in that label, filter or folder go to processing and are kept in the archive you choose.

  3. Reading the header and lines

    Works today

    Arhivix reads the order with your type: the header values and the rows of the lines table in the order they are printed, each value with the page it was read from. Every read value is a proposal until a person confirms it. An attachment that does not clearly match one of your types waits under Document classification for a person to choose the type.

  4. Your condition on the order

    Works today

    Once the order is read, a Check a condition step in your order flow tests a header value as it was read, for example whether the total is above an amount you choose or the requested delivery date falls within the next few days. The order then takes the Yes or the No path, and a value that cannot be read sends it to review.

  5. Order approval

    Works today

    A Send for approval step on that path puts the order in Business approvals for the person or role you choose, with up to five approvers in a row and escalation to a role after the minutes you set. The approver sees the original and the read values and approves or rejects with a reason. With a single approver, the approval can also confirm the read values.

  6. Check against the original

    Works today

    In Document data the original and the read values sit side by side. A person checks the values and confirms them with Confirm all values, the lines table included, and corrects a value read wrong, such as a number, a date or an amount, with a written reason. Every confirmation and correction stays in the Value history, and the original stays unchanged.

  7. Orders register

    Works today

    In document processing you build a register with one row per order and the columns you pick from the order type, such as customer, order number, delivery date and total, plus the system columns Received at and Source. Filters compare confirmed values, saved views keep your lists, and from any row you open the order with its original.

  8. Handover to order entry

    Works today

    With the Move the document and Notify in the app steps you add after the approval, the flow moves the order to the folder you choose and notifies the person who enters orders. Entering the sales order stays in your ERP, and that person works from the values next to the original in Document data, where each value shows whether it has been confirmed. You export a register view to Excel or CSV, one row per order with the columns you picked and the status of each value.

The same job in different industries.

Bills for subscriptions, equipment and commissions arrive at three email addresses, and each venue reads only its own.

A bill nobody opens does not reach your accountant in time, and sometimes the same bill arrives twice.

commission_0915.pdf Filed
  • Arrived at reception@company.com
  • Folder Supplier invoices / Commissions
Possible duplicate: the same bill also arrived at invoices@company.com
Arhivix today
Connect the inboxes of every venue (Gmail, Microsoft 365 or IMAP), and Arhivix reads each attachment and files it by a rule; uncertain ones wait for your approval in Smart Inbox. When the same bill arrives twice, Arhivix flags it as a possible duplicate, and you decide.

A customer asks for a copy of the March delivery note, and the only person who knows where it is, the warehouse keeper, is on holiday.

Sales loses hours searching, and while the customer waits for an answer, so does your payment.

delivery_note_3117.jpg Shared
  • Interpreted as Velmora Retail · March
  • Customer link 7 days, password
Log: share link accessed 11:02
Arhivix today
You describe what you need, and search understands the document type, partner and date and reads the text of scanned paper too. The copy goes out as a link with an expiry date and a password.

You shipped a hundred, the customer says ninety-⁠eight arrived, and the complaint comes a month later without a single paper.

A quantity dispute ends in a reduced invoice you never planned, and sales spends days rebuilding the delivery.

complaint_4518.pdf Auto-filed
  • Folder Customers / Velmora Retail
  • Already there Signed note, photos
Rule: sender Velmora Retail Ltd
Arhivix today
At the dock you photograph the goods and the receiving record with the phone into the customer's folder, next to the signed delivery note. A complaint that arrives by email can be filed there by a rule.

It starts without a project.

  1. Connect the company inbox or upload your existing folders, and Arhivix reads everything in the background.

  2. Paper from the field is photographed with the phone or scanned; Arhivix proposes the type and the details, and you confirm.

  3. Confirm an inbox rule once: next time such an attachment files itself, and uncertain ones wait for your approval.

For more than 20 accounts and for agencies

One conversation about your flows, migration and the programs you use. We answer within one working day.

Request a quote

For small companies

No card needed. Paid plans are priced per company, not per user.

Content search and AI search come with every paid plan.

Try the free plan

Public pricing, per company

The Arhivix Lite plan is free and needs no card. Paid plans are priced per company, and even the smallest includes 5 user accounts, with no per-user pricing. For more than 20 accounts we prepare a custom quote.

See plans and prices

Frequently asked questions

Connect the mailbox where they arrive to your published order flow and turn the source on: a Gmail account with a label or a filter, or a shared mailbox in Microsoft 365 with a folder. Arhivix takes the attachments of every new message in that label, filter or folder and reads them with the order type you set up, and a person on your team confirms the values next to the original.

With a Table field in your order type, whose columns you choose, such as item code, description, quantity and unit. Arhivix reads the rows in the order they are printed, each value with its page, and a person confirms the table after comparing it with the original.

In the order flow, a Check a condition step tests the total as it was read, and a Send for approval step sends orders above your amount to the person or role you choose, in Business approvals. The approver approves or rejects with a reason, and the decision stays in the Review history.

Entering the sales order stays in your ERP and with the person who does it. With a Notify in the app step after the approval in your order flow, Arhivix notifies that person when an order is approved, and in Document data that person sees the values next to the original, each showing whether it has been confirmed. You export the orders register to Excel or CSV, one row per order with the columns you picked.

Mark that field as required in your order type. For an order read without it, Document data shows Required data missing, and at a Send for approval step with one approver the approval waits until the approver enters the value from the order or from the customer, with a reason for the entry.

The person who enters an order records it in the order's notes, with a Business label such as Entered and the Responsible person. Notes columns you add to the orders register show both, and every change keeps who made it and why.

Request a quote. You then set up the order document type with the Type assistant and a few sample orders, test it on a document and publish it. After that you save the mailbox as a source, build the order flow on it with a sample order and publish it, turn the source on, and build and publish the orders register.

You upload your existing folders or connect your email inbox, and Arhivix indexes everything in the background. Standard plans need no migration project and no consultants. With an Enterprise contract, your existing archive is moved in with its folder logic, metadata and retention dates preserved.

Absolutely. You can cancel from your account settings with one click. Your data remains accessible until the end of your current billing period. After that, your account is paused and you have 30 days to export your data.

Can't find your answer? Write to us at support@arhivix.com

Send your first document. Arhivix organizes it.

Request a quote Try the free plan

No commitment, no credit card.

NOTIX DOO Beograd · MB 21993310 Verify the registration number in the public APR business register (opens in a new window) · PIB 114240716

Dušana Matića 26, 11000 Belgrade

Monday to Friday, 09:00 to 17:00 CET

Invoice_Hansa_118.pdf Forwarded
  • Arrived by email 14:32
  • Read, details confirmed
  • Checked in the field and approved
  • Forwarded to your accountant and your software

Next: your first document

Footage: Pexels (Tima Miroshnichenko), Pexels License.