> ## Documentation Index
> Fetch the complete documentation index at: https://docs.platform.pink/llms.txt
> Use this file to discover all available pages before exploring further.

# Buyers and Sellers

> Understanding the key entities in Platform Pink's marketplace ecosystem

Platform Pink connects two essential entities in our ecosystem: **Buyers** and **Sellers**. Understanding these roles is crucial for integrating with our platform effectively.

<Info>
  Every interaction in Platform Pink involves at least one Buyer and one
  Seller, creating a dynamic marketplace where data flows seamlessly between
  all parties.
</Info>

## Overview

<CardGroup cols={2}>
  <Card title="Buyers" icon="users">
    Entities that purchase products or services through Platform Pink
  </Card>

  <Card title="Sellers" icon="store">
    Entities that offer products or services for sale via the platform
  </Card>
</CardGroup>

## Buyer

A **buyer** represents any entity that purchases products or services through Platform Pink. This includes restaurateurs, businesses, or organizations seeking to acquire goods or fulfill specific operational needs.

### Key Capabilities

1. Access real-time product catalogs with current pricing and availability
2. Place and track orders seamlessly across multiple sellers
3. Receive automated delivery notes, invoices, and transaction documents

## Seller

A **seller** is any entity that offers products or services for sale through Platform Pink. This encompasses manufacturers, distributors, service providers, or any business looking to reach buyers in our network.

### Key Capabilities

1. Maintain comprehensive product catalogs with real-time inventory and pricing
2. Process incoming orders with automated workflows and fulfillment tracking
3. Generate and distribute delivery notes, invoices, and transaction documents

## Integration Considerations

<Warning>
  When integrating with Platform Pink, ensure your system correctly identifies
  whether you're acting as a Buyer, Seller, or both. Some entities may play
  dual roles depending on the transaction context.
</Warning>