Head-office reports and BI
The customer asks: Head-office reports and our BI tool fed with sales and stock
- Verdict: Ready, with limits (3)
- Door: Outside app · area: Reports and data › Reports and BI
- Recipe: Feed a data warehouse from the shop
- Sample: S9 — a BI feed: sales, lines, payments and returns into a warehouse file, picking up where it stopped
- Checked: carried 2026-10-16 · not re-run
What you build
An outside app on the feed and bulk reads fills the BI tool.
Limits
- Rows are as of extraction: a later change to a booked sale, other than a return or a cancellation, is not followed.
- The kit's samples read the shared feed, whose key is not limited to one app (a feed scoped to your app is an extension point, chapter 9).
- Offline sales arrive late, when the till syncs.
Tell the customer
Head office sees sales and stock in its own BI tool, shortly after they are booked.
What next
- Tell the customer the 3 limits above, and write them into the proposal.
- Follow the recipe: Feed a data warehouse from the shop.
- Copy the sample: S9 — a BI feed: sales, lines, payments and returns into a warehouse file, picking up where it stopped, 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.
Stop your service for a while and start it again: it must catch up from the event feed, missing nothing.
Related needs
- A statement of what each customer owes, printed and sent on a schedule — Ready, with limits (3)
Start a project shortlist with this need · Put it in your blueprint · Every need