PRISM Commerce: A Framework for Inventoryless Cross-Border Retail with On-Demand Sourcing

Publication date: 2026-09-26 DOI: 10.5281/zenodo.22978759 Canonical source: https://doi.org/10.5281/zenodo.22978759 Related work, version 1.1: https://doi.org/10.5281/zenodo.22978762 Language: English normative text

Version: 1.1 Author: Andrei Pobezhimov / Побежимов Андрей Станиславович ORCID: https://orcid.org/0009-0002-5217-5593 License: Creative Commons Attribution 4.0 International (CC BY 4.0)

Abstract

Existing e-commerce labels do not always distinguish between the identity of the customer-facing seller, the location and ownership of inventory, the timing of procurement, the role of distributed expertise, and the party responsible for coordinating fulfillment. This paper defines PRISM Commerce, expanded as Proxy Retail with Inventoryless Sourcing Model, as a framework for a retail architecture in which a platform presents products without pre-purchasing the displayed inventory, receives a paid customer order through a unified retail relationship, then sources and purchases the corresponding product from an external inventory source and manages the downstream operational flow. The core architecture is many inventory sources -> one retailer / MoR -> customer. PRISM combines distributed global inventory with distributed human expertise through a unified retail, payment and fulfillment infrastructure. The framework separates consumer/conceptual, financial/compliance, and technical/operational terminology; distinguishes PRISM Commerce from marketplaces, classic dropshipping, forwarding services, and classic proxy buying; and establishes Expert Commerce as a core architectural pillar comprising the Expert Commerce Curator, Expert-Curated Storefront, and Distributed Expert Curation Network. It also defines Market Access Enablement as legitimate infrastructure for connecting suppliers and products with otherwise underserved markets, never as a means of bypassing restrictions. The paper provides a vocabulary for describing the documented architecture and a precise, citable framework that can be attributed, versioned, and applied in professional analysis.

Keywords: PRISM Commerce; Proxy Retail with Inventoryless Sourcing Model; inventoryless retail; cross-border retail; Virtual Inventory; On-Demand Sourcing; Merchant of Record; distributed expert curation; Market Access Enablement

1. The terminology problem

E-commerce systems are often described by a single familiar label even when several independent architectural questions are involved:

• Who makes the retail offer to the end customer?
• Who is the customer’s contractual retail counterparty?
• Who receives the customer payment and, where applicable, acts as Merchant of Record?
• Must the displayed goods already be owned by the customer-facing retailer?
• When is a product selected and purchased from an upstream source?
• Does the upstream source sell to the platform or directly to the end customer?
• Who coordinates fulfillment, delivery, returns, refunds, and claims?
• How can subject-matter experts contribute knowledge, reputation, community, judgment, and demand without becoming independent sellers?

Labels such as marketplace, dropshipping, forwarding, and proxy buying each emphasize one possible relationship or operational method. None necessarily communicates the combination of a unified retail counterparty, Virtual Inventory, order-triggered procurement from distributed external sources, and distributed expert curation as a core architectural pillar.

The resulting ambiguity has practical consequences. A consumer description can obscure the transaction structure. A technical description can be mistaken for a legal classification. A banking description can imply agency or funds forwarding when the activity is intended to be retail procurement. A model that needs several paragraphs to explain in every context lacks a stable reference term.

PRISM Commerce is proposed as a precise framework for that combination of characteristics. The framework does not eliminate the need for fact-specific analysis; it creates a common starting point for that analysis.

2. Limitations of existing classifications

2.1 Marketplace

A marketplace classification generally directs attention to multiple sellers offering through a platform. The identity of the seller and the allocation of customer obligations may vary, but the marketplace concept commonly preserves a seller-to-customer relationship distinct from the platform’s facilitating role.

That organizing relationship does not describe the PRISM base architecture. In PRISM Commerce, upstream inventory sources are procurement counterparties, not independent sellers to the platform’s end customer merely because they provide the product. The platform’s customer-facing retailer remains unified.

2.2 Classic dropshipping

