Phone orders sent to the store that serves the customer's district
The customer asks: Our call centre takes orders by phone; each order should go to the store that serves the customer's district
- Verdict: Ready, with limits (7)
- Door: Desk action · area: Integrations, payments and hardware › Online shops and order systems
- Recipe: Call-centre orders by district: send each phone order to its store
- Sample: S35 — Call-centre orders by district (pp_cco): a button that routes a phone order
- Checked: 2026-10-21 · bench
What you build
A Serving store field on the shop's own Territory tree (a district's store, or the store of the territory above it), and a button on a draft sales order, Send to store, answered by your service: it walks the order's territory up the tree, checks the store's warehouse, and writes it on the order and on every line. The store then sees the order in its own list.
Limits
- An agent presses the button: an order is not routed on its own when it is saved.
- The territory is the customer's: an order for another district needs its territory changed before the press.
- Drafts only, one order at a time; a submitted order is cancelled and amended to move it.
- The service reads the whole order and writes it back: the app's user needs read and write on every sales order and read on every customer, territory and warehouse.
- A store's own tax or prices can change the total when the warehouse changes; the agent is told.
- A store with a User Permission on its warehouse still sees an order whose Set Source Warehouse is empty.
- No notice to the store: its filtered list is its inbox.
Tell the customer
Your call centre enters each phone order once, presses one button, and the order ships from the store that serves the customer's district.
What next
- Tell the customer the 7 limits above, and write them into the proposal.
- Follow the recipe: Call-centre orders by district: send each phone order to its store.
- Copy the sample: S35 — Call-centre orders by district (pp_cco): a button that routes a phone order, and change it.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Related needs
- Click and collect — the store sees which web orders to pick and which customers are coming to collect — Ready, with limits (7)
- Orders from our own online shop come in; stock and prices go out — Ready, with limits (2)
- Our order-management or warehouse system linked to the stores — Ready, with limits (2)
- Our WooCommerce shop linked to the stores — Ready, with limits (2)
Start a project shortlist with this need · Put it in your blueprint · Every need