*Gap samples / Gap 10 - Revenue partners (admins)*

# Reseller and AWS Marketplace deals: how they fit in EULER

A short guide for an admin adding a reseller channel or an AWS Marketplace motion to a program that already runs referrals. It says which EULER features each motion uses, routes you to the pages that set them up, and lists the setup questions to answer first.

**Gap:** 10 of 13 · **Reader:** Admin, alliances lead · **Type:** Guide (orientation)

## Why this page needs to exist

eulerhq.com has full pages for Reseller and Hyperscaler, and an AWS integration listed under Integrations. The help center has no article on either. A reseller program reuses features that are documented separately, and nobody says which ones. AWS Marketplace adds three capabilities with no setup page at all.

---

*Sample documentation starts here*

## Go to the part you need

- Adding resellers: [Reseller deals](#reseller-part).
- Adding AWS Marketplace: [AWS Marketplace](#aws-part).

## Reseller deals

A reseller quotes, contracts and invoices the customer, which a referral partner never does. In EULER the reseller motion is assembled from features you may already use:

| Reseller need | EULER feature | Set it up |
| --- | --- | --- |
| Margin protection on a deal | A **Deal Registration** form, with an expiry window you set | [Forms 2.0](https://support.eulerapp.com/en/c/core-euler-features/customization-content/forms-2-0) |
| Registration without the form | DealFlow AI: forwarded email or Slack | [DealFlow AI](03-dealflow.md) |
| Tiers and rebates | Incentive tiers, calculated on attributed revenue | [Incentives](06-incentives.md) |
| Certified reps | Flows assigned by tag or tier, with completion tracked per person | [Using Flows with Your Partners](https://support.eulerapp.com/en/c/core-euler-features/flows/using-flows-with-your-partners) |
| Renewals seen early | Renewals tracked on the reseller account **[VALIDATE WHERE]** | [page to confirm] |
| What they earned | Invoices and payment history on the partner record, visible in their portal | [Getting Paid](https://support.eulerapp.com/en/c/partner-journey/getting-paid/getting-paid-commissions-transactions-and-invoices) |

A **Reseller** charge means the partner sent you the deal, so you owe the partner. Give resellers their own incentive structure: paying them like referral partners is a common mistake.

## AWS Marketplace

EULER runs three AWS Marketplace capabilities next to the rest of your program:

- **[Private offers](https://docs.aws.amazon.com/marketplace/latest/userguide/creating-private-offer.html)** built and sent from EULER, followed from changeset to active, without opening the AWS console.
- **[ACE opportunity sync](https://docs.aws.amazon.com/partner-central/latest/getting-started/coselling-with-aws.html)** in both directions, so co-sell pipeline with AWS sits next to referrals and reseller deals.
- **Catalog sync**, daily, so marketplace revenue reports with the rest of partner revenue.

**Setup is not publicly documented**

No public source says what connecting AWS requires on your side, such as which AWS Partner Central access or permissions. Do not start until your EULER contact confirms the list below.

## Before you add either motion

- Deal Registration form built and tested, with an expiry window that matches your program terms.
- Reseller incentive structure separate from referral partners.
- One owner for marketplace deals, so alliances and the partner team are not working the same opportunity twice.
- For AWS: the access requirements confirmed with EULER before connecting.

## What wrong looks like

**WRONG - RESELLER ONBOARDING**

```
Resellers added to the referral program, same form,
same incentive, "we'll split them out later".

Why it fails: a referral form gives no expiry, so a
reseller's claim on a deal has no defined end. The
referral incentive pays a referral rate on resale. And
every report built before the split mixes both motions.
```

## Confirm with engineering

1. Connecting AWS needs [Partner Central role / IAM role / other]. Correct me with the list.
2. The AWS connection is set up at [location], by [self-serve / EULER team]. Correct me.
3. Reseller renewals are tracked at [object or page]. Correct me.
4. ACE opportunities synced into EULER attach to a partner by [rule]. Correct me.
5. Marketplaces other than AWS are [supported / planned / not supported]. Correct me.

### Related documentation

- [Forms 2.0: the Deal Registration form type](https://support.eulerapp.com/en/c/core-euler-features/customization-content/forms-2-0)
- [Submitting a Referral or Registering a Deal](https://support.eulerapp.com/en/c/partner-journey/referrals-and-deals/submitting-a-referral-or-registering-a-deal) (registration expiry)
- [Flows](https://support.eulerapp.com/en/c/core-euler-features/flows/flows)
- [Getting Paid](https://support.eulerapp.com/en/c/partner-journey/getting-paid/getting-paid-commissions-transactions-and-invoices)
- [Reseller](https://eulerhq.com/solutions/reseller) and [Hyperscaler](https://eulerhq.com/solutions/hyperscaler) on eulerhq.com
- [Creating and managing private offers](https://docs.aws.amazon.com/marketplace/latest/userguide/creating-private-offer.html) (AWS docs)
- [Co-selling with AWS](https://docs.aws.amazon.com/partner-central/latest/getting-started/coselling-with-aws.html) and [APN Customer Engagements (ACE)](https://aws.amazon.com/partners/programs/ace/) (AWS docs)

### Sources for this page

- eulerhq.com/solutions/reseller: registration by form, email or Slack; tiers, rebates, payouts; certification; renewals on the account.
- eulerhq.com/solutions/hyperscaler and its FAQ: private offers changeset to active, bidirectional ACE sync, daily catalog sync. eulerhq.com/integrations: AWS under Hyperscaler.
- Forms 2.0: Deal Registration form type. Submitting a Referral: registration expiry. MCP reference: Reseller charge direction.

### Next

- Gap 5: [Incentives](06-incentives.md). Build the reseller's own structure.
- Gap 2: [DealFlow AI](03-dealflow.md). Registration from email and Slack.

---

*Independent writing sample by Bachtiar Widyantoro (bachwidy.site), November 2026. Not published or endorsed by EULER. Free to reuse and edit. Customer names in examples are fictional. Anything marked [VALIDATE ...] or [CONFIRM ...] is not settled by a public source and needs checking before publishing.*