Customer groups
A customer group collects customers together under a label. It has a name, a code, a description, and members.
What a group does today
Nothing beyond that.
A group is a way of recording that some customers belong together — a segment, a tier, a region, whatever grouping is useful to you. You can create groups, put customers in them, and see who is in which.
Nothing in Yessort behaves differently because a customer is in a group. Prices do not change, promotions do not apply, and no rule keys off membership.
Why it looks like it should do more
Because the machinery is half-built and visible. A sales price list can be scoped to a customer group in the underlying data — but there is no field anywhere in the Yessort screens to set that scope.
The same is true of scoping a price list to a customer account or a sales channel. In practice the default list for the currency is what applies. See sales price lists, which sets this out for all three.
So the honest position: groups are ready for pricing to use them, and pricing does not use them yet.
What they are still good for
Recording a segmentation you act on elsewhere. If you treat certain customers differently — a call before dispatch, a particular contact — a group records who they are so anyone can check.
Reporting and finding. Grouping customers makes them findable as a set.
What they are not good for is anything you need the system to enforce. If a group is meant to mean a different price, that price has to be applied another way, and the group will not do it for you.
Membership
A customer belongs to a group by being added to it. Membership is a plain list — a customer can be in more than one group, and removing them from one leaves the others alone.
Before you create one
Ask what you expect it to do. If the answer involves prices or automatic behaviour, the group will not deliver it and something else has to.