In an Across based application, the primary order of bean interaction should be defined by the module dependencies. When scanning for beans in all modules (eg. when using a RefreshableRegistry or @RefreshableCollection), the beans will be returned according to the module order: beans from earlier bootstrapped modules will be before beans from later modules. The reasoning is simple: if I depend on module A, i can rely on module A having done its things before I will. If you need more sophisticated ordering, there are two extension points to the default behavior:

Core Spring classes. If you define these on beans, these will take precedence over the order of the modules themselves. The Ordered interface takes precedence over an @Order annotation, if both are present. Using global ordering should be avoided as much as possible, but using for example Ordered.LOWEST_PRECEDENCE you can ensure that a bean comes after all other context created beans in the list.

The equivalent of @Order and Ordered, but they only apply within a single module. Use these if you have multiple beans (eg security configurers) of the same type in a single module, and it is important they follow a sequence.