How FRB works

Product matching with visible exception review

Product matching is an important part of sales order automation. Customers may order the same item under different names. FRB uses your product catalogue and confirmed aliases to match line items, while unknown items and ambiguous matches are sent for review.

The product catalogue is the starting point

The business adds a product catalogue, for example as CSV. FRB compares order lines with SKUs, product names and registered GTINs where available. Text is normalised for comparison, but similar names alone are not grounds to select a different product.

Confirm a name once

A confirmed alias can be saved for future orders. It can apply across the business or to a particular sender. Sender-specific aliases let the same expression refer to different products for different customers.

These are stored rules, not language-model self-training. A correction does not promise that every future variation will be understood. New names, changed document layouts and conflicting information may still require review.

Uncertainty should be visible

Unknown products, ambiguous matches, unusual quantities and possible duplicates can trigger warnings. A staff member compares the draft with the original, corrects it where needed and approves it before export.

The product catalogue and aliases belong to the business. Another business’s corrections must not change how your products are matched.