Skip to main content

The unit is wrong: boxes became pieces, or a pallet became a box

  • User
  • Admin

The unit on a line of an order in To validate is not the unit the document gives. Correct the unit on the line and validate.

If the same wrong unit returns for the same customer and item on every order, check Codex first. To correct the unit, follow Change the quantity and the unit. How quantities and units are read and converted explains how Hyperfox reads and matches the unit.

The same wrong unit comes back for one customer and item​

The document says pallet, and every order from this customer for this item gets box, or the reverse.

Cause: A Codex entry sets this unit. A colleague changed the unit on an earlier order from this customer for this item and validated that order. Codex now applies that unit for that customer and item whenever Hyperfox reads a similar unit word. A unit entry is limited to that customer and that item. How entries apply is explained in How Hyperfox uses entries and Scope: for which orders an entry counts.

Fix:

  1. Correct the unit on the line. To correct it, follow Change the quantity and the unit.
  2. Click Codex.
  3. Click Filters and filter Field on your unit field.
  4. Look for an entry whose Scope shows this customer and this item. The entry shows the unit the document gives after AI matched: and the wrong unit after Changed to:.
  5. To see the order the entry came from, point to the row and click Source Order (eye).
  6. If the entry is wrong, switch it off or delete it.

Find an order and check where it is shows how to find who validated the source order. If no such entry exists, an admin can check which entries Hyperfox used on this order.

For next time, before you change a unit and validate, check that the unit is right for every order of that customer and item. Validating records a Codex entry for that customer and that item.

Boxes became pieces: the unit is not one of the item's units​

The document says boxes, the line has the same number in pieces, and the unit picker on the line has no box.

Cause: In a stock order, every item has its own units. When Hyperfox reads the document, it can read a unit that is not one of the item's units, or no unit at all. The unit check then replaces that unit with the item's base unit and keeps the quantity, so 12 boxes become 12 pieces. If the item has no units of its own, any unit is allowed and the line keeps the matched unit. This is a gap in your reference data, not a reading error. The unit check: why boxes can become pieces explains the check.

Fix:

For next time, ask whoever maintains your reference data to add the unit to the item's units, with its Base unit quantity. Once the box is one of the item's units, the line keeps the box.

The document gives two units or two quantities for one line​

One line names two packagings, such as a pallet of 48 boxes or 10 kg in bags of 2 kg. It can also give a number of outer boxes next to a number of pieces. The line took the unit or the quantity you did not want.

Cause: Hyperfox records every quantity and unit it reads on the line and then keeps one of each. For the unit, it keeps one of the item's units. If both units are among the item's units, nothing tells Hyperfox which one this customer means. On a spreadsheet, it takes the quantity from one column only. The quantity and the unit can then come from different packagings.

Fix:

  • Set a quantity and a unit that belong together, for example 1 pallet or 48 boxes, never 1 box. In a stock order, the hint under the quantity shows what your ERP receives.

If the unit you want is not in the unit picker, the unit is not one of the item's units. If the quantity came from a column of pieces while the customer meant the column of packages, the fix is under The quantity comes from the wrong column.

For next time, ask your admin to state in the instructions on the unit field and the quantity field which packaging to take. Example: "When a line gives pallets and boxes, always take the pallets and their number." Another example: "When the customer gives outer boxes, take that number. Otherwise take the quantity." Steer how the AI reads a field has more examples.

Codex learns a unit you changed, but never a quantity. After you change both, the next order from that customer for that item can get your unit with the document's quantity. Which corrections become an entry lists what Codex learns.

The customer's word for the unit is not recognised​

The customer writes "pakje", "colli", "overdoos", "PAL" or "P", and the line gets a different unit, often for every item that customer orders.

Cause: Hyperfox matches the unit word on the line to your list of units. It searches the unit code and the other columns your admin set as searchable. A word your list does not hold, or an abbreviation only one customer uses, can match the wrong unit or none. So can a letter that means one thing in Dutch and another in French, such as "P" for pallet or for pièce. If the word matches no unit, the line gets the item's base unit. How the unit is chosen is described in How quantities and units are read and converted.

Fix:

For next time, if the word returns for other items or other customers, ask your admin to add the customer's unit words to the instruction on the unit field. Example: "'Doos', 'ds' and 'overdoos' mean the box unit. 'PAL' means pallet. On French orders, 'P' means piece."

For a word that every customer or every item uses, ask your admin for an instruction on the unit field. For a word that belongs to one customer and one item, correct the unit and validate.

The unit in Hyperfox is right, but your ERP receives another unit or number​

You validated 20 boxes, and your ERP shows 240 pieces, or a number of pieces you did not expect.

Cause: In a stock-order environment, Hyperfox converts every line to the item's base unit when it sends the order. Hyperfox multiplies the quantity by the Base unit quantity of the line's unit and rounds the result up to a whole number. Hyperfox sends these lines unchanged: lines already in the base unit, lines without an item and lines whose unit has no entry for the item. Hyperfox never chooses the smallest unit by itself. How quantities and units are read and converted shows what Hyperfox sends.

Fix:

  • Before you validate, read the hint under the quantity, such as "→ 240 × Piece". The hint shows what your ERP receives. A line already in the base unit has no hint.

If the number is wrong, ask whoever maintains your reference data to check the Base unit quantity of that item and unit.

For next time, ask whoever maintains your reference data to keep the item's units right. The conversion uses only the item's units and their Base unit quantity.

Still wrong?​

If the problem persists, contact support at [email protected]. Mention the inquiry id, the line, the unit the document gives and the unit on the line. How to report a problem with an order to support names what else to send.

See also​

Last updated on