Mapping Your ERP
This page is an equivalence table between common concepts in logistics or agri-industry ERPs and the DigiAnt schema fields. Its purpose is to reduce pre-integration analysis time.
Equivalence table
| Common ERP concept | DigiAnt field | Notes |
|---|---|---|
| Transport order ID, delivery note, CMR | externalId (text) | Required. The document ID in the ERP. DigiAnt uses it for idempotency — retrying with the same externalId does not create duplicates. |
| Tonnes, kg, litres, m³ | quantity (decimal number) | Free unit — DigiAnt does not validate it. Agree on the unit with the DigiAnt team during onboarding. |
| Product, goods, grain, cereal | productId (UUID) | UUID from the DigiAnt product catalog. Query with GET /partner/products. The response returns the name as product. |
| Batch, lot, campaign | batch (text) | Optional — free text. |
| Packaging format, container | format (text) | Optional — free text. |
| Customer, shipper, cargo owner | productOwnerName / productOwnerCif / productOwnerPhone / productOwnerEmail | All required. |
| Loading point / sender | operationType: "loading" + partnerName / partnerCif / partnerPhone / partnerAddress / partnerWarehouseCode | All partner* fields required. |
| Unloading point / receiver / consignee | operationType: "unloading" + partnerName / partnerCif / … | Same partner* fields. |
| Carrier company | carrierTaxId (NIF/CIF, text) | DigiAnt resolves the tax ID to its internal UUID. The carrier must be registered in DigiAnt; if not found, returns 422. |
| Driver (on creation) | driverNif (NIF, text) | Optional in push. DigiAnt resolves it to an internal UUID. |
| Driver (on update) | driverNif (NIF, text) via PATCH /authorizations/{id} | Same format as on creation. DigiAnt resolves it to its internal UUID. |
| Tractor plate / truck head plate | tractorPlate (text) | Optional — 1 to 8 alphanumeric characters, normalized to uppercase. |
| Trailer plates, semi-trailer plates | trailerPlates (array of text) | Optional — empty array by default. |
| Facility, silo, plant, logistics center | totemGroupId (UUID) | The physical "where" in DigiAnt — query with GET /partner/totem-groups. |
| Bay, silo, internal warehouse reference | warehouseId (UUID) | UUID from the DigiAnt warehouse catalog. Query with GET /partner/warehouses. The response returns the reference as warehouse. |
| Expected load/unload date | scheduledDate (ISO datetime) | Omit for weight-based authorizations with no fixed date. |
| Expiry date / end of validity | endDate (ISO datetime) | Optional. |
Common transformation patterns
Quantity units
Agree with the DigiAnt team on the unit to use (metric tonnes is most common for dry bulk). The unit is not validated or stored alongside the value — a scale error (kg instead of tonnes) is stored silently and affects weighing reports.
Carrier identification
The Partner API accepts the carrier's tax ID (NIF/CIF) directly in the carrierTaxId field. DigiAnt resolves it to an internal UUID at creation time. The carrier must be registered in DigiAnt beforehand; if the tax ID is not found, the request returns 422.
Driver identification
On creation, pass the driver's NIF in driverNif. DigiAnt resolves it to an internal UUID.
To update the driver later, use PATCH /authorizations/{id} with driverNif (NIF). Same format as on creation — DigiAnt resolves it to its internal UUID.
Authorization status
Authorizations created via the Partner API are always born in Active state — status cannot be set at creation time. To end an authorization, call POST /authorizations/{id}/cancel, which marks it as Finished. The status field in responses returns "Active" or "Finished" (capitalized).
License plates
DigiAnt normalizes plates to uppercase automatically. You may send them in any capitalisation. Only alphanumeric characters (A–Z, 0–9) are allowed — hyphens, spaces, or other special characters produce a 400 error.