About the project
A public sample of the standard, not the whole system
ORPR — Open Retail Process Reference — is an open standard for a reference process architecture in retail. It organises domains, processes, flows, responsibilities and the interfaces between areas of a retail organisation. The public repository holds a map of 74 processes and a public description of each; the full scope — complete cards, workshop documentation and Regulatory Matrix — stays with the author.
A product snapshot from a private workshop repository
The public mirror was seeded from a deterministic product artifact. References to private paths were replaced with public descriptions; no private Git history was copied.
Includes
- a navigation map of 74 processes in 22 areas plus one candidate
- a catalogue of all 74 cards: six full examples and 68 public digests
- cross-cutting flows, mappings and reference profiles
- card templates, licences, known limitations, an integrity manifest and provenance
Excludes
- workshop decision registers and editorial material
- adopter data — adopter names do not appear in official documentation
- the private content of Regulatory Matrix
- the history of the private repository
Every file in the public sample has a checksum
The publication is reproducible: the mirror records the source release commit, the SHA-256 of the product artifact and a checksum manifest of the resulting snapshot.
- Mirror release
- v0.1.0
- Source release commit
- 98a44cc6364637c123d9f9cec8b9479725b42def
- Artifact SHA-256 (36 files)
- 11d716d6e965f437408b0d8154b87d71eeea524613ca91b987facf225faa15f2
- Integrity manifest
- MANIFEST.sha256
The boundaries of the first public snapshot — stated openly
Limitations are published so a user can tell what is ready to use from what still needs validation.
- 1
This is an early release
The structure is useful for navigation, analysis and design, but is not yet a complete implementation catalogue.
- 2
Most cards are shown as digests
A digest shows purpose, boundary, owner and sample questions. It does not settle the complete set of triggers, inputs, outputs, rules, exceptions or controls.
- 3
Some relations remain working hypotheses
Relations marked "to validate" need checking in specific operating models.
- 4
Operating models are contextual
Not every process appears in every type of business — warehouse, order fulfilment or category management may be optional.
- 5
The regulatory layer is not advice
Regulatory Matrix helps establish which duties touch a process, but does not replace legal, tax, accounting or compliance analysis.
- 6
Country context is developed gradually
Poland is the first profile. Use in another country requires separate regulatory validation.
- 7
No implementation guarantee
Roles, systems, control evidence and lines of responsibility must be fitted to a specific organisation.
- 8
The source language is Polish
The release has no authoritative English translation. The English version of this site is a convenience.
Content under CC BY-SA 4.0, code under Apache-2.0
Full texts of both licences live in the repository: LICENSE (Apache-2.0) and LICENSE-CONTENT (CC BY-SA 4.0 with an attribution header). External sources are cited bibliographically; APQC and GS1 content is not reproduced.
Standard content
The standard/ directory and substantive documentation. Derivatives under the same licence.
Code
Scripts, validators, generators.
- Attribution
- Open Retail Process Reference (ORPR), R. Myrta, https://orpr.dev
- Suggested citation
- Open Retail Process Reference (ORPR), release version used, Rafał Myrta, 2026.
- Concept DOI
- 10.5281/zenodo.22304798
The licence note for commercial adopters is a separate document outside the repository, signed by the owner.
Questions, ideas and examples of use
Public discussion of the standard happens in the repository’s GitHub Discussions. If you are considering ORPR or Regulatory Matrix for a project and want to see the full material, contact the author directly.