> For the complete documentation index, see [llms.txt](https://docs.driffle.com/driffle-seller-api-legacy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.driffle.com/driffle-seller-api-legacy/reference/pre-order-declare-stock.md).

# Pre-Order-Declare-Stock

## Pre-Order Declare Stock - Seller Documentation

### Overview

Declared stock is now available for pre-order products, allowing sellers to take more orders than they currently have in physical inventory by leveraging external stock providers.

### How It Works

#### Key Concepts

* **`auctionedKeys`**: Maximum number of orders you can accept for a product
* **`declaredStock`**: Number of items you actually have ready for immediate delivery
* **`available`**: Total available inventory (regular inventory + declared stock)

#### Example Scenario

```json
{
  "yourPrice": 1,
  "product": {
    "productId": 113538
  },
  "declaredStock": 20,
  "auctionedKeys": 100
}
```

**What this means:**

* ✅ You can accept **100 orders** (auctionedKeys)
* ✅ You have **20 items** ready for immediate delivery (declaredStock)
* ✅ **20 orders** will be fulfilled immediately
* ⏳ **80 orders** will wait until more stock becomes available

### Order Processing Flow

#### 1. Immediate Fulfillment

* Orders are fulfilled using available inventory first
* If declared stock is available, orders are processed through external providers
* Successful orders are marked as fulfilled and customers receive their items

#### 2. Declare Stock Processing

When regular inventory is insufficient, the system attempts to fulfill orders using declared stock:

1. **Reservation**: Items are reserved from the declared stock provider
2. **Provision**: Keys are requested from the provider
3. **Validation**: Keys are validated (text/image format, content quality)
4. **Allocation**: Valid keys are allocated to customers
5. **Email Notification**: Customers receive delivery emails

Service fees are charged in the following scenarios:

**1. Provision Failures**

* **When**: External provider fails to deliver valid keys
* **Charged To**: Seller's account
* **Purpose**: Covers platform costs for failed provision attempts

**2. Key Validation Failures**

* **When**: Provider delivers invalid keys (empty, malformed, or low-quality)
* **Examples of Invalid Keys**:
  * Empty or null values
  * Keys with incorrect format

### Important Rules & Limitations

#### 2. Order Priority

* **Driffle Plus Members**: Get priority in the fulfillment queue
* **FIFO**: Within the same tier, orders are processed first-come-first-served
* **Early Access**: Orders placed 14+ hours before release get early access emails

### Conclusion

Pre-order declare stock is a powerful feature that allows you to scale beyond your immediate inventory while maintaining customer satisfaction. Success depends on:

1. **Reliable Providers**: Choose providers with high success rates
2. **Proper Pricing**: Ensure margins can cover service fees
3. **Active Monitoring**: Track metrics and respond to issues quickly
4. **Customer Communication**: Set clear expectations and provide updates

By following these guidelines and best practices, you can maximize the benefits of the declare stock system while minimizing risks and service fee charges.