Classic dropshipping commonly highlights inventory not held by the seller and direct shipment by a supplier. Those characteristics can overlap with an implementation of PRISM Commerce, but they do not fully classify it. Direct supplier shipment is neither required nor sufficient for PRISM. A PRISM flow may route goods through the platform’s or a logistics partner’s facility for consolidation, inspection, repacking, relabeling, or coordinated fulfillment.

The PRISM framework focuses on the complete retail, sourcing, and responsibility architecture rather than on one shipping method.

2.3 Forwarding service

A forwarding service principally assists with receipt or transport of goods that a customer has purchased in another transaction. The forwarding provider need not be the retailer of the product.

In the PRISM base model, the customer buys from the PRISM retailer. The platform’s purchase from an external inventory source is part of the retailer’s procurement cycle. Logistics may be performed internally or by partners, but forwarding alone does not define the customer relationship.

2.4 Classic proxy buying

Classic proxy buying may involve an intermediary purchasing on a customer’s instruction or acting within an agency-like relationship. Such services can be valuable, but the label can suggest that customer funds are merely passed to another seller.

PRISM Commerce uses Proxy within the approved conceptual acronym, but the base architecture is retail: the platform presents the offer and the customer purchases from the retailer. For this reason, Proxy is not the leading financial/compliance descriptor.

2.5 Why a separate framework is useful

The adjacent classifications are not rejected or treated as uniform. They remain appropriate where their defining relationships match the facts. The terminology gap appears when a model combines:

1. a unified customer-facing retail relationship;
2. a displayed assortment not dependent on advance platform ownership of all goods;
3. procurement initiated by a paid customer order;
4. many upstream inventory sources;
5. platform-managed downstream responsibility; and
6. distributed human expertise organized through expert-curated environments that do not create independent sellers.

PRISM Commerce names this combination.

3. Definition of PRISM Commerce

PRISM Commerce means Proxy Retail with Inventoryless Sourcing Model.

It describes a retail model in which a platform presents products to end customers without pre-purchasing the displayed inventory; after a customer order is paid, the platform sources and purchases the relevant product from an external inventory source and manages the downstream operational flow to the customer.

The core architecture is:

many inventory sources -> one retailer / MoR -> customer

The complete architecture can also be expressed as:

Distributed Global Inventory
+
Distributed Human Expertise
↓
PRISM Commerce Infrastructure
↓
Unified Customer Experience

PRISM combines distributed global inventory with distributed human expertise through a unified retail, payment and fulfillment infrastructure.

The phrase is an architectural summary, not a universal legal conclusion. The Merchant of Record description applies only where supported by the actual payment and contractual structure. The Platform Operator, Retailer, and Merchant of Record may be performed by one entity, but the roles are analytically distinct and must not be collapsed without examining the implementation.

4. Direct and metaphorical meaning

PRISM is an acronym for Proxy Retail with Inventoryless Sourcing Model. Its components have functional meanings:

• Proxy: an accessible retail entry point to products held by external inventory sources, without making an automatic claim of legal agency;
• Retail: a customer purchase from the platform’s retailer rather than purchase of forwarding alone;
• Inventoryless: no requirement to pre-purchase and physically stock all displayed goods;
• Sourcing: selection and purchase from an external source after demand is expressed through the paid order;
• Model: an integrated commercial and operational architecture.

The prism also provides the approved metaphor. A fragmented set of inventory sources is converted into one coherent retail experience; one customer interface provides access to a broad spectrum of distributed products. The metaphor explains the organizing role of the platform without replacing the formal definition.

5. Business architecture

5.1 Unified retail proposition

The customer interacts with one retail proposition. The platform controls or coordinates the customer-facing catalogue, offer, checkout, order management, support, and post-purchase process. The upstream source supplies a product into that retail flow but does not automatically become the customer-facing seller.

5.2 Distributed inventory sources

Potential inventory sources include independent retailers, manufacturers, distributors, wholesalers, and other eligible suppliers. Sources may be located across markets and may differ in availability, price, delivery capability, and commercial terms.

