Requirements Catalogue — Kingsway Retail Group

No catalogue items match — clear the filter.

Use cases

ID	Use case	Sponsor	Success criteria	Status	Links
UC-001	Daily Stock Availability Monitoring TBD	TBDsponsor	TBD	draft	— Q1.2
UC-002	Automated Monday Trading Pack TBD	TBDsponsor	TBD	draft	— Q1.2
UC-003	Finance-Aligned Metric Definitions TBD	TBDsponsor	TBD	draft	— Q1.2
UC-004	Trading Pack Delivery Milestones TBD	TBDsponsor	TBD	draft	— Q1.3
UC-005	Like-for-Like Sales Analysis TBD	TBDsponsor	TBD	draft	— Q2.3
UC-006	Margin Impact Analysis TBD	TBDsponsor	TBD	draft	— Q2.3
UC-007	Legacy DW Transition TBD	TBDsponsor	TBD	draft	— Q3.3
UC-008	Governed Self-Service Analytics TBD	TBDsponsor	TBD	draft	— Q5.2
UC-009	Product Daily-Grain Modelling TBD	TBDsponsor	TBD	draft	— Q5.4
UC-010	Historical Price and Cost Tracking TBD	TBDsponsor	TBD	draft	— Q5.4
UC-011	Historical Data Retention TBD	TBDsponsor	TBD	draft	— Q5.5
UC-012	Data Residency and Compliance TBD	TBDsponsor	TBD	draft	— Q6.2
UC-013	Data Retention and Privacy TBD	TBDsponsor	TBD	draft	— Q6.3
UC-014	Data Availability and Service Levels TBD	TBDsponsor	TBD	draft	— Q7.1
UC-015	Reporting Performance and Capacity TBD	TBDsponsor	TBD	draft	— Q7.4
UC-016	Project Governance and Communication TBD	TBDsponsor	TBD	draft	— Q9.1
UC-017	Sales and Stock Reconciliation TBD	TBDsponsor	TBD	draft	— Q3.2
UC-018	Trusted Sales Reporting TBD	TBDsponsor	TBD	draft	— 00:00:26.900
UC-019	Daily Channel Performance Reporting TBD	TBDsponsor	TBD	draft	— 00:10:05.000
UC-020	Product Master Data Quality TBD	TBDsponsor	TBD	draft	— 00:07:59.300
UC-021	Store Master Data Quality TBD	TBDsponsor	TBD	draft	— 00:09:20.000
UC-022	Phase-One Scope Control TBD	TBDsponsor	TBD	draft	— 00:13:30.000
UC-023	Stock Shrinkage Analysis TBD	TBDsponsor	TBD	draft	— 00:06:30.000
UC-024	Conformed Sales and Stock Dimensions TBD	TBDsponsor	TBD	draft	— 00:05:49.200
UC-025	Stock Data Quality Handling TBD	TBDsponsor	TBD	draft	— 00:07:27.300
UC-026	Receipts Feed Modelling TBD	TBDsponsor	TBD	draft	— email
UC-027	Receipts Feed Cadence Handling TBD	TBDsponsor	TBD	draft	— email
UC-028	Stock Snapshot Business Dating TBD	TBDsponsor	TBD	draft	— email
UC-029	Stock Snapshot Failure Handling TBD	TBDsponsor	TBD	draft	— email
UC-030	Phase-One Scope Definition TBD	TBDsponsor	TBD	draft	— email
UC-031	Decision-Ready Issue Resolution TBD	TBDsponsor	TBD	draft	— email

User stories hide retired

