One BU has one Item Master Listing. A dedicated person manages it through permission, not role name.
| Thing | Count (read 2026-09-15) |
|---|---|
| Items with an id | 620 (623 rows) |
| Package component rows | 430 |
| Account rows | 114 |
The 17 August sheet had 619 item rows, 430 package-component rows and 92 account rows. Its relationships and identifiers are mostly consistent, but it was not ready for direct import.
A package is a parent plus components, and the component total must equal the package price. Package allocation of an overall discount must still preserve that equality.
Known bug: a search for Bottle Trap returns nothing, although Bottle Trap is in the list — it is one of the seven parts behind Basic and Premium Plumbing Fittings, both posting to 505-3100. The likely cause is that search matches only the parent package name and never the parts inside it. Every trade has parts sitting inside a package the same way, so this is worth checking before more of these arrive.
OTHER is ONE controlled Item Master record with one fixed Item Master ID and one generic Sales ACC No. (Confirmed by Charlie, 19/08/2026.)
Proposed: 599-9990 — Others / Unclassified line. Awaiting Account's confirmation; this is a recommendation, not a lock. The export cannot carry a blank. Q11.
The reasoning is a precedent already set. Site Visit was collapsed to one product, 599-9300, rather than one per trade, because the order already carries the trade. OTHER is the same shape: one account per trade would add fifteen accounts to answer a question the order already answers. All ten 599-9x00 slots are taken, so 9990 is the next clean number and reads as the end of the block.
The Sales ACC No. belongs on the item. Sales, OE and field workers do not choose or see it during normal work.
When Account generates the AutoCount template, the system reads each itemize row's Item Master ID, looks up the Sales ACC No. and writes it into the template. The exported payload keeps the exact value used, for audit after posting.
Current gap: the order-item API still exposes this value to order viewers.
Every countable row is buy-to-order, except a short keep-stock list that only the store team can name. A purchase is raised per order once the customer has said yes; there is no standing purchasing cycle. A zero stock balance is the normal reading and must never show as "out of stock".
| Blocker |
|---|
| The current app has no real package-component model or importer for the final sheet structure |
| 41 item rows have no default price; 30 packages are affected by 60 blank component prices |
| 19 duplicate display-name groups cannot be distinguished in a name-and-description picker |
| 14 package rows carry only a Sales ACC No., not the full AutoCount field set |
| All 619 rows are still Draft, so an activation gate is required |
| The sheet has one generic Site Visit product and contra line. Operationally, Site Visit remains a Trade choice on the order; the later converted order uses the major trade |
| The visible RAW LIST evidence tab must be excluded from import or moved to an archive location |
The simplest launch boundary is to activate completed standalone items first; incomplete items and packages stay Draft. Missing Cost may leave margin and commission unavailable without blocking a sale, when Account has approved the selling price.
Who verifies what: Decisions § A12.