The Retail PCF decomposes store-channel execution 60 elements deep, and the orthogonality argument now needs a stated retail-format exception
The question
"Does the APQC Retail PCF (and any 8.0 re-cut) decompose store-channel execution the way cross-industry declines to, forcing a stated retail-format exception to the orthogonal-axes argument?"
Context: the Organizational Platform's function/motion tree rests on a claim that business function and go-to-market motion are orthogonal axes, and the load-bearing proof of that claim is that APQC's cross-industry Process Classification Framework (PCF) names three selling motions and then refuses to give them children. This brief tests whether APQC's own retail cut breaks that proof. The "8.0 re-cut" half was already answered and closed on 2026-08-22 and was not re-researched.
What we already know (from the vault)
- [[2026-08-21-apqc-pcf-80-channel-motion-leaves]] verified against the full PCF 8.0 PDF that cross-industry elements 3.5.6 Perform sales at physical outlets (21427), 3.5.7 Perform field sales (21428) and 3.5.8 Perform digital sales (21429) are bare leaves with zero children in both 7.4 and 8.0, while channel strategy is decomposed nine ways under 3.2.4. Its own open follow-up flagged retail as the one industry where APQC has a business reason to decompose channel execution.
- [[2026-08-17-apqc-pcf-function-motion-mapping]] states the orthogonality argument in its strongest form: "PCF cannot decompose them because there is nothing process-shaped to decompose. That is exactly the material our motion layer exists to carry, and it is why the motion layer has to be built rather than borrowed."
- [[2026-08-17-gtm-motion-origins-industry-reference-models]] carried an explicit KNOWN-UNVERIFIED flag: apqc.org returned 403 throughout, no APQC page was fetched, and its Retail PCF category structure was "from search snippets only, unverified against primary text." It also logged grocery, convenience and fuel as an unsettled gap.
- [[2026-08-22-cstore-fuel-retail-reference-models]] primary-verified that there is no Retail PCF 8.0. Retail sits at 7.2.1, was skipped in the March 2025 industry refresh that moved eleven other industries to 7.2.2, and a keyword sweep of all 30 pages for fuel, convenience, c-store, grocery, foodservice, perishable, private label and pharmacy returns zero matches. Its verdict that the Retail PCF is the wrong anchor for Kwik Trip stands and is not re-litigated here.
What the web says
This section is primary-document evidence, not search snippets. Everything below is VERIFIED-FROM-PRIMARY unless marked INFERRED.
- The static-asset route worked.
https://www.apqc.org/system/files/K09368_Retail%20Process_v721_011519.pdfreturned HTTP 200,application/pdf, 1,468,938 bytes, with no cookie, referrer or registration. The listing page at/resource-library/resource-listing/...-retail-pdf-version-721is gated behind sign-in and exposes no asset link in its DOM, and apqc.org search pages return 403 to curl, so the asset route is the only unauthenticated path. Document title: RETAIL PROCESS CLASSIFICATION FRAMEWORK, Version 7.2.1, 30 pages, dated January 2019. Text extracted locally withpdftotext. - The snippet-derived category list from the earlier brief was correct. Verified with concept identifiers: 1.0 Develop Vision and Strategy (10002), 2.0 Develop and Manage Customer Experience (16477), 3.0 Market Products and Services (16610), 4.0 Merchandise Products and Services (16634), 5.0 Deliver Products (16679), 6.0 Deliver Services (20025), then 7.0 through 13.0 unchanged from cross-industry. The KNOWN-UNVERIFIED flag on [[2026-08-17-gtm-motion-origins-industry-reference-models]] can be cleared.
- Category 2.0's own level-2 axis is channel, not process stage. Its five process groups are 2.1 Operate direct channels (16478), 2.2 Develop and manage retail store channel (16506), 2.3 Operate retail store (16521), 2.4 Develop and manage omni channel (16571), 2.5 Manage customer relationship (16588). Four of the five are named for a channel.
- Store-channel execution is decomposed 60 elements deep. 2.3 Operate retail store has 49 descendants to depth 4, across nine process groups: 2.3.1 Operate customer checkout (16522), 2.3.2 Operate in-store customer service desk (16526), 2.3.3 Provide floor customer service (16533), 2.3.4 Manage store inventory (16539), 2.3.5 Manage store cash (16546), 2.3.6 Plan and manage retail store workforce (16552), 2.3.7 Execute floor merchandising and promotions (16558), 2.3.8 Analyze and manage store performance (16564), 2.3.9 Manage retail story regulatory compliance (16567 - the typo for "store" is APQC's, present in the primary text). Add 2.2's 11 descendants for store format, site plan and layout, and the store channel carries 60 elements against cross-industry's single childless 21427.
- The cross-industry selling trio has no counterpart in retail. Case-insensitive sweeps of the full document return zero hits for "Perform sales", "Develop sales strategy", "Develop and manage sales plans" and "Sell products and services", and zero occurrences of concept identifiers 10103, 10105, 21427, 21428 or 21429. Selling execution was not inherited and then extended; it was relocated wholesale into a channel-shaped Category 2.0. Likewise "Provide customer self-service (16483)" exists in retail with three children, where [[2026-08-21-apqc-pcf-80-channel-motion-leaves]] found zero hits for the term "self-service" anywhere in cross-industry 7.4 or 8.0.
- Concept-identifier forensics show exactly where APQC drew the line. Category 2.0 (pages 6 and 7) contains 147 distinct concept identifiers. 126 are retail-native, minted in the contiguous 16477 to 16609 block. Only 21 are inherited from cross-industry, and they are exactly: 10122 plus 10126 to 10128 (Define and manage channel strategy), 10378 to 10385 (Develop customer service strategy), and 10401 to 10407 plus 11236 to 11239 (Measure and evaluate customer satisfaction). Everything APQC borrowed is strategy or measurement. Everything it minted new is channel execution. That is the cross-industry editorial position stated in reverse.
- The exception leaves a visible scar: cross-axis duplication. 2.3.6 Plan and manage retail store workforce (16552) with children Estimate retail store workload / Schedule retail store labor / Assign tasks / Approve overtime / Monitor and adjust labor levels (16553 to 16557) is a near-verbatim clone of 5.1.5 Plan and manage workforce (16698) with children Estimate workload / Schedule labor / ... / Monitor and adjust labor level (16699 to 16703) sitting under Deliver Products, while 7.0 Develop and Manage Human Capital owns workforce strategy at 10433. Same pattern for cash: 2.3.5 Manage store cash (16546 to 16551) against 9.7.2 Manage cash (10759) and 9.2.3.2 Receive/Deposit customer payments (10800). Same for compliance: 2.3.9 (16567) against 11.2.2 Manage regulatory compliance (16463). APQC minted duplicate process content under three different functions rather than let store execution be split across the function axis.
Convergences and contradictions
- Convergence. Nothing here contradicts [[2026-08-21-apqc-pcf-80-channel-motion-leaves]]. Cross-industry genuinely does not decompose channel execution, and the retail cut confirms the reason by inversion: the only cross-industry material APQC carried into its channel-shaped category was strategy and measurement.
- Contradiction, and it is the point. The generalized form of the claim in [[2026-08-17-apqc-pcf-function-motion-mapping]] - "PCF cannot decompose them because there is nothing process-shaped to decompose" - is falsified. In retail there is something process-shaped, APQC found it, and it wrote 126 new concept identifiers to hold it. The narrower claim (cross-industry declines to) survives untouched; the causal claim (there is nothing there to decompose) does not.
- A quieter convergence with the c-store finding. The 2.3 subtree is a general-merchandise store model. Its nine groups have no fuel dispensing, no foodservice production, no perishables and no pharmacy, which is consistent with the zero-hit keyword sweep in [[2026-08-22-cstore-fuel-retail-reference-models]] and with the document's January 2019 date and Microsoft co-authorship.
Synthesis for RDCO
The answer is yes, decisively, and the exception should be written into the Organizational Platform's framing rather than papered over. APQC's retail cut takes the one element cross-industry leaves childless - selling at a physical outlet - and expands it into a 60-element subtree with its own checkout, service desk, floor service, inventory, cash, workforce, merchandising, performance and compliance branches. Any claim that "the PCF declines to decompose motion" has to be stated as "the cross-industry PCF declines to decompose motion, and its retail cut does not."
The refined rule is more useful than the one it replaces, because it is testable. Cross-industry declines to decompose physical-outlet, field and digital selling because those three differ in cost structure, headcount shape and cycle time while running the same process content: qualify, quote, close, book. Retail decomposes the store channel because operating a store generates work that has no counterpart in the direct channel at all. Reconciling a cash drawer, estimating store workload, maintaining shelf tagging and arranging floor displays are not the digital channel's activities performed differently; they do not exist there. So the test is: does the motion generate process content that has no home anywhere else on the function axis? If no, the axes stay orthogonal and the motion layer carries only economics and staffing shape. If yes, the axes are locally non-orthogonal and the motion has to carry process content of its own. Physical-outlet selling at a business-to-business software company fails the test. Operating a convenience store passes it.
That gives the platform a diagnostic it did not have, and it comes with a detectable signature. When a motion is strong enough to break orthogonality, the same process content gets minted twice under two different functions, which is exactly what APQC did with store workforce (duplicated against both Deliver Products and Human Capital), store cash (duplicated against Manage Financial Resources) and store compliance (duplicated against Manage Enterprise Risk). Cross-axis duplication is the observable tell. The practical consequence for phase 3: the motion pages for site-based, asset-heavy motions cannot use the same template as the pages for sales motions. They need an explicit provenance or "duplicates function X" pointer and a stated composition rule for which owner wins, rather than a tree that pretends every element has exactly one home. INFERRED, but the inference is cheap to check: if the 36-motion catalog contains any site-based motion whose role pages would list duties that already appear under Finance or Human Capital, the rule is needed.
On Kwik Trip, nothing here reopens the anchor decision. [[2026-08-22-cstore-fuel-retail-reference-models]] recommended Consumer Products plus Downstream Petroleum, and this brief strengthens rather than weakens that: the Retail PCF's store model is a 2019 general-merchandise artifact that was skipped in APQC's 2025 refresh, and for a fuel-and-foodservice format roughly half the store's actual work has no element in it. What the 2.3 subtree is genuinely good for is a coverage checklist. It is the most detailed published decomposition of store-execution process content that exists off the shelf, so it is worth running against any store-operations scope as a "did we miss a branch" test, while sourcing the fuel, foodservice and perishables branches elsewhere.
Why this is in the vault
It clears the KNOWN-UNVERIFIED flag on [[2026-08-17-gtm-motion-origins-industry-reference-models]] with primary text, and it forces a specific edit to the borrow-versus-build verdict in [[2026-08-17-apqc-pcf-function-motion-mapping]]: the causal justification for the motion layer has to be restated from "PCF cannot decompose motion" to "PCF declines to decompose motion where it is economics-shaped, and does decompose it where it is process-shaped," which in turn means the phase-3 motion-page template needs a duplication and provenance rule for site-based motions.
Open follow-ups
- Does the 36-motion catalog currently contain any site-based or asset-heavy motion, and if so do its role pages already collide with Finance or Human Capital duties? This is the cheap check on the composition-rule recommendation above.
- APQC's Consumer Products PCF 7.2.2 and Downstream Petroleum PCF 7.2.2 are still ungated only through the static-asset route and their item codes are unknown. Do either of them decompose site or forecourt execution the way Retail decomposes store execution? Downstream Petroleum is the likelier candidate for the fuel branch Kwik Trip needs.
- Retail 7.2.1 predates the 3.5.6/3.5.7/3.5.8 leaves, which carry concept identifiers in the 21xxx block minted for 7.4. Did cross-industry introduce those three bare leaves because the retail cut had already shown what decomposing them costs? Answering it would need PCF release notes or the 7.3.x diff, neither of which has been located.
- Does any other industry PCF exhibit the same cross-axis duplication signature (a category that clones workforce or cash management under a channel or site)? Utilities 8.0 shipped 2026-08-20 and is the newest test case available.
- The Retail PCF names its channel groups but never defines "channel" in the elements read here. Do APQC's Definitions and Key Measures companion documents give a channel definition that would settle whether 2.1 through 2.4 are meant as channels, formats or motions? Those documents are gated and their item codes are unknown.
Related
- [[2026-08-21-apqc-pcf-80-channel-motion-leaves]]
- [[2026-08-17-apqc-pcf-function-motion-mapping]]
- [[2026-08-17-gtm-motion-origins-industry-reference-models]]
- [[2026-08-22-cstore-fuel-retail-reference-models]]
- [[2026-08-22-scor-digital-standard-level2-process-types]]
- [[2026-08-17-bizbok-operating-model-function-motion-mapping]]
- [[2026-08-04-kwik-trip-ai-architecture-engagement-context]]
- [[2026-08-21-kwik-trip-roi-operating-model]]
- [[2026-04-03-management-is-prediction-spc]]
Sources
Primary document (read directly, extracted locally)
- APQC, Retail Process Classification Framework, Version 7.2.1, January 2019, item code K09368, 30pp.
https://www.apqc.org/system/files/K09368_Retail%20Process_v721_011519.pdf(HTTP 200, application/pdf, 1,468,938 bytes, unauthenticated)
Gated, flagged, not retried
- APQC listing page for Retail PCF 7.2.1:
https://www.apqc.org/resource-library/resource-listing/apqc-process-classification-framework-pcf-retail-pdf-version-721(loads, but the asset link is behind sign-in; no item code exposed in the DOM) - apqc.org site search: returns HTTP 403 to curl
Vault
~/rdco-vault/06-reference/research/2026-08-21-apqc-pcf-80-channel-motion-leaves.md~/rdco-vault/06-reference/research/2026-08-17-apqc-pcf-function-motion-mapping.md~/rdco-vault/06-reference/research/2026-08-17-gtm-motion-origins-industry-reference-models.md~/rdco-vault/06-reference/research/2026-08-22-cstore-fuel-retail-reference-models.md~/rdco-vault/06-reference/research/2026-08-22-scor-digital-standard-level2-process-types.md~/rdco-vault/06-reference/research/2026-08-17-bizbok-operating-model-function-motion-mapping.md~/rdco-vault/01-projects/phdata/2026-08-04-kwik-trip-ai-architecture-engagement-context.md~/rdco-vault/01-projects/phdata/2026-08-21-kwik-trip-roi-operating-model.md~/rdco-vault/06-reference/2026-04-03-management-is-prediction-spc.md