Future Opportunity — Sustainable Sourcing Network and Marketplace

1. Status and scope

This document records a future strategic opportunity, not a commitment to build a marketplace in the current EPU implementation phase.

The current architecture should remain focused on:

• governed EPU product identity;
• supplier/manufacturer product-data onboarding;
• reusable product sustainability information;
• product intelligence;
• procurement decision support;
• supplier contribution and evidence workflows;
• trustworthy calculations and disclosure projections.

However, these capabilities can evolve naturally into a sustainability-aware sourcing network and, later, a marketplace layer.

The architecture should therefore preserve this option without allowing marketplace concepts to contaminate the canonical EPU identity model.

EPU remains the product identity spine. A future marketplace listing, sourcing offer, bid or transaction would reference an EPU; it would never replace or redefine EPU identity.

2. Strategic progression

A plausible evolution path is:

EPU Product Intelligence
        ↓
Product Sustainability Resolution Network
        ↓
Supplier / Product Discovery Network
        ↓
Sustainable Sourcing Intelligence
        ↓
RFQ / Negotiation Intelligence
        ↓
Permissioned Marketplace

Each stage should deliver independent value. The marketplace is optional and should only be considered after the underlying product identity, trust, supplier-data and procurement-intelligence layers are mature.

3. Core future sourcing question

A representative future procurement question is:

Which suppliers can provide aluminium of the quality we need at the lowest sustainability-adjusted cost?

ZAYAZ should be able to translate this into a governed sourcing requirement rather than treating it as an unconstrained semantic search.

Example requirement:

Sourcing Requirement
├── material / product specification
├── technical grade / quality
├── quantity
├── delivery geography
├── delivery dates
├── supplier capacity requirements
├── required certifications
├── required sustainability evidence
├── PCF comparability profile
├── maximum risk thresholds
├── minimum TrustGate state
├── buyer sustainability policies
└── internal carbon price / shadow prices

4. Supplier and product discovery

A future sourcing layer could traverse the EPU Product Graph to identify candidate suppliers and products.

Sourcing Requirement
        ↓
Product / Material Capability Resolver
        ↓
Candidate EPU products
        ↓
Candidate supplier ECO identities
        ↓
Technical qualification
        ↓
Sustainability qualification
        ↓
Trust / evidence qualification
        ↓
Commercial / logistics scenario evaluation

Discovery should be permission-aware. A supplier may choose which information is public, marketplace-visible, RFQ-only, contracted-customer-only or verifier-only.

5. Sustainability-adjusted acquisition cost

A future procurement decision layer may calculate a governed Sustainability-Adjusted Acquisition Cost rather than comparing only invoice price.

The simplest carbon-adjusted form is:

Carbon-adjusted acquisition cost
=
purchase price
+
(product PCF × internal carbon price)

With unit normalization:

CAC = P + ((PCF_kgCO2e / 1000) × ICP_per_tCO2e)

Where:

• P = negotiated purchase price;
• PCF_kgCO2e = comparable product footprint per purchased functional unit;
• ICP_per_tCO2e = buyer's internal carbon price or shadow price.

The system must preserve the distinction between:

• supplier invoice price;
• internal carbon cost;
• logistics cost;
• modeled risk adjustment;
• expected lifecycle or end-of-life values;
• total sustainability-adjusted decision metric.

ZAYAZ must not present internal shadow costs as literal supplier prices.

6. Example comparison

Illustrative comparison only:

Candidate	Purchase price	Product PCF	Internal carbon cost	Sustainability-adjusted cost
Supplier A	€100	40 kgCO₂e	€6.00	€106.00
Supplier B	€103	12 kgCO₂e	€1.80	€104.80
Supplier C	€101	25 kgCO₂e	€3.75	€104.75

At an internal carbon price of €150/tCO₂e, the lowest nominal-price offer is not necessarily the lowest carbon-adjusted acquisition cost.

This creates a direct bridge between product sustainability intelligence and procurement economics.

7. Comparability must precede ranking

ZAYAZ must not rank supplier products by PCF unless the results are sufficiently comparable.

The comparison layer should evaluate at least:

functional unit
system boundary
methodology
allocation approach
reference period
geography
production context
primary vs secondary data
factor / dataset versions
uncertainty
verification state
TrustGate state

If two PCFs are not materially comparable, ZAYAZ should state that explicitly rather than create false precision.

A future Comparability Resolver may normalize or route results into comparable profiles where methodology permits.

8. Delivered sustainability-adjusted cost

The relevant procurement question may be delivery-specific rather than factory-gate-specific.

A broader decision model could include:

SAAC
=
Product Purchase Price
+ Freight Cost
+ Internal Carbon Cost(product + freight)
+ Risk Adjustment
+ Compliance Adjustment
+ Lifecycle Adjustment

All terms must be transparently labeled as actual, estimated, modeled or internal shadow values.

This allows ZAYAZ to compare not only suppliers but supply routes and sourcing configurations.

9. Logistics-aware sourcing

The Product Graph already provides the conceptual foundation for route-aware sourcing.

Future questions may include:

• Which supplier can deliver the required product to a specified facility with the lowest sustainability-adjusted cost?
• Which port, warehouse or transport mode yields the best GHG/cost/service trade-off?
• Can multiple supplier shipments be consolidated?
• Would relocating final assembly change the preferred supplier?
• Which sourcing configuration minimizes both Scope 3 emissions and lead-time risk?

MICE/Computation Hub can evaluate scenario combinations while EPU provides the governed product, supplier, facility and logistics context.

10. Multi-objective procurement optimization

Future sourcing decisions may be formulated as constrained optimization rather than simple ranking.

Example objective:

Minimize:
  commercial acquisition cost
+ internal carbon cost
+ logistics cost
+ modeled supply risk

Subject to:

technical specification
required quantity
supplier capacity
delivery schedule
maximum GHG intensity
minimum evidence quality
minimum TrustGate score
supplier concentration limits
jurisdiction / compliance requirements
inventory / safety-stock requirements

The output may be a sourcing portfolio rather than a single supplier.

11. Supplier-side commercial value

Supplier adoption should be driven by commercial utility, not only compliance burden.

The strategic principle is:

Register once. Maintain at source. Resolve many times.

Suppliers should be encouraged during onboarding to:

• connect ERP, PLM, PIM or product-data infrastructure;
• synchronize product definitions and identifiers;
• register sustainability data and evidence once;
• maintain authoritative product information at source;
• define access/disclosure policies;
• allow qualified buyers to resolve permitted product intelligence automatically.

Manual product-data registration remains a fallback for suppliers without suitable infrastructure.

The supplier benefit is reduced repetitive questionnaires and greater commercial discoverability.

12. Sustainability performance as a commercial asset

A future discovery layer could allow suppliers with strong sustainability performance to be found by buyers searching for explicit outcomes.

Example supplier-visible product characteristics may include:

technical capability
verified PCF
recycled content
chemical/compliance readiness
DPP readiness
evidence quality
TrustGate status
geographic production capability
capacity availability

Subject to access policies, high-quality sustainability data becomes a commercial asset rather than merely a compliance cost.

13. Buyer-side anticipatory acquisition

The marketplace opportunity depends on an earlier capability: sustainability data should be acquired when commercial leverage is strongest.

Potential triggers include:

RFQ_CREATED
SOURCING_EVENT_STARTED
SUPPLIER_SELECTED
CONTRACT_NEGOTIATION_STARTED
PURCHASE_REQUISITION_CREATED
PURCHASE_ORDER_DRAFTED
PURCHASE_ORDER_APPROVED
BOM_RELEASED
NEW_PRODUCT_INTRODUCED
CONTRACT_RENEWAL_STARTED

The Requirement Anticipation layer can determine what product information is likely to be needed and resolve existing information before requesting anything new.

Acquire at the point of leverage; resolve at the point of need.

14. Reuse before request

Before any supplier request is created, ZAYAZ should attempt to resolve authoritative reusable information.

Need identified
    ↓
Check EPU Product Graph
    ↓
Check supplier-maintained product record
    ↓
Check connected ERP / PLM / PIM
    ↓
Check valid evidence / contributions
    ↓
Check permitted federated/external source
    ↓
Ask only for unresolved delta