ID	Story	Use case	Owner	Sources	Metrics	Status	Src
US-001	As a Supply Chain Director, I want a trusted daily stock and availability view so that I can monitor inventory position reliably each day.	UC-001	TBDSupply Chain Director	—	—	draft	Q1.2
US-002	As a Head of Trading Analytics, I want the Monday trading pack to be automated so that weekly trading reporting is produced consistently without manual effort.	UC-002	TBDHead of Trading Analytics	—	—	draft	Q1.2
US-003	As a Finance Controller, I want revenue and margin definitions to match the management accounts so that reported financial outputs are consistent with finance reporting. → superseded by US-037	UC-003	TBDFinance Controller	—	—	draft	Q1.2
US-004	As a trading stakeholder, I want the trading pack to be live for the August bank-holiday trading week so that the solution supports that key trading period.	UC-004	TBDstakeholder	—	—	draft	Q1.3
US-005	As a project stakeholder, I want delivery completed before the Christmas trading freeze in mid-November so that deployment does not disrupt the freeze period.	UC-004	TBDstakeholder	—	—	draft	Q1.3
US-006	As a Head of Trading Analytics, I want the Monday trading pack to be produced automatically with like-for-like sales, margin, and discount by store, channel, and category and delivered by 09:00 so that trading performance is available on time at the required level of detail. → superseded by US-035	UC-002	TBDHead of Trading Analytics	—	—	draft	Q2.2
US-007	As a Head of Trading Analytics, I want to analyse like-for-like sales for last week by store and channel so that I can assess recent trading performance across locations and routes to market. → superseded by US-036	UC-005	TBDHead of Trading Analytics	—	—	draft	Q2.3
US-008	As a Supply Chain Director, I want a daily morning view of out-of-stock and thin-cover positions by store and SKU so that I can identify and respond to availability risks early each day. → superseded by US-054	UC-001	TBDSupply Chain Director	—	—	draft	Q2.3
US-009	As a Finance Controller, I want to analyse the margin impact of sales and markdowns so that I can understand profitability drivers. → superseded by US-039	UC-006	TBDFinance Controller	—	—	draft	Q2.3
US-010	As a delivery team, I want the legacy Retail DW to run in parallel for one quarter after go-live so that outputs can be compared during transition before retirement.	UC-007	TBDstakeholder	—	—	draft	Q3.3
US-011	As a business user, I want Power BI reports and a governed semantic model for self-service so that I can consume trusted analytics and perform governed self-serve analysis.	UC-008	TBDstakeholder	—	—	draft	Q5.2
US-012	As a data consumer, I want both products modelled at daily grain so that analysis can be performed consistently at day level.	UC-009	TBDstakeholder	—	—	draft	Q5.4
US-013	As a finance and trading user, I want price and cost history preserved as it changes so that I can analyse historical values accurately over time.	UC-010	TBDstakeholder	—	—	draft	Q5.4
US-014	As an analyst, I want 3 years of sales history available so that I can perform trend and comparative analysis over a multi-year period.	UC-011	TBDstakeholder	—	—	draft	Q5.5
US-015	As an analyst, I want 13 months of daily stock snapshots and monthly stock history thereafter so that I can analyse recent stock movements in detail and older periods at summary level.	UC-011	TBDstakeholder	—	—	draft	Q5.5
US-016	As a compliance stakeholder, I want all data kept in the UK South region with no cross-region replication so that data residency requirements are met.	UC-012	TBDstakeholder	—	—	draft	Q6.2
US-017	As a compliance stakeholder, I want sales transactions retained for 7 years so that statutory and audit retention obligations are met.	UC-013	TBDstakeholder	—	—	draft	Q6.3
US-018	As a compliance stakeholder, I want customer file data retained while active plus 2 years so that customer data retention follows policy.	UC-013	TBDstakeholder	—	—	draft	Q6.3
US-019	As an analyst, I want stock snapshots retained for 13 months daily and then as monthly aggregates so that I can analyse recent stock history in detail and older history in summary form.	UC-011	TBDstakeholder	—	—	draft	Q6.3
US-020	As a compliance stakeholder, I want GDPR erasure requests supported on the customer file so that personal data can be removed in line with regulation.	UC-013	TBDstakeholder	—	—	draft	Q6.4
US-021	As a business user, I want data available by 07:00 UK each weekday so that I can start daily analysis with current information. → superseded by US-042	UC-014	TBDstakeholder	—	—	draft	Q7.1
US-022	As a trading stakeholder, I want the trading pack issued by 09:00 on Mondays so that weekly trading reporting is available on time.	UC-002	TBDstakeholder	—	—	draft	Q7.1
US-023	As a service owner, I want business-hours availability to be sufficient so that the platform is operated to the agreed support window.	UC-014	TBDstakeholder	—	—	draft	Q7.2
US-024	As a reporting stakeholder, I want the platform to support approximately 80 concurrent report users on Monday mornings so that peak reporting demand can be handled.	UC-015	TBDstakeholder	—	—	draft	Q7.4
US-025	As a project participant, I want a Teams channel used for project communication so that collaboration happens in a shared agreed location.	UC-016	TBDstakeholder	—	—	draft	Q9.1
US-026	As a project stakeholder, I want a weekly 30-minute progress call and a fortnightly demo so that delivery progress and outputs are reviewed regularly.	UC-016	TBDstakeholder	—	—	draft	Q9.2
US-027	As a project stakeholder, I want decisions confirmed within 3 working days of a written summary so that governance actions are closed promptly.	UC-016	TBDstakeholder	—	—	draft	Q9.4
US-028	As a compliance stakeholder, I want privacy controls applied to customer data, including restricted access and handling appropriate for Confidential classification so that confidential personal data is protected appropriately.	UC-013	TBDstakeholder	—	—	draft	Q6.1
US-029	As a compliance stakeholder, I want deletion or anonymisation processes that propagate GDPR erasure requests through downstream customer datasets so that all derived customer data can honor erasure obligations.	UC-013	TBDstakeholder	—	—	draft	Q6.4
US-030	As a data engineer, I want historisation or snapshot-based logic for product price and cost attributes because the source overwrites values in place so that historical price and cost changes are preserved accurately. → superseded by US-043	UC-010	TBDstakeholder	—	—	draft	Q5.4
US-031	As a platform owner, I want the semantic model and reporting capacity designed to handle peak Monday morning usage so that report performance remains acceptable during the busiest period.	UC-015	TBDstakeholder	—	—	draft	Q7.4
US-032	As a business user, I want reconciliation logic between sales and stock outputs so that current mismatches from different spreadsheet sources are resolved in the new platform. → superseded by US-034	UC-017	TBDstakeholder	—	—	draft	Q3.2
US-033	As a business sponsor, I want sales reporting that the business trusts so that business decisions can be made from reliable reported numbers.	UC-018	TBDBusiness sponsor	—	—	draft	00:00:26.900
US-034	As a business sponsor, I want a stock view that is not assembled from multiple spreadsheets so that stock reporting is consolidated and reliable in the new platform.	UC-017	TBDBusiness sponsor	—	—	draft	00:00:26.900
US-035	As a business sponsor, I want the Monday trading pack to produce week-on-week and like-for-like sales by store and by channel, with margin, every Monday morning so that the pack contains the core trading measures needed each week.	UC-002	TBDBusiness sponsor	—	—	draft	00:02:05.000
US-036	As a trading analytics lead, I want like-for-like sales to include only stores that have been trading for at least fifty-two weeks so that like-for-like analysis uses the agreed store eligibility rule. → superseded by US-076	UC-005	TBDTrading analytics lead	—	—	draft	00:03:18.000
US-037	As a trading analytics lead, I want revenue in the trading pack reported as net revenue excluding VAT, after line discounts so that pack revenue is calculated on the agreed basis. → superseded by US-048	UC-003	TBDTrading analytics lead	—	—	draft	00:04:02.000
US-038	As a data and insights lead, I want the reporting layer to strip VAT out of VAT-inclusive till prices so that reported revenue is net of VAT. → superseded by US-049	UC-003	TBDData and insights lead	—	—	draft	00:05:20.900
US-039	As a trading analytics lead, I want gross margin by category to use the cost that was true when the item was sold, not today's cost so that margin reporting reflects historical sale-time cost accurately.	UC-006	TBDTrading analytics lead	—	—	draft	00:06:24.000
US-040	As a business sponsor, I want the online versus store channel split every day so that channel performance is visible daily rather than only in monthly reporting.	UC-019	TBDBusiness sponsor	—	—	draft	00:10:05.000
US-041	As a trading analytics lead, I want markdown spend reported by category showing how much discount was given away in the sale so that discount impact can be analysed alongside margin. → superseded by US-052	UC-006	TBDTrading analytics lead	—	—	draft	00:11:00.000
US-042	As a trading stakeholder, I want the platform to support automated Monday-pack delivery from nightly-loaded source data rather than requiring intraday source refreshes so that the Monday pack can be produced from overnight ingestion.	UC-014	TBDstakeholder	—	—	draft	00:14:33.100
US-043	As a data engineer, I want the platform to maintain effective-dated product price and cost history independently of Merlin so that accurate historical margin reporting is possible even when the source overwrites values.	UC-010	TBDstakeholder	—	—	draft	00:07:11.800
US-044	As a data engineer, I want product master ingestion or transformation logic to deduplicate rows using the later updated date as the live record so that duplicate product rows do not corrupt reporting.	UC-020	TBDstakeholder	—	—	draft	00:07:59.300
US-045	As a data consumer, I want the sales model to tolerate sales SKUs that are missing from the current product master rather than dropping or failing those records so that reporting remains complete for discontinued or unmatched products.	UC-017	TBDstakeholder	—	—	draft	00:08:43.200
US-046	As a business user, I want the store dimension process to handle late-arriving or incomplete store master data so that new stores are not excluded from reporting. → superseded by US-065	UC-021	TBDstakeholder	—	—	draft	00:09:20.000
US-047	As a project stakeholder, I want customer-level analytics excluded from the initial phase-one scope so that delivery focuses on sales and stock first. → superseded by US-077	UC-022	TBDstakeholder	—	—	draft	00:13:30.000
US-048	As a trading analytics lead, I want net revenue in the trading pack to exclude card fees and delivery income, with those reported on separate management-account lines, so that trading-pack revenue aligns to finance presentation and avoids mixing measures.	UC-003	TBDFinance	—	—	draft	email
US-049	As a data and insights lead, I want standard-rated POS till prices converted from VAT-inclusive to VAT-exclusive by dividing by 1.2 so that reported revenue is net of VAT on the agreed basis.	UC-003	TBDData Engineering	—	—	draft	email
US-050	As a finance stakeholder, I want the trading pack VAT-removal logic to assume all sold items are standard-rated and apply a flat 1.2 divisor so that revenue is calculated consistently without unnecessary VAT complexity.	UC-003	TBDFinance	—	—	draft	email
US-051	As a trading analytics lead, I want returns treated as negative quantity lines that net off revenue in the week the return occurs rather than the week of the original sale so that weekly revenue reflects return timing correctly.	UC-003	TBDData Engineering	—	—	draft	email
US-052	As a trading analytics lead, I want margin in the trading pack left gross of supplier funding for now so that the build follows the current interim finance position until final policy is provided.	UC-006	TBDFinance	—	—	draft	email
US-053	As a trading stakeholder, I want the trading pack to present net revenue separately from card fees, delivery income, and margin lines so that finance-aligned reporting remains trusted and consistent with management accounts.	UC-018	TBDstakeholder	—	—	draft	email
US-054	As a Supply Chain Director, I want yesterday's stock position for every store and every SKU on one screen before the 08:30 trade call so that I can review the prior trading day's stock position in time for the morning trade call.	UC-001	TBDSupply Chain Director	—	—	draft	00:01:05.000
US-055	As a Supply Chain Director, I want the daily stock view to include stock on hand, out-of-stock status, and thin cover indicators so that I can identify stock availability risks and low-cover positions.	UC-001	TBDSupply Chain Director	—	—	draft	00:01:05.000
US-056	As a Supply Chain Director, I want stockout defined as a ranged SKU with zero on hand at close, not low stock, so that stockout reporting uses a precise and consistent business rule.	UC-001	TBDSupply Chain Director	—	—	draft	00:04:50.000
US-057	As a Supply Chain Director, I want a daily count of stockouts by store so that I can compare availability issues across stores each day.	UC-001	TBDSupply Chain Director	—	—	draft	00:04:50.000
US-058	As a Supply Chain Director, I want days of cover calculated as stock on hand divided by average daily sales over the last four weeks so that the cover metric is derived consistently.	UC-001	TBDSupply Chain Director	—	—	draft	00:05:00.000
US-059	As a Supply Chain Director, I want days of cover included as an early-warning metric in the stock view so that the trade call can use it to identify emerging availability risks.	UC-001	TBDSupply Chain Director	—	—	draft	00:05:00.000
US-060	As a Supply Chain Director, I want shrinkage calculated as opening stock plus receipts minus sales minus closing stock so that shrinkage is measured consistently across stores and SKUs.	UC-023	TBDSupply Chain Director	—	—	draft	00:06:30.000
US-061	As a Supply Chain Director, I want the stock reporting solution refreshed and available before 08:30 each day using the previous trading day's close snapshot so that the morning trade call uses the correct prior-day stock position. → superseded by US-067	UC-001	TBDstakeholder	—	—	draft	00:03:05.000
US-062	As a data consumer, I want the stock product to integrate sales data so that days-of-cover can be calculated.	UC-001	TBDstakeholder	—	—	draft	00:05:40.000
US-063	As a data consumer, I want store and product dimensions conformed between sales and stock datasets so that days-of-cover calculations are valid across both products.	UC-024	TBDstakeholder	—	—	draft	00:05:49.200
US-064	As a Supply Chain Director, I want days-of-cover calculations to tolerate missing snapshot days rather than interpreting them as zero stock so that false availability alerts are avoided when a snapshot is absent. → superseded by US-069	UC-001	TBDstakeholder	—	—	draft	00:08:09.900
US-065	As a business user, I want the solution to account for orphan stores present in source systems but missing from the master store list across both sales and stock products so that affected stores are not excluded or mismatched in reporting.	UC-021	TBDstakeholder	—	—	draft	00:08:40.000
US-066	As a business user, I want data quality rules and user guidance to distinguish legitimate negative on-hand values from actual load errors so that known operational behaviours are visible without being silently corrected. → superseded by US-068	UC-025	TBDstakeholder	—	—	draft	00:07:27.300
US-067	As a Supply Chain Director, I want StockRoom snapshot qty_on_hand interpreted as the previous trading day's closing position rather than a live 02:00 position or morning opening position so that daily stock reporting uses the correct business meaning of the snapshot.	UC-001	TBDdata engineer	—	—	draft	email
US-068	As a business user, I want data profiling and downstream logic to treat negative qty_on_hand rows for Glasgow (ST-0006) as valid business records rather than load corruption so that known operational behaviours are preserved correctly in stock reporting.	UC-025	TBDdata engineer	—	—	draft	email
US-069	As a Supply Chain Director, I want the Leeds (ST-0004) store-day for 21 June handled as a known blank caused by snapshot job failure, not assumed to be zero stock or normal completeness, so that missing snapshots do not create false availability signals.	UC-001	TBDdata engineer	—	—	draft	email
US-070	As a data engineer, I want the receipts feed modelled at one row per delivery line so that receipt-level analysis and downstream processing use the correct source grain.	UC-026	TBDdata engineer	—	—	draft	email
US-071	As a data engineer, I want receipts feed ingestion and downstream expectations to account for deliveries landing on Mondays and Thursdays so that completeness checks and operational handling align to the actual delivery cadence.	UC-027	TBDdata engineer	—	—	draft	email
US-072	As a data consumer, I want stock snapshots to carry an explicit trading date separate from the technical load timestamp so that stock positions are reported against the correct business day.	UC-028	TBDstakeholder	—	—	draft	email
US-073	As a service owner, I want monitoring and exception handling to detect missing store-day snapshots and support operational rerun escalation so that snapshot failures that do not self-heal are identified and corrected promptly.	UC-029	TBDstakeholder	—	—	draft	email
US-074	As a data engineer, I want receipts-feed completeness checks and reporting logic to expect no delivery arrivals outside Mondays and Thursdays unless business rules change so that false data-quality alerts are avoided on non-delivery days.	UC-027	TBDstakeholder	—	—	draft	email
US-075	As a project stakeholder, I want phase one to include two data products only: sales analytics at order-line grain and the daily stock snapshot so that the initial delivery scope is explicit and signed off.	UC-030	TBDstakeholder	—	—	draft	email
US-076	As a trading analytics lead, I want like-for-like sales to include only stores that have been trading for at least fifty-two weeks and to exclude any store closed for refit for more than two weeks so that like-for-like analysis uses the agreed store eligibility rule.	UC-005	TBDstakeholder	—	—	draft	email
US-077	As a project stakeholder, I want phase-one analytics deliverables to exclude dependencies on loyalty data so that the initial scope is not delayed by unsupported customer-level data.	UC-022	TBDstakeholder	—	—	draft	email
US-078	As a project sponsor, I want the team to return a single recommended resolution for each open item rather than multiple alternatives so that unresolved issues can be closed decisively.	UC-031	TBDstakeholder	—	—	draft	email