The platform’s work therefore includes more than presenting links. It must determine which sources are eligible, select a source for a particular order, create a traceable procurement transaction, and manage exceptions when a selected product cannot be acquired as expected.

5.3 Dual catalog architecture

PRISM Commerce supports two parallel ways of forming assortment.

The Platform-Sourced Base Catalog is a descriptive construction, not a newly frozen term. The platform obtains and maintains this broad base assortment through retailers, distributors, manufacturers, APIs, feeds, catalog integrations, and other permitted sources. Its role is breadth / assortment coverage.

Expert-Curated Storefronts contain assortments formed by Expert Commerce Curators. Their role is depth / relevance / trust / expertise / demand generation.

Platform sourcing gives PRISM breadth. Expert curation gives PRISM depth.

Both catalog paths use the unified PRISM commerce infrastructure and preserve the same customer-facing retail architecture.

5.4 Platform responsibility

The PRISM base model assigns the unified customer-facing retail flow to the platform’s retailer. Depending on the actual implementation, the platform operates or coordinates payment collection, procurement, fulfillment, delivery, returns, refunds, and claims.

This does not mean that every operational function must be performed by one legal entity or with owned infrastructure. Outsourcing a logistics or technical function does not necessarily transfer the customer-facing retail relationship. Conversely, use of PRISM terminology cannot override contracts, payment records, customer disclosures, or applicable law.

6. Transaction architecture

The canonical transaction logic is:

customer revenue -> customer order -> procurement requirement -> supplier payment

A typical transaction proceeds as follows:

1. The platform presents a retail offer derived from Virtual Inventory.
2. The customer selects a product and completes checkout with the customer-facing retailer.
3. The platform receives confirmation of the paid order.
4. The order creates an identifiable procurement requirement.
5. The platform selects an eligible source; the retailer or its designated purchaser purchases the corresponding product.
6. The purchased product enters the configured fulfillment route.
7. The platform manages or coordinates delivery and the customer-facing post-purchase process.

The designated purchaser may be an organization or an individual contractor. This procurement function preserves the retailer’s customer-facing role and responsibilities.

The supplier payment is linked to procurement for the customer order rather than treated merely as transmission of the customer’s payment to an independent seller. An implementation must be able to support that description with appropriate contracts, order records, payment flows, accounting treatment, and disclosures.

Merchant of Record language must be used conditionally. Operating checkout or receiving funds does not alone establish every legal or regulatory attribute associated with the term.

7. Sourcing architecture

7.1 Virtual Inventory

Virtual Inventory is the platform assortment that can be presented without advance purchase and physical stocking by the platform of every displayed product. It allows assortment breadth to be separated from ownership of a pre-positioned stock pool.

Virtual Inventory is not fictional inventory and does not imply guaranteed availability. Products must exist at eligible sources, and the platform must manage the interval between offer presentation and successful procurement. Availability checks, price controls, exception handling, cancellation, refunds, and customer communication remain implementation responsibilities.

7.2 On-Demand Sourcing / Procurement

On-Demand Sourcing / Procurement begins when a paid customer order creates the need to acquire the corresponding product. The platform selects a source according to its permitted operational criteria and purchases the goods for the retail flow.

The source-selection process may consider availability, authenticity, total acquisition cost, delivery time, geographic route, supplier eligibility, or other implementation-specific requirements. These criteria are not additional canonical terminology and are not prescribed by this paper.

7.3 Fulfillment paths

After procurement, the product may:

• move through a platform-controlled facility;
• move through a logistics partner’s facility;
• be consolidated with other products;
• be inspected, repacked, or relabeled where applicable; or
• in an appropriate implementation, be shipped from a supplier-controlled location.

These are optional operational paths. The model is not defined by mandatory possession of a warehouse or by mandatory supplier-direct shipment.

7.4 Aggregated procurement logic

Individual customer orders may collectively produce aggregated procurement demand from PRISM to upstream sellers. As actual volume and supplier relationships develop, this demand may create a basis for negotiated pricing, volume discounts, preferred procurement terms, supplier accounts, API or feed access, priority allocation, or wholesale or semi-wholesale commercial terms.

