Glossary
- User
- Admin
The words the documentation uses for each concept, in English, Dutch and French; one word per concept, never a second word for style.
| Term (en) | nl | fr | Meaning |
|---|---|---|---|
| inquiry | aanvraag | demande | One incoming message or document, such as an e-mail with its attachments, an API call or an EDI file, that Hyperfox turns into one or more orders. Processing, retry, reject and the lock act on the whole inquiry. See Inquiries, orders and lines. |
| order | bestelling | commande | One order a customer places, inside an inquiry: what you check and validate, and what Hyperfox sends to your ERP. See Order. |
| split inquiry | gesplitste aanvraag | demande répartie | An inquiry with two or more orders. Its orders are called orders, never split orders or sub-orders. See How a split inquiry works: one document, several orders. |
| line | regel | ligne | One item on an order, with its quantity and unit. See Line. |
| validate (approve) | valideren | valider | Confirm an order after checking it, so Hyperfox sends it to your ERP. See Validate an order: check it and send it to your ERP. |
| retry (re-run extraction) | opnieuw proberen | réessayer | Let the AI read the whole inquiry again; every order of the inquiry is replaced. See Retry an order so Hyperfox reads it again from the start. |
| route | route | route | A bucket on a mail channel that decides which mapping reads an incoming mail; see Routes. |
| mapping (AI mapping) | mapping | mapping | The document that tells the AI what to extract and how. A column mapping in an import is a field mapping, an EDI configuration an EDI mapping, and an export template is never called a mapping. See Mappings. |
| Forward E-mail channel | Doorstuur-e-mail | e-mail transféré | The channel that receives orders you forward to your Hyperfox address. See Channels. |
| Microsoft 365 | Microsoft 365 | Microsoft 365 | The channel that reads orders from Microsoft 365 mailboxes you connect. See Channels. |
| reference data | referentiedata | données de référence | Your lookup lists, such as items, customers and units, that Hyperfox matches orders against. See Add, edit and delete reference data records. |
| entity | entiteit | entité | One kind of record: the order, the line, or one reference data list such as items or customers. The admin screen still calls it an asset type. See How the order model and the reference data lists work. |
| record | record | enregistrement | One record in a reference data list. The app's own buttons say entry (Add entry, Delete entry). |
| picker | keuzelijst | sélecteur | A field that takes a record from a reference data list; type to search, and the list shows what the admin set as the main text and second text. See Change what a picker shows. |
| Codex entry | Codex-vermelding | entrée Codex | One record in Codex, the rules Hyperfox learns from corrections. See How Codex learns from your corrections. |
| extraction instruction | extractie-instructie | instruction d'extraction | The text in an AI mapping that tells the AI what one field means and where to find it. See Steer how the AI reads a field. |
| accuracy | nauwkeurigheid | précision | How complete the AI's result for an order is, as a percentage. Not a measure of whether the values are right. See How Hyperfox reads and fills in an order, step by step. |
| base unit | basiseenheid | unité de base | The smallest unit of an item. Hyperfox sends stock-order lines to your ERP in the base unit. See How quantities and units are read and converted. |
| connection | verbinding | connexion | One FTP, API, OAuth or S3 connection record on the Integrations page. see Integrations. |
| order model | — | — | The order and its lines as Hyperfox set them up for your environment, a stock order or a transport order, with their fields and relationships. See How the order model and the reference data lists work. |
| organisation | organisatie | organisation | A customer of Hyperfox. Use environment for its host names; tenant appears only in the API documentation. |