The dial
Three settings, per process.
Your team does the work.The application works the way enterprise software always has. Your team makes every decision.
Common starting point for every process.
AI recommends. People approve.AI recommends. A person reviews and approves every change before it takes effect.
Most teams move here first, one process at a time.
AI acts inside your limits.AI acts within the limits you set. Anything outside them goes to the person you name.
For processes where the rules are clear and trust is earned.
The controls
You stay in charge at every setting.
Per process, not per product
Automate markdowns and keep regular price on Assist. Each process gets its own setting.
Limits you set
Price floors, allocation minimums, content rules. AI can’t act outside them.
Named approvers
Decide who approves what, by process, category or size of change.
Full audit trail
Every recommendation, approval and change, with who approved it and why.
Reversible
Move any process back to Assist or Off at any time. Nothing is locked in.
Reasoning shown
Recommendations come with the reasoning behind them, so your team can check the work.
By application
What each setting looks like.
| Application | Off | Assist | Automate |
|---|---|---|---|
| MDM | Data stewards create, match and approve records. | AI suggests matches, fixes and missing attributes, and a steward approves each one. | Records that pass your validation rules publish, and exceptions go to a steward. |
| PIM | Your content team writes and enriches every item. | AI drafts descriptions and attributes in your brand voice, and an editor approves them. | Content that meets your completeness and brand rules publishes, and the rest goes to review. |
| Planning | Planners build and reforecast plans. | AI proposes forecasts and reforecasts, and a planner accepts or edits them. | In-season reforecasts within your tolerance update on their own, and anything outside it is flagged. |
| Allocation | Allocators set the rules and run allocations. | AI recommends store quantities, and an allocator approves them. | Allocations within your rules release, and exceptions go to an allocator. |
| Lifecycle pricing | Your team sets prices, promotions and markdowns in the application. | AI proposes this week’s markdowns, and a merchant approves them. | Markdowns within your rules go through, and exceptions go to a merchant. |
Start at Off. Move when you’re ready.
We’ll walk through the dial on the process you care about most.