From any inbound format, straight into your systems.

Each document becomes its own job, and the original file or message is kept against the order it produces. That original is the start of the audit trail: anyone can open the order later and see exactly what the customer sent.

Very large documents get a first pass that finds where one order ends and the next begins, so a long PDF of store allocations is split before it is read. A document too large to process safely is set aside for a person rather than half-read.

Every field carries a confidence score. A clearly printed PO number scores high; a smudged quantity on a phone photo scores low. The score decides what happens next, so your team only looks at the fields that need a second pair of eyes.

Documents with several orders inside are split into one order each, and Weeva never invents a figure. If a subtotal is missing it is computed and labelled as computed. If the printed total disagrees with the lines, both are kept and the order is flagged.

Then every line. A 13-step matching algorithm combines deterministic and statistical methods with frontier LLMs and reasoning models to match the customer's product description to your exact product code. A line it is still unsure of is flagged for a person to confirm.

Match Memory sits over all of this. It learns how each customer has ordered before and remembers the amendments your team makes, per customer. Once your team confirms that a customer's "Cola 500 x12" is your COLA-500-PET-12, that answer is used for that customer from then on. The same memory holds each customer's units and pack sizes, so an order for "1 case" and an order for "12" both land correctly.

Anything that needs a person gets a review reason in plain words. Hard reasons stop the order until they are resolved, such as a missing required field, a customer not in your list or a product not in your catalogue. Soft reasons ask for a quick check, such as a low-confidence field or a total that does not add up.

Weeva also compares every new order with recent ones on PO number, customer, dates, totals and lines. A likely duplicate is held for a person to confirm or dismiss before it can be captured twice.

Every push carries a unique key, so a retry after a dropped connection can never create a second sales order. Businesses with more than one company in the ERP have each order routed to the right one. If a customer does not exist in the ERP yet, the operator is offered the option to create it; Weeva never creates one on its own.

When the push succeeds, the ERP's own reference is recorded against the order with a link straight to it. When it fails, the error is shown to the operator in plain words and nothing is retried silently.