# T-Shirt DPP Recipe for Integrating VERA DPP with eCommerce Platforms such as Shopify

### I) Introduction

#### Objective and Scope

This recipe outlines a streamlined approach for integrating Digital Product Passports (DPPs) into eCommerce platforms such as Shopify. The primary objective is to enable shop operators to easily implement DPPs without requiring deep platform integration, making it accessible across a wide range of platforms, including Shopify, Amazon, WooCommerce, Magento, BigCommerce, and Print-on-Demand (PoD) platforms like Printful and Gelato.

The DPP integration is designed to work seamlessly with VERA APIs, ensuring that the implementation process is straightforward and efficient for shop operators. Additionally, for DPP URLs, we may utilize the [trusted-dpps.com](https://www.trusted-dpps-com) domain, offering a whitelabeling option under this domain. This allows our customers to present a trusted, brand-aligned experience for their end-users, enhancing credibility and user trust while maintaining the flexibility and functionality of the DPP system.

#### Summary of the Approach

We propose a straightforward method for integrating DPPs by utilizing batch-level serialization. This approach allows for the generation of batch DPPs that can be linked to products using QR codes, which are incorporated into the product designs, such as T-Shirts. Each batch of products, identified by a Batch ID, shares a common QR code that directs users to a batch DPP containing general product information and compliance data.

For individualized customer engagement, the system generates unique DPPs linked to specific orders, which are sent to customers via order confirmation emails. To make the example as specific as possible, we decided to focus on Shopify. However, this approach is also adaptable to other eCommerce or Printing on Demand platforms, making it a versatile solution for various online retail environments.

#### Optional Integrations and Customization

This approach also supports further optional integrations, such as:
- **Synchronization of eCommerce Platform Product Master Data with the DPP**: Automating the synchronization of your eCommerce platform’s product master data with the DPP system to ensure that batch data is accurately populated in the DPPs. This integration helps maintain consistency across all platforms, ensuring that product details, compliance information, and other essential data are up-to-date in both your eCommerce platform and the DPP. This reduces manual data entry and errors, enhancing efficiency and accuracy across your operations.
- **Cart Integration**: Adding DPPs and serialised QR codes at the cart level.
- **Leaflet Printing**: Including serialised QR codes on printed materials like leaflets or packaging inserts.
- **Return Processing**: Using DPPs to manage product returns more efficiently and releasing customer benefits after the return period has ended without the return of the product.
- **Historic Purchases & T-Shirt Closet**: Providing customers with a digital “closet” that tracks all their past T-Shirt purchases linked to their DPPs. This feature could allow customers to view the entire history of their purchased items, including material details, sustainability information, and special offers associated with previous purchases. This digital closet can also facilitate reordering favorite items or managing warranty claims through DPPs, further enhancing the customer experience and promoting brand loyalty.
- **Influencer Marketing & Referrals**: Leveraging DPPs to drive influencer marketing campaigns by allowing influencers to share their personalized DPPs or create content around specific products. Customers can be incentivized to refer friends by sharing their DPPs, which could include unique referral codes or offers linked to the DPP, encouraging organic growth and customer acquisition through social proof.
- **Social Media Integration and ‘Share your Look’**: Enabling customers to share their DPP-linked purchases on social media platforms with integrated features like ‘Share your Look.’ After scanning their QR code, customers can access options to post about their purchase on platforms like Instagram or Facebook, tagging the brand and even linking back to the DPP. This not only enhances brand visibility but also allows customers to participate in community-driven content, fostering a sense of connection and engagement with the brand.
- **Customer Engagement and Benefits**: Offering personalized engagement features like lotteries, vouchers, and mystery boxes through individual DPPs as well as personalised marketing for cross- and up-selling.

We investigated the deatails on how to achieve such a customization with Shopify and Gelato already.

#### Why This Approach?

Our goal is to make DPP integration as easy as possible for shop operators. While alternative approaches—such as generating serialized item-level QR codes on the fly for Print-on-Demand products—are technically feasible, they require deeper platform integration. Such integrations are complex and may not be practical across multiple eCommerce platforms due to varying technical constraints.

Some platforms offer very flexible customization and code injection options, allowing for extensive API usage, custom scripts, and real-time data handling (e.g., Shopify, WooCommerce, and Magento). These platforms are ideal for more advanced integrations, such as generating and embedding unique QR codes for each item on demand. However, other platforms, like Amazon, have closed ecosystems with very limited customization options. On such platforms, the ability to inject custom code or leverage advanced API integrations is restricted, making complex real-time QR code generation and serialization challenging.

The batch DPP approach we propose is designed to be universally applicable, including on platforms with limited customization capabilities like Amazon. By focusing on batch-level serialization and pre-generating QR codes, this method ensures that DPPs can be implemented across all major eCommerce platforms, regardless of their customization limitations. This strategy offers a practical and scalable solution that simplifies integration for shop operators, even in environments where deep platform integration is not feasible.

#### Batch vs. Individual DPPs

We distinguish between batch DPPs and individual DPPs for authenticated users. Batch DPPs offer a simpler, more scalable solution by not requiring unique QR codes for each product. However, serialized item-level DPPs, which involve generating random serial numbers for each product, provide enhanced anti-counterfeiting capabilities. These capabilities rely on a product verification API that cross-references the serialized number against a database, ensuring product authenticity.

For simplicity and broad applicability, this recipe uses batch serialization. In this example, we focus on a T-Shirt printed on demand (PoD), where the pre-defined T-Shirt PoD design includes a batch QR code already. Each eCommerce platform may use different Batch IDs and QR codes to link products to specific platforms for better order mapping and user authentication, ensuring the approach scales effectively across different platforms.

This method provides a practical and scalable solution for integrating DPPs into eCommerce platforms, making it easier for shop operators to implement without needing extensive customization or platform-specific development.

See *Appendix A.1* for how this approach will work with Amazon.

See *Appendix A.2* for fact check about the assertions made in this introcution.

See *Appendix A.3* for information about Global IDs, Oder IDs and Item IDs.

### II) eCommerce DPP Integration Approach

#### 1. Overview of the Approach

Your approach involves creating a unique Digital Product Passport (DPP) for each batch of T-Shirts and individual serialized DPPs for each purchased T-Shirt. This information will be delivered to the customer via QR codes, both printed on the T-Shirts and included in order confirmation emails. The main objectives include providing general product information, customer engagement features, and compliance data via batch DPPs, while offering additional, personalized content through individual DPPs linked to the specific order.

#### 2. Viability of the Approach

**Batch DPPs and QR Code Printing**:
- **Batch ID and Batch DPP**: Associating a batch of T-Shirts with a common Batch ID and corresponding DPP is feasible. You can use Shopify’s product and variant options to manage this. The Batch DPP URL can be generated by the VERA API, and the QR code can be printed on the T-Shirts during production.
- **QR Code Consistency**: Since all T-Shirts in a batch share the same design and information, printing the same QR code on all items in that batch is manageable and can be automated.

**Individual DPPs and Email Integration**:
- **Individual DPP Generation**: When a customer places an order, Shopify can send the order details to the VERA API, which then generates a unique DPP URL for each T-Shirt based on the order ID and item ID. This is technically feasible using Shopify’s API and webhooks.
- **Email Integration**: The individual DPP URL can be encoded as a QR code and included in the order confirmation email. Shopify provides flexibility for customizing emails either directly within the platform or through third-party integrations.

#### **3. Detailed Analysis of Email Integration Options**

**Option A: Modify Shopify Confirmation Email**
- **Feasibility**: Shopify allows customization of the order confirmation email via its built-in email templates. You can inject the QR code URL into the template, but there are limitations in terms of how dynamic content is handled.
- **Limitations**:
- Shopify’s Liquid templating language supports some dynamic content, but it may not directly support external API calls at the time of email rendering. This might require workarounds, such as pre-generating content before it’s injected into the email.
- Another consideration is that changing the email template to include custom logic for generating QR codes might be complex and not as flexible as using an external service like AWS Lambda.

**Option B: Use AWS Lambda to Send a Second Email**
- **Feasibility**: A more flexible approach would be to use AWS Lambda to listen to Shopify order events via webhooks. When an order is placed, the Lambda function is triggered, which then generates the individual DPP QR code and sends a custom email using Amazon SES.
- **Advantages**:
- This method offers greater flexibility in customizing the email content, as it’s handled outside of Shopify’s limitations.
- It also allows for complex logic, such as conditional content or additional customer engagement features that may not be possible directly within Shopify.
- **Considerations**:
- Implementing this requires setting up and maintaining AWS infrastructure, which adds complexity but provides more control and scalability.

#### **4. Linking Orders to Individual DPPs and Authentication Options**

**Option A: Using Shopify Account for Authentication**
- **Feasibility**: Shopify provides a customer authentication mechanism through Shopify accounts. Customers can log in with their Shopify credentials, and you can link their orders to the corresponding individual DPPs.
- **Considerations**:
- This approach leverages Shopify’s existing user authentication, making it simpler to implement. However, it may not be as flexible if you need to offer additional features that require separate or enhanced authentication processes.

**Option B: Using VERA Account Linked to Shopify Account**
- **Feasibility**: This approach involves creating a VERA account system that can be linked to a customer’s Shopify account. Upon scanning the QR code, customers would authenticate through their VERA account, which would be linked to their Shopify orders.
- **Advantages**:
- This allows you to offer more advanced features, such as customer engagement tools (e.g., mystery boxes, lotteries, vouchers) that may require more complex account management.
- **Challenges**:
- Setting up and managing a separate authentication system adds complexity and requires ensuring that the VERA account system integrates seamlessly with Shopify.
- You’ll also need to manage account linking, which could complicate the user experience if not handled smoothly.

#### **5. Additional Considerations and Potential Options**

- **Webhook Flexibility**: Shopify’s webhooks are highly flexible and can be used to trigger various processes, such as generating individual DPPs, sending emails, or updating order status.
- **Using Shopify Plus**: If you’re on Shopify Plus, you may have access to additional customization options like Shopify Scripts and Flow, which can automate and customize various aspects of the order process more effectively.
- **Third-Party Integrations**: Consider using third-party services like Zapier or Integromat to automate some parts of the workflow if you want to avoid custom coding or AWS management.

#### **Feasibility**

The proposed approach is feasible, but with some considerations:

1. **Batch DPPs and QR Code Printing**: Easily implemented and managed within Shopify and during production.
2. **Individual DPPs and Email Integration**: More complex, with two viable options—modifying Shopify’s email template directly or using AWS Lambda to send a second, custom email.
3. **Authentication Options**: Both using Shopify’s existing authentication and a custom VERA account system are possible, with trade-offs in complexity and flexibility.

This approach, particularly the use of AWS Lambda for handling dynamic content and custom email delivery, provides the most flexibility and control, although it requires more advanced setup and ongoing management.

### III) Detailed Recipe for Integrating VERA DPP with Shopify and Custom QR Code Implementation

#### **List of Steps:**

1. **Set Up Shopify Store and Products**
- Register and configure your Shopify store.
- Set up product listings for T-Shirts with appropriate batch IDs.

2. **Set Up VERA API for Batch and Individual DPPs**
- Configure VERA API to handle batch DPP creation and individual DPP generation.
- Set up endpoints for generating QR codes.

3. **Integrate Batch DPP QR Codes into Product Designs**
- Generate Batch DPP QR codes using the VERA API.
- Include these QR codes in the design files for T-Shirts.

4. **Modify Shopify Order Confirmation Process**
- Option A: Modify the Shopify confirmation email template to include individual QR codes.
- Option B: Set up AWS Lambda to handle custom email processing triggered by Shopify order events.

5. **Set Up Authentication for Accessing Individual DPPs**
- Option A: Use Shopify’s customer accounts for authentication.
- Option B: Create a VERA account system linked to Shopify accounts.

6. **Test and Deploy the System**
- Test the entire workflow, from ordering to email receipt and QR code scanning.
- Deploy and monitor the system for any issues.

### III.1) Step 1: Set Up Shopify Store and Products

**Objective**: Ensure that your Shopify store is properly set up with product listings for the T-Shirts, each associated with a specific batch ID.

#### **Steps**:

1. **Register a Shopify Account**:
- Sign up for a Shopify account at [shopify.com](https://www.shopify.com).
- Follow the guided steps to set up your store, including setting up payment gateways, shipping options, and store settings.

2. **Create Product Listings**:
- **Add Products**: Go to the Shopify admin panel and navigate to "Products" > "Add product".
- **Assign Batch IDs**: Use product tags or a specific metafield to assign a Batch ID to each T-Shirt design.
- Example: Tag products with `Batch-ID-001`, `Batch-ID-002`, etc.
- **Set Up Variants**: If your T-Shirts come in different sizes or colors, create variants under the same product listing.

3. **Product Descriptions**:
- Include information about the Batch DPP and how customers can access it through the QR code on the T-Shirt.

#### **Sample Code (Liquid for Batch ID Display)**:
If you want to display the Batch ID on the product page, you can use Shopify’s Liquid templating language:

{% if product.tags contains 'Batch-ID-001' %}
  <p>This product belongs to Batch ID: 001</p>
{% endif %}

#### **Outcome**:
At the end of this step, your Shopify store should have all the necessary product listings, each tagged or marked with a Batch ID. This will be important for linking the products to their respective Batch DPPs.

Please let me know if you would like to proceed with Step 2 or if you need further details on Step 1.

### III.2) Step 2: Set Up VERA API for Batch and Individual DPPs

**Objective**: Configure the VERA API to manage both batch-level Digital Product Passports (DPPs) and individual serialized DPPs. This involves setting up endpoints for generating QR codes that link to these DPPs.

#### **Steps**:

1. **Configure VERA API for Batch DPPs**:
- **Create Batch DPP Endpoint**: Set up an endpoint in the VERA API that creates and stores a DPP for each batch of T-Shirts.
- Example Endpoint: `POST /api/create-batch-dpp`
- **Input Data**:
- `batchId`: The unique identifier for the batch.
- `productDetails`: General information about the T-Shirt design.
- `esprInfo`: Information related to compliance (e.g., ESPR regulations).
- **Response**: The API should return a URL to the Batch DPP.
- **Store the Batch DPP URL**: Store this URL in Shopify as a product metafield or tag, so it can be referenced when generating QR codes for printing.

   {
     "batchId": "Batch-ID-001",
     "productDetails": {
       "productName": "Eco-Friendly T-Shirt",
       "material": "Organic Cotton",
       "color": "Green"
     },
     "esprInfo": {
       "regulationCompliance": "ESPR-2024"
     }
   }

**Example API Response**:

   {
     "batchDppUrl": "https://api.spherity.com/dpp/batch/Batch-ID-001"
   }

2. **Configure VERA API for Individual DPPs**:
- **Create Individual DPP Endpoint**: Set up an endpoint in the VERA API that creates a unique DPP for each individual T-Shirt based on the order and item ID.
- Example Endpoint: `POST /api/create-individual-dpp`
- **Input Data**:
- `orderId`: The unique identifier for the customer order.
- `itemId`: The unique identifier for the item within the order.
- `batchId`: The Batch ID to link the individual DPP with the batch.
- `additionalInfo`: Any customer-specific or engagement-related information.
- **Response**: The API should return a URL to the individual DPP.

   {
     "orderId": "Order-12345",
     "itemId": "Item-001",
     "batchId": "Batch-ID-001",
     "additionalInfo": {
       "customerName": "John Doe",
       "specialOffer": "10% Discount on Next Purchase"
     }
   }

**Example API Response**:

   {
     "individualDppUrl": "https://api.spherity.com/dpp/individual/Order-12345-Item-001"
   }

3. **Generate QR Codes for DPPs**:
- **QR Code Generation**: The VERA API should also provide functionality to generate a QR code image from the DPP URL.
- Example Endpoint: `POST /api/generate-qr`
- **Input Data**:
- `dppUrl`: The URL to the Batch or Individual DPP.
- **Response**: A URL to the generated QR code image.

   {
     "dppUrl": "https://api.spherity.com/dpp/individual/Order-12345-Item-001"
   }

**Example API Response**:

   {
     "qrCodeUrl": "https://api.spherity.com/qrcodes/Order-12345-Item-001.png"
   }

#### **Outcome**:

By the end of this step, you should have a fully functioning VERA API that can generate both batch-level and individual DPPs, as well as the corresponding QR codes. These QR codes can then be used for both the physical T-Shirts and for inclusion in Shopify order confirmation emails.

### III.3) Step 3: Integrate Batch DPP QR Codes into Product Designs

**Objective**: Ensure that the Batch DPP QR codes generated in Step 2 are integrated into the design files for the T-Shirts. This involves generating the QR codes and embedding them into the design that will be printed on each T-Shirt.

#### **Steps**:

1. **Generate Batch DPP QR Codes**:
- Using the VERA API set up in Step 2, generate a QR code for each Batch DPP URL.
- Example API Request:

     const axios = require('axios');

     async function generateBatchQrCode(batchDppUrl) {
         const response = await axios.post('https://api.spherity.com/generate-qr', {
             dppUrl: batchDppUrl
         });
         return response.data.qrCodeUrl;
     }

     // Example usage
     const batchDppUrl = "https://api.spherity.com/dpp/batch/Batch-ID-001";
     generateBatchQrCode(batchDppUrl).then(qrCodeUrl => {
         console.log('Batch QR Code URL:', qrCodeUrl);
     });

2. **Integrate QR Code into Design Files**:
- **Design Software**: Use graphic design software such as Adobe Illustrator, Photoshop, or any design tool compatible with your T-Shirt printing method.
- **Embed QR Code**: Embed the generated QR code URL into the design template for the T-Shirt.
- **Placement**: Choose a location on the T-Shirt that’s visible and practical, such as the lower hem, sleeve, or back.
- **Save Design**: Once the QR code is embedded in the design, save the file in the format required by your printing service (e.g., .AI, .PSD, .PNG, etc.).

3. **Upload Design to Shopify (Optional)**:
- If you want to showcase the T-Shirt design with the QR code in your Shopify store, upload the design as a product image.
- **Steps**:
- Go to Shopify Admin > Products.
- Select the T-Shirt product associated with the batch.
- Upload the design image that includes the embedded QR code.

#### **Outcome**:
By the end of this step, all T-Shirts in a batch should have the Batch DPP QR code embedded in their design, ready for printing. This QR code will direct users to the general information about the batch when scanned, providing access to product and compliance details.

### III.3.a) Explanation: Generating and Storing QR Code URLs Before Sending Confirmation Emails

**Context**:
When integrating individual QR codes into Shopify order confirmation emails, there are limitations with Shopify’s built-in email customization capabilities. Specifically, Shopify's Liquid templating language, used for customizing emails, does not support making external API calls at the time the email is generated. This means that you cannot dynamically call the VERA API to generate a QR code URL within the email template itself.

**Solution**:
To work around this limitation, you may need to generate and store the QR code URLs *before* the confirmation email is sent. This ensures that the QR code is available when the email is rendered and sent to the customer. There are two main ways to achieve this: using Shopify webhooks or scheduled tasks.

#### **Option 1: Using Shopify Webhooks**

**Webhooks** are a powerful feature in Shopify that allows you to trigger actions based on events, such as when an order is created or paid for. Here's how you can use them:

1. **Set Up a Webhook**:
- In your Shopify Admin, navigate to "Settings" > "Notifications" > "Webhooks".
- Create a new webhook for the "Order creation" or "Order paid" event, depending on when you want to generate the QR code.

2. **Webhook Endpoint**:
- Set the webhook to send order data to an external server or a serverless function (like AWS Lambda) that processes the order data.

3. **Generate and Store QR Code URL**:
- When the webhook triggers, your server will:
- Extract the relevant order and product details.
- Call the VERA API to generate the individual QR code URL.
- Store this URL in a Shopify metafield, order note, or an external database linked to the order.

4. **Modify Email Template**:
- Customize the Shopify email template to include the stored QR code URL. Since the URL is pre-generated and stored, it can be directly inserted into the email using Liquid code.

**Example Liquid Code in Email Template**:

   {% assign qr_code_url = order.metafields.custom.qr_code_url %}
   <h1>Order Confirmation</h1>
   <p>Thank you for your order, {{ order.name }}!</p>
   <p>Product: {{ line_item.title }}</p>
   <img src="{{ qr_code_url }}" alt="QR Code">

#### **Option 2: Using Scheduled Tasks**

**Scheduled Tasks** are another approach, where you periodically check for new orders and generate QR codes in bulk:

1. **Scheduled Task Setup**:
- Use a server (e.g., a cron job) or a cloud-based task scheduler (e.g., AWS Lambda with scheduled triggers) to periodically fetch new orders from Shopify via the API.

2. **Generate QR Code URLs**:
- For each new order, call the VERA API to generate the QR code URL.
- Store the QR code URL in the same manner as with the webhook option (metafields, order notes, or an external database).

3. **Modify Email Template**:
- As with the webhook approach, customize the Shopify email template to pull in the pre-generated QR code URL.

#### **Advantages of Pre-Generating QR Code URLs**:

- **Reliability**: By generating and storing the QR code URLs ahead of time, you ensure that the email will always include the correct QR code, without relying on dynamic generation during email rendering.
- **Flexibility**: You can manage the QR code generation process externally, allowing for more complex logic or error handling.
- **Speed**: Since the QR code URL is already stored, the email can be sent out faster without waiting for real-time API calls.

#### Sample Code for a Webhook Implementation:

Here’s an example of how you might set up a webhook to generate and store QR code URLs:

const axios = require('axios');
const Shopify = require('shopify-api-node');

// Initialize Shopify API client
const shopify = new Shopify({
  shopName: 'your-shop-name',
  apiKey: 'your-api-key',
  password: 'your-api-password'
});

exports.handler = async (event) => {
  const order = JSON.parse(event.body);

  for (const item of order.line_items) {
    const orderId = order.id;
    const itemId = item.id;

    // Generate QR code URL
    const qrResponse = await axios.post('https://api.spherity.com/create-individual-dpp', {
      orderId: orderId,
      itemId: itemId,
      productDetails: { productName: item.name }
    });
    const qrCodeUrl = qrResponse.data.qrCodeUrl;

    // Store QR code URL in Shopify metafield
    await shopify.metafield.create({
      key: 'qr_code_url',
      value: qrCodeUrl,
      value_type: 'string',
      namespace: 'custom',
      owner_resource: 'order',
      owner_id: orderId
    });
  }

  return { statusCode: 200, body: 'QR codes generated and stored successfully' };
};

#### Conclusion:

This approach—pre-generating and storing QR code URLs—ensures that the correct QR code is readily available when the order confirmation email is sent. This method avoids the limitations of Shopify’s Liquid templating by handling all dynamic content generation beforehand, either through webhooks or scheduled tasks. By implementing one of these options, you can reliably include individual QR codes in your Shopify order confirmation emails, enhancing customer engagement and providing personalized experiences.

### III.3.b) Q&A

#### Option 1: Does Shopify Liquid Code Wait for VERA API?

**Answer:**
No, Shopify’s Liquid templating engine does not wait for external API calls like those made to the VERA API. Liquid is a server-side templating language used by Shopify to render HTML before the page or email is delivered to the client. When you inject Liquid code into a Shopify email template or page, it processes the code synchronously and does not support asynchronous operations such as waiting for an external API response.

**Implication:**
This means that if you try to call an external API like VERA within a Liquid template, the Liquid engine will not wait for the API response, and thus the request will either fail or not be executed at all. This limitation is why the pre-generation of QR codes (using webhooks or scheduled tasks) before the email is sent is necessary, as mentioned earlier.

#### Option 2: Bulk Approach with Sequential Assignment of DPPs

**Objective:**
Ensure that each order confirmation email includes a unique DPP QR code by selecting the first available, unused DPP from a pre-generated list, avoiding duplicates.

**Steps to Implement:**

1. **Pre-Generate DPPs Using VERA API:**
- You would first need to generate a bulk list of individual DPPs using the VERA API. This can be done through a scheduled task or as part of a batch processing job.
- Store these DPPs in a database or an external storage system, marking each DPP as "unused" initially.

**Example Database Schema for Storing DPPs:**

   CREATE TABLE dpp_codes (
       id SERIAL PRIMARY KEY,
       dpp_url TEXT NOT NULL,
       is_used BOOLEAN DEFAULT FALSE,
       order_id TEXT,
       created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
   );

2. **Assigning DPPs to Orders:**
- When an order is created or processed, retrieve the first available (unused) DPP from the database, mark it as used, and associate it with the order.

**Example Code for Fetching and Marking a DPP as Used:**

   const { Pool } = require('pg'); // PostgreSQL client
   const pool = new Pool(); // Configure your database connection

   async function assignDppToOrder(orderId) {
       const client = await pool.connect();
       try {
           await client.query('BEGIN');
           const res = await client.query(
               'SELECT id, dpp_url FROM dpp_codes WHERE is_used = FALSE ORDER BY id ASC LIMIT 1 FOR UPDATE'
           );
           if (res.rows.length === 0) {
               throw new Error('No unused DPP codes available');
           }

           const dpp = res.rows[0];
           await client.query(
               'UPDATE dpp_codes SET is_used = TRUE, order_id = $1 WHERE id = $2',
               [orderId, dpp.id]
           );
           await client.query('COMMIT');
           return dpp.dpp_url;
       } catch (err) {
           await client.query('ROLLBACK');
           throw err;
       } finally {
           client.release();
       }
   }

3. **Modifying the Email Template:**
- After assigning a DPP to an order, store the DPP URL as a Shopify metafield or in an external database linked to the order. Then, customize the Shopify email template to pull in this pre-assigned DPP URL.

**Example Liquid Code in Email Template:**

   {% assign dpp_url = order.metafields.custom.dpp_url %}
   <h1>Order Confirmation</h1>
   <p>Thank you for your order, {{ order.name }}!</p>
   <p>Product: {{ line_item.title }}</p>
   <img src="{{ dpp_url }}" alt="QR Code">

4. **Ensuring Uniqueness:**
- The database operations should be designed to ensure that each DPP URL is used only once. This is achieved by marking the DPP as "used" immediately when it is retrieved and associated with an order, and by using database transactions to avoid race conditions.

5. **Handling Edge Cases:**
- If no unused DPPs are available, consider implementing a fallback mechanism, such as generating a new DPP on-demand or sending a default message until the issue is resolved.

**Outcome:**
This approach ensures that each order receives a unique, non-duplicated DPP by carefully managing the pre-generated DPPs and sequentially assigning them to orders. The bulk generation process helps in efficiently managing large volumes of orders, and the sequential assignment prevents the risk of duplicate DPPs being issued.

#### Implication and Ensuring QR Code Availability

**Implication**:
As previously mentioned, Shopify’s Liquid templating engine does not support asynchronous operations such as making API calls during the rendering process. This means that if you attempt to call an external API like the VERA API within a Liquid template, the Liquid engine will not wait for the API to respond. Consequently, the request would either not execute or fail, resulting in the inability to retrieve and display the necessary QR code in real-time.

This limitation necessitates the pre-generation of QR codes before the email template is rendered and sent to the customer.

**Ensuring QR Code Availability Before Email Rendering**

To ensure that the pre-generated QR code is ready and available by the time the Liquid code in the email template is executed, the following steps should be taken:

1. **Synchronous Handling in Webhooks**:
- **Immediate Generation and Storage**: When using a webhook to handle the order creation or order paid event, ensure that the QR code generation and storage process is synchronous. This means that the webhook should fully complete the QR code generation and store the URL in Shopify (e.g., in a metafield) before responding to Shopify.
- **Webhook Response Timing**: Shopify waits for the webhook response before moving on to the next action. If your webhook takes a second or two to complete the QR code generation, Shopify will wait for the webhook to finish before proceeding with the next steps, such as sending the email. This ensures that the QR code URL is ready by the time the email is generated.

**Example of Synchronous Processing**:

   const axios = require('axios');
   const Shopify = require('shopify-api-node');

   exports.handler = async (event) => {
       const order = JSON.parse(event.body);
       const orderId = order.id;
       const itemId = order.line_items[0].id;

       // Generate QR code URL
       const qrResponse = await axios.post('https://api.spherity.com/create-individual-dpp', {
           orderId: orderId,
           itemId: itemId
       });
       const qrCodeUrl = qrResponse.data.qrCodeUrl;

       // Store QR code URL in Shopify metafield
       await shopify.metafield.create({
           key: 'qr_code_url',
           value: qrCodeUrl,
           value_type: 'string',
           namespace: 'custom',
           owner_resource: 'order',
           owner_id: orderId
       });

       return { statusCode: 200, body: 'QR code generated and stored successfully' };
   };

2. **Delaying the Email Sending**:
- **Webhook Execution First**: Configure your process so that the email is sent only after the webhook has fully processed the order and stored the QR code URL. Shopify's internal workflow will naturally handle this if the QR code is stored as a metafield before the email template is rendered.
- **Using a Small Delay (if necessary)**: If you're concerned about timing, consider introducing a short delay in the email sending process (this would generally be handled within Shopify's native flow, but can be further managed through workflow apps or custom scripts).

3. **Error Handling**:
- **Fallback Mechanism**: Implement a fallback mechanism in the webhook or the email template. For example, if the QR code URL is not available for any reason, the email template could display a default message or image instructing the customer to follow up, or you could resend the email once the QR code becomes available.

**Example of a Fallback in Liquid Code**:

   {% if order.metafields.custom.qr_code_url %}
     <img src="{{ order.metafields.custom.qr_code_url }}" alt="QR Code">
   {% else %}
     <p>Your QR code is being generated. Please check your account later for access to your personalized information.</p>
   {% endif %}

By ensuring that the QR code is generated and stored in Shopify before the email is rendered and sent, you avoid the issue of asynchronous API calls within Liquid templates and ensure a smooth and reliable customer experience.

### III.4) Step 4: Modify Shopify Order Confirmation Process

**Objective**: Modify the Shopify order confirmation process to include individual QR codes linked to the personalized DPPs for each T-Shirt ordered. This step involves choosing between two options: modifying the Shopify confirmation email directly or using AWS Lambda to send a second, custom email.

#### **Option A: Modify Shopify Confirmation Email**

1. **Access Shopify Email Templates**:
- Go to your Shopify Admin Dashboard.
- Navigate to "Settings" > "Notifications".
- Scroll to find the "Order confirmation" email template and click "Customize".

2. **Customize the Email Template**:
- Shopify uses the Liquid templating language to render email templates.
- Insert a placeholder in the template where you want the QR code to appear. You need to pre-generate the QR code URL and inject it into the template.

**Example Liquid Code**:

   {% assign qr_code_url = 'https://api.spherity.com/qrcodes/' | append: order.id | append: '-Item-' | append: line_item.id | append: '.png' %}
   
   <h1>Order Confirmation</h1>
   <p>Thank you for your order, {{ order.name }}!</p>
   <p>Product: {{ line_item.title }}</p>
   <img src="{{ qr_code_url }}" alt="QR Code">

- This code assumes that you have a pre-defined pattern for generating QR code URLs using order IDs and item IDs. The example above uses placeholders to construct the URL dynamically.

3. **Test the Email Template**:
- Place a test order to ensure the QR code appears correctly in the confirmation email.
- Adjust the design or layout as needed to fit the email’s style.

4. **Limitations**:
- Shopify’s Liquid templating language does not support making external API calls directly. This means that while you can dynamically generate URLs using pre-known patterns, you cannot call the VERA API to generate the QR code URL on-the-fly within the email template itself.
- You may need to generate and store the QR code URLs before sending the confirmation email, which can be done through webhooks or scheduled tasks.

#### **Option B: Use AWS Lambda to Send a Second Custom Email**

1. **Set Up Shopify Webhooks**:
- Navigate to "Settings" > "Notifications" > "Webhooks" in Shopify.
- Create a new webhook for "Order creation" or "Order paid", depending on when you want the email to be triggered.
- Set the webhook to send data to an AWS API Gateway endpoint, which triggers a Lambda function.

2. **Create AWS Lambda Function**:
- Use AWS Lambda to handle the webhook event from Shopify. The Lambda function will process the order data, generate the individual DPP using the VERA API, and send a custom email with the QR code.

**Lambda Function Example**:

   const AWS = require('aws-sdk');
   const axios = require('axios');
   const ses = new AWS.SES();

   exports.handler = async (event) => {
       const order = JSON.parse(event.body);
       const orderId = order.id;
       const lineItems = order.line_items;

       for (const item of lineItems) {
           const itemId = item.id;
           const productName = item.name;

           // Generate Individual DPP QR Code URL
           const response = await axios.post('https://api.spherity.com/create-individual-dpp', {
               orderId: orderId,
               itemId: itemId,
               productDetails: { productName }
           });
           const qrCodeUrl = response.data.qrCodeUrl;

           // Send custom email via SES
           const emailParams = {
               Destination: { ToAddresses: [order.email] },
               Message: {
                   Body: {
                       Html: {
                           Charset: "UTF-8",
                           Data: `
                               <h1>Order Confirmation</h1>
                               <p>Thank you for your order, ${order.name}!</p>
                               <p>Product: ${productName}</p>
                               <img src="${qrCodeUrl}" alt="QR Code">
                           `
                       }
                   },
                   Subject: { Charset: 'UTF-8', Data: 'Your Order Confirmation' }
               },
               Source: '[e-mail]'
           };

           await ses.sendEmail(emailParams).promise();
       }

       return { statusCode: 200, body: 'Email sent successfully' };
   };

3. **Deploy and Test the Lambda Function**:
- Deploy the Lambda function via the AWS Console.
- Test the entire process by placing an order on Shopify and ensuring that the Lambda function is triggered, the DPP is created, and the email with the QR code is sent correctly.

4. **Benefits and Flexibility**:
- Using AWS Lambda gives you complete control over the email content and allows you to include more dynamic content and logic than Shopify’s native email customization.
- It also separates the QR code generation process from Shopify’s email system, providing better error handling and scalability.

#### **Outcome**:
At the end of this step, you will have a fully integrated system that sends order confirmation emails with individual QR codes linked to personalized DPPs. Depending on your choice, this can be done either directly within Shopify or through a more flexible and powerful AWS Lambda setup.

### III.5) Step 5: Set Up Authentication for Accessing Individual DPPs

**Objective**: Implement a system that ensures customers can authenticate themselves before accessing the personalized Digital Product Passports (DPPs) for the T-Shirts they have purchased. This authentication can be done using either their Shopify account or a VERA account that is linked to their Shopify account.

#### **Authentication Options**

**Option A: Use Shopify Account for Authentication**

**Overview**:
Leverage Shopify's built-in customer authentication system to allow users to log in with their Shopify credentials and access their individual DPPs. This method is straightforward and utilizes Shopify's existing infrastructure.

**Steps**:

1. **Shopify Customer Account Setup**:
- Ensure that customer accounts are enabled in your Shopify store settings.
- Go to Shopify Admin > Settings > Checkout, and under "Customer accounts," select "Accounts are optional" or "Accounts are required" based on your store’s needs.

2. **Link Orders to Customer Accounts**:
- When an order is placed, it is automatically linked to the customer’s Shopify account (if they are logged in during the purchase).
- Store the individual DPP URL generated by the VERA API in the order's metafields.

3. **Secure DPP Access**:
- Set up a page in your Shopify store where customers can log in to view their orders.
- On this page, display the DPPs linked to their orders only after they have authenticated themselves using their Shopify account.

**Example of a Secure DPP Access Page**:

   {% if customer %}
     <h1>Welcome, {{ customer.first_name }}!</h1>
     <p>Here are your products and their associated DPPs:</p>
     {% for order in customer.orders %}
       <h3>Order {{ order.name }}</h3>
       {% for line_item in order.line_items %}
         <p>Product: {{ line_item.title }}</p>
         <a href="{{ order.metafields.custom[line_item.id].dpp_url }}" target="_blank">View Your DPP</a>
       {% endfor %}
     {% endfor %}
   {% else %}
     <p>Please log in to view your Digital Product Passports.</p>
     <a href="/account/login">Login</a>
   {% endif %}

4. **Ensure Security**:
- Since the page displaying DPPs is behind Shopify’s customer authentication, only logged-in users can access their personalized DPPs.
- Ensure that the metafields containing DPP URLs are secure and not exposed in any public-facing parts of the site without authentication.

**Benefits**:
- **Ease of Implementation**: Leverages Shopify’s existing authentication infrastructure.
- **Integration with Shopify Ecosystem**: No need to manage a separate authentication system, reducing complexity.

**Considerations**:
- **Limited Flexibility**: Shopify’s customer account features are relatively basic and may not support more advanced customer engagement strategies without additional customization.

**Option B: Use a VERA Account Linked to Shopify Account**

**Overview**:
Create a separate VERA account system that can be linked to Shopify customer accounts. This method offers greater flexibility and allows for more personalized customer engagement, such as managing separate loyalty programs, advanced customer interaction features, or more detailed access control.

**Steps**:

1. **Set Up VERA Account System**:
- Develop or deploy a VERA account management system where customers can register, log in, and manage their DPPs.
- Ensure the VERA account system has API endpoints to handle account creation, authentication, and linking with Shopify accounts.

2. **Link VERA and Shopify Accounts**:
- During the order process, prompt the customer to either link their Shopify account with a VERA account or create a new VERA account.
- Use a unique identifier (such as email or Shopify customer ID) to link the two accounts securely.

3. **Generate and Store DPPs**:
- Once an order is placed, generate the individual DPPs using the VERA API.
- Store these DPPs in the VERA system, linked to the customer’s VERA account.

4. **Authentication and Access**:
- Create a secure page on your website or within the VERA system where customers can log in to access their DPPs.
- Allow customers to log in using their VERA credentials. Once authenticated, they can access their personalized DPPs.

**Example Authentication Flow**:
- Customer places an order on Shopify.
- Post-purchase, they receive an email prompting them to log in or create a VERA account.
- Once logged in, they can view their individual DPPs and engage with any additional features provided by VERA.

5. **Enhanced Customer Engagement**:
- Leverage the VERA account system to offer more personalized customer interactions, such as loyalty programs, special offers, and detailed product information.

**Benefits**:
- **Greater Flexibility**: More control over customer interactions and the ability to offer advanced features.
- **Customizable User Experience**: Tailor the customer journey more effectively, including multi-step authentication, personalized marketing, and detailed analytics.

**Considerations**:
- **Increased Complexity**: Managing a separate authentication system requires more resources and infrastructure.
- **Account Linking**: Ensure that the account linking process is smooth and secure to avoid confusion or security issues.

#### Conclusion about Authentication Options

Both options offer viable methods for securing access to individual DPPs generated by the VERA API:

- **Option A** leverages Shopify’s built-in customer authentication for ease of use and simpler integration within the Shopify ecosystem.
- **Option B** provides greater flexibility and control, allowing for a more tailored customer experience but requires additional infrastructure and management.

Your choice will depend on your specific needs, such as the desired level of customer engagement, customization, and resource availability.

Please let me know if you would like to proceed with further details on either option, or if you need assistance with another step.

#### Outcome

By completing Step 5, you will have implemented a secure and efficient authentication system for accessing individual Digital Product Passports (DPPs). This ensures that only authenticated users can view personalized DPPs linked to their purchased items. If using Shopify’s native account system, customers can seamlessly access their DPPs through their Shopify login, maintaining a unified experience within the platform. Alternatively, with a VERA-linked account system, you gain the flexibility to offer advanced customer engagement features, enhancing the overall user experience while ensuring robust security. This setup not only secures access to sensitive product information but also lays the groundwork for scalable and customizable customer interactions.

### III.6) Step 6: Test and Deploy the System

**Objective**: After setting up the integration between Shopify, the VERA API, and the authentication system, it's crucial to thoroughly test the entire workflow. This step ensures that all components work together seamlessly before deploying the system to a live environment.

#### **Steps to Test and Deploy**

1. **Set Up a Test Environment**:
- **Create a Test Store in Shopify**: If possible, create a separate Shopify development store for testing purposes. This allows you to test the integration without affecting your live store.
- **Use a Staging Environment for VERA API**: If your VERA API has a staging environment, use it to avoid any unintended consequences in the production environment.

2. **Run End-to-End Tests**:
- **Place Test Orders**:
- Place multiple test orders on your Shopify store, simulating various scenarios (e.g., orders with single items, multiple items, different product variants).
- Ensure that each order triggers the generation of both batch and individual DPPs through the VERA API.
- **Verify QR Code Generation**:
- Confirm that the QR codes are generated correctly for both the batch DPP (printed on the T-Shirt) and the individual DPP (sent via email).
- Scan the QR codes to verify that they link to the correct DPP URLs.
- **Test Authentication**:
- Test the login process for accessing individual DPPs using both Shopify and VERA account options.
- Ensure that only authenticated users can access the personalized DPP information.
- **Email Verification**:
- Check that the order confirmation emails contain the correct QR code and that the QR code is scannable and leads to the individual DPP.
- If using the AWS Lambda option for sending a second email, ensure that this email is sent correctly and contains the proper content.

3. **Monitor Error Handling**:
- **Test Error Scenarios**:
- Simulate scenarios where QR code generation might fail or where the VERA API is unavailable. Verify that the system handles these errors gracefully (e.g., sending a fallback email or displaying a default message).
- **Review Logs**:
- Review the logs from Shopify, AWS Lambda, and the VERA API to ensure that errors are being logged and handled appropriately.

4. **Optimize Performance**:
- **Assess Processing Times**:
- Measure the time it takes to generate QR codes and send confirmation emails. Ensure that these processes meet acceptable performance standards and do not introduce significant delays.
- **Load Testing**:
- Perform load testing on the system to ensure it can handle high volumes of orders and API requests, especially if you anticipate large-scale sales events.

5. **Deployment Strategy**:
- **Gradual Rollout**:
- If possible, perform a gradual rollout of the system, starting with a subset of your products or customers. This allows you to monitor the system in a live environment and make adjustments before full deployment.
- **Full Deployment**:
- Once the system has been thoroughly tested and any issues have been resolved, proceed with full deployment. This involves enabling all components in your live Shopify store, VERA API production environment, and AWS Lambda functions (if used).

6. **Post-Deployment Monitoring**:
- **Monitor the System**:
- Continuously monitor the system after deployment to ensure that everything functions as expected. Pay attention to any customer feedback, error logs, and performance metrics.
- **Regular Maintenance**:
- Schedule regular maintenance to update the VERA API, Shopify templates, and AWS infrastructure as needed. Ensure that the system remains secure and efficient over time.

#### **Outcome**:
By the end of this step, you will have a fully tested and deployed system that integrates Shopify, the VERA API, and customer authentication, providing a seamless experience for customers to access both batch and individual DPPs.

### Appendix A.1: Amazon DPP Integration Recipe with Individual QR Codes

##### **Objective and Scope**

This recipe provides a comprehensive guide for integrating Digital Product Passports (DPPs) into the Amazon platform using batch-level serialization and individual QR codes. The approach is tailored to Amazon's restrictive customization environment, ensuring that shop operators can implement DPPs effectively. It also includes a method for sending custom order confirmation emails containing individual QR codes using Amazon SNS and SES.

#### **Summary of the Approach**

The proposed method involves generating batch-level DPPs linked to products via QR codes and integrating these codes into product designs or packaging. Additionally, the recipe covers sending individualized DPPs through customized confirmation emails using Amazon's services. This approach ensures DPPs are accessible to customers while adhering to Amazon's platform constraints.

#### **Why This Approach?**

Amazon's closed ecosystem limits customization options compared to platforms like Shopify or WooCommerce. Deep integrations, such as generating item-specific QR codes on demand, are not feasible due to Amazon's restrictions. This recipe uses batch DPPs and pre-generated QR codes, ensuring broad applicability across Amazon's platform. The addition of individual QR codes via custom emails sent through Amazon SNS and SES enhances the customer experience without requiring direct customization of Amazon's native emails.

#### **Step-by-Step Recipe for Amazon DPP Integration**

#### **Step 1: Set Up Amazon Seller Account and Products**

1. **Register an Amazon Seller Account**:
- Sign up for an Amazon Seller account via [Amazon Seller Central](https://sellercentral.amazon.com).
- Configure your store settings, including payment and shipping options.

2. **Create Product Listings**:
- Add your products to Amazon through Seller Central.
- Assign Batch IDs to each product listing. Since Amazon lacks custom fields, manage Batch IDs externally or include them in product descriptions or SKUs.

#### **Step 2: Configure VERA API for Batch DPPs**

1. **Create Batch DPPs**:
- Use the VERA API to generate batch-level DPPs for each product group.
- Example API request:

     {
       "batchId": "Batch-ID-001",
       "productDetails": {
         "productName": "Eco-Friendly T-Shirt",
         "material": "Organic Cotton",
         "color": "Green"
       },
       "esprInfo": {
         "regulationCompliance": "ESPR-2024"
       }
     }

- Store the generated DPP URLs externally for reference.

#### **Step 3: Integrate Batch DPP QR Codes into Product Designs**

1. **Embed QR Codes in Product Designs**:
- Embed the Batch DPP QR codes in the product designs or packaging. For example, the QR code can be printed on the garment’s label or packaging.

2. **Upload Design Files**:
- If required, upload the product designs with embedded QR codes through Amazon’s product listing tools.

#### **Step 4: Leverage Amazon’s Limited Customization**

1. **Product Descriptions**:
- Mention the Batch DPP in the product description and instruct customers to scan the QR code on the product or packaging.

2. **Enhanced Brand Content**:
- Utilize Amazon's Enhanced Brand Content (EBC) to further explain the DPP and QR code, enhancing customer understanding and engagement.

#### **Step 5: Webhook and QR Code Generation**

1. **Set Up Amazon SNS and SES**:
- Create an SNS topic that triggers when an order is placed.
- Set up Amazon SES to send customized emails, including the QR code.

2. **Webhook and QR Code Generation**:
- Set up a webhook to capture order events. This webhook will trigger the generation of individual QR codes via the VERA API.

- **Generate Individual DPPs and QR Codes**:
- When an order is placed, generate an individual DPP for each item using the VERA API.
- Example API request:

       {
         "orderId": "Order-1002",
         "itemId": "1234567890",
         "batchId": "Batch-ID-001",
         "productDetails": { "productName": "Eco-Friendly T-Shirt" }
       }

- Generate a QR code for each individual DPP URL.

3. **Send Custom Email via SES**:
- Use the SNS topic to trigger a Lambda function that sends a customized email via SES, including the QR code.
- Example SES Email Template:

     <h1>Order Confirmation</h1>
     <p>Thank you for your order, {{customer_name}}!</p>
     <p>Your product: {{product_name}}</p>
     <p>Scan the QR code below to access your Digital Product Passport:</p>
     <img src="{{qr_code_url}}" alt="QR Code">

4. **Accessing DPPs**:
- Customers scan the QR code in the confirmation email or on the product to access their individual DPPs. For personalized information, redirect them to an external site where they can authenticate with a VERA account if needed.

#### **Step 6: Test and Deploy**

1. **Product Testing**:
- Test the QR codes on sample products and in confirmation emails to ensure they correctly link to the DPPs.

2. **Monitor and Adjust**:
- After deployment, monitor customer feedback and system performance, making adjustments as necessary.

#### User Authentication Options with Amazon

When integrating Digital Product Passports (DPPs) on Amazon, the platform's restrictive customization environment limits the ability to implement sophisticated user authentication directly within Amazon’s ecosystem. Unlike platforms like Shopify, which offer more flexibility in integrating custom user authentication flows, Amazon's environment requires alternative approaches.

**User Authentication through External Sites**

Given these limitations, one effective method is to redirect customers to an external site for authentication. After a customer scans the QR code from the product or the confirmation email, they can be redirected to a secure external site, such as the VERA platform. Here, customers can authenticate using an account system that is either linked to their Amazon purchase details (e.g., via order ID or email) or through a separate account that they create specifically for accessing their DPPs.

**Options for Authentication:**

1. **Amazon-Linked Authentication**:
- Although Amazon does not support direct API access for user authentication related to DPPs, you can verify users by cross-referencing information provided at the time of purchase (such as email addresses or order IDs) with data stored in your external DPP system.
- After scanning the QR code, users could be prompted to enter their email or order number on the external site to confirm their identity and access their individual DPPs.

2. **VERA Account Authentication**:
- Customers can be encouraged to create a VERA account, which they can then link to their Amazon purchase. This VERA account can store their DPPs and offer additional personalized features such as rewards, product history, or enhanced content.
- This approach allows you to build a more engaging customer relationship, as the VERA account can offer richer interactions and benefits beyond what Amazon provides.

By leveraging external authentication methods, shop operators can provide a secure and scalable way for customers to access their individual DPPs, even when operating within Amazon’s restrictive environment. This ensures that only authenticated users can view sensitive product information, enhancing both security and customer experience.

#### **Outcome**

By following this recipe, you can effectively integrate batch-level DPPs into Amazon product listings and enhance customer interaction with individual QR codes via customized confirmation emails. This approach is designed to work within Amazon's restrictive environment, ensuring that DPPs are implemented smoothly and provide customers with valuable product information and engagement opportunities.

### **Appendix A.2: Fact check**

Let's fact-check the paragraph by breaking it down into key assertions:

#### Assertion 1: **"This recipe outlines a streamlined approach for integrating Digital Product Passports (DPPs) into eCommerce platforms such as Shopify."**

- **Fact Check**: Shopify does support integration with various APIs and custom workflows, which could include Digital Product Passports. DPPs are a conceptual framework for tracking product details, origins, and compliance information, often used in regulated industries. While Shopify itself doesn’t natively provide a DPP service, it allows for integration with third-party services like VERA via APIs, webhooks, and other custom methods.
- **Source**: [Shopify API Documentation](https://shopify.dev/docs) and general DPP industry practices.

#### Assertion 2: **"The primary objective is to enable shop operators to easily implement DPPs without requiring deep platform integration, making it accessible across a wide range of platforms, including Shopify, WooCommerce, Magento, BigCommerce, and Print-on-Demand (PoD) platforms like Printful and Gelato."**

- **Fact Check**: Shopify, WooCommerce, Magento, BigCommerce, Printful, and Gelato are all widely used eCommerce and PoD platforms that allow various levels of customization through APIs, webhooks, and app integrations. However, the complexity of integrating DPPs might vary depending on the platform’s flexibility. Shopify, WooCommerce, and Magento are known for their extensive plugin ecosystems and API support, making them suitable for custom integrations like DPPs.
- **Source**: [WooCommerce API Documentation](https://woocommerce.com/document/rest-api/), [Magento API Documentation](https://developer.adobe.com/commerce/webapi/rest/), [BigCommerce API Documentation](https://developer.bigcommerce.com/), [Printful API Documentation](https://www.printful.com/docs), [Gelato API Documentation](https://www.gelato.com/en-US/api).

#### Assertion 3: **"Each batch of products, identified by a Batch ID, shares a common QR code that directs users to a batch DPP containing general product information and compliance data."**

- **Fact Check**: Using a Batch ID to group products and share a common QR code that links to a batch DPP is a valid method used in various industries, especially for compliance and traceability purposes. This approach is feasible and can be implemented across eCommerce platforms that support metadata storage, such as Shopify’s metafields.
- **Source**: General industry practices in supply chain management and compliance systems.

#### Assertion 4: **"For individualized customer engagement, the system generates unique DPPs linked to specific orders, which are sent to customers via order confirmation emails."**

- **Fact Check**: Generating unique DPPs for individual products and sending them via confirmation emails is a common practice in industries requiring traceability and customer transparency. Platforms like Shopify allow for such integrations through their API and webhook systems, where custom logic can be implemented to generate and send unique DPPs.
- **Source**: [Shopify Order Processing Documentation](https://shopify.dev/docs/apps/order-processing), general best practices in customer engagement.

#### Assertion 5: **"However, this approach is also adaptable to other eCommerce or Printing on Demand platforms, making it a versatile solution for various online retail environments."**

- **Fact Check**: The approach of using Batch DPPs and generating individual DPPs through custom integrations is adaptable across different eCommerce and PoD platforms. These platforms typically provide API access and webhook support, allowing for such custom workflows.
- **Source**: [Printful API Documentation](https://www.printful.com/docs), [Gelato API Documentation](https://www.gelato.com/en-US/api), and general documentation for eCommerce platforms.

#### Assertion 6: **"While alternative approaches—such as generating serialized item-level QR codes on the fly for Print-on-Demand products—are technically feasible, they require deeper platform integration."**

- **Fact Check**: Generating serialized item-level QR codes on the fly is technically feasible but requires more advanced integration into both the eCommerce platform and the PoD services. This is because each product would need a unique identifier generated in real-time, which must be embedded into the design and printed on the product. This level of integration often requires access to real-time production data and a more complex API setup.
- **Source**: Custom API integration practices and examples from platforms like Shopify and Printful.

#### Assertion 7: **"Batch DPPs offer a simpler, more scalable solution by not requiring unique QR codes for each product. However, serialized item-level DPPs provide enhanced anti-counterfeiting capabilities."**

- **Fact Check**: Using Batch DPPs is indeed simpler and more scalable, as it reduces the need for individualized processing. Serialized item-level DPPs are used in industries requiring high levels of product authenticity and traceability (e.g., pharmaceuticals, luxury goods) because they can uniquely identify and verify each product against a central database.
- **Source**: Industry practices in anti-counterfeiting and supply chain management.

#### Assertion 8: **"For simplicity and broad applicability, this recipe uses batch serialization."**

- **Fact Check**: Batch serialization is a practical approach for general eCommerce use cases where high-level traceability and compliance are necessary, but individual serialization might be overkill or too complex.
- **Source**: General eCommerce and supply chain practices.

#### Assertion 9: **"Each eCommerce platform may use different Batch IDs and QR codes to link products to specific platforms for better order mapping and user authentication, ensuring the approach scales effectively across different platforms."**

- **Fact Check**: It’s feasible to generate and use different Batch IDs and QR codes per platform, which would help in order tracking, mapping, and authentication. This practice ensures that each platform can maintain its batch and product tracking while integrating with a broader system like VERA for DPP management.
- **Source**: General principles of batch tracking and multi-platform integration.

#### Conclusion:
The assertions made in the paragraph are generally accurate and supported by industry practices in eCommerce, PoD platforms, and supply chain management. The approach of using batch-level serialization with the potential for individualized DPPs is practical and aligns with current technological capabilities and integration practices across various platforms.

### Appendix A.3: Global IDs, Oder IDs and Item IDs

When you order multiple items in Shopify, each order and its associated items are structured as follows:

#### **Shopify Order ID:**
- **Order ID**: This is a unique identifier assigned to every order placed in your Shopify store. It is a sequential number that is unique to each order. For example, if your last order was `Order-1001`, the next order might be `Order-1002`.
- **Global ID**: Shopify also provides a global ID, often called the `order_id` or `order_number`, which is unique across all orders in your store. This is a numeric value that typically increases with each new order.

#### **Shopify Item ID (Line Item ID):**
- **Item ID**: Each item within an order is referred to as a "line item" in Shopify. Each line item has its own unique identifier within the context of the order, often called `line_item.id`.
- **Structure**: The `line_item.id` is unique to each item in the order but is only unique within the context of the specific order. This means that the same product ordered in different orders will have different `line_item.id` values in each order.
- **Example**:
- **Order**: `Order-1002`
- **Line Item 1**: `{ "id": 1234567890, "title": "Product A", "quantity": 1 }`
- **Line Item 2**: `{ "id": 1234567891, "title": "Product B", "quantity": 2 }`

#### **Ordering Multiple Items:**
- When an order contains multiple items, each item (or line item) is associated with its own unique `line_item.id`. The overall order will have a single `order_id`, but each item in the order can be individually identified by its `line_item.id`.

#### **Example Structure**:
Here’s how a Shopify order with multiple items might look:

{
  "order_id": 1002,
  "order_number": "Order-1002",
  "line_items": [
    {
      "id": 1234567890,
      "title": "Product A",
      "quantity": 1
    },
    {
      "id": 1234567891,
      "title": "Product B",
      "quantity": 2
    },
    {
      "id": 1234567892,
      "title": "Product C",
      "quantity": 1
    }
  ]
}

In this example:
- The `order_id` (1002) is the unique identifier for the entire order.
- Each `line_item` has a unique `id` (`1234567890`, `1234567891`, `1234567892`) which is specific to each product in this order.

#### **Using Order ID and Line Item ID Together:**
When integrating with systems like the VERA API, you can use both the `order_id` and `line_item.id` to uniquely identify and track each product ordered by a customer. This allows you to generate and link individual DPPs to each specific item within an order, ensuring that even if multiple items are ordered, each one can be tracked separately.

This structure is essential for ensuring that the correct DPP is associated with each individual item in cases where customers purchase multiple products in a single transaction.