Open questions & contradictions

OQ-001open→ resolve in design_refinement

What is the authoritative business definition of like-for-like sales for the trading pack?

surfaced from: questionnaire Q2.2

OQ-002open→ resolve in design_refinement

What exact revenue, margin, and discount definitions should be used so outputs match management accounts?

surfaced from: questionnaire Q1.2

OQ-003open→ resolve in sources_quality

What source or business rule should be used to repair the current margin-report failure when clearance lines hit discontinued SKUs?

surfaced from: questionnaire Q3.2

OQ-004open→ resolve in design_refinement

Should revenue for the pack include or exclude card fees and supplier funding, per Finance's view?

surfaced from: transcript https://contoso.sharepoint.com/sites/kingsway/transcripts/kickoff-2026-06-16.vtt @ 00:04:30.000: 'Before we carve that in stone — run it past Mark in finance before we lock it in. He has views about card fees and supplier funding.'

OQ-005open→ resolve in design_refinement

How should like-for-like treat store closures and refits in addition to the fifty-two-week rule?

surfaced from: transcript https://contoso.sharepoint.com/sites/kingsway/transcripts/kickoff-2026-06-16.vtt @ 00:03:30.100: 'Fifty-two weeks trading. Anything else in the definition? Closures, refits?'

OQ-006open→ resolve in data_custodians

