Commercially sensitive changes tend to be caught by someone noticing, or not caught at all. In Pimberly, a workflow is built in the drag and drop builder, triggered when a calculated margin falls below a minimum held in a data set, then tested live: reducing margin below the threshold raises a warning and routes the change for approval. The approver sees the rule breached, the current value and the proposed one, and every decision is recorded against the product.
With Pimberly’s workflow builder, you can:
- Build a workflow in the drag-and-drop builder, so the team that owns the process can maintain it without developer support
- Trigger a workflow from a schema condition — such as a calculated margin falling below a minimum
- Hold the minimum in a data set rather than on individual products, so one change applies globally
- Warn on save when a live product breaches the rule, with the option to correct the value or submit it for approval
- Show the approver the rule that was breached, the current value and the proposed one, so they can approve or reject with full context
- Record every decision against the product, so sensitive changes are checked automatically rather than relying on someone noticing
See how it works in the video below: