For the complete documentation index, see llms.txt. This page is also available as Markdown.

Storing and Cancelling Services

Services rarely end one at a time. Someone leaves the company, a project wraps up, a team switches to different hardware — and suddenly you are looking at a list of services that all need the same treatment.

Storing and cancelling are both built as bulk actions, and both work the same way: equipme checks every selected service against the conditions for that action before anything is carried out. You can start either action from the list view or from the detail view of a service. The dialog behaves identically in both places.

Storing services

When you store services, you first decide where they should go.

Internal storage keeps the item in your own warehouse, where it stays available for a later assignment.

External storage returns it to the supplier.

The storage dialog with the selected services and the available options.

Depending on the action, the dialog also offers further options, such as a return reason or a preferred execution time. These are set once for the whole selection.

Cancelling services

Cancelling follows the same pattern. The dialog lists the services you selected and shows which of them can actually be cancelled.

The cancellation dialog showing the affected services.

When a service cannot be processed

Not every service in a selection is always eligible. A service can be blocked by its current status or by other conditions that apply to the action.

Both dialogs handle this the same way:

  • They show how many of the selected services are eligible for the action.

  • They explain why the remaining services cannot be processed.

  • They let you remove those services directly in the dialog.

So you do not have to abandon the dialog and rebuild your selection. Take out what is blocked, continue with the rest, and deal with the blocked services separately once you know what is holding them up.

This is the same availability logic you already know from moving services.

Cancelling a service is not the same as cancelling an order

The actions above apply to services that already exist in your inventory. Cancelling an order that is still being processed follows a different rule.

Confirmation is the point where the supplier signals that processing has started, which makes the order binding. This matters most when orders are approved automatically, because confirmation can follow very shortly after the order is placed.

If an order needs to be stopped after that point, it has to be clarified with the supplier directly.

Last updated

Was this helpful?