Realization of this economic function depends on actual volume, supplier agreements, and operating evidence. Statements about specific terms or access should identify the arrangement supporting them.

7.5 Market Access Enablement

Market Access Enablement (Russian: инфраструктурное обеспечение доступа к неохваченным рынкам) is the PRISM Commerce function that connects suppliers and products with markets they do not serve directly, or serve only to a limited extent, because they lack local payment, logistics, customs, fulfillment, compliance, or customer-service infrastructure.

From the upstream seller’s perspective, PRISM may provide access to an otherwise underserved market without requiring the seller to build local acquiring, local payment methods, currency handling, cross-border logistics, customs processes, local fulfillment, returns infrastructure, or customer support. An external retailer or supplier does not automatically become a PRISM partner merely because PRISM may source its products; partnership status depends on an actual relationship.

PRISM Commerce is positioned as market-access infrastructure, not as a mechanism for circumventing seller, geographic, regulatory or commercial restrictions. If a product cannot lawfully, contractually, or regulatorily be supplied to a market, PRISM must not be represented as a means of bypassing the restriction.

8. Expert curation layer

Expert Commerce is a core architectural pillar of PRISM Commerce alongside the centralized commerce infrastructure. It connects distributed human expertise with distributed global inventory while the platform preserves a unified retail, payment, procurement, compliance, fulfillment, delivery, returns, and claims architecture.

The primary contribution of the Expert Commerce Curator is:

knowledge + reputation + community + judgment

An Expert Commerce Curator (ECC) is a subject-matter specialist who selects products, identifies relevant sources, forms assortments, adapts the proposition to a particular market or community, creates and improves product records, and provides deep category-specific guidance. An ECC understands demand, the pricing environment, and the characteristics of the relevant audience, and may generate demand through professional reputation and participation in a specialist community.

The ECC does not invest in owned inventory and does not need to construct independent commerce infrastructure. Instead, the ECC uses PRISM infrastructure for the retail transaction, payments, procurement, compliance, fulfillment, delivery, returns, and claims. Managing assortment, permitted price positioning, product content, professional guidance, or demand generation does not by itself make the ECC an independent seller.

An Expert-Curated Storefront (ECS) is a commerce destination built around domain expertise and trust. It is formed around subject-matter competence, selection quality, audience trust, professional guidance, market relevance, and connection to a specialist community. It is more than a set of product records assigned to an expert.

A Distributed Expert Curation Network (DECN) is the network of ECCs and their curated environments.

This architecture separates retail identity from domain expertise. An ECC contributes knowledge, reputation, community, and judgment while the platform retains the unified retail, payment, procurement, compliance, fulfillment-coordination, delivery, returns, and claims architecture. In the base model, ECCs and ECSs are not independent sellers.

If a real implementation gives a curator its own seller relationship with the customer, the arrangement must be described according to that fact. The PRISM label cannot be used to conceal a multi-seller architecture.

9. Financial and compliance interpretation

The approved financial/compliance terminology is:

• Short: MoR Inventoryless Retail
• Full: Merchant-of-Record Cross-Border Retail Platform with Virtual Inventory and On-Demand Sourcing

This layer explains why the platform may receive customer payments and subsequently make numerous supplier payments. In the PRISM architecture, those outflows may be ordinary procurement expenditures associated with identifiable customer orders.

The terminology is designed to avoid an incomplete interpretation of the platform as a funds-forwarding or purchasing agent merely because procurement occurs after payment. Nevertheless, terminology cannot decide the classification. Banks, payment service providers, auditors, regulators, and other counterparties must receive an accurate description of the actual entities, contracts, payment paths, customer terms, refund responsibilities, and records.

Where the operator is not factually the Merchant of Record, the full MoR formulation must not be used. The financial description must be adapted without altering the canonical conceptual name.

10. Comparison with adjacent models

The table is an analytical comparison, not a declaration about every service using these labels. Hybrid structures are possible. A platform should be classified from its actual end-to-end architecture.

11. Practical applicability

