¶ Customers - individual and company accounts in one store
Customers in Hummerce is one shared database of individual and company accounts - store staff manage them from the panel regardless of whether the store sells retail, wholesale, or both at once. A customer account can belong to a company, have assigned views and price lists, and its data can also be read by REST API and the AI assistant (MCP).
As of Hummerce 2.30-2.35, updated 2026-10-16.
¶ Benefits and use cases
- One database for B2C and B2B - an individual customer and a company employee in the same module, with a filter by company and by the person managing the company account.
- Protection against accidental data loss - Hummerce blocks, by default, deleting customer accounts linked to orders and external integrations.
- Quick insight through the AI assistant - top customers, recently registered ones, order history and customer segmentation with a single command, without a manually prepared report.
- Knowing how much a customer has bought - the store totals each customer's turnover from completed orders and shows it on the customer list and card, with no manually prepared report.
- Safe handling of data-deletion requests - customer data can be anonymized manually in the panel or removed from the ERP side, without breaking order links.
¶ Individual account and company account
- A customer sets up an account either as an individual, or as a company employee. A company account links several employees of one company under shared prices and addresses, with a manager and an employee as two permission levels - full description: Company accounts and roles.
- The customer list in the panel shows the Company field and has a filter by company and by the people managing a company account.
- The store can record each customer's turnover - the sum of the value of their orders in a single chosen currency. In the panel it is the Obrót property (description: "Approved turnover"); the label is shown in Polish.
- Turnover is counted from orders that reached the Completed status. When an order enters that status, its value is added to the customer's turnover; when it leaves it (e.g. the status is reverted), the value is subtracted. The store updates turnover immediately on the status change, with no scheduled task.
- By default the value of the order's items is counted, gross. Settings let you change:
- gross or net counting,
- whether shipping and payment costs are included,
- the turnover currency - after a change, existing turnover is converted at the exchange rate of the next update.
- Turnover is stored for a specific customer account. Orders with no account (e.g. guest purchases) and zero-value orders do not change it. The store does not total a whole company's turnover - each company employee has their own.
- Orders from before the module was enabled can be included with a one-time recalculation of all customers' turnover from order history - the Turnover initialization option.
- Turnover is visible in the panel as the Obrót field on the customer list and on the customer card. It is an ordinary customer property, so store staff can take it into account when assessing customers by hand, e.g. when setting discounts.
¶ Deleting and anonymizing customer data
- From version 2.30, a customer can't be deleted from the panel list or from their card - the account is linked to orders and external integrations (e.g. an ERP), and deleting it would break those links.
- From version 2.32, the panel shows this information directly instead of ending the attempt with an error.
- The Allow to delete customers from the customers list setting (off by default) lets you turn deletion back on in stores on version 2.31 and later - the store decides.
- On a customer's request to delete their data, the account data can be anonymized manually in the panel - by overwriting their property values - or deleted from the ERP side, if the integration covers customers.
- The Customers settings group in the panel also covers customer session protection and login rules - full description of the security mechanisms: Admin panel and store security.
- Changing the email address used as a login requires confirmation via a link - Customer login change.
- Blocking customer deletion from the list - from version 2.30; the panel showing that deletion is disabled - from version 2.32 (also available in implementations from version 2.31).
- Company accounts - from version 2.30 (details: Company accounts and roles).
- Login change with email confirmation - from version 2.34.
- Customer turnover - a core platform feature, available in all current versions.
- Company accounts require the company accounts module (Company accounts and roles).
- Customer turnover requires the turnover module to be enabled in the store configuration.
- Deleting or anonymizing customer data on the ERP side requires an integration that covers customers (e.g. Business Central, Comarch ERP XL).
- Reading customer data through the AI assistant requires a running MCP server (AI assistant - MCP server).
- Basic customer handling works after an update - no implementation needed.
- Enabling customer deletion from the list is a single panel setting. Company accounts and ERP-side data anonymization require separate implementation.
- Minimum estimated time: enabling or disabling customer deletion - from 0.5 h. Company accounts - see Company accounts and roles.
- Customer turnover requires enabling the module, setting the currency and the counting method (gross or net, with or without shipping costs) and a one-time recalculation of existing orders - from 1 h.
- What the time depends on: the number of external integrations linked to the customer, the scope of data anonymization, whether the store also sells to companies.
- Deleting a customer from the list is disabled by default, and deleting data on the ERP side requires an integration that covers customers - there's no single-step deletion of all of a customer's data on request in the standard configuration.
- Customer turnover is a single amount in a single currency, accumulated for the customer account. There is no split by period (e.g. yearly turnover) and no company-level turnover.
- Turnover counts only orders in the Completed status; a different triggering status is set in the module configuration during implementation.
- The MCP tools (
ec2_customers_top, ec2_customers_segment) compute their own summaries from orders in the chosen period and do not use the Obrót property.
- Anonymizing customer data in the panel is manual - there's no automatic mechanism for it.
- REST API and MCP don't support managing companies (see Company accounts and roles) - customer operations apply to a single account.
- We do not verify the task for legal compliance (e.g. licenses of submitted materials, GDPR, store terms of service).
- Automatic, self-service anonymization of customer data.
- Managing companies and their data through REST API and MCP.
Can one customer have both an individual and a company account at the same time?
A customer sets up one account - either as an individual, or as a company employee. The full company account path is described on Company accounts and roles.
Which orders does the store count towards customer turnover?
Orders in the Completed status: an order's value is added to turnover when the order is completed and subtracted when the status is reverted. By default it is the gross value of the items, without shipping and payment.
Is turnover recalculated daily?
No. Turnover changes when an order's status changes. For past orders there is a one-time recalculation from order history (Turnover initialization).
Where can I see a customer's turnover?
In the panel, in the Obrót field on the customer list and on the customer card.
Does the store count a whole company's turnover?
No - turnover belongs to the customer account, so each company employee has their own.
Can store staff delete a customer from the list?
Not in the standard configuration. From version 2.30, deleting customers is blocked because of links to orders and external systems - the store can turn this option on with a panel setting.
What do we do when a customer asks to have their data deleted?
Customer data can be anonymized manually in the panel, by overwriting their property values, or deleted from the ERP side, if the integration covers customers.
Can the customer list be filtered by company?
Yes - the customer list in the panel has a filter by company and by the people managing a company account.
Can the AI assistant (MCP) read customer data?
Yes - the MCP tools show top and recently registered customers, account details, order history and customer segmentation, within the permissions of the account the assistant is connected with.
Want to see how Hummerce could manage individual and company customers in your store? Contact the Hummerce team (in Polish).
- Customer list: CRM -> Customers, with a filter by company and by the people managing a company account.
- Configuration -> Settings, the Customers group: Allow to delete customers from the customers list (No by default), login settings (Email as a login, Change login after email update) and customer session protection.
- Editing a customer: the Company and Manages the company account fields (see Company accounts and roles); the delete-customer option is shown or hidden depending on the setting above.
¶ REST API and MCP
- REST API: read, create and update customer data.
- MCP (AI assistant - MCP server):
ec2_customers_recent - recently registered customers,ec2_customers_top - customers with the highest order value in a given period,ec2_customers_details - customer details (data, group, number of orders),ec2_customers_order_history - a customer's order history,ec2_customers_segment - segmenting customers by how recently, how often and how much they've bought (RFM).
¶ Customer turnover - settings and property
- Configuration -> Settings, the Customers group (once the turnover module is running):
| Setting |
Effect |
Default |
| Taxed turnover |
On - gross turnover, off - net |
On |
| Additional cost to turnovers? |
Include shipping and payment costs in turnover |
Off |
| Turnover currency |
The currency in which turnover is remembered; after a change, turnover is converted at the exchange rate of the update |
the shop's default output currency |
| Turnover initialization |
One-time calculation of all customers' turnover from existing orders; set back to "no" afterwards |
Off |
- Customer property Obrót (description "Approved turnover", type money) - shown on the customer list and on the customer card in the panel. Managing properties: Properties and locations.
Customer profile content and registration error messages are changed in the message editor; customer property values (first name, last name, company data) - through Properties and locations.