Delete a product after its dependencies are removed
Purpose
An administrator chooses Delete for a product that no longer needs a continuing identity.
How It Works
An administrator chooses Delete for a product that no longer needs a continuing identity. The service checks its lock and the accounting setup’s lock. Database references prevent removal while another bundle or a transaction depends on it. Successful deletion removes the product’s owned configuration. The template cleanup happens after that commit. A cleanup failure therefore leaves a removed product and requires operational follow-up. Some transaction-reference refusals still surface as server errors rather than useful explanations. Product delete authority does not bypass those dependencies.
Relationships
The product record supplies the identity and configuration used by this outcome.