Process customers
You can change customer data subsequently, for example if a company name changes, a name needs to be corrected or a customer should be temporarily blocked.
When do I need this function?
Section titled “When do I need this function?”You need this feature to keep customer data current and consistent. Typical use cases are:
- Updating name, company or address data.
- Addition of a sales tax ID (VAT ID) for a B2B customer.
- Change in customer status, for example in the event of temporary blocking, payment defaults or end of contract.
Requirements
Section titled “Requirements”- The customer must exist in the portal.
- You need the appropriate authorization role to edit customer data.
Step-by-step instructions
Section titled “Step-by-step instructions”Unlike new creation, processing is always carried out from the detailed view of a specific customer.
1. Call up the customer profile
Section titled “1. Call up the customer profile”Find the desired customer in the customer overview. Further information can be found under Search customers. Then click on the customer entry to open the detailed view.
On the left side you can see the customer information card with the most important basic data. In the customer info card, click Edit Customer.
2. The editing mask
Section titled “2. The editing mask”The editing mask opens. In many areas it corresponds to the mask for the customer system. For business customers (BUSINESS), the company name is a mandatory field. In addition, tax category and VAT ID are logically combined.
In addition to the familiar fields, you will find the Status drop-down field at the top right (right next to the customer type).
3. The status model
Section titled “3. The status model”Depending on the configuration of your portal, a customer can go through different statuses in the lifecycle. The dropdown field gives you the option to change the customer status manually.
The status model in tebio follows a defined logic. This defines which status transitions are possible:
graph TD
LEAD(("LEAD"))
VALIDATION(("VALIDATION"))
ACTIVE(("ACTIVE"))
BARRED(("BARRED"))
DEACTIVE(("DEACTIVE"))
LEAD --> VALIDATION
LEAD --> ACTIVE
LEAD --> DEACTIVE
VALIDATION --> ACTIVE
VALIDATION --> DEACTIVE
ACTIVE --> DEACTIVE
ACTIVE <--> BARRED
BARRED --> DEACTIVE
- LEAD: Initial state, for example for interested parties or incomplete customer records.
- VALIDATION: Intermediate status, for example if an email address still needs to be verified.
- ACTIVE: Regular status for active customers.
- BARRED: Temporarily blocked, for example due to outstanding invoices. As a rule, the customer cannot make new purchases, but remains in the system.
- DEACTIVE: Deactivated customer. The customer usually loses access to the self-care / customer portal and is no longer displayed in standard lists.
4. Save changes
Section titled “4. Save changes”As soon as you have made all the necessary adjustments (for example correcting the company name or adding the VAT ID), scroll all the way down and click on Save.
Result
Section titled “Result”The changes will be applied to the system after saving. From this point onwards, future receipts, invoices and messages will be generated with the updated master data. Invoices that have already been generated remain unchanged for audit reasons.
Notes and typical errors
Section titled “Notes and typical errors”- Change of billing address for B2B: If you subsequently change the country of billing address for a business customer, the system automatically checks whether this changes the tax category (buyer). This may impact tax calculations on future billings or subscription renewals.
- Find deactivated customers: Deactivated customers may not appear in the default view. In the customer overview under more filters, set the status filter to
DEACTIVEto call up these customers again.
API Notes
Section titled “API Notes”Customer master data can also be updated via the API. The endpoint expects a PUT request that overwrites the entire data set.
[!WARNING] For a
PUTrequest, the transmitted payload replaces the existing customer data record. Therefore, send all relevant master data, even if you only change individual fields. Fields that have not been submitted can be overwritten or emptied. Before making any changes, first retrieve the current customer record usingGET, adjust the desired fields, and then send the complete updated record back usingPUT.
| End point | Method | Description | OperationId |
|---|---|---|---|
/v1/customer/{uuid} | PUT | Update customer information | updateCustomer |