A branch sees its own store's stock and the head office's

The customer asks: A branch sees the stock of its own store and the head office's, no other

• Verdict: Ready, with limits (4)
• Door: Configure · area: Stock and buying › Who sees which stock
• Recipe: Set a shop up with no code
• Sample: none yet
• Request: P-STORESCOPE · ask for an extension point
• Checked: run on a sandbox 2026-10-16 · POS 2.0.0.647 · a user with one warehouse permission: three lists and five report layouts fenced, three reports not; not run: two stores' permissions together, the till's stock panel, the other stock reports

What you build

A User Permission on Warehouse for each store a user may see, their own and the head office's, set in iVendNext Desk.

Limits

• With one permission, the Bin, Stock Ledger Entry and Warehouse lists, and the reports Stock Balance (also with another store chosen), Stock Ageing by store, Stock Ledger, Total Stock Summary and Warehouse Wise Stock Balance, showed that store only (run).
• Three reports showed other stores to the same user (run): Item Balance (Simple) and Warehouse wise Item Balance Age and Value showed every store, and Stock Ageing in its default layout showed the stock of every store, and of any store chosen in its filter. Test each stock report a branch may open, in each layout, and take away the ones that leak.
• A user with two permissions (own store and head office) was not run; nor were the other stock reports.
• At the till the Other stores stock panel shows every store or none, never own and head office (from the product's code, not run): ask for P-STORESCOPE.

Tell the customer

A branch sees its own store's stock in the lists and in the reports we tested; some stock reports must be taken away from it, each one tested first, and the till's stock panel shows every store or none.

What next

1. Tell the customer the 4 limits above, and write them into the proposal.
2. Follow the recipe: Set a shop up with no code.
3. Build and test it on your sandbox (request one if you have none; what is on it).
4. 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).
5. Make the same settings on the customer's site, from the list you wrote down, through the customer's own change process.
6. To lift a limit, ask for P-STORESCOPE (the extension-point request; members only).

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

• A coded reason when a cashier voids, returns or discounts — Ready, with limits (3)
• An e-mail at each approval step with the purchase order's PDF attached, and the uploaded CSV — Ready, with limits (4)
• Members pay less, by tier — Ready, with limits (5)
• One more detail on a line, for goods with no serial number — Ready, with limits (2)

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

This card in the kit