Approval Worklist
Whatever a gate parked collects here — with the reason next to it. Releasing an entry sends the order to the supplier.
Reach it through the Awaiting Approval cue or by searching for Trading Approvals.
What lands here
Runs with the result Pending Approval. That happens in two ways:
- A gate parked the run — order value, price deviation or daily limit
- The automation level is Transmit with Approval — then every run waits
A run a gate stopped (margin too low, offer too old) does not land here. It has ended and only appears in the sourcing log.
The columns
| Column | Meaning |
|---|---|
| Sales Order No. | The order in question |
| Selected Vendor Name | The vendor the run picked |
| Landed Cost | What the order costs at that vendor, including freight and insurance |
| Margin % | What the order leaves afterwards |
| Why it is waiting | Which gate parked the run, and by how much |
| Purchase Order No. | The purchase order already created — empty when the gate fired before it was written |
An empty order number is not an error
If a gate fired before the purchase order was written, the column is empty. Releasing creates it — there is nothing to catch up on.
Releasing
The Release action does three things:
- Creates the purchase order if it does not exist yet
- Checks the price again — prices move while an order waits
- Hands the purchase order to the supplier connector
The re-check can prevent the release
If the supplier price now deviates further than Max. Price Deviation % allows, the order does not go out. The run ends with Price Deviation and names both prices — the one it was decided on and the current one.
This is intended: an order that sat in the worklist for two days should not go out at the price from two days ago.
Several rows can be released together. The summary then reports how many were released and how many were not; the reasons sit on the individual runs.
Turning down
Turn Down ends the run with the result Rejected and records who did it.
An existing purchase order stays
Turning down does not clean up. If the purchase order was already written it still exists in Business Central and has to be handled by hand — deleted or used otherwise.
This is deliberate: automatically deleting an order somebody may already have worked on would be the more dangerous path.
When the worklist is permanently full
Then a gate is too tight — or the automation level does not match everyday operation.
| Observation | Obvious adjustment |
|---|---|
| Nearly all waiting on order value | Raise the limit or set it to 0 |
| Nearly all waiting on daily limit | Match the limit to your actual daily volume |
| All waiting, regardless of reason | The automation level is Transmit with Approval — that is by design |
| Individual ones waiting on price deviation | The supplier moves prices faster than you release. Check the tolerance, or release more often |