# Add and edit an offering (https://docs.xraise.ai/vendor/offerings/add-and-edit)
A perk is an offering that a vendor gives to startups: a credit, a discount or cashback. Every perk goes through a review by XRaise before founders see it.
At this time, partners cannot add or change perks in the panel. If you open the perk form, the panel shows: "At this time, you can see the catalog and its listings, but you cannot add or change them." The **Add perk** and **Edit** buttons do not show.
To add a perk or to change one, contact XRaise. Send the information that this page lists. XRaise enters it for you.
## How a perk goes live [#how-a-perk-goes-live]
You send the perk information to XRaise.
The perk is created with the status **Pending review**. Founders cannot see it.
XRaise reviews the perk. XRaise approves it, or sends it back to you with **Changes requested** and a reason.
After approval, the status changes to **Live**. Founders can see and claim the perk.
A change to a live perk follows the same review. Founders see the live version until XRaise approves the change. The status shows **Live ยท changes in review** during that time. If you send a second change before XRaise reviews the first one, the second change replaces the first one.
For each status, see [Statuses](../statuses.mdx#offering-statuses).
## What the perk form asks, when editing is turned on [#what-the-perk-form-asks-when-editing-is-turned-on]
This section lists every part of the perk form. Use it to prepare the information that you send to XRaise. When XRaise turns on editing for partners again, this is the form that you will fill in.
The form has four sections. A required field has a star. The **Submit for review** button stays off until all required fields are correct.
{/* SCREENSHOT: /partner/offerings/new | the empty perk form, The basics section */}
### The basics [#the-basics]
| Field | Required | Limits and choices | What it is for |
| ----------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------- |
| **Perk type** | Yes | **Credit**: founders get the deal from you directly. **Cashback**: founders buy from you, then get money back. | How the founder gets the deal. It changes what XRaise shows founders after approval. |
| **Purchase link (your site)** | Yes, for cashback only | A full web address that starts with https\:// or http\://. Up to 500 characters. | XRaise sends approved founders to this page through a tracked link. The field shows only for a cashback perk. |
| **Perk name** | Yes | Up to 120 characters. | The title of the perk. Example: "Acme for Startups". |
| **Offer headline** | Yes | Up to 160 characters. | The green savings line that founders see. Example: "Free Team plan for 12 months". |
| **Value** | No | A whole number above zero, up to 100,000,000. No commas, spaces or decimals. Pick a unit: **US dollars**, **% off** or **$ per user per month**. | What the perk is worth. Founders see it on the perk card. Leave it blank if the perk has no price. |
| **Categories** | Yes | Pick 1 to 4. | Founders use categories to find perks. |
The error messages for **Value**:
* "Enter a whole number. No commas, spaces or decimals."
* "Enter a number above zero, or leave it blank if the perk has no price."
* "That's above the 100,000,000 ceiling."
The error messages for **Purchase link**:
* "A cashback perk needs a purchase link."
* "Enter a full link, starting with https\://."
* "Use a web link that starts with https\://."
### Details (optional) [#details-optional]
| Field | Required | Limits | What it is for |
| ------------------- | -------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| **Subtitle** | No | Up to 160 characters. | The grey tagline under the perk title. Example: "AI-powered analytics platform". |
| **About this perk** | No | Up to 8,000 characters. You can format the text: bold, bullets, headings. | The description on the perk page: what the perk is, who it is for, what it includes. |
### After approval [#after-approval]
This section sets how a founder gets the perk.
| Field | Required | What it does |
| --------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Public: anyone can get the instructions without logging in** | No | Shows only for a credit perk. See [Public perks](#public-perks). |
| **Instructions** | Yes, if the perk is approved automatically or is public. Otherwise optional. | Up to 2,000 characters, with formatting. What the founder must do to get the deal, for example "Sign up with your work email, then reply to the welcome mail with code ACME." See [The instructions rule](#the-instructions-rule). |
| **Approve automatically, so founders see the instructions the moment they apply** | No | Turns on automatic approval. See [Automatic or manual approval](#automatic-or-manual-approval). |
| **Who can claim it** | Yes | The lowest founder plan that can claim the perk. See [Plan access](#plan-access). |
#### Automatic or manual approval [#automatic-or-manual-approval]
| Approval mode | What happens when a founder applies |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Automatic** (box selected) | The claim is approved at once. The founder sees the instructions immediately. |
| **Manual** (box clear) | The claim waits for an XRaise operator. The operator approves or declines it. The founder sees the instructions only after approval. |
#### The instructions rule [#the-instructions-rule]
* An automatically approved perk must have instructions. The founder sees them the moment the claim is approved, so they must be ready.
* A public perk must have instructions. Anyone can read them.
* A manually approved perk does not need instructions. An XRaise operator handles each claim. If you add instructions, the founder sees them only after approval.
* Founders never see the instructions in the catalog. They see them only after approval, or at once on a public perk.
#### Plan access [#plan-access]
| Choice | Who can claim |
| ------------------------------------- | ------------------------------------- |
| **Free: every founder can claim it** | Every founder. |
| **Plus: founders on Plus or Insider** | Founders on the Plus or Insider plan. |
| **Insider: founders on Insider only** | Founders on the Insider plan only. |
Founders on a lower plan still see the perk, but it shows as locked, with an **Upgrade** button.
#### Public perks [#public-perks]
When you select **Public**, the section title changes to **Public access**, and these rules apply:
* The perk is approved automatically.
* Every founder can claim it. The plan choice does not show.
* The perk asks no questions. The questions section does not show.
* The instructions are required, and anyone can read them. A founder can skip the login prompt and still see them.
The form shows: "This is deliberately public. The login modal can be skipped and the instruction above will still be shown."
Only a credit perk can be public. If you change the perk type to cashback, the **Public** box clears.
### What you'll ask for [#what-youll-ask-for]
This section holds the questions that a founder answers when they claim the perk. XRaise always collects the startup name. You add every other question.
{/* SCREENSHOT: /partner/offerings/new | the questions section with one profile field and one custom question */}
You can add up to 50 questions. The counter shows, for example, "3 of 50".
There are two kinds of question:
* **A profile field.** Founders keep their XRaise profile up to date. A profile field on your form is filled in from the founder's profile, so the answer is more accurate and the founder finishes faster. Click **Add a profile field** and search the list to add one. You cannot change the words, the type or the choices of a profile field.
* **Your own question.** Click **+ Add a question** and write it.
When you finish writing your own question, XRaise checks it against the profile. If your question asks for profile fields, XRaise replaces it with those fields. Click **Keep my question** to undo the replacement.
Each of your own questions has these fields:
| Field | Required | Limits and choices |
| ----------------------------------------------------- | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Question** | Yes | Up to 200 characters. |
| **Answer type** | Yes | **Short text**, **Long text**, **Pick one**, **Pick several**, **Number**, **Link**, **Email**, **Date**, **Yes / no**, **File upload**, **Location** or **Country**. |
| **Choices** | Yes, for **Pick one** and **Pick several** | One choice on each line. Do not add "Other". The form adds an "Other" box for free text to every choice question. |
| **Help text** | No | Shown under the question. Example: where to find the answer, or the format that you need. |
| **Required: a founder can't claim without answering** | No | Select it to make the answer required. |
A **File upload** question also has **Upload options**: the file types that it accepts (PDF, JPEG, PNG, WebP, Excel, Word, PowerPoint, CSV) and the largest file size, a whole number from 1 to 100 MB. If you leave the options empty, the question accepts JPEG, PNG, WebP or PDF, up to 10 MB.
Some answer types also take rules, for example **Min** and **Max** for a number, or **Earliest** and **Latest** for a date.
To remove a question, click **Remove** on it.
### The buttons [#the-buttons]
| Button | What it does |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Cancel** | Closes the form without saving and takes you back to **Offerings**. If you made changes, XRaise asks you first. |
| **Submit for review** | On a new perk. Saves the perk as **Pending review** and sends it to XRaise. The message "Perk submitted. It's pending XRaise review." shows. |
| **Save** | On a perk in review. Saves the change. The perk stays in review. |
| **Submit changes for review** | On a live perk. Sends the change to XRaise. The live version stays visible until XRaise approves the change. |
| **Resubmit for review** | On a perk with **Changes requested**. Saves your answer and sends the perk back to XRaise. |
## Editing a perk [#editing-a-perk]
The edit form is the same form, filled in with the current values. Notices at the top of the form tell you what applies:
| Notice | When it shows |
| ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ |
| "XRaise asked for changes:" and the reason, in red | XRaise sent the perk back to you. Answer the reason, then click **Resubmit for review**. |
| "You already have changes waiting for XRaise. Saving here replaces your earlier pending change." | You sent a change that XRaise has not reviewed yet. |
| "Live perk, the current version keeps showing on Discover." | The perk is live. Your changes go live only after XRaise approves them. |
| "A previous edit couldn't be read and was discarded." | A change that you sent earlier could not be used. The form shows the live values. Save again to send a new change. |
Do not rename or remove a question that founders already answered unless you must. The answers that founders already sent stay with the question.
## What founders see [#what-founders-see]
| Part of the form | Where founders see it |
| -------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| Perk name, Offer headline, Value | On the perk card in the catalog, and on the perk page. |
| Subtitle | Under the perk title. |
| Categories | In the catalog filters and on the perk page. |
| About this perk | On the perk page. |
| Who can claim it | A founder on a lower plan sees the perk as locked, with **Upgrade**. |
| Questions | On the claim form, when the founder claims the perk. A profile field is filled in from the founder's profile. |
| Instructions | Only after approval. At once on an automatically approved perk. Without login on a public perk. |
| Purchase link | After approval of a cashback perk, through a tracked XRaise link. |
## How to prepare a new perk for XRaise [#how-to-prepare-a-new-perk-for-xraise]
Decide the perk type: credit or cashback.
Write the perk name and the offer headline.
Decide the value and its unit, or leave the value blank.
Pick 1 to 4 categories.
Decide the approval mode: automatic or manual.
Write the instructions. They are required for automatic approval.
Decide the lowest plan that can claim the perk.
List the questions that founders must answer.
Send all of this to XRaise.