> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/sponsors/linking-sponsors-to-products.md).

# Linking sponsors to products

Vendor Space allows you to link a sponsor record to a sponsor product. This connects a specific sponsorship to a defined package with consistent pricing, making it easier to manage standardized sponsorship offerings across your events.

## What Is a Sponsor Product?

A sponsor product is a pre-configured sponsorship package that you create in Vendor Space's product system. It includes a name, description, and price. Think of it as a template for a sponsorship tier -- for example, a "Gold Sponsorship" product priced at $2,500 that includes specific benefits.

By creating sponsor products, you establish a clear menu of sponsorship options that you can reuse across events.

## How to Link a Sponsor to a Product

1. Open the sponsor record you want to link.
2. Look for the **Product** field or the option to link a product.
3. Select the appropriate sponsor product from the list.
4. Save the sponsor record.

The sponsor is now linked to that product. The product's pricing and details are associated with the sponsor record, giving you a consistent reference point.

## Why Link Sponsors to Products?

### Consistent Pricing

When you define sponsorship packages as products, every sponsor at the same level pays the same amount. There is no need to manually enter pricing for each sponsor -- the product handles it.

### Standardized Packages

Linking to products means your sponsorship offerings are clearly defined. Your team and your sponsors both know exactly what each package includes, reducing confusion and back-and-forth.

### Simplified Reporting

With sponsors linked to products, you can quickly see how many sponsors have purchased each package and calculate total sponsorship revenue by tier.

## Best Practices

* **Create products before adding sponsors.** Having your sponsorship packages defined upfront makes it faster to set up new sponsor records.
* **Use descriptive product names.** Names like "Gold Sponsorship - 2026 Summer Market" are easier to manage than generic labels.
* **Update products when pricing changes.** If your sponsorship rates change for a new event season, update the products so all future sponsor records reflect the correct amounts.
* **Use the Custom tier for exceptions.** If a sponsor negotiates a unique deal that doesn't match any product, you can skip the product link and enter the details manually on the sponsor record.

> **Tip:** Linking sponsors to products is optional. If your sponsorship structure is simple or every deal is unique, you can manage sponsors without products. But for events with recurring, standardized sponsorship tiers, the product link saves time and keeps everything consistent.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vendorspace.gitbook.io/docs/sponsors/linking-sponsors-to-products.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.