| name | retail-transformation-proposal |
| description | Use when drafting a consulting proposal, EOI, bid, or methodology for retail, omnichannel, e-commerce, POS, merchandising, pricing, promotions, markdowns, loyalty, CRM, fulfilment, returns, store operations, shrink, vendor terms, private label, planogram, new-store opening, or retail KPI/WBR work. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
Retail Transformation Proposal
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Use When
- The assignment is for a retailer, distributor with retail branches, supermarket chain, pharmacy chain, fashion/apparel retailer, fuel/convenience network, direct-to-consumer brand, marketplace operator, or omnichannel commerce business.
- The scope includes retail strategy, diagnostic, transformation, software implementation, e-commerce improvement, POS/inventory rollout, store operations, customer lifecycle, pricing, promotion, markdown, vendor funding, private label, shrink, planogram, or performance management.
- The proposal must prove retail-specific delivery credibility through workstreams, data asks, deliverables, risks, governance, and acceptance evidence.
Do Not Use When
- The task is only a generic corporate strategy proposal with no retail operating model.
- The work is only a static website with no commerce, fulfilment, inventory, or customer lifecycle scope. Use the website proposal strategy instead.
- The proposal makes accounting, tax, statutory, inventory valuation, or reconciliation commitments without also routing to the finance doctrine engine.
Required Inputs
| Artefact | Source | Required? | If absent |
|---|
| Brief, channels, stores, categories, geography, systems, and target output | Client or tender pack | required | Stop module selection and request retail scope. |
| POS, order, SKU, inventory, returns, CRM, vendor, labour, and finance evidence | Client systems and authorised records | conditional | Label value cases and diagnostics provisional. |
Workflow
Stop or block the workflow when a required input, permission, or acceptance basis is missing. Recover by revising the scope, obtaining evidence, or returning the narrowest qualified draft before proceeding.
- Classify the capability modules and exclude adjacent retail topics not in scope.
- Build a source-data request and mark unavailable evidence before making performance claims.
- Route all money, stock, settlement, tax, and finance-system elements through the external finance doctrine and its quality gate.
- Design diagnostic, target operating model, business-case, implementation, pilot, transfer, and performance phases proportionately.
- Reconcile deliverables, team, work plan, acceptance, and price; stop if a finance or data dependency remains hidden.
Quality Standards
- Name the retail modules, channels, data, owners, decisions, and acceptance evidence in scope.
- Separate verified client performance from assumptions and benchmarks.
- Keep finance doctrine, operational design, technology, and change dependencies visible.
Anti-Patterns
- Treating “retail transformation” as all retail topics. Fix: select modules from the actual brief and evidence.
- Promising margin or sales uplift without client baselines. Fix: define the hypothesis, formula, source, and validation period.
- Designing from interviews alone. Fix: request transaction, inventory, customer, vendor, labour, and control evidence.
- Adding finance review after design. Fix: route money and stock flows through doctrine during diagnosis.
- Ending at recommendations. Fix: include pilot, owner, training, decision gates, rollout, and WBR evidence.
Outputs
| Artefact | Consumer | Acceptance condition |
|---|
| Retail transformation methodology and deliverable pack | Evaluator, retail executive, delivery leads | Maps scoped modules to evidence, decisions, controls, pilot, rollout, KPIs, finance gate, and acceptance. |
Evidence Produced
| Evidence | Consumer | Acceptance condition |
|---|
| Retail capability, data, value, and finance trace | Linked registers | Each claim is sourced or labelled; every money/stock flow names its finance-doctrine route. |
Capability and Permission Boundaries
Read and search are required; any edit or external action remains within the explicit authority and permission boundary stated below.
Review defaults to read-only. Client data access must be least-privilege. Price, promotion, assortment, customer communication, vendor claim, system, store, or finance changes require explicit authorised-owner approval.
Degraded Mode
Without retail data, store/channel access, system evidence, or finance doctrine, return a scoped diagnostic and evidence request. Do not claim uplift, compliance, reconciliation, or implementation readiness.
Decision Rules
| Condition | Action | Risk avoided |
|---|
| Scope spans many capabilities | Prioritise by binding constraint and evidence | “Everything retail” programme |
| Value case lacks a baseline | Use a hypothesis and measurement plan | Invented ROI |
| Money, tax, settlement, or stock value is involved | Apply external finance doctrine gate | Incorrect accounting promise |
Worked Example
For a supermarket shrink assignment, reconcile POS, stock counts, adjustments, returns, and settlement evidence; pilot controls in representative stores; measure exceptions; and obtain finance-owner approval before rollout.
Retail Capability Diagnostic
Before writing the methodology, classify the assignment into one or more modules:
| Module | Proposal trigger | Typical buyer concern |
|---|
| Omnichannel merchandising | stores + web/app/marketplace, channel assortment, product content | inconsistent customer promise and fragmented execution |
| Assortment and SKU rationalisation | range review, slow-moving SKUs, category roles | excess complexity, weak availability, poor margin mix |
| Merchandising calendar and line review | seasonal campaigns, launches, resets | late decisions and cross-functional congestion |
| Pricing architecture | price zones, ladders, KVIs, competitor response | margin leakage and inconsistent price logic |
| Promotion planning | promotion calendar, funding, campaign mechanics | discounting without measured incrementality |
| Markdown optimisation | clearance, aged stock, exit rules | stock value erosion and delayed decisions |
| Loyalty and CRM | retention, tiers, lifecycle journeys, offers | unmeasured customer economics and weak repeat purchase |
| E-commerce CRO | PDP, cart, checkout, payments, speed, accessibility | traffic not converting into profitable orders |
| Search and navigation | taxonomy, attributes, filters, relevance | customers cannot find or compare products |
| Fulfilment | inventory availability, routing, pickup, ship-from-store | promise failures and high fulfilment cost |
| Returns | return rate, reverse logistics, disposition, fraud | margin loss and customer friction |
| Labour and store operations | scheduling, tasking, SOPs, audits | variable execution and productivity loss |
| Shrink and loss prevention | stock loss, fraud, controls, investigations | unexplained losses and weak accountability |
| Space and planogram | category space, facings, compliance | poor space productivity and rollout drift |
| Vendor terms and trade spend | rebates, allowances, co-op, claims | missed funding and weak commercial governance |
| Private label | brand role, sourcing, cost, launch | margin opportunity with quality and cost risk |
| New-store opening |
Methodology Pattern
Use this phase structure unless the tender mandates a different format:
- Mobilise and evidence request: confirm scope, stakeholders, workplan, data room, confidentiality, and decision cadence.
- Current-state diagnostic: review data, systems, stores/channels, workflows, controls, customer journey, and management reports.
- Retail operating-model design: define target capabilities, processes, roles, decision rights, data model, controls, KPIs, and governance cadence.
- Business case and prioritisation: quantify or qualify value drivers without inventing market or financial figures; separate verified client data from assumptions.
- Implementation roadmap: sequence workstreams, quick wins, dependencies, technology changes, training, pilots, rollout, and change management.
- Pilot and capability transfer: test in selected stores/categories/channels, tune process and systems, train owners, and prepare adoption evidence.
- Performance management: establish dashboards, weekly business review actions, benefits tracking, and post-implementation improvement loop.
Deliverables Menu
Select only deliverables that match the assignment:
- Retail diagnostic report with capability scorecard and binding constraints.
- SKU/category/price/promotion/markdown opportunity register.
- Customer journey and omnichannel service blueprint.
- Product data, taxonomy, search, PDP, checkout, fulfilment, and returns requirement pack.
- Store SOP, labour, audit, and tasking improvement pack.
- Shrink/loss-prevention control matrix and investigation workflow.
- Vendor funding and trade-spend recovery framework.
- Private-label launch and landed-cost readiness checklist.
- Planogram and space productivity governance pack.
- Retail KPI dictionary, dashboard specification, and weekly business review cadence.
- Implementation roadmap with owners, dependencies, risks, milestones, and acceptance evidence.
- Training, handover, and capability-transfer materials.
Data Ask
A credible retail proposal asks for the source evidence required to deliver the work:
- SKU master, category hierarchy, product attributes, product content, prices, promotions, markdowns.
- Sales, margin, inventory, stock count, returns, refunds, shrink, vendor funding, and fulfilment data.
- Store list, store formats, labour schedules, task lists, SOPs, audit results, new-store opening checklists.
- Web analytics, search logs, zero-result queries, product page events, cart and checkout events, payment failures.
- Loyalty/CRM segments, campaign results, opt-in records, voucher/reward issuance and redemption.
- Vendor agreements, rebate/allowance rules, claim evidence, recovery and dispute reports.
- Existing dashboard packs, weekly trading review decks, action logs, and finance reconciliations.
Finance and Accounting Route
If the proposal touches inventory value, refunds, markdowns, discounts, vendor funding, loyalty liabilities, gift cards, POS settlement, mobile money, card settlement, cash drawer, shrink, or management reporting, also load:
Do not promise accounting treatment, tax treatment, statutory filing, or audit sign-off without the finance doctrine route and human reviewer caveat.
Risk Register Starters
| Risk | Proposal mitigation |
|---|
| Weak data quality | Begin with data inventory, quality checks, source reconciliation, and explicit assumption log. |
| Scope becomes "everything retail" | Use capability modules, phase gates, and a prioritised backlog. |
| Store teams reject head-office process | Pilot in representative stores, co-design SOPs, and include field feedback loops. |
| Finance controls are added late | Route finance/control review during diagnostic and design, not after implementation. |
| Technology work outruns operating design | Define process, roles, data, controls, and acceptance tests before build or configuration. |
| Vendor funding claims lack evidence | Require agreement register, claim basis, source transaction linkage, and dispute workflow. |
| Dashboards do not drive action | Include metric owners, WBR cadence, action log, and decision rights. |
Output Checks
- Does the proposal name the exact retail capability modules in scope?
- Does the methodology ask for the right source data instead of relying on interviews only?
- Are deliverables concrete enough for the evaluator to see what will be produced?
- Are store, digital, fulfilment, finance, and executive stakeholders represented where relevant?
- Are finance/control gates visible for inventory, refunds, markdowns, discounts, vendor funding, shrink, POS, and dashboards?
- Does the workplan include pilot, rollout, training, and performance review instead of ending at recommendations?
- Are claims about value, market size, ROI, and benchmarks sourced or explicitly framed as assumptions?
Evidence Basis
This skill is based on the internal digital-research-engine project umbrex-retail-playbooks-engine-enhancement, which extracted the public Umbrex retail playbook corpus on 2026-06-25. Umbrex is used as source evidence for retail project taxonomy and topic coverage, not as proof of client-specific facts, financial benchmarks, or legal/accounting treatment.
References
