PIP 5C1 — Distribute Product List

RosettaNet choreography in cluster 5, transported on RNIF V02.00 and signed with S/MIME. Operational unit between Manufacturer and Distributor across the high-tech supply chain.

PIP purpose

PIP 5C1 distributes a catalogue list of products authorised for resale, from manufacturer to its distributors or channel partners. Carries GTIN identifiers, categories, canonical descriptions. Marketing channel governance building block. No business confirmation.

Message structure

The 5C1 choreography follows the RosettaNet action model:

Primary action: Product List Notification Action
Signal: Receipt Acknowledgment (RNIF)
Response action: Receipt Acknowledgment

The action is wrapped in a multipart MIME RNIF V02.00 envelope signed with S/MIME. Here is a condensed view of the envelope:

text rnif-envelope-5C1.eml

MIME-Version: 1.0
Content-Type: multipart/related; type="application/xml";
  boundary="RN-BOUNDARY-2026"

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-Preamble.xml

<Preamble xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <standardName>RosettaNet</standardName>
  <standardVersion>V02.00</standardVersion>
</Preamble>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: RN-ServiceHeader.xml

<ServiceHeader xmlns="http://www.rosettanet.org/RNIF/V02.00">
  <GlobalProcessIndicatorCode>5C1</GlobalProcessIndicatorCode>
</ServiceHeader>

--RN-BOUNDARY-2026
Content-Type: application/xml
Content-Location: Pip5C1ProductListNotification.xml

<!-- PIP 5C1 payload above -->

--RN-BOUNDARY-2026--

Simplified XML example

Minimal PIP 5C1 payload for didactic purposes. The structural elements (fromRole, toRole, thisDocumentGenerationDateTime, and the PIP-specific business block) are required in any conformant implementation.

xml pip-5C1.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip5C1ProductListNotification xmlns="http://www.rosettanet.org/PIP5C1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Manufacturer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Distributor</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260516T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
    <ProductList>
      <listIdentifier>
        <ProprietaryDocumentIdentifier>PL-2026-Q3-APAC</ProprietaryDocumentIdentifier>
      </listIdentifier>
      <effectiveDate><DateStamp>20260601</DateStamp></effectiveDate>
      <ProductListItem>
        <LineNumber><FreeFormText>1</FreeFormText></LineNumber>
        <ProductIdentification>
          <GlobalProductIdentifier>00614141444440</GlobalProductIdentifier>
        </ProductIdentification>
        <productCategory><FreeFormText>Microprocessor</FreeFormText></productCategory>
        <productStatus>Active</productStatus>
      </ProductListItem>
    </ProductList>
</Pip5C1ProductListNotification>

Transport and acknowledgment

Core of the standard: HTTPS POST to the partner endpoint or via AS2. S/MIME signature and Receipt Acknowledgment are systematic. PIP 5C1 is typically transported asynchronously.

The transport channel is typically AS2 or direct HTTPS (RNIF over HTTP). For a reference of the security layers in use, see the AS2 on ediverse page.

Use case

AMD distributes monthly to Avnet a PIP 5C1 authorised list of 1,850 SKUs available for APAC resale in the next quarter, with explicit drop-dates for EOL references.

Foundations

Standards

Flagship messages

Tools