The future sourcing network becomes substantially more valuable if buyer systems can receive trusted product information in milliseconds rather than initiating repeated manual questionnaires.

15. Machine-to-machine product information exchange

A future federated model may allow one ZAYAZ environment or permitted external system to request standardized product information from another supplier endpoint.

Buyer system
    ↓
resolve product identifier
    ↓
resolve EPU / federated product identity
    ↓
request governed information profile
    ↓
supplier authorization / policy
    ↓
machine-readable response
    ↓
TrustGate / validation
    ↓
buyer product graph

Humans should be required primarily when:

• the information does not exist;
• new evidence must be originated;
• permission is required;
• identities are ambiguous;
• conflicting assertions exist;
• verification or governed approval is required.

16. Future RFQ and negotiation intelligence

A later sourcing layer could support reverse-RFQ patterns.

Example:

Required:
1,500 tonnes aluminium
specified grade
specified delivery region
maximum PCF threshold
verified evidence
required delivery period

ZAYAZ could identify qualifying supplier/product combinations and, subject to permissions, support RFQ workflows.

Supplier-side decision support could also model alternative offers using different production sites, transport routes, recycled-content levels or logistics modes.

17. Carbon-price break-even analysis

A useful future procurement metric is the internal carbon price at which one supplier/product becomes economically preferable to another.

This supports questions such as:

• At what internal carbon price does Supplier B become cheaper than Supplier A?
• How much commercial premium is justified by a verified lower PCF?
• How much nominal price reduction would a high-carbon supplier need to offset its footprint disadvantage?

Such results are internal decision intelligence and must respect confidentiality/access policy.

18. Confidentiality and market-discovery policy

A future marketplace must support fine-grained visibility such as:

PUBLIC
MARKETPLACE_DISCOVERABLE
QUALIFIED_BUYER
RFQ_PARTICIPANT
CONTRACTED_CUSTOMER
VERIFIER
REGULATOR
INTERNAL_ONLY

Data access and graph-discovery policy must remain separate.

A supplier may allow buyers to discover that a qualifying low-carbon product exists without disclosing confidential formulation, production economics or sub-tier supplier relationships.

19. Marketplace layer must remain separate

If transactional marketplace capabilities are ever introduced, they should be layered above EPU.

Possible future marketplace objects may include:

MarketplaceListing
SourcingRequirement
RFQ
Offer
Bid
CapacityCommitment
CommercialTermSet
NegotiationScenario
AwardDecision
ContractReference

None of these should become fields on EPUIdentity.

Likewise, payment, commission, contracting, dispute resolution or transaction settlement are separate business domains and should not be introduced merely to enable supplier/product discovery.

20. Architectural capabilities to preserve now

Although the marketplace is not current scope, EPU should preserve future compatibility with:

• supplier/product discoverability policies;
• technical product capability/specification semantics;
• supplier ECO relationships;
• comparable footprint profiles;
• evidence and TrustGate quality states;
• geographic/facility information;
• production capacity references;
• logistics routes and scenarios;
• internal carbon prices / governed shadow-pricing models;
• commercial-event triggers;
• permission-scoped machine-to-machine information exchange;
• multi-objective sourcing optimization;
• white-label marketplace/discovery experiences.

These capabilities should be introduced only when independently useful to current EPU/product-intelligence use cases.

21. Explicit non-goals for current EPU phase

The current EPU roadmap does not require implementation of:

• public supplier marketplace;
• transaction settlement;
• payment processing;
• commissions;
• auction engines;
• legally binding contracting workflows;
• marketplace dispute handling;
• marketplace escrow;
• dynamic commodity trading.

Recording the opportunity is intended to avoid future architectural dead ends, not expand current delivery scope.

22. Strategic principles

The future opportunity rests on four principles:

Register once. Maintain at source. Resolve many times.

Acquire at the point of leverage; resolve at the point of need.

Sustainability information should become a commercial asset for the supplier and a decision asset for the buyer.

Make better sustainability performance commercially discoverable without weakening product identity, confidentiality, evidence or trust governance.

If these principles are preserved in current EPU architecture, ZAYAZ can evolve toward sustainable sourcing and marketplace capabilities later without redesigning the identity and product-intelligence foundation.