The framework is intended to support several practical uses.

11.1 Business-model communication

Founders, operators, partners, and analysts can distinguish the retail counterparty from upstream sources and describe the timing of inventory acquisition without relying on a misleading single adjacent label.

11.2 Financial and payment onboarding

The financial terminology can support accurate explanations of customer revenue, order-linked procurement, and supplier-payment volume, subject to fact-specific documentation and review.

11.3 System and operating-model design

The framework highlights the need to connect offer data, customer orders, source selection, supplier payments, fulfillment events, refunds, and claims. It does not prescribe a particular software architecture.

11.4 Cross-border retail analysis

The model can be used to analyze platforms that provide a unified retail entry point to goods distributed across countries or supplier networks. It does not resolve customs, tax, sanctions, product-compliance, or consumer-law questions.

11.5 Expert-driven assortment

The ECC/ECS/DECN architecture provides a way to organize distributed category expertise while preserving the single-retailer base architecture.

11.6 Four-sided value proposition

The model creates a potential value proposition for four sides:

Realization of these architectural value propositions depends on implementation quality, supplier relationships, customer outcomes, and the actual arrangements for expert participation.

11.7 Conceptual commerce flywheel

The combined inventory and expertise architecture may create the following network effect:

more experts -> better specialist assortment -> more relevant communities -> more demand -> higher procurement volume -> stronger supplier relationships -> potentially better commercial terms -> stronger customer proposition -> more experts and customers

Each transition in this conceptual commerce flywheel depends on execution, product-market fit, customer trust, supplier willingness, compliance, and measurable performance. Commercial terms and supplier partnerships depend on the actual relationship and agreements.

12. Terminology framework

Term provenance classes

• Industry terms (IND): established industry vocabulary used according to the relevant factual context, including Platform Operator, Retailer, Merchant of Record, marketplace, dropshipping, forwarding service, and proxy buying. Their industry provenance is preserved.
• PRISM-defined terms (PRISM): terminology introduced or formally fixed within this framework, including PRISM Commerce, Proxy Retail with Inventoryless Sourcing Model, Expert Commerce Curator, Expert-Curated Storefront, Distributed Expert Curation Network, and Market Access Enablement.
• Adapted terms (ADAPT): industry language given a more precise role within the PRISM framework, including Global Shopping Platform, Asset-Light Global Retail Platform, Virtual Inventory, and On-Demand Sourcing / Procurement. Their industry provenance and PRISM-specific usage are distinguished.

12.1 Consumer / conceptual

• PRISM Commerce
• Proxy Retail with Inventoryless Sourcing Model
• Global Shopping Platform

12.2 Financial / banking / compliance

• MoR Inventoryless Retail
• Merchant-of-Record Cross-Border Retail Platform with Virtual Inventory and On-Demand Sourcing

Proxy must not lead the financial/compliance description because it can create an inaccurate agency or funds-forwarding implication.

12.3 Technical / investment / operational

• Asset-Light Global Retail Platform
• Asset-Light Global Retail Platform with Virtual Inventory, On-Demand Sourcing and Distributed Expert Curation

Asset-light refers to reduced dependence on pre-purchased inventory. It does not mean an absence of infrastructure, cost, working capital, risk, or responsibility.

12.4 Market Access Enablement

• Market Access Enablement — Russian: инфраструктурное обеспечение доступа к неохваченным рынкам

Market Access Enablement means infrastructure that allows suppliers and products to reach markets they do not directly serve, or serve only to a limited extent, because local payment, logistics, customs, fulfillment, compliance, or customer-service infrastructure is absent. It must not be used to frame PRISM as a means of bypassing legal, contractual, regulatory, geographic, seller-imposed, or commercial restrictions.

12.5 Usage discipline

The three layers describe one model for different audiences. The normative glossary follows the approved terminology register. Changes to frozen terminology require an explicit Human Authority decision and controlled versioning.

13. Scope and research boundaries

The paper develops a conceptual and architectural framework. Its scope is defined by the following application conditions:

1. The model definition supports professional description and comparison of retail architectures.
2. Measurement of market prevalence, adoption, and performance requires separate empirical research.
3. Legal, regulatory, tax, customs, accounting, and payment analysis is specific to the jurisdiction and implementation.
4. The roles of Retailer, Merchant of Record, agent, marketplace operator, importer, and other parties are determined through the actual arrangements and applicable requirements.
5. Copyright and open licensing of the documentation concern protectable expression; the underlying business idea and model are distinct.
6. Trademark availability and rights require a separate assessment.
7. Source-selection algorithms, fulfillment technology, contracts, accounting policies, and compliance controls are implementation decisions.
8. Expert Commerce is a core architectural pillar of the complete PRISM Commerce framework; the number of active experts and the maturity of the network may vary by implementation.
9. Hybrid implementations may require more than one classification.
10. Repository records, DOIs, and cryptographic hashes provide complementary provenance, citation, and integrity information.
11. Market Access Enablement retains the restriction boundary set out in Section 7.5.
12. Supplier relationships, discounts, preferred terms, supplier accounts, API or feed access, priority allocation, and wholesale treatment depend on actual agreements and operating conditions.

14. Governance and future development

The PRISM Commerce project preserves chronological records, provenance audits, and canonical reconstruction through its PTKR records. These sources support the version history and traceability of the published framework.

The core terminology is frozen. Substantive changes require explicit approval by Human Authority, a recorded decision, a new version where appropriate, and updated hashes. Published canonical versions must remain recoverable rather than being silently overwritten.

The first public release is identified as Version 1.0, published on 2026-09-21 with DOI 10.5281/zenodo.22872293. Its canonical companion specification is identified by DOI 10.5281/zenodo.22872324. Release integrity is recorded through SHA-256 hashes, Git provenance, and verified repository metadata.

15. Conclusion

PRISM Commerce identifies a retail architecture built around Virtual Inventory, On-Demand Sourcing / Procurement, one customer-facing retailer, many external inventory sources, distributed human expertise, and platform-managed downstream flow. Its core formula—many inventory sources -> one retailer / MoR -> customer—distinguishes the model from architectures centered on multiple independent sellers, customer-owned purchases being forwarded, or an intermediary acting only as a purchasing agent.

The three-layer terminology allows the same model to be communicated accurately to consumers, financial and compliance counterparties, and technical or investment audiences. The ECC/ECS/DECN architecture makes distributed human expertise a core pillar without changing seller identity in the base model. Market Access Enablement describes legitimate infrastructure for underserved markets and never a mechanism for bypassing restrictions.

The framework provides a common reference for professional analysis, system design, and research. Precise use, transparent provenance, controlled versioning, open critique, and independent application support its continuing development.

16. Author metadata

• Author: Andrei Pobezhimov
• Author name in Cyrillic: Побежимов Андрей Станиславович
• ORCID: https://orcid.org/0009-0002-5217-5593
• Title: PRISM Commerce: A Framework for Inventoryless Cross-Border Retail with On-Demand Sourcing
• Version: 1.1
• Previous published version: Version 1.0, 2026-09-21, https://doi.org/10.5281/zenodo.22872293
• Related Canonical Specification, published Version 1.0: https://doi.org/10.5281/zenodo.22872324
• License: Creative Commons Attribution 4.0 International (CC BY 4.0), https://creativecommons.org/licenses/by/4.0/, applied to the documentation to the extent the licensor has authority to license it

References

1. PRISM Commerce Concept & Terminology Framework, Edition 1.0, project source document.
2. PRISM Commerce Adoption, Authorship & Canonical Source Master Plan, Edition 1.0, project source document.
3. PTKR-1 — Chronological Reconstruction, PRISM Commerce Knowledge Transfer Package v1.0.
4. PTKR-2 — Audit, PRISM Commerce Knowledge Transfer Package v1.0.
5. PTKR-3 — Canonical Reconstruction for Codex, PRISM Commerce Knowledge Transfer Package v1.0.
6. PRISM Commerce — Decision Register, PRISM Commerce Knowledge Transfer Package v1.0.