Who owns the product hierarchy: trading or merchandising?

surfaced from: transcript https://contoso.sharepoint.com/sites/kingsway/transcripts/kickoff-2026-06-16.vtt @ 00:18:00.000: 'Before we close — who actually owns the product hierarchy — trading or merchandising?'

OQ-007open→ resolve in design_refinement

Should supplier-funded markdown be netted off margin, and what is the exact treatment Finance requires?

surfaced from: transcript https://contoso.sharepoint.com/sites/kingsway/transcripts/kickoff-2026-06-16.vtt @ 00:18:40.000: "Also parking — some of that markdown is supplier-funded, finance will want it netted off margin. Mark's the one to ask, same email as the revenue definition."

OQ-008open→ resolve in data_custodians

How should the model handle the known orphan store Croydon, which exists in StockRoom but is missing from the store list, across both sales and stock products?

surfaced from: transcript https://contoso.sharepoint.com/sites/kingsway/transcripts/stock-deepdive-2026-06-23.vtt @ 00:08:40.000: 'Croydon is in StockRoom already but still not on the store list. So the orphan store hits both products, sales and stock.'

OQ-009open→ resolve in sources_quality

What remediation or business handling should apply when a store snapshot day is blank, such as Leeds on the twenty-first, beyond tolerating it in days-of-cover logic?

