Postman collection
Customers Write

pixiCustomerInfoSet

Updates the invoice due days and reminder (dunning) settings of one customer identified by CustKey or by external customer number/email plus shop.

Changes the payment and reminder settings of exactly one customer record in Customers.

Identifying the customer

  • Pass CustKey, or pass ShopId together with CustomerNrExternal and/or CustomerEmail.
  • CustomerNrExternal, CustomerEmail and ReminderAction are trimmed; empty strings count as not provided.
  • The lookup matches customers where (CustomerNrExternal matches or CeMail matches CustomerEmail) and CustomerOf = ShopId, or where CustKey matches.
  • If no customer matches, or more than one customer matches, the call fails.

Validation

  • ReminderAction must be one of NONE, PRINT, MAIL, PRINT&MAIL or 0.
  • InvoiceDueDays, DaysForFirstReminder, DaysForNextReminder, ReminderDueDays and ReminderCost must not be negative.

How values are applied

  • A parameter that is omitted (NULL) keeps the value currently stored for the customer.
  • A value of 0 (or '0' for ReminderAction) clears the setting, i.e. it is stored as NULL (option disabled).
  • Any other value overwrites the stored value.

The update also sets UpdateDate to the current date/time and UpdateEmp to API-CustomerInfoSet.

The call always returns one status row with Status (OK or ERROR) and StatusMessage.

Notes

  • All validation errors are raised inside a TRY block and caught; they are returned as a status row with Status = ERROR, not as a SqlMessage. Only the first failing check is reported.
  • The procedure's return value is 0 on success and 1 on error; SOAP clients should evaluate the Status column.
  • The candidate lookup reads Customers with NOLOCK. There is no explicit transaction around lookup and update.
  • Pitfall: the search conditions are combined with OR. If CustKey is passed together with ShopId and CustomerNrExternal/CustomerEmail, or if both CustomerNrExternal and CustomerEmail are passed and point to different customers, several records can match and the call fails with "More than one customer found". Pass only one identifier for a reliable result.
  • ShopId is not trimmed, unlike the other identifiers.
  • NONE and 0 differ for ReminderAction: NONE stores the value NONE, 0 stores NULL. Whether the value check is case-sensitive depends on the database collation.
  • A ReminderCost of 0 is stored as NULL, so a cost of exactly zero cannot be saved explicitly.

Tables used

Customers · Write
SQL object:
dbo.pipiCustomerInfoSet
Updated at 2026-10-30