PIP 3C1 — Return Product

RosettaNet choreography in cluster 3 (Order Management — Returns), covering the XML exchange between Buyer ↔ Seller. Operational unit for order management — returns on RNIF V02.00.

PIP purpose

PIP 3C1 requests a product return (Return Material Authorization — RMA). The buyer declares to the seller a product to return (defect, overstock, end of life). The seller responds with an RMA number, return instructions, and financial conditions (credit, exchange).

Message structure

The 3C1 choreography follows the two-action (request / response) RosettaNet model:

Primary action: Return Product Request Action
Signal: Receipt Acknowledgment
Response action: Return Product Confirmation Action

Each 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-3C1.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>3C1</GlobalProcessIndicatorCode>
</ServiceHeader>

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

<!-- payload PIP 3C1 ci-dessus -->

--RN-BOUNDARY-2026--

Simplified XML example

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

xml pip-3C1.xml

<?xml version="1.0" encoding="UTF-8"?>
<Pip3C1ReturnProductRequest xmlns="http://www.rosettanet.org/PIP3C1">
  <fromRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </fromRole>
  <toRole>
    <PartnerRoleDescription>
      <GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>
    </PartnerRoleDescription>
  </toRole>
  <thisDocumentGenerationDateTime>
    <DateTimeStamp>20260515T101500Z</DateTimeStamp>
  </thisDocumentGenerationDateTime>
      <ReturnRequest>
        <ReturnRequestIdentifier>
          <ProprietaryDocumentIdentifier>RMA-2026-444112</ProprietaryDocumentIdentifier>
        </ReturnRequestIdentifier>
        <ProductLineItem>
          <ProductIdentification>
            <GlobalProductIdentifier>00614141999996</GlobalProductIdentifier>
          </ProductIdentification>
          <returnQuantity>
            <ProductQuantity>200</ProductQuantity>
            <unitOfMeasure>EA</unitOfMeasure>
          </returnQuantity>
          <ReturnReason>
            <GlobalReturnReasonCode>DefectiveProduct</GlobalReturnReasonCode>
          </ReturnReason>
        </ProductLineItem>
      </ReturnRequest>
</Pip3C1ReturnProductRequest>

Transport and acknowledgment

Asynchronous cycle, RNIF V02.00 over HTTPS POST or AS2. Often followed by a PIP 3B2 return (the EMS actually ships the defective components) and a PIP 3C3 credit invoice.

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

An EMS detects a defective batch of 200 components received two weeks earlier. It sends a PIP 3C1 to the distributor (Arrow): RMA requested, reason DefectiveProduct, return conditions to confirm. Arrow responds with a PIP 3C1 confirmation including RMA number, return label, and accounting credit.

Foundations

Standards

Flagship messages

Tools