F-E-001

Required {fieldType}(s) {fieldName} is/are missing or blank

The field is mandatory. It cannot be absent or empty.

• Example: if a mandatory custom field is missing, the missing CF(s) will be returned.

If several fields are missing, they will be listed as follows: ‘Required {fieldType}(s) {fieldName#1} or {fieldName#2} is/are missing or blank’.

F-E-002

At least one {fieldName} does not exist in Djust system : {unknownFieldValues} with type {idType}

The field corresponds to a reference. It must exist in the Djust system. For example, it could be an external reference to update an object (an offer, a product, etc.). The idType indicates the type of id that is used, for example: 'EXTERNAL_ID'.

F-E-003

Unique reference {fieldName} already exists in Djust system

The field is a reference that already exists in the Djust system. As it must be unique, the line is rejected.

F-E-004

DEPRECATED ERROR - Use F-E-012 Instead Wrong format for field {fieldName}, expected standard URL format

The field does not follow the standard formatting pattern for URLs: http(s)://(www).extension(:port)/*.

F-E-005

DEPRECATED ERROR - Use F-E-012 Instead Wrong format for field {fieldName}, expected a number

The field does not have the expected number format.

F-E-006

Field {fieldName} has to be {numberCondition} to {value}

The expected number cannot be {strictly less than / less than or equal to / strictly greater than / less than or equal to} a given value.

F-E-007

Field {fieldName} is not in the correct range, expected a value between {range}

The expected number must be in the range between X and Y.

F-E-008

Unexpected value {value} for field {fieldName}, must be one of {enumValues}

The expected value is not good, it must be part of a predefined list of values.

F-E-009

DEPRECATED ERROR - Use F-E-012 Instead Wrong format for field {fieldName}, expected a boolean

The field does not have the expected Boolean format: false or true.

F-E-010

Size limit exceeded for field {fieldName}, must be lower than {limitSize} characters

The field must be less than X characters long. For example, a telephone field must be no more than 15 characters long.

F-E-011

Missing mandatory attributes {missingAttributes} required for classification category {classificationCategoryName} / {classificationCategoryId}

The mandatory classification category attributes associated with the inserted product are not filled.

F-E-012

Field {fieldName} does not respect expected format {fieldType}

The field does not match the expected format. For example, when importing attributes into the product flow, if the field is a list and the type is TEXT, an error is raised.

F-E-013

No price range defined for quantity = 1

There is no price range for this offer for a quantity of 1. There must be at least one unit price.

F-E-014

Incorrect offer type value, expected ACCOUNT

If a valid external account id is entered for an offer, the offer type must be ACCOUNT.

F-E-015

maxOrderQuantity can not be lower than minOrderQuantity

The maximum orderable quantity must be greater than the minimum orderable quantity.

F-E-016

The number of {fieldName} elements is limited to {maxListSize}

The number of items expected for a list is finite and cannot exceed a limit. For example, the number of associated products is limited to 20, beyond which the items cannot be processed.

F-E-017

Ambiguous reference for fields {fieldName1, fieldName2}, can’t proceed to treatment.

Two references have been entered. It is not possible to know which one should be taken into account.

F-E-018

DEPRECATED ERROR - Use F-E-012 Instead Wrong format for field {fieldName}, expected standard email format

The field does not match the expected email format. /^[a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-][a-zA-Z0-9.!#$%&'*+/=?^_`{|}~-]+@[a-zA-Z0-9-]+(?:.[a-zA-Z0-9-]+)*$/

F-E-019

DEPRECATED ERROR - Use F-E-012 Instead Wrong format for field {fieldName}, expected standard telephone format

The field does not match the expected telephone format. It must start with a 0 or + and must not exceed 15 characters.

F-E-020

New classification category detected. Change is unauthorized due to conflict with this attribute setting variant : {attributeName}

This message occurs when you try to assign a new classification category to a product, but the classification has a mandatory variation attribute, or conversely, when you change a category that had a mandatory variation attribute, and the new category does not have one. The variant product cannot change from a variant case to an invariant case and vice versa.

F-E-021

The store affectation of the offer price {wantedOfferPriceStore} does not match the store affectation of the supplier {wantedSupplierStoresList}

The list of stores assigned to the offer price does not match the assignment of stores to the supplier who created the offer.

F-E-022

The store affectation of the offer price {wantedOfferPriceStore} does not match the store affectation of the variant {wantedVariantStoresList}

The list of stores assigned to the offer price does not match the assignment of stores to the linked product variant.

F-E-023

Remove classification category {categoryId - categoryName} is not possible. At least one product is still linked to this category

It is not possible to delete the classification category because products are still attached to it. You must move the products to delete the classification category.

F-E-024

The navigation category with external id {navExternalId} cannot be imported. It already exists in the Store View {storeviewName}

Message returned when a request to create a navigation category is made to an id that already exists across the platform. The id must be unique regardless of the store used.

F-E-025

The account with external id {accountExternalId} has not been exported due to {partnerErrorMessage}

If an account has not been exported to a remote system (e.g. Mirakl), the error specified by the customer will be displayed, giving visibility of the problem encountered.

F-E-026

The customer tag with external id {customerTagExternalId} has not been exported due to {partnerErrorMessage}

If a customer tag has not been exported to a remote system (e.g. Mirakl), the error given by the customer is displayed, giving visibility of the problem.

F-E-027

Unable to link account {accountExternalId} with customer tag {customerTagExternalId} due to {partnerErrorMessage}

The link between the account and the customer tag could not be created in the remote system. The error displayed is the one provided by the system. It is likely that the customer tag has not yet been synchronised and this is causing an association error.

F-E-028

Unauthorized operation {operationType} : {object} must not be in status {unauthorizedStatus} to perform this operation.

An operation is not allowed on an object in a particular state. For example, attempting to add a message to a closed discussion thread will return the error 'Unauthorised operation UPDATE : thread must not be in state CLOSED to perform this operation'.

F-E-029

DEPRECATED ERROR The Mirakl offer cannot be linked to the variant ID {variantId}. This offer already has an associated variant ID, which cannot be changed

DEPRECATED ERROR For Mirakl offers, it is not permitted to modify the associated variant when updating an existing offer via an SFTP or API import.

F-E-030

Permission denied. User {userId} with the role {role name} is not allowed to perform this action on entity {entityType} with id {entityId}.

If a user attempts to perform an action for which they do not have the required permissions

F-E-031

The entity {entityType} cannot be linked to the entity {entityLinkedType} (ID : {entityId}). The {entityLinkedType} is already linked to {entityType} {entityId}.

Error F-E-029 should be moved to this more general error. An association between entities is attempted but not possible because another association has already been made in the past. Example: Attempting to associate a discussion thread with an incident that already has one.

F-E-032

Unauthorized. Missing or invalid authentication token.

Authentication fails, the token is not valid.

F-E-033

Unknown reference : {fieldName} with value {fieldValue} does not exist in Djust system.

A mandatory field is not known in the Djust system. It can be a reference to an object on which you want to perform a read or write action.

F-E-034

Buyer {customerUserId} cannot be approver at the same time and vice versa.

Raised when updating a buying policy where a user is configured simultaneously as buyer and approver. A given user cannot hold both roles in the same configuration.

F-E-035

Missing shared customer account between {entity} {entityId}.

Raised when a configuration requires a shared customer account context between linked entities but none exists (e.g., buyers and approvers sets do not share a common account).

F-E-036

Unauthorized operation {operationType}. The entity {entityType} (ID : {entityId}) is not linked to {entityType} (ID : {entityId}).

Raised when the requested operation implies a relationship that does not exist (e.g., attempting to unlink an item that is not linked).

F-E-037

Missing billing address. The account must have at least one billing address.

On account creation or update, at least one billing address must be present.

F-E-038

{featureName} feature is disabled.

Returned when an endpoint or workflow is called while the corresponding feature flag is disabled.

F-E-039

No eligible {entityName} can be processed under current constraints.

After applying business rules and constraints (visibility, status, dates, catalog views, min and max bounds, stock, etc.), no candidate item remains eligible. Do not use for invalid inputs, unknown references, or uniqueness conflicts; use F-E-001, F-E-005, F-E-008, F-E-033, F-E-003 instead.

Examples Creating order from Operation with mode FULL: every line is rejected by constraints → 422 / F-E-039. Reorder from a past order: all lines are now non-sellable → 422 / F-E-039. Cart generation v2: no line passes checks → 422 / F-E-039.

F-E-040

Incompatible combination of field values. Field {fieldName1} has to be {condition} to {fieldName2}.

Raised when a cross-field constraint is not respected (less than, less than or equal, equal to, greater than or equal, greater than).

Examples Operations: minQuantity must be ≤ maxQuantity. Operations: startDate must be ≤ endDate. Search filters: startDateFrom ≤ startDateTo; endDateFrom ≤ endDateTo (422, or 400 if you decide to reject the request instead of ignoring the invalid pair). Validity windows: effectiveStartDate ≤ effectiveEndDate.

F-E-041

Inconsistent customer accounts across linked entities. All linked {entity} in the configuration must belong to the same customer account.

Used when a grouping configuration (e.g., quota groups, co-validation rules) mixes entities from different customer accounts.

Example Creating a quota group where at least one quotaRuleId belongs to a different customerAccountId → 422.

F-W-001

At least one {fieldName} does not exist in Djust system : {unknownFieldValues}

The field corresponds to a reference that must exist in the Djust system. For example, it could be an external reference to update an object (an offer, a product, etc.).

F-W-002

Field {fieldName} is highly recommended.

If a default value exists, add :

Value has been set to {defaultValue}

This field is not mandatory but is strongly recommended. The default value is given and will be filled in if a default value is possible.

For example, when inserting a navigation category, the classification category is not mandatory, but if the reference to it is empty, the navigation node will be orphaned and serve no functional purpose.

F-W-003

Missing attributes {missingAttributes} for classification category {classificationCategoryName} / {classificationCategoryId}

The non-mandatory attributes of the classification category associated with the product to be inserted are not filled in.

F-W-004

Field {fieldName} does not respect expected format {fieldType}

The field does not match the expected format. For example, when importing attributes into the product flow, if the field is a list and the type is TEXT, a warning is issued.

F-W-005

Field {fieldName} cannot be a reference to itself {referenceId}.

The field cannot refer to itself. For example, when importing related products, if the field is the ID of the related product, it cannot reference itself.

F-W-006

Unexpected field {fieldName}, the field will be ignored

If the added field should not exist, it will be ignored. For example, when importing products, if a productDescription field is present but a variant is inserted, it will be ignored because it has nothing to do with the processing to be performed.

F-W-007

The deleted {entity} does not exist

This message appears when you try to delete an entity that does not exist in the database.

F-W-008

Password does not match the Djust system rules

The password entered does not match the Djust system rule.

F-W-009

Entity {fieldName} is highly recommended.

It is not mandatory, but strongly recommended.

F-W-010

The previous navigation category with ID {navigationId} does not exist. It will be change to {newNavigationId}

F-W-011

Field {fieldName} will be ignored, the role {roleName} has not been configured.

The field to be inserted cannot be saved because the custom field associated with the requested role has not been filled. For example, the stockAvailableStartDate field corresponds to a role for which a custom field is associated with the quote. If no custom field is associated, it is not possible to know where to save the data.

F-W-012

Unauthorized operation {operationType} : {object} must not be in status {unauthorizedStatus} to perform this operation.

Non-blocking variant of F-E-028. The operation is ignored for items in an ineligible status; the rest of the batch proceeds.

F-W-013

The entity {entityType} cannot be linked to the entity {entityLinkedType} (ID : {entityId}). The {entityLinkedType} is already linked to {entityType} {entityId}.

Non-blocking variant of F-E-031. The conflicting association is skipped; the batch continues.

T-E-001

Unexpected error : operation {operationType} on entity {entityType} could not be correctly processed.

An entity could not be created/updated correctly. operationType can take the values creation, update, delete. Example: It was not possible to create a thread on an incident.