Approvals by store

The customer asks: Each store's purchase orders or transfers are approved by that store's manager

• Verdict: Ready, with limits (1)
• Door: Configure · area: Documents and print › Approvals
• Recipe: Approvals across stores
• Sample: S14 — price-change approvals across stores
• Checked: carried 2026-10-16 · not re-run

What you build

A workflow whose approver is chosen by the document's store. Configuration only.

Limits

• Who may edit a record in a workflow state is checked in the browser only: follow the four safeguards in chapter 13a.

Tell the customer

Each store's documents go to that store's approver.

What next

1. Tell the customer the 1 limit above, and write it into the proposal.
2. Follow the recipe: Approvals across stores.
3. Copy the sample: S14 — price-change approvals across stores, and change it.
4. Build and test it on your sandbox (request one if you have none; what is on it).
5. Check it on your sandbox as the people who will use it; where it touches a price or a total, the money kit's release gate proves it (testing and release).
6. Make the same settings on the customer's site, from the list you wrote down, through the customer's own change process.

Nothing to code: write down each setting you make on your sandbox, so it is made the same way on the customer's site.

Related needs

• The approver must give a reason when rejecting a purchase order, and it is kept on the document — Ready, with limits (4)
• An e-mail at each approval step with the purchase order's PDF attached, and the uploaded CSV — Ready, with limits (4)
• Fields cannot be changed once the document is approved — Ready, with limits (1)
• Only the receiving store receives a transfer; only a supervisor cancels it — Not yet

Start a project shortlist with this need · Put it in your blueprint · Every need

This card in the kit