Customers

In DJUST, customers can be several identities with different access levels:

• Account: Name of the company where the end-users of your store belong to. Example: Airbus.
• Organisation: Optional, sub-group or category within the company. Example: Airbus Space.
• User: End-user purchasing products on your store. Example: John Smith.

Creating accounts

Accounts are mandatory as each user must be attached to at least one account.

💡

Adding a customer user during account creation is optional. You can create an account without a user and attach an existing user later.

1. Click Customers → Accounts → + Create Account.

   

2. Fill in the Information:

   • Account name
   • External Id
   • Account manager (optional)
   • Website (optional)
   • Company registration name
   • Business registration number
   • VAT number (optional)
   • Customer tags (optional)

3. (Optional) Fill in the User information to create a customer user attached to the account:

   • Civility

   • First name

   • Last name

   • Email

   • External Id

   • Phone

   💡

   If you skip this step, you can attach an existing customer user to the account after creation from the Customer users section.

4. Fill in the New address:

   • Country
   • Label (optional)
   • External Id
   • Full name
   • Address
   • Address (additional) (optional)
   • City
   • State (optional)
   • Department (optional) — administrative department (e.g. 75, 2A, 971), used to determine the applicable delivery zone
   • Zip code
   • Phone (optional)
   • Select whether the address is used for shipping, billing, or both.

5. Click Create.

   

⚠️

If the Customer account approval parameter is active, each account create requires a manual approval by an internal user.

Creating accounts via API

Use createCustomerAccount (POST /v1/customer-accounts) to create a customer account programmatically. The createCustomerUserRequest field in the request body is optional — you can create an account without a customer user.

To attach an existing customer user to the account afterwards, use ADM-CUSTOMER-USER-250 (PUT /v1/customer-users/{customerUserId}/accounts), which replaces the full list of accounts linked to a customer user.

To retrieve the list of accounts linked to a customer user, use ADM-CUSTOMER-USER-550 (GET /v1/customer-users/{customerUserId}/accounts).

Filtering the account list

The account list can be narrowed on accounts, customer tags, status, store, custom field values and, since 3.138, on two dates:

• Creation date
• Update date

They use the same presentation, the same labels and the same behaviour as the date filters of the other Back-Office lists, the order list in particular: same way of picking a period, same rules on the bounds. They combine with each other and with the existing filters, and are displayed like them once applied. The indicator cards at the top of the list are not affected, as with the other filters. Without these filters, the list behaves exactly as before.

Filtering via API

GET /v1/customer-accounts — operationId: ADM-ACCOUNT-551 · Access: dj-client: OPERATOR

• Dates are ISO-8601 instants. Each bound is optional and included.
• A range whose start is after its end returns an empty page, not an error.
• The update date is the one of the account itself: attaching a customer user to the account does not move it.

GET /v1/customer-accounts?creationDateFrom=2026-09-01T00:00:00Z&creationDateTo=2026-09-30T23:59:59Z&status=ACTIVE
dj-client: OPERATOR
dj-api-key: <your-api-key>

✅

Tip: Segmenting the accounts created last month, or updated since a given date, no longer requires exporting the list and reprocessing it.

Account list indicators

Three indicators are computed by the platform over all the customer accounts of the environment, all stores together. They are exposed by the Statistics API; the Back-Office screen that displays them will follow in a later version.

Reading the amounts

• Two amounts are always returned: the products excluding taxes and excluding shipping fees, and the total paid including taxes and shipping fees.
• Amounts are returned per currency. They are never summed, never converted.
• The date attaching an order to the period is the validation date of the logistic order. Both bounds are included and interpreted in UTC.
• Without any period, the indicators cover the whole activity since the creation of the environment — there is no maximum duration.

Scope and permissions

• The indicators do not take the filters or the search of the list into account, and no dedicated role is required: whoever can access the customer accounts can read them.
• A supplier only ever obtains figures within their own perimeter. The restriction is applied server-side, so a direct API call cannot widen it:
  • Accounts per status covers the customer accounts linked to that supplier only — a supplier linked to no customer account gets no account indicator.
  • Business volume and average basket cover all the orders placed with that supplier, including those of a customer account that is not linked to them. They therefore reflect the whole of their sales.
• The operator's own indicators are unchanged by these supplier rules.

📘

Note: The business volume counts from the supplier acceptance, while the ordered amount of the order list counts earlier in the lifecycle. On the same perimeter, the ordered amount is therefore always greater than or equal to the business volume — see Search, Filter & Sort Logistic Orders.

Importing accounts

Import customer accounts by using the Data Hub.

Accounts can be imported in DJUST using an FTP client and a .csv file, or using our API connector.

Refer to the Data hub section for more information.

Creating users

1. Click Customers → Customer users → + Add user.

   

2. Fill in the following information:

   • Civility
   • First name
   • Last name
   • Email
   • External ID (with no accent and no space)
   • Phone
   • Groups (add link)
   • Account name (account to which the user is attached to)

3. Click Add.

   The new user appears in the Customer users list.

Users can be edited by clicking on the chosen user from the users' list. Once the customer user starts placing orders and sending or receiving quotes, those will appear on their page, right below the user information. To deactivate a user:

1. Select it from the users' list.
2. Click the Actions button.
3. Select Deactivate user.

💡

This can be done on several users at the same time.

Importing users

Import user accounts by clicking Data Hub → Create a new job → Import job → Customer user csv.

Add legal user

If using a payment service provider, you can declare a specific user to contact (for billing or legal purposes).

📘

You can only add one legal user per account.

1. Click Customers → Accounts.

2. Select an account.

3. Click More actions at the top-right and click Add a legal user.

   

4. Fill in the information:

   • First name

   • Last name

   • Birthday

   • Nationality

   • Country of residence

   • Email

   ❗️

   All fields are mandatory.

   

5. Click Add.

Creating customer tags (optional)

Customer groups are required to offer different prices to different groups of customers. To create customer groups, you need to create customer tags.

Customer tags can only be created manually. They must be created before the offers so that you can associate offers with specific groups of customers.

1. Click Settings → Customer Management → Customer tags.

   

2. Click + Add customer tag.

   

3. Fill in the fields:

   • Name
   • External Id
   • Description

4. Click Create.

Tags can have any value or description you like ("premium", "hotel"...) depending on your usage. DJUST recommends using simple tag names.

Associating customer tags via API (External IDs)

A dedicated API endpoint allows you to manage customer tag associations using External IDs instead of tag names, providing stable and reliable identifiers for programmatic integrations:

Endpoint: PUT /v1/customer-accounts/{customerAccountId}/customer-tags — operationId: ADM-ACCOUNT-250

• Path parameter: customerAccountId — the External ID of the Customer Account.
• Access: dj-client: OPERATOR
• Response: 204 No Content

{
  "customerTagExternalIds": ["premium", "wholesale"]
}

Behavior:

• This endpoint performs a full replacement of the tag associations for the specified account.
• Sending an empty array [] removes all tag associations.
• The operation is atomic: if any External ID is invalid, no changes are applied.

✅

Tip: Use this endpoint instead of the customerTagList field on PUT /v1/customer-accounts/{customerAccountId} for programmatic integrations. External IDs are stable identifiers that do not change when a tag is renamed.

Creating organizations and sub-organizations (optional)

Users can be assigned to organizations and sub-organizations, so they can access content that is relevant to them.

For instance, one member of sub-organization A is not able to see the back-office content of a user from sub-organization B, and so on.

💡

You can create custom fields for organizations as well. Go to Settings → Customer Management → Organisation custom fields.

You can create a new organizations either in:

• Customers → Organisations

  

• Customers → Accounts → Select an account → go to the Organisations section of the page → Add an organisation

  

  

1. Click + Add organisation.

2. Fill in the fields:

   • Name
   • External ID
   

3. Click Add.
   The organisation appears on the account's screen.

4. Hover the new organisation and click the + appearing to add a sub-organisation.

   

5. Fill in the fields:

   • Name
   • External ID
   

   ⚠️

   Even if the pop-up name shows "Organisation", it creates a sub organisation.

6. Click Add.
   The organisation and its sub appear on the account's screen.

   

Linking a customer user to an organisation (optional)

1. Click Customer → Customer Users.

   

2. Select the user you want to add to the organisation.

3. Click Add Organisations from the "Accounts and Organisations" section of the page.

   

4. Search for the organisation, select it and click Add.

   

Creating buying policies

1. Click Customer → Buying policies.

   

2. Click the Add policy button.

   

3. Fill in the policy's Details:

   • Name
   • Description
   • Message (displayed to the customer)
   

   Click Next step.

4. Fill in the policy's Rules:

   • Select an account
   • Select users from that account that will need to have their purchases reviewed
   

   Click Next step.

5. Fill in the Approvals: select up to two "super" users which will review
   the user's purchases.

   

   Click Next step.

6. Review the buying policy configuration. Click Create.