Signal turns Channel sales history into a review queue. An outlet-health sweep compares each outlet's sales invoices over the last fifteen days with the fifteen before and queues the outlets whose order value has fallen. A suggested-order-quantity request works out a reorder quantity for one outlet and product. Both use fixed rules with stated reasons, with no machine learning, and neither ever creates an order by itself. A person accepts or dismisses each item, and accepting a suggestion can draft one purchase order in Channel. The workspace has three tabs: Overview, Decision queue and Generate.
01
Review queue that drafts purchase orders
AvailableEvidence-backed items to accept or dismiss. Accepting a suggestion drafts one purchase order.
Each recommendation stores the evidence and the version of the rules it was calculated with, so a decision can be checked against what the rules said at the time. Open items are not duplicated. Dismissing needs a reason. Accepting a suggested-order-quantity item and sending it on creates a single draft purchase order in Channel for a supplier you choose, shipped to the outlet's parent distributor by default. Sending it twice returns the same draft.
- Suggestion kinds: outlet health, suggested order quantity
- Sending is safe to repeat, so a retry cannot create a second draft
- The workspace shows the rules as fixed, with a version label for each of the two calculations
- Through the sweep, only declining and high-decline outlets enter the queue
Where to find it: Signal workspace, Decision queue tab
02
Suggested order quantity
Built and testedA reorder quantity for each outlet and product from purchase history, with reasons and a confidence value.
The calculation takes the median quantity per purchase over the median gap between an outlet's purchases as its daily run rate, covers lead time plus review period plus safety days, and rounds to pack size and minimum order quantity. In the workspace the constraints are fixed defaults (pack size 1, minimum order 1, lead time 2 days, review period 7 days, safety 3 days), and outlet stock on hand is not supplied, so the calculation assumes none (reason shown: no stock data assumed zero). It is used through the review queue above.
- History window of 30 to 365 days (default 60)
- Reasons shown include insufficient history, pack rounded, lead-time cover and no stock data assumed zero
- Suggestions never place orders
- Pack sizes and minimums for each product cannot be set in the workspace yet
Where to find it: Signal workspace, Generate tab
03
Outlet health classification
Built and testedOutlets are classified by the change in order value between two periods; the workspace sweep queues the declining ones.
The sweep compares the last 15 days of an outlet's sales invoices with the previous 15 and applies fixed thresholds: a fall of 10 percent or more is declining and a fall of 40 percent or more is high decline. An outlet needs at least two invoices in each window, otherwise it is labelled new and left alone. Only declining and high-decline outlets become recommendations. The rules also define a dormant state (no order for 45 days), but the sweep does not supply days since the last order and only looks at outlets invoiced in the last 30 days, so it cannot produce dormant today.
- States defined: high growth, growth, stable, declining, high decline, dormant, new
- Compares order count and order value across the two windows
- The thresholds are defaults; the workspace does not expose them
Where to find it: Signal workspace, Generate tab
04
Target disaggregation
Built and testedA calculation that splits a target down the hierarchy with exact reconciliation is built and tested; the workspace does not expose it.
The calculation and its tests exist. Nothing in the Signal workspace or the API uses it, so there is no target screen today.
- Built and tested
- Not reachable from the workspace
05
Fraud and leakage signals
Built and testedA calculation that produces inputs for review is built and tested; the workspace does not expose it.
Its output is meant as input for review, never as an accusation, and it has tests. Nothing in the Signal workspace or the API uses it.
- Built and tested
- Not reachable from the workspace
06
Channel performance dashboards and backtesting
RoadmapDashboards and backtesting are planned only.
The plan optionally combines Channel and Field data. Nothing is built yet.