Behavior
In the Behavior tab you control who may order, whether a branch is mandatory and how the product list is sorted and loaded.
Login & branch
Section titled “Login & branch”| Setting | Description | Default |
|---|---|---|
| Login required for ordering | An order can only be submitted if the user is logged in | Off |
| Branch required when ordering | A branch must be selected before submitting | Off |
When is login useful?
Section titled “When is login useful?”Procurement is an internal tool by nature. Whether a login is needed depends on your setup:
- Login off (default): Fast entry when the app runs internally on secured devices anyway. The user is guided to login on demand when needed - there is no hard block.
- Login on: Useful when it should be traceable who ordered (the logged-in user lands as “Ordered by” in the email) or when the approval workflow is used.
When is a branch useful?
Section titled “When is a branch useful?”Branches come from the locations module (internally locations). With “Branch required when ordering” on, a branch picker appears in the cart. The selected branch (name + address) is automatically included in the supplier email - so the supplier knows where to deliver.
Sorting & pagination
Section titled “Sorting & pagination”| Setting | Description | Default |
|---|---|---|
| Default sorting | Initial sorting of the product list on open | Name (A–Z) |
| Products per page | Number of products loaded per page (pagination) | 20 |
Sort options
Section titled “Sort options”| Option | Effect |
|---|---|
| Name (A–Z) | Alphabetically by product name |
| Supplier | Grouped/sorted by supplier |
| Last ordered | Frequently/recently ordered products first |
Related topics
Section titled “Related topics” Features Enable the approval workflow and order templates
Mail Template Show branch and orderer in the order email