Feature toggles

Some parts of Yessort are switched on per organisation rather than being available to everyone at once. A feature toggle is that switch.

Under the organisation's settings; needs organisation-admin access.

A feature is off until it is turned on

Toggles default to off. An organisation that has never touched them has every optional feature disabled.

That is worth knowing before concluding something is broken. A feature that appears to do nothing may simply not be on.

The order routing engine

The most consequential one today.

When it is off, incoming orders are assigned to the channel's default site and none of your routing rules run — even if you have built a rule set and activated it.

So a rule set that seems to have no effect is usually this. See fulfilment routing, which assumes throughout that the engine is on.

Why features arrive this way

Turning something on for one organisation at a time makes it possible to try a change where it is wanted, and to stop if it goes badly, without affecting anyone else.

The cost is that a feature's availability is not the same question as whether it exists. Both matter when working out why something is not happening.

Not everything optional is here

Some features are held back centrally during a preview and do not appear in the organisation's settings at all. If a capability exists but you cannot find a switch for it, it is likely not yet open for organisations to enable themselves.

Turning one on

Open the organisation's feature settings and switch it. The change applies to the whole organisation, not to individual members.

Check the effect on new activity rather than existing records — enabling the routing engine, for example, changes how orders arriving afterwards are handled and does not re-route anything already in flight. See rule sets and versions.