New in Endora Commerce: a built-in CRM with sales opportunities See it →
Endora Commerce
November 2026 · 9 min read

Endora Commerce 0.111.0: from individual buyer to company, one tax ID for a head office and its branches

We have released Endora Commerce 0.111.0. It spans 81 packages and 236 changes, including a new module: the customer notification centre. Most of the action is around the customer’s organization and its tax ID, and around quote requests.

Michał Zabielski
Michał Zabielski
Founder and CEO, Endora

For a year, a workshop owner bought from a wholesaler as a private person. Now they want invoices in the company’s name, a credit limit and access for two employees. Until now that meant a new account and orders split across two accounts. In version 0.111.0 an operator turns the private account into a company account with one form, and the history stays where it is.

Below I describe the most important changes. The full list, broken down by package, is on the 0.111.0 release page on GitHub.

An individual buyer becomes a company

In Endora Commerce an individual (B2C) buyer has their own one-person organization. From this version an operator can turn it into a company organization. They enter the company name, an optional legal name, the tax ID, the registered address and the VAT status. The organization keeps its id, orders, carts, addresses and sales channels, and its existing member becomes its administrator and can invite colleagues.

Converting a personal organization into a company: company details and tax ID validation after the conversion
  • The conversion is one-way. A company cannot be turned back into a private account.
  • The tax ID can be validated straight away. After the conversion the panel checks the number in the registry and shows the result. A registry that is down does not undo the conversion.
  • Returns follow the order date. An order placed while the customer was still a consumer keeps the consumer’s right of withdrawal.
  • A separate permission. The conversion is available on the personal organization’s page in the panel and as the “Convert personal organization” screen in the command palette (Ctrl/⌘K), only for roles with the new permission.

A personal organization no longer has an artificial tax ID. The system used to give it a 32-character identifier in place of a tax ID. Now that field is empty, so an individual buyer’s order carries no tax ID and a quote PDF does not print one.

One tax ID for a head office and its branches

In B2B a branch is often not a separate company. It buys on its own, has its own delivery address and its own users, but is invoiced to the head office’s tax ID. Until now only one organization could hold a given tax ID. Now the installation chooses one of two rules:

  • Global (the default, as before): every tax ID belongs to one organization.
  • One tree per tax ID: a head office and its branches may share a tax ID, unrelated companies may not.
Tax-ID scope: one rule for the whole installation, enforced by the database

The rule is enforced by the database, not only by the form. The Organizations → Tax-ID scope screen shows which rule is in force and how many numbers are shared. When you try to go back to the global rule, it lists the organizations that share a number. In addition:

  • A branch is created under its head office straight away. The new organization form has an optional “parent organization” field.
  • A wrong tax ID can be corrected. A typo, or a head office’s number copied to a branch that has its own, is changed without deleting the organization. Members, roles and orders stay, and invoices and quotes already issued keep the number they were issued with.
  • Tax IDs are stored in one form, without spaces or dashes. The same number typed once as 525-000-00-00 and once as 5250000000 no longer makes two companies.

Quote request notifications

Every change to a quote request now reaches the people it concerns:

  • The sales team gets an entry under the bell in the admin panel when a customer submits or re-submits a request, accepts or rejects an offer, and when a request expires. On top of that comes an e-mail about a new or re-submitted request, with a link to the request in the panel.
  • The buyer gets an e-mail at every change, from submission through preparing and revising the offer to approval, cancellation and expiry. The message links to the request in the store.
  • The notification centre in the customer’s account is a new module. The request’s author and the members of their company who may open it see an entry in the store, and the unread count on the account entry. Entries are in the store’s language and are deleted after 90 days (the period can be changed in the settings).

There are eleven new e-mail templates, in Polish and English. Each one can be edited or switched off. The request’s history shows, for every entry, who was notified and whether the message arrived. A failed delivery is retried several times over two hours.

New ERP and PIM integration points

An integration module can now do more on the platform side, without calling the admin API:

  • The ERP order number on the order. The integration records the number the ERP, warehouse or fulfilment system gave the order, where the hand-over stands (pending, synced, error) and the message of a refusal. The order page in the panel has a new “External systems” section, and the order search finds an order by its ERP number.
  • Customer-specific prices from the ERP. The integration writes a product’s prices into a customer-group, organization, catalogue or sale price book, under the same rules as the price book editor. Prices an administrator entered by hand are not overwritten.
  • The customer master. The integration finds companies by tax ID, creates them, also as branches, and updates their details and custom fields.

For teams that extend the platform there is a new System → Command hooks screen. It shows which modules hook into organization writes and in what order, and the list of failed deliveries with a retry button. A module can also add its own columns to the organizations table, and the instance CLI has a command that lists and cleans them up.

Sales representatives see their customers, and only theirs

A sales representative sees the organizations they handle and those no representative handles, for example fresh registrations. Companies handled by another representative are hidden from them on every screen of the panel: in lists, search, pickers and at their direct address. The reach is computed once per request, so the panel of a representative with hundreds of customers runs faster.

A change for quote requests: only sales representatives are narrowed now. A custom role with the permission to handle quote requests sees the requests of every organization, as on other screens.

Security and personal data

  • The audit log no longer stores customer data. For organizations, orders, quote requests, returns, invoices, credit limits, projects and tasks it records who changed which fields and when, but not their values: no names, tax IDs, addresses, amounts or free text. The log is read by people who do not need access to every company, so this data stays out of it.
  • A private file without a valid signature answers “not found”, just like a file that does not exist. The old answer revealed that a file with that id existed.
  • The last two-step verification method cannot be switched off while a two-step requirement applies to the account.
  • Webhook delivery history has a retention period: 365 days by default, set in the panel.

Easier in the panel and the store

  • One “Save” button on the organization, customer and sales channel pages and on a product’s inventory tab. The panels on those pages used to have their own save buttons. Sections that save at once are now marked “Applies immediately”. On a long product page the save button stays in view as you scroll.
  • The panel’s own confirmation dialogs instead of the browser’s, for example when rejecting a return, where the reason goes into an ordinary form field.
  • A product feed can be pinned to a price book in the panel, for example to give Google Merchant Center the sale prices. The list shows which price books can be chosen and gives the reason for the others. This used to require an API call.
  • Error messages in the reader’s language. Dozens of refusals in orders, returns, invoices, promotions, price books, payments and the catalogue have their own error code and a clear sentence in English and Polish instead of a generic English “validation failed”.
  • A credit limit reservation shows its order number, in the store and in the panel.
  • The store picks the language better. The storefront API takes every language in the customer’s browser settings into account, with their priorities, and matches them against the sales channel’s languages. This covers the catalogue, cart, search, content, blog, forms and quote requests.
  • The back-in-stock e-mail names the product in the language the customer subscribed in, and the subscription’s status changes to “notified”.
  • A shopping list’s name and quantities are saved together, in one request.
  • Abandoned carts are marked automatically, every 15 minutes, with no separate cron job.
  • A line quantity has an upper limit. An absurdly large number used to end in a server error; now the customer gets a clear message.
  • A new instance’s backend restarts itself when its process is alive but no longer answering. The storefront has worked this way since earlier versions.

What to watch out for when upgrading

The release has two breaking changes, both for integrations and custom modules: a personal organization has an empty tax ID (null instead of a string), and the functions that check a sales representative’s reach are now asynchronous. Behaviour changes matter more for a running store:

  • Quote request e-mails are switched on by default. After the upgrade customers and sales staff start getting them. Switch off the ones you do not want in the e-mail templates before upgrading.
  • A custom role with the permission to handle quote requests will see the requests of every organization, not only assigned ones.
  • Tax IDs will be stored without spaces or dashes. The migration will not run if two organizations would then hold the same number, and it lists such pairs. Check for duplicates before upgrading.
  • Integrations that recognise errors by the VALIDATION_FAILED code will get a specific code in many places. The HTTP status does not change.

You upgrade an instance with the Endora Commerce CLI’s upgrade command. Details are in the instance upgrade documentation. All changes, the comparison with version 0.110.0 and the notes for each package are on the release page on GitHub.


Do you sell to companies with branches, while some customers start out as private buyers? Get in touch and we will show you how it works in Endora Commerce.

Selected modules explained on YouTube
Open the playlist →

Keep reading

Read the blog →