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

> ## Agent Instructions
> ## What this documentation covers
> This is the documentation for ArcSolar, the solar-retailer operating system: the web app a solar retailer uses to run quoting, sales, installation, rebates, inventory and reporting. ArcSolar is a hosted web application at https://app.arcsolar.com.au. There is no public API for most workflows, so agentic operation of ArcSolar is UI-driven. Navigate the app, read the labels and controls, and act through the interface, unless a page explicitly documents an API, contract or integration endpoint.
>
> ## How to read these pages
> - Pages are split by audience using Mintlify's Visibility component, and this split is deliberate. Sections marked 'for agents' are hidden on the website and appear only in the Markdown you are reading. They are the authoritative behavioural specification for the page. Where the remaining human-facing prose and an agent section disagree, the agent section is correct.
> - Sections outside any Visibility block appear in both outputs. They are the shared spine of the page: what the feature is and why it matters.
> - Treat every bold label, field name, route, status string and error message quoted in an agent section as canonical. They are copied verbatim from the product. Use that exact wording when telling a user where to click, or when matching an error message to its cause.
> - Australian solar vocabulary is used precisely and not interchangeably: STC (Small-scale Technology Certificate), PRC (Peak Reduction Certificate), REPS, NMI, CEC accreditation, VPP. Do not substitute an overseas equivalent.
> - Money is Australian dollars. Dates shown to users are day-first (DD/MM/YYYY).
>
> ## Behaviour rules for operating or advising on ArcSolar
> - Respect prerequisites and ordering. Agent sections state which inputs block progress and which steps must happen first. Do not skip a step, and do not assume a default that the product itself does not supply.
> - Never invent a value the product requires but the user has not supplied. Ask for mandatory fields rather than guessing. Several features reject a request outright when one is missing, and submissions to external authorities are effectively irreversible.
> - Respect permissions and scoping. Features name the roles, capabilities and access rules that may act. Do not attempt an action the operator's role cannot perform, and do not describe a restricted feature as available to them.
> - Features that are gated, pending release, or blocked on a vendor are documented as exactly that. Never present a gated or unmerged behaviour as live. When availability is unclear for a given workspace, direct the user to support rather than asserting that the feature works.
> - Where a page states something is genuinely undetermined, treat it as unknown. Do not fill the gap with a plausible guess.
> - ArcSolar's supported intelligence tools appear where they help with the task, including bill analysis, call summaries and reporting. Check the underlying evidence. Intelligence does not replace provider approval, verified records or the customer's own confirmation.
>
> ## Getting help
> Support is support@arcsolar.com.au. The customer-facing website is https://www.arcsolar.com.au.

# Promo bundles

> Offer a set of products, such as a solar and battery pair, at one special price.

A promo bundle gives two or more catalogue products one special price. Reps see the offer in the quote builder only when they pick exactly those products. Nothing changes for any other quote.

**Open:** [**Product Catalogue**](https://app.arcsolar.com.au/dashboard/product-catalogue) → **Promotions**.

## Create a bundle

1. Select **New bundle**.
2. Enter a **Promo bundle name**. Reps see this name in the quote builder.
3. Choose an **Offer type**:
   * **One price for the whole set**: enter the **Bundle price**, GST inclusive. This is what the customer pays for all the products together.
   * **Amount off the component prices**: enter the **Amount off**. It's taken off the products' normal prices added together.
4. Under **Included products**, tick at least two products. Search by product, SKU or category.
5. Add a **Description (optional)**, such as conditions the rep should mention.
6. Select **Add promo bundle**.

![Add promo bundle dialog with a name field, the Offer type set to One price for the whole set, a Bundle price field and a list of catalogue products to tick.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/gp-promo-bundle-dialog.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=ab124c28c4f31de657db6c057cc175ea)

The Add promo bundle dialog. Sample data.

> [!TIP]
>
> Give every product in the bundle a quote price first. A bundle with missing prices shows **Needs component prices**, and one that costs more than the normal prices shows **No saving at current prices**.

## How reps use it

1. The rep builds the quote and selects the products.
2. On **Review quote**, under **Extras & adjustments**, **Promo bundles** lists every bundle that matches. Each shows its price and the products it covers.
3. The rep picks the bundle, or **No promo bundle**. Nothing is applied on its own.

Once picked, the quote shows **Saving \$… on this quote.** If the rep later swaps one of the products, the bundle stops applying and a note explains why.

Bundles that don't match yet appear under **Other promo bundles**, with the reason, for example *"Not offered for the products selected right now."*

## Edit or end a bundle

* **Edit:** select **Edit** on the bundle's row, change it and select **Save promo bundle**. Quotes already sent keep their price.
* **End:** select **Remove**, then **Remove bundle**. Reps stop seeing it straight away. Sent quotes keep the price they were issued at.

## Bundle status

| Status | Meaning |
| - | - |
| **Active** | Reps can pick it when the products match |
| **Not offered** | One of its products is no longer active in the catalogue |
| **Archived** | You removed it |

[Continue with**Product catalogue**](https://docs.arcsolar.com.au/delivery/catalogue.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.