AI in trade: units and packs in an order

The product name does not tell you the pack size

In a fictional order, a client asks for 10 cartons of product A. The current product record says 12 units per carton. The result is 120 units, as long as the record really covers the variant ordered. If a similar product B has 24 units recorded, that number cannot be used to convert A.

GS1 US distinguishes packaging levels, including the single unit, the inner pack and the case. The description shows why a product code should be tied to the way it is packed. It does not mean that every supplier uses the same number of units. Packaging level definitions, checked on 9 October 2026.

If the order says only „10 packs” and the company handles several pack sizes, leave the line for clarification. The client's answer should go into the case, so the warehouse does not have to reconstruct the agreement again.

If a wholesaler accepts item codes assigned by its clients, check the buyer first. The same code can mean a different product at two companies, and a change of the assigned customer requires the line to be assessed again. The client's item code is matched before the unit and the conversion are checked.

Keep the original wording before the conversion

Next to the draft line, show the source text, the product code, the unit ordered, the conversion and the result in the stock unit. A final number on its own makes it hard to judge whether a mistake came from reading, matching the product or multiplying.

Do not overwrite a historical conversion with a new one only because the product record changed. The process owner should decide which terms apply to an order already accepted. The table above is an exercise, with no integration running.

When do you need a model?

With a tidy file and agreed codes, an import and a conversion rule are enough. AI can help extract data from messages written in many different ways. Saving to the order system, spotting a repeated order and handling a correction need further rules; reading one email correctly does not prove they work.

Before you build, check the features of the sales system you use. If the difficulty is the supplier's later reply, a separate guide covers comparing an order with its confirmation.

Once the conversion is agreed, you still have to choose the document type in the order system and check what creating it sets off.

On the purchasing side come the labels suppliers use. Keep global unit synonyms apart from names assigned to a supplier and a product. Recognising the word „shrink pack” still needs a separate confirmation of the number of units in the pack.

A correct conversion then has to be tied to the document, the reservation and the agreed stage of fulfilment.

Syntalith builds automations. A possible first scope is a list of lines for approval, with the source and the conversion visible. We price the integration with the system and the cases of ambiguous packs after reviewing the materials. Syntalith prices: an automation, app or agent from €3,000 net, training from €1,150 net a day (pricing). It is enough to describe an order that recently came back from the warehouse for correction.

What it costs

Where to start

In the free review we choose one process and count the volume and the team's working time, and within 2 working days you receive a written summary with a price. We build the automation as part of AI automations, from €3,000 net.