A company with a three-person purchasing team orders from a wholesaler. The buyer puts the cart together, the manager approves orders above budget, and the accountant needs to see all of the company’s orders and invoices but never orders anything. Until now a customer’s organization in Endora Commerce knew only two roles: administrator and regular user. In version 0.110.0 the customer sets up the roles of their own team.
Below I cover the most important changes. The full list, broken down by package, is on the 0.110.0 release page on GitHub.
Roles and permissions in the customer’s organization
Every company organization now has two built-in roles, Administrator and Member, plus up to 50 custom roles. A role is a set of permissions declared by the individual modules. For example:
- creating a cart and ordering without approval,
- approving other people’s carts,
- submitting quote requests,
- viewing the whole organization’s orders, not just one’s own,
- filing returns and complaints and viewing the whole organization’s cases,
- managing the organization’s addresses,
- one-click ordering and working with shopping lists.
The customer’s organization administrator sets up roles in their storefront account. Your team can do the same in the admin panel: the organization screen has a new Roles section with a permission editor grouped by module and a link to the change history. Two new operator permissions give access to this section, one to read roles and one to manage them.
A few details that matter in practice:
- An invitation to the organization names a role, and the invitation e-mail shows the role’s name in the recipient’s language.
- A role someone holds can only be deleted with a replacement role. Every holder and every open invitation moves to it in a single operation.
- A member sees their role in their profile and can check what it allows.
- Permissions apply across the whole storefront, the API included: reordering, copying an order into a quote request, quick-order import and credit limit reservations. A member who cannot see colleagues’ orders will not see their reservations against the limit either.
- The audit log names the customer who made a change. A role change or an invitation sent by the organization administrator in the storefront used to be recorded as a “system” change.
Cart approval works end to end
An organization can require an authorised person to approve a cart before it becomes an order. In this version we completed the whole process:
- The storefront shows a “Send for approval” button instead of the checkout when a cart needs approval.
- Approvers get an e-mail about a cart waiting for a decision, and the buyer gets one when the cart is approved or rejected, with the reason. You edit these messages in the e-mail templates.
- Any role with the approval permission can approve, not only the administrator. Nobody can approve their own cart.
- Changing an approved cart requires approval again.
- After a rejection the buyer does not start from scratch: their next cart starts with the rejected cart’s lines.
- Placing an order checks the approval. An unapproved cart will not go through, even if someone calls the orders API directly, bypassing the storefront.
Company registration with data from the registry
A company signing up in the storefront can fetch its name, address and VAT status from its tax ID. Polish NIP numbers are checked in GUS (REGON) and on the Ministry of Finance VAT White List, and VAT numbers from other EU countries in VIES. The registry’s answer is saved with the registration. When moderating a new account, the panel shows the registry data next to what the customer typed, with the number of fields that differ.
The feature is off by default and is switched on in the organization settings. GUS requires an API key, stored in the credentials module. Without it, Polish numbers are checked against the White List alone.
On a related note: the Ministry of Finance has moved the White List to a new address and will serve the old one only until 1 December 2026. From this version Endora Commerce connects to the new address. If you use tax ID validation, upgrade your instance before that date.
Content: Page Builder product descriptions, forms and post authors
- A new attribute type, “Page Builder content”. A product description can be built from Page Builder blocks, separately in each language, instead of fitting into a single text field. Duplicating a product copies this content too.
- A form block in Page Builder. A form from the forms module can be placed on any storefront page. It supports every field type, conditional visibility, consents and CAPTCHA, works without JavaScript, and its look is chosen from ready-made variants.
- Blog post authors. A post has an author, one of the administrators. An administrator sets a photo and a short “about me” text in each language in their profile.
- Deleting an attribute shows how many products use it before anything disappears.
Returns, invoices and VAT
- A consumer’s withdrawal from the contract also refunds the delivery cost and the payment surcharge when the customer returns the whole order, in line with Directive 2011/83/EU and the Polish Consumer Rights Act. Settling it other than with a refund (e.g. a replacement or a repair) requires the customer’s recorded consent.
- A complaint settled with a price reduction goes on the corrective invoice as a price reduction rather than returned goods, with the case’s RMA number.
- An invoice issued after a return covers only what the customer kept.
- A product’s gross price uses its own VAT rate instead of a flat 23%. The cart shows VAT broken down by rate, and the delivery cost is split across the goods’ rates the same way as in the order.
- Polish invoice PDFs no longer carry English labels, and the invoice template editor preview shows exactly what the PDF prints.
Security and personal data
- Security fix: an organization member who is not its administrator could reorder a colleague’s order or copy it into a quote request. The same access rule as for viewing an order now applies.
- A sales representative sees only the organizations assigned to them, also when opening their address in the admin panel directly. Before, they could open and edit another representative’s organization.
- The external orders API accepts an order only on a sales channel assigned to the organization.
- The two-step verification requirement for an administrator role is enforced at sign-in, with a password as well as with Google or Microsoft. The roles screen warns when the server has no encryption key and the requirement is not in force.
- Deleted customer accounts are anonymized after the retention period set in the admin panel. Before, this daily job did not run. Anonymization now clears every field holding personal data, including block or rejection reasons entered by operators, and an interrupted run is completed the next time.
Easier in the admin panel
- Deleting a product frees its SKU and its variants’ SKUs, including for products deleted before the upgrade.
- “Select” attributes can be created and edited in the admin panel, options included.
- Settings group headings and switch descriptions are translated, so a Polish administrator no longer reads them in English.
- Page Builder pages and the blog no longer overload the database when they are missing from the cache.
endora devstarts faster: the first layer starts in under 0.1 seconds instead of after about two seconds.
What to watch out for when upgrading
The release contains seven breaking changes. Three matter most for a storefront:
- One address book per customer. The personal address book is gone. Every customer has one address book, their organization’s, shown as “My addresses” or, in a company, “Organization addresses”.
- An order placed for a customer in the admin panel accepts only a sales channel assigned to their organization.
- An order from a cart that requires approval is refused until the cart is approved.
The rest concern integrations and extensions, among them the error codes of sign-in through an external provider, the names of modules created with endora new module and the asset library settings. If you have your own integrations or modules, review the breaking changes section on the release page.
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.109.0 and the notes for each package are on the release page on GitHub.
Do your customers buy as a team and need roles, limits and order approval? Get in touch and we will show you how it works in Endora Commerce.