surfaced from: transcript https://contoso.sharepoint.com/sites/kingsway/transcripts/stock-deepdive-2026-06-23.vtt @ 00:08:00.000: "Also the Leeds snapshot failed on the twenty-first, that day is blank for the whole store. It happens a couple of times a year, the job just doesn't rerun itself."

OQ-010open→ resolve in data_custodians

Who owns correction of Glasgow shrinkage adjustments that create negative on-hand values, given Stock office are supposed to correct them and mostly do not?

surfaced from: transcript https://contoso.sharepoint.com/sites/kingsway/transcripts/stock-deepdive-2026-06-23.vtt @ 00:07:15.000: "Stock office are supposed to correct them and mostly don't."

OQ-011open→ resolve in design_refinement

What is the required business handling for negative qty_on_hand at Glasgow (ST-0006): preserve as-is in reporting, cap at zero in curated outputs, or expose both raw and adjusted values?

surfaced from: email <[email protected]>: 'These are real rows, not load\n corruption. The stock office is supposed to zero them out and does not.'

OQ-012open→ resolve in design_refinement

For missing store-days such as Leeds on 21 June, should downstream datasets surface nulls, backfill after rerun, or apply any imputation/reporting annotation standard?

surfaced from: email <[email protected]>: 'Leeds (ST-0004): the snapshot job failed on the night of 21 June, so\n that store-day is blank in the feed. The job does not self-heal; a rerun\n needs raising with ops.'

Decision log

ID	Decision	Status	Decided	Approver	Evidence	Affects
D-0001	Run the legacy Retail DW in parallel for one quarter after go-live, then retire it	proposed	—	—	—	—
D-0002	Use the existing Microsoft estate with Fabric capacity in UK South and Power BI	proposed	—	—	—	—
D-0003	Deliver Power BI reports and a governed semantic model for self-serve	proposed	—	—	—	—
D-0004	Target business-hours availability	proposed	—	—	—	—
D-0005	Use the 'Kingsway–Acme Data Platform' Teams channel for project communication	proposed	—	—	—	—
D-0006	Adopt a weekly 30-minute progress call and a fortnightly demo cadence	proposed	—	—	—	—
D-0007	Confirm decisions within 3 working days of issuing a written summary	proposed	—	—	—	—
D-0008	Defer customer-level analytics to phase two	proposed	—	—	—	—
D-0009	Use a nightly extract cadence for the Monday pack	proposed	—	—	—	—
D-0010	Define net revenue for the trading pack as gross takings excluding VAT after line-level discounts and before card fees	proposed	—	—	—	—
D-0011	Use a flat 1.2 divisor to remove VAT from standard-rated sales	proposed	—	—	—	—
D-0012	Recognize returns in the week the return occurs	proposed	—	—	—	—
D-0013	Keep margin gross of supplier funding until CFO policy is provided	proposed	—	—	—	—
D-0014	Flag negative on-hand values at Glasgow as known behaviour	proposed	—	—	—	—
D-0015	Confirm snapshot timing in writing by email	proposed	—	—	—	—
D-0016	Review the draft model for both products at the design review on the thirtieth	proposed	—	—	—	—
D-0017	Keep the receipts feed at one row per delivery line	proposed	—	—	—	—
D-0018	Proceed with the signed-off scope one-pager	proposed	—	—	—	—
D-0019	Include sales analytics and daily stock snapshot in phase one	proposed	—	—	—	—
D-0020	Fix the like-for-like store definition	proposed	